BuilderNet vs Vanilla

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

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

Decentralized block-building network initiated by Flashbots, with Beaverbuild and Nethermind among the early node operators. Blocks are built inside TEEs by multiple operators and carry the `BuilderNet` extraData tag; conceived as the mutualized counterweight to private-builder concentration.

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

BuilderNet

Trails

7.78 %

p99
7.78%
rank
#5
samples
558

Vanilla

Leads

9.78 %

p99
9.78%
rank
#4
samples
702

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

BuilderNet vs Vanilla: which one is better?

BuilderNet 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, BuilderNet or Vanilla?

On the Ethereum block builder market share benchmark, Vanilla leads at 9.78% versus BuilderNet at 7.78%. Live measurement is updated continuously by the OpenChainBench harness.

How is the BuilderNet 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.