OpenChainBench

CMI vs Hypurrscanning

CMI leads on the only live benchmark. CMI wins on Hyperliquid validator leaderboard (2.23% vs 2.21%).

Read methodology Last measured Window: rolling 24h1 shared benchmark
CM
CMI
HY
Hypurrscanning

Side by side measurements

Hyperliquid validator leaderboard: live net APR, uptime, commission

Blockchains

CMI

Leads

2.23 %

p99
2.23%
rank
#3
samples
784,456,000

Hypurrscanning

Trails

2.21 %

p99
2.21%
rank
#5
samples
1,982,200,000

net_yield = predictedApr.day x uptimeFraction from /info validatorSummaries. No MEV layer at the validator level on Hyperliquid; the centralised sequencer captures order-flow value upstream. Jailed validators land at 0 bps regardless of published APR. APRs cluster at 200 to 225 bps across the active set; commission rate is the primary differentiator for delegators.

Frequently asked questions

CMI vs Hypurrscanning: which one is better?

CMI and Hypurrscanning are compared on 1 shared OpenChainBench benchmarks. CMI leads on Hyperliquid validator leaderboard. See the live table on this page for every metric.

Which is cheaper, CMI or Hypurrscanning?

On the Hyperliquid validator leaderboard benchmark, CMI leads at 2.23% versus Hypurrscanning at 2.21%. Live measurement is updated continuously by the OpenChainBench harness.

How is the CMI vs Hypurrscanning 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.