docs(ccip): link OpenChainBench live latency measurement on execution-latency page#3999
Open
Flotapponnier wants to merge 1 commit into
Open
Conversation
|
@Flotapponnier 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.
The
ccip-execution-latency.mdxpage documents the theoretical source-chain finality component of CCIP's total execution time (finality tags, block depth, etc.). This PR adds a small "Observed end-to-end latency" section pointing readers to a live third-party measurement of the full source-to-destination pipeline.The linked benchmark polls the public CCIP Tools API, filters to
status: SUCCESSmainnet messages, and publishes per-source-chain p50/p90/p99 over a rolling 24h window. The methodology explicitly frames the source-chain finality wait as a security tradeoff (matching this doc's framing) rather than a performance limitation. Harness source is open in the linked repo so readers can audit the query and sampling.Placed at the end of the finality table so it reads as complementary observational data, not a replacement for the architectural explanation above it.