Fastest Wormhole VAA finalization by source chain, live latency
BridgesAvalanche
Leads7.30 s
- p99
- 14.45 s
- rank
- #4
- samples
- 33
Celo
Trails1050.00 min
- p99
- 1197.00 s
- rank
- #11
- samples
- 1
Avalanche leads on 1 of 2 shared benchmarks, Celo on 1. Avalanche wins on Fastest Wormhole VAA finalization by source chain, live latency (7.30 s vs 1050.00 s). Celo wins on Fastest LayerZero source chain by end-to-end message delivery (47.48 s vs 48.10 s).
Primary Network runs the Snowman BFT consensus derived from Snow protocols. Sub-second deterministic finality with no chain reorganizations.
Avalanche
Leads7.30 s
Celo
Trails1050.00 min
Avalanche
Trails120.02 min
Celo
No data in window
Avalanche
Trails48.10 s
Celo
Leads47.48 s
Avalanche
No data in window
Celo
No data in window
Avalanche
Trails90.00 min
Celo
No data in window
Avalanche and Celo are compared on 5 shared OpenChainBench benchmarks. Avalanche leads on Fastest Wormhole VAA finalization by source chain, live latency. Celo 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 Wormhole VAA finalization by source chain, live latency benchmark, Avalanche leads at 7.30 s versus Celo at 1050.00 s. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Celo leads at 47.48 s versus Avalanche at 48.10 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.