feat(cli): fetch CCV attestations directly from a verifier's aggregator - #390
Open
aelmanaa wants to merge 2 commits into
Open
feat(cli): fetch CCV attestations directly from a verifier's aggregator#390aelmanaa wants to merge 2 commits into
aelmanaa wants to merge 2 commits into
Conversation
|
You must have Developer access to commit code to Chainlink Labs on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes. Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles |
|
👋 aelmanaa, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
aelmanaa
marked this pull request as draft
August 30, 2026 13:45
Coverage Report |
aelmanaa
force-pushed
the
feat/direct-aggregator-fetch
branch
from
August 30, 2026 14:59
0938bc9 to
470329c
Compare
aelmanaa
marked this pull request as ready for review
August 30, 2026 15:02
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
This pull request introduces major enhancements to the CCIP CLI and its documentation, focusing on flexible and robust support for CCV attestation sources during manual execution. It adds new CLI options and backend logic to fetch CCV attestations directly from verifiers or to supply them manually, ensuring messages can be executed even when attestations are not available via the default indexers or API. The CLI builder and documentation are updated to reflect these new capabilities, and tests are added to ensure correct grouping and rendering of options.
Manual Execution & Verification Enhancements:
Added
--verifier/--verifier-endpointand--ccv-dataCLI options, allowing users to fetch CCV attestations directly from verifier aggregators over gRPC or supply them out-of-band, ensuring execution is possible even when indexers lack the required CCV. The command logic ensures that these sources are used as fallbacks only when managed sources are insufficient, and prevents unverified execution that would revert onchain. [1] [2] [3] [4] [5]Updated CLI option parsing and error handling to robustly process new verification flags, including improved coercion and validation for
--verifier,--ccv-data, and--indexer.Documentation & CLI Builder Updates:
Expanded documentation for manual execution to detail the new verification source options, their formats, usage scenarios, and fallback behaviors. [1] [2] [3]
Updated the CLI Builder UI to include a new "Verification Sources" group, ensuring the new options are visible and properly grouped in the interface. Added tests to guarantee correct rendering and grouping. [1] [2] [3] [4] [5] [6]
Build & Dependency Changes:
@grpc/grpc-js,@grpc/proto-loader) and updated the build process to include necessary protocol buffer assets. [1] [2]These changes significantly improve the flexibility and reliability of CCIP manual execution, especially for advanced or recovery scenarios where attestations are not available from standard sources.