[CCIP 8187] CCTP deployment tooling #1523
Merged
+2,761
−3,804
Conversation
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
# Conflicts: # ccv/chains/evm/gobindings/generated/latest/burn_mint_with_lock_release_flag_token_pool/burn_mint_with_lock_release_flag_token_pool.go # ccv/chains/evm/gobindings/generated/latest/onramp/onramp.go # ccv/chains/evm/gobindings/generated/latest/usdc_token_pool/usdc_token_pool.go # ccv/chains/evm/gobindings/generated/latest/usdc_token_pool_cctp_v2/usdc_token_pool_cctp_v2.go # ccv/chains/evm/gobindings/generated/latest/usdc_token_pool_proxy/usdc_token_pool_proxy.go # chains/evm/.gas-snapshot # chains/evm/contracts/pools/USDC/USDCTokenPool.sol # chains/evm/contracts/pools/USDC/USDCTokenPoolCCTPV2.sol # chains/evm/contracts/test/helpers/USDCTokenPoolCCTPV2Helper.sol # chains/evm/contracts/test/helpers/USDCTokenPoolHelper.sol # chains/evm/contracts/test/pools/BurnFromMintTokenPool/BurnFromMintTokenPoolSetup.t.sol # chains/evm/contracts/test/pools/BurnMintTokenPool/BurnMintTokenPool.lockOrBurn.t.sol # chains/evm/contracts/test/pools/BurnMintTokenPool/BurnMintTokenPool.releaseOrMint.t.sol # chains/evm/contracts/test/pools/BurnToAddressMintTokenPool/BurnToAddressMintTokenPoolSetup.t.sol # chains/evm/contracts/test/pools/BurnWithFromMintTokenPool/BurnWithFromMintTokenPool.lockOrBurn.t.sol # chains/evm/gobindings/generation/generated-wrapper-dependency-versions-do-not-edit.txt
# Conflicts: # ccv/chains/evm/gobindings/generated/latest/onramp/onramp.go # chains/evm/.gas-snapshot # chains/evm/gobindings/generation/generated-wrapper-dependency-versions-do-not-edit.txt
RensR
reviewed
Jan 2, 2026
| ChainSelector: input.ChainSelector, | ||
| Address: common.HexToAddress(input.TokenPoolAddress), | ||
| Args: input.FinalityValue, | ||
| Args: input.MinFinalityValue, |
Collaborator
There was a problem hiding this comment.
We dont use this wording onchain, should be change this to refer to block depth instead?
Contributor
Author
There was a problem hiding this comment.
No because this is intended to support multiple chain families, and not all chains use block depth to identify finality. They may pass an ID here instead.
RensR
reviewed
Jan 2, 2026
ccv/chains/evm/deployment/v1_7_0/sequences/deploy_verifier_resolver_via_create2.go
Show resolved
Hide resolved
RensR
reviewed
Jan 2, 2026
| SupportingContracts []S | ||
| type CommitteeVerifierConfig[C any] struct { | ||
| // CommitteeVerifier is a set of addresses comprising the committee verifier system. | ||
| CommitteeVerifier []C |
Collaborator
There was a problem hiding this comment.
I guess this is needed because we can have multiple live at the same time right?
Contributor
Author
There was a problem hiding this comment.
Yea, EVM verifiers will have a resolver contract and all the active impls. It is up to the sequence implementation to error if it doesn't have all the contracts it needs to properly configure the environment.
RensR
reviewed
Jan 2, 2026
RensR
reviewed
Jan 2, 2026
RensR
reviewed
Jan 2, 2026
RensR
reviewed
Jan 2, 2026
ccv/chains/evm/deployment/v1_7_0/sequences/cctp/deploy_cctp_chain.go
Outdated
Show resolved
Hide resolved
ccv/chains/evm/deployment/v1_7_0/sequences/cctp/deploy_cctp_chain.go
Outdated
Show resolved
Hide resolved
0xsuryansh
reviewed
Jan 5, 2026
ccv/chains/evm/deployment/v1_7_0/sequences/cctp/deploy_cctp_chain.go
Outdated
Show resolved
Hide resolved
|
0xsuryansh
approved these changes
Jan 5, 2026
RensR
approved these changes
Jan 5, 2026
KodeyThomas
approved these changes
Jan 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
https://smartcontract-it.atlassian.net/browse/CCIP-8187
Requires pin to develop post-merge