Fastest Wormhole VAA finalization by source chain, live latency
BridgesArbitrum
Trails16.6 min
- rank
- #10
- samples
- 25provisional
Polygon
Leads4.42 s
- p99
- 14.18 s
- rank
- #4
- samples
- 164
Arbitrum leads on 1 of 4 shared benchmarks, Polygon on 3. Arbitrum wins on Fastest LayerZero source chain by end-to-end message delivery (27.24 s vs 1.6 min). Polygon wins on Fastest Wormhole VAA finalization by source chain, live latency (4.42 s vs 16.6 min), Fastest Chainlink CCIP source chain by end-to-end delivery latency (11.9 min vs 17.6 min), Fastest Axelar GMP source chain by end-to-end delivery (45.70 s vs 20.0 min).
Optimistic rollup built on Nitro stack with a fast-finality sequencer. Sub-second block times (~250 ms) via a 250 ms default block interval, far below the 2 s OP Stack convention. 7-day fraud-proof window for L1 finality.
Arbitrum
Trails16.6 min
Polygon
Leads4.42 s
Arbitrum
Trails17.6 min
Polygon
Leads11.9 min
Arbitrum
Leads27.24 s
Polygon
Trails1.6 min
Arbitrum
Trails20.0 min
Polygon
Leads45.70 s
Arbitrum and Polygon are compared on 4 shared OpenChainBench benchmarks. Arbitrum leads on Fastest LayerZero source chain by end-to-end message delivery. Polygon leads on Fastest Wormhole VAA finalization by source chain, live latency. See the live table on this page for every metric.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Arbitrum leads at 27.24 s versus Polygon at 1.6 min. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest Wormhole VAA finalization by source chain, live latency benchmark, Polygon leads at 4.42 s versus Arbitrum at 16.6 min (provisional). Live measurement is updated continuously by the OpenChainBench harness.
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.
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.