Builder+ vs Titan

Name: Builder+ vs Titan OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

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

Read methodology Last measured Mon, 31 Aug 2026 04:35:34 UTCWindow: rolling 24h1 shared benchmark

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.

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

Builder+

Trails

0.54 %

rank: #7
samples: 39provisional

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.

Frequently asked questions

Builder+ vs Titan: which one is better?

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, Builder+ or Titan?

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

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