Fastest Wormhole VAA finalization by source chain, live latency
BridgesEthereum
Trails15.3 min
- p99
- 19.9 min
- rank
- #9
- samples
- 734
Injective
Leads7.50 s
- rank
- #6
- samples
- 1provisional
Ethereum vs Injective
Injective leads on the only live benchmark. Injective wins on Fastest Wormhole VAA finalization by source chain, live latency (7.50 s vs 15.3 min).
Ethereum
PoS chain using Gasper (Casper FFG plus LMD-GHOST). 12-second slots with deterministic finality every two epochs, roughly 12.8 minutes.
Injective
Cosmos SDK L1 with a native onchain orderbook and EVM compatibility layer. CometBFT consensus, sub-second block time, deterministic finality per block. TokenFactory MsgCreateDenom carries a flat 0.1 INJ governance fee on top of gas.
Side by side measurements
Fastest LayerZero source chain by end-to-end message delivery
BridgesEthereum
Trails4.1 min
- p99
- 19.6 min
- rank
- #16
- samples
- 1,278
Injective
No data in window
Fastest Axelar GMP source chain by end-to-end delivery
BridgesEthereum
Trails16.8 min
- rank
- #5
- samples
- 82provisional
Injective
No data in window
Frequently asked questions
Ethereum vs Injective: which one is better?
Ethereum and Injective are compared on 3 shared OpenChainBench benchmarks. Injective leads on Fastest Wormhole VAA finalization by source chain, live latency. See the live table on this page for every metric.
Which is faster, Ethereum or Injective?
On the Fastest Wormhole VAA finalization by source chain, live latency benchmark, Injective leads at 7.50 s (provisional) versus Ethereum at 15.3 min. Live measurement is updated continuously by the OpenChainBench harness.
How is the Ethereum vs Injective 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.
Related comparisons
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.