Builder+ vs Vanilla

Vanilla leads on the only live benchmark. Vanilla wins on Ethereum block builder market share (8.99% vs 0.54%).

Read methodology Last measured Window: rolling 24h1 shared benchmark
Builder+ logo
Builder+

Builder+ is the Ethereum block-building operation of BTCS Inc., a Nasdaq-listed blockchain infrastructure company (NodeOps staking, Builder+, Imperium DeFi). Attributed via the `Builder+` extraData self-label.

Vanilla logo
Vanilla

Not a company: blocks whose extraData is empty or carries an execution client's default tag (geth, reth, nethermind, besu, erigon), meaning the proposer built the block locally instead of outsourcing to a MEV-Boost builder. The live measure of how much of Ethereum still self-builds.

Side by side measurements

Ethereum block builder market share

Trading

Builder+

Trails

0.54 %

rank
#7
samples
39provisional

Vanilla

Leads

8.99 %

p99
8.99%
rank
#4
samples
645

Attribution relies on the extraData tag each builder voluntarily stamps. A builder can change or strip its tag; unrecognized tags land in Other and raw strings are logged so the table grows. The Vanilla row (locally built) could be marginally overstated if a builder uses a client-default tag; the relay cross-check surfaces this. High share is a centralization datapoint, not a quality ranking.

Rolling 24h · Block share (24h)Raw JSON

Frequently asked questions

Builder+ vs Vanilla: which one is better?

Builder+ and Vanilla are compared on 1 shared OpenChainBench benchmarks. Vanilla leads on Ethereum block builder market share. See the live table on this page for every metric.

Which is more reliable, Builder+ or Vanilla?

On the Ethereum block builder market share benchmark, Vanilla leads at 8.99% versus Builder+ at 0.54% (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the Builder+ vs Vanilla comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.