beaverbuild vs Other

Other leads on the only live benchmark. Other wins on Ethereum block builder market share (9.03% vs 0.070%).

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

Pseudonymous Ethereum block builder that dominated block building through 2023-2024 alongside rsync. Labels its blocks `beaverbuild.org` in extraData; no legal entity is publicly identified.

Other logo
Other

Aggregate long-tail bucket, not a single provider. On the block-builder bench it collects blocks whose extraData tag is not in the curated attribution table; every raw string is logged so named rows can be added as the table grows.

Side by side measurements

Ethereum block builder market share

Trading

beaverbuild

Trails

0.070 %

rank
#9
samples
5provisional

Other

Leads

9.03 %

p99
9.03%
rank
#4
samples
648

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

beaverbuild vs Other: which one is better?

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

Which is more reliable, beaverbuild or Other?

On the Ethereum block builder market share benchmark, Other leads at 9.03% versus beaverbuild at 0.070% (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the beaverbuild vs Other 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.