chore: CCTPv2 destinationCaller for managed relayer#12664
Merged
Conversation
dckc
force-pushed
the
dc-537
branch
10 times, most recently
from
933c6c2 to
534e192
Compare
mhofman
reviewed
May 15, 2026
mhofman
left a comment
mhofman
left a comment
Member
There was a problem hiding this comment.
I'm surprised the design doesn't call for a vstorage difference for CCTP v1 vs v2 transfers. In particular the destinationCaller address is a piece of information that may be operationally relevant (e.g. if / when we need to rotate / update the relayer mechanism).
Member
That sounds like a dubious security claim. Will discuss this offline. |
…VM CCTPv2 Add cctpRelayer test address to Optimism mock. Decode GMP memo in CCTPv2 flow test and assert depositForBurn receives the correct destinationCaller. Also document that real relayer addresses are TBD from PAK-354.
Latest upgrade txs: ymax0: 2026-03-25 tx 59A19F0B97B1ACE150CB0C2FCFE188487BC7921A303FAA2F94462E9398BF7A5B ymax1: 2026-04-03 tx CB97FABCE49DFD8957CE92641112380C10A91B0641F2C6EB4CFE2C9CCA953928
…-configs and chain snapshots
mhofman
approved these changes
May 21, 2026
mhofman
left a comment
mhofman
left a comment
Member
There was a problem hiding this comment.
LGTM, but removing the automerge label to let you address non blocking feedback
mergify Bot
added a commit
that referenced
this pull request
May 22, 2026
) refs: - #12454 - #12415 - #12664 ## Description re-enable CCTPv2 routes in planner by reverting #12454 ### Security / Scaling Considerations none beyond #12454 (which has "n/a") There is perhaps an availability impact; resolver responsibility is different as of #12664. ### Documentation Considerations none beyond #12454 ### Testing Considerations - restores some tests ### Upgrade Considerations requires contract is upgraded to include #12664 (done for ymax0; see [ymax-v0.3.2605-beta1 release](https://github.com/Agoric/agoric-sdk/releases/tag/ymax-v0.3.2605-beta1) ).
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
2 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.
closes: AGO-537
Description
Enable CCTP v2 direct EVM-to-EVM USDC transfers with a managed relayer (
destinationCaller) to reduce latency from ~18 min to ~60 sec.CCTPv2.applypasses the relayer asdestinationCallertodepositForBurn(padded to bytes32); falls back toZERO_BYTES32when unsetcctpRelayeraddress to per-chain contract configsymax-upgrade-run-logs --save-txs <n>dumps recent upgrade transactions for override extractionSecurity Considerations
Setting
destinationCallerto a managed relayer address makes that relayer required for destination-chain receipt. If the configured address is wrong, unavailable, or loses key control, the mint cannot be completed by another relayer under the normal any-caller flow.Scaling Considerations
n/a
Testing Considerations
destinationCallerverification to the CCTPv2 flow test (decodes GMP memo)evm-overrides.test.tsvalidates shape on computed overrides, compares contract addresses against golden filesUpgrade Considerations
Backwards compatible —
cctpRelayeris optional, v1 flows don't setcctpVersion = 2n. Relayer addresses from PAK-354 required before adding toprivateArgsOverridesat upgrade time. ymax0 upgrades run via CI; ymax1 via Makefile.