USDC migration post validation script

[0xsuryansh]

What It Does

The validator runs two independent checks:

1. chains checks (any EVM chain):

   • Step 1: resolve expected TAR active pool (direct address, datastore ref, or pool-kind)
   • Step 2: validate proxy local wiring (token + supported token)
   • Step 3: validate proxy backing pools (optional) and validate each remote lane

2. homeChainLiquidity checks (Ethereum mainnet or Sepolia only):

   • Step 1: validate siloed pool token is USDC
   • Step 2: fetch lockbox topology from the siloed pool and assert uniqueness
   • Step 3: for each remote selector, validate lock-release mode, lockbox authorization, and liquidity deltas

The validator aggregates findings: it attempts to run all independent validations and reports all
misconfigurations it can observe in a single error, only skipping checks that are blocked by a
failed upstream read/bind.

Typical Rollout Usage Patterns

1. Pre-cutover (in-flight messages must use legacy pool):

   • On canonical chains: validate TAR points to legacy USDCTokenPool 1.6.2
   • On Ethereum mainnet: validate TAR points to legacy HybridLockReleaseUSDCTokenPool 1.6.2

2. Post-cutover (proxy becomes active pool):

   • Validate TAR points to USDCTokenPoolProxy 2.0.0
   • Validate proxy backing pools match expected deployed pools (kinds)

3. Remote pool list evolution (legacy only -> legacy + new):

   • For a lane where you want the proxy to accept both old and new remotes, set:
     • expectedremotepoolkinds: [{legacy kind...}, {new kind...}]

Minimal YAML Sketch

This matches the repo’s existing YAML style where keys are lowercase field names:

environment: mainnet
domain: ccip
changesets:
  - validate_usdc_cld_rollout:
      payload:
        chains:
          5009297550715157269: # Ethereum Mainnet
            usdctoken: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
            tokenadminregistryref:
              type: "TokenAdminRegistry"
              version: "1.5.0"
            expectedtokenpoolkind:
              kind: "USDC_TOKEN_POOL_PROXY"
            usdctokenpoolproxyref:
              type: "USDCTokenPoolProxy"
              version: "2.0.0"
            expectedproxypoolkinds:
              cctpv1pool: { kind: "CCTP_V1_POOL" }
              cctpv2pool: { kind: "CCTP_V2_POOL" }
              cctpv2poolwithccv: { kind: "CCTP_V2_POOL_WITH_CCV" }
              siloedlockreleasepool: { kind: "SILOED_LOCK_RELEASE_POOL" }
            remotechains:
              3849287863852499584: # BOB mainnet selector (example)
                expectedmechanism: "LOCK_RELEASE"
                expectedremotepoolkinds:
                  - kind: "LEGACY_NON_CANONICAL_BURN_MINT_TOKEN_POOL"
                    qualifier: "0x<remote-qualifier>"

[github-actions]

👋 0xsuryansh, 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!

[Copilot]

Pull request overview

Adds a read-only changeset and basic tests to validate the post-migration on-chain state for the USDC CLD rollout across EVM chains (token admin registry active pool, USDCTokenPoolProxy routing/config, remote lane config, and Ethereum home-chain liquidity migration invariants).

Changes:

• Introduces ValidateUSDCCLDRollout changeset with config schema, precondition validation, and on-chain reads/assertions.
• Adds home-chain liquidity migration checks (hybrid lock-release mode, lockbox auth, locked/balance derived expectations).
• Adds unit tests covering key VerifyPreconditions failures and an Apply missing-chain failure.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
ccv/chains/evm/deployment/v1_7_0/changesets/validate_usdc_cld_rollout.go	New post-validation changeset implementing config validation + on-chain assertions for USDC CLD rollout.
ccv/chains/evm/deployment/v1_7_0/changesets/validate_usdc_cld_rollout_test.go	New tests for precondition validation and basic apply error behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Metric	cctp_migration_post_validation	main
Coverage	70.1%	69.8%