[eth] Add zksync deployment files #450
Merged
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
jayantk
approved these changes
Jan 3, 2023
Contributor
jayantk
left a comment
jayantk
left a comment
There was a problem hiding this comment.
thanks. thankfully managing the contracts shouldn't be as bad since upgrades etc. are done via wormhole.
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.
This PR adds the requied files and configurations for deploying Pyth to zkSync networks (currently only testnet).
Unfortunately they only support hardhat and I needed to rewrite deployment scripts. The zksync plugin expects deployment scripts to be on
deploydirectory and I couldn't get away from it.Also as our deployment/sync script is based in truffle contract upgrades won't work automatically and I added a script for the part that needs to be done in hardhat with proper documentation. It is not very clean and I might change it in the future (or the deployment automation might improve it).
Please read Deploying.md for more information on how this works.