Bob The Builder vs Titan

Titan leads on the only live benchmark. Titan wins on Ethereum block builder market share (45.5% vs 0.45%).

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

Pseudonymous Ethereum block builder, self-labeled `bob-the-builder` in block extraData with the bob-the-builder.eth fee recipient. No operating entity is publicly identified; identity rests on the extraData self-label.

Titan logo
Titan

Dominant private Ethereum block builder, self-labeled `Titan (titanbuilder.xyz)` in block extraData. Regularly builds around half of all MEV-Boost blocks and also operates the Titan relay.

Side by side measurements

Ethereum block builder market share

Trading

Bob The Builder

Trails

0.45 %

rank
#8
samples
32provisional

Titan

Leads

45.5 %

p99
45.5%
rank
#1
samples
3,265

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

Bob The Builder vs Titan: which one is better?

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

Which is more reliable, Bob The Builder or Titan?

On the Ethereum block builder market share benchmark, Titan leads at 45.5% versus Bob The Builder at 0.45% (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the Bob The Builder vs Titan 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.