Fastest Wormhole VAA finalization by source chain, live latency
BridgesArbitrum
Trails1050.00 min
- p99
- 1768.80 s
- rank
- #12
- samples
- 26
Polygon
Leads7.43 s
- p99
- 14.39 s
- rank
- #5
- samples
- 183
Arbitrum leads on 2 of 5 shared benchmarks, Polygon on 3. Arbitrum wins on Fastest LayerZero source chain by end-to-end message delivery (27.94 s vs 110.85 s), Fastest Hyperlane source chain by end-to-end message delivery (12.53 s vs 12.88 s). Polygon wins on Fastest Wormhole VAA finalization by source chain, live latency (7.43 s vs 1050.00 s), Fastest Chainlink CCIP source chain by end-to-end delivery latency (750.00 s vs 1050.00 s), Fastest Axelar GMP source chain by end-to-end delivery (52.50 s vs 1500.00 s).
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
Trails1050.00 min
Polygon
Leads7.43 s
Arbitrum
Trails1050.00 min
Polygon
Leads750.00 min
Arbitrum
Leads27.94 s
Polygon
Trails110.85 min
Arbitrum
Leads12.53 s
Polygon
Trails12.88 s
Arbitrum
Trails1500.00 min
Polygon
Leads52.50 s
Arbitrum and Polygon are compared on 5 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.94 s versus Polygon at 110.85 s. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest Wormhole VAA finalization by source chain, live latency benchmark, Polygon leads at 7.43 s versus Arbitrum at 1050.00 s. 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.
A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.