Open
Conversation
|
Linked to Slack thread successfully |
|
Forge code coverage:
|
ee0eecf to
3f497a0
Compare
O1ahmad
commented
Dec 11, 2025
3f497a0 to
aaef78e
Compare
dv3-000
requested changes
Jan 12, 2026
952766c to
709acc9
Compare
…okenMinter to tokenMinterV2, and implement Create2 CCTPv2 contract deployments
411b67b to
821d7cc
Compare
821d7cc to
ab65752
Compare
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.
Motivation
contributes to ENG-1492
Solution
depositForBurnTokenMessengerV2function now exposes the destinationCaller property which can either limit message processing to a specific address or allow any with specification of the 0 address - v1 contracts currently hardcode this property to the 0 address. Setting of this property can be propagated from FE clients to the instruction settings and offchain executor logisticsReviewer Checklist