Fastest Wormhole VAA finalization by source chain, live latency
BridgesMantle
No data in window
Polygon
Trails4.38 s
- p99
- 14.42 s
- rank
- #4
- samples
- 152
Mantle leads on 1 of 3 shared benchmarks, Polygon on 2. Mantle wins on Fastest LayerZero source chain by end-to-end message delivery (1.2 min vs 1.8 min). Polygon wins on Fastest Chainlink CCIP source chain by end-to-end delivery latency (12.9 min vs 22.5 min), Fastest Axelar GMP source chain by end-to-end delivery (46.80 s vs 45.0 min).
Modular OP Stack fork using EigenDA for data availability rather than Ethereum calldata, cutting L1 anchoring cost. 2-second sequencer block time, MNT token for gas (ETH-pegged).
Mantle
No data in window
Polygon
Trails4.38 s
Mantle
Trails22.5 min
Polygon
Leads12.9 min
Mantle
Leads1.2 min
Polygon
Trails1.8 min
Mantle
No data in window
Polygon
Trails10.33 s
Mantle
Trails45.0 min
Polygon
Leads46.80 s
Mantle and Polygon are compared on 5 shared OpenChainBench benchmarks. Mantle leads on Fastest LayerZero source chain by end-to-end message delivery. Polygon leads on Fastest Chainlink CCIP source chain by end-to-end delivery latency. See the live table on this page for every metric.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Mantle leads at 1.2 min versus Polygon at 1.8 min. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest Chainlink CCIP source chain by end-to-end delivery latency benchmark, Polygon leads at 12.9 min versus Mantle at 22.5 min. 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.