USDC deployment #1
Merged
Conversation
This file contains 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
fedealconada
requested review from
CryptoMan0x,
federava,
RomanHiden and
lutr0
CryptoMan0x
approved these changes
Sep 18, 2024
SOP-55 Deploy Circle's USDC on Sophon testnet
Try deploying native USDC to Sophon testnet following their guide |
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.
Summary
This PR makes the USDC deployment compatible so as to be deployed on a zkSync based chain.
Detail
NOTE: The USDC contracts remained unchanged.
Changes:
selfdestructonAbstractV2Upgrader.solSignatureCheckerlibrary needs to be deployed separately and then linked (this is a constraint from zksync-foundry)add-new-minterscript as a util to add a new minterFixes #SOP-55