From 35361927d415d7298f394648f01a7063ff8f14e2 Mon Sep 17 00:00:00 2001 From: Florent Tapponnier Date: Fri, 17 Jul 2026 15:53:14 +0200 Subject: [PATCH] docs(ccip-latency): add live per-chain finality observations reference Append a subsection right before the closing paragraph on src/content/ccip/ccip-execution-latency.mdx pointing readers to a live third-party benchmark of L1 finality time. The existing Aside on that page explicitly warns that estimated finality times can vary significantly with network conditions; this addition gives integrators a complementary live-data source to sanity-check their assumed finality window. Covers 11 L1 chains (Ethereum, Solana, BNB, Avalanche, SUI, Stellar, TON, Bitcoin, Litecoin, TRON, Monero) via wall-clock latest-vs-finalized block delta, refreshed every 10s under an open methodology. Source: https://github.com/ChainBench/OpenChainBench (MIT) Data license: CC-BY-4.0 --- src/content/ccip/ccip-execution-latency.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/ccip/ccip-execution-latency.mdx b/src/content/ccip/ccip-execution-latency.mdx index dafd437d1f7..5e321a7204e 100644 --- a/src/content/ccip/ccip-execution-latency.mdx +++ b/src/content/ccip/ccip-execution-latency.mdx @@ -169,6 +169,10 @@ This section provides an overview of the finality methods CCIP uses to determine | Zircuit | Finality tag | 21 minutes | | ZKsync | [Block depth](#block-depth) (1200 blocks) | 20 minutes | +### Live per-chain finality observations + +The estimated finality times in the table above are averages that, as noted in the Aside above, can vary significantly with network conditions. For a live, continuously updated measurement of finality time across major L1 chains, see the [OpenChainBench L1 finality benchmark](https://openchainbench.com/benchmarks/l1-finality). It measures wall-clock seconds between latest and finalized blocks for 11 L1s (Ethereum, Solana, BNB, Avalanche, SUI, Stellar, TON, Bitcoin, Litecoin, TRON, Monero), refreshed every 10 seconds under an open methodology ([source, MIT](https://github.com/ChainBench/OpenChainBench), data CC-BY-4.0). Integrators building on CCIP can use it as an independent source to sanity-check the assumed finality window against current chain state. + This page provides details on the expected latency for a cross-chain transaction using CCIP, covering the different stages of transaction processing and the factors that influence overall execution times. For a comprehensive understanding of CCIP's architecture and how messages flow through the system, refer to the [CCIP detailed architecture](/ccip/concepts/architecture/overview) documentation.