-
Notifications
You must be signed in to change notification settings - Fork 1
build/devenv: multiple verifier and receiver deployment #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Add Justfile recipe to do it easily for root module and build/denvenv.
* Fix extraArgs offchain encoding * Specify multiple commit verifier deployments * Specify multiple mock receiver deployments
[committees.default.quorumConfigs.4793464827907405086] | ||
committeeVerifierAddress = "0x9A9f2CCfdE556A7E9Ff0848998Aa4a0CFD8863AE" | ||
threshold = 1 | ||
threshold = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unifying everything for now until we figure out a better way to generate these configs from code.
ChainSel: selector, | ||
RemoteChains: remoteChains, | ||
CommitteeVerifiers: []datastore.AddressRef{ | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RensR It would be useful to a description on the Verifier contract to identify it apart from typeandversion and direct address.
Would be a lot easier to ensure the source/dest chain verifier pair match for any given ccv
Code coverage report:
|
Requires: smartcontractkit/chainlink-ccip#1298
This PR is a pre-requisite to testing messages with multiple verifiers specified. Also bumps chainlink-ccip to the version that no longer has the required/optional/threshold distinction in the extraArgs.