Fastest Wormhole VAA finalization by source chain, live latency
BridgesLinea
No data in window
Polygon
Trails4.69 s
- p99
- 14.37 s
- rank
- #6
- samples
- 214
Polygon leads on both live benchmarks. Polygon wins on Fastest LayerZero source chain by end-to-end message delivery (1.8 min vs 3.4 min), Bridged TVL by chain ($3.77B vs $343.23M). Data as of 2026-10-10 UTC.
ConsenSys zkEVM rollup with a prover-bound block cadence. Idle periods batch into longer intervals (p50 around 3-6 s) while busy periods produce blocks closer to the nominal 2 s mark.
Linea
No data in window
Polygon
Trails4.69 s
Linea
No data in window
Polygon
Trails12.5 min
Linea
Trails3.4 min
Polygon
Leads1.8 min
Linea
No data in window
Polygon
Trails44.17 s
| Provider | Bridged TVL | Bridged share | 7d change | 7d vs peers | Native | Canonical | External |
|---|---|---|---|---|---|---|---|
| Linea | $343.23M | 99.6% | - | - | $1.49M | $115.12M | $228.11M |
| Polygon | $3.77B | 95.1% | - | 0.15% | $194.55M | $2.36B | $1.42B |
Bridged TVL is value secured by the chain's bridge, not value locked in its DeFi protocols; a chain can rank high on one and low on the other. The split is L2Beat's: canonical is escrowed on the host chain by the chain's own contracts, external came through a third-party bridge, native was minted here. Rows are the chains L2Beat tracks in its scaling summary; a settled L1 has no row by construction, not by omission. Size is not quality: a large balance says capital came, not that it stayed.
Linea and Polygon are compared on 5 shared OpenChainBench benchmarks. Polygon leads on Fastest LayerZero source chain by end-to-end message delivery. See the live table on this page for every metric.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Polygon leads at 1.8 min versus Linea at 3.4 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.