docs(ccip-latency): add live per-chain finality observations reference#3976
Open
Flotapponnier wants to merge 1 commit into
Open
docs(ccip-latency): add live per-chain finality observations reference#3976Flotapponnier wants to merge 1 commit into
Flotapponnier wants to merge 1 commit into
Conversation
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
|
Someone is attempting to deploy a commit to the Chainlink Labs Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a small subsection at the end of
src/content/ccip/ccip-execution-latency.mdx(right before the closing paragraph) that points readers to a live third-party benchmark of L1 finality time. The existingFinality by blockchaintable gives useful estimated averages and the accompanying Aside explicitly notes that "these times can vary significantly due to network conditions and other factors". This addition gives integrators a complementary live-data source to sanity-check their assumed finality window against current chain state.Why
ccip-execution-latency.mdxis centred on the impact of source-chain finality on CCIP end-to-end latency. The table lists ~45 supported chains with estimated finality times ranging from< 1 second(Avalanche, Solana) to12 hours(Corn). Devs building on CCIP often need to know whether those numbers still hold in current network conditions, especially:OpenChainBench 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. Not a replacement for the CCIP-specific finality methods documented above; a live sanity-check complement.
About OpenChainBench
Test plan
###subsection appended before the existing closing paragraphFinality by blockchaintable and the Aside note aboveHappy to reword, move to an
<Aside>, or drop entirely if this does not fit the docs' tone.