Fastest Wormhole VAA finalization by source chain, live latency
BridgesCelo
Trails17.5 min
- p99
- 19.9 min
- rank
- #10
- samples
- 6
Solana
Leads17.53 s
- p99
- 20.69 s
- rank
- #8
- samples
- 6,707
Celo leads on 2 of 3 shared benchmarks, Solana on 1. Celo wins on Fastest LayerZero source chain by end-to-end message delivery (41.74 s vs 49.12 s), Fastest Hyperlane source chain by end-to-end message delivery (22.50 s vs 39.57 s). Solana wins on Fastest Wormhole VAA finalization by source chain, live latency (17.53 s vs 17.5 min).
Proof-of-History sequencing combined with Tower BFT consensus. Probabilistic finality at 32 confirmed slots. Slot time around 400 milliseconds.
Celo
Trails17.5 min
Solana
Leads17.53 s
Celo
No data in window
Solana
Trails1.5 min
Celo
Leads41.74 s
Solana
Trails49.12 s
Celo
Leads22.50 s
Solana
Trails39.57 s
Celo and Solana are compared on 4 shared OpenChainBench benchmarks. Celo leads on Fastest LayerZero source chain by end-to-end message delivery. Solana 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, Celo leads at 41.74 s versus Solana at 49.12 s. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest Wormhole VAA finalization by source chain, live latency benchmark, Solana leads at 17.53 s versus Celo at 17.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.