feat: deployment info tool for L1 deployments #3795
Draft
+993
−1
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
…ltisig support Support multiple named multisigs (serviceco, tokenco, espresso_labs) instead of a single multisig address. Add deployment info for mainnet and decaf networks with all contract addresses and multisig configurations. Improve CLI with --network flag for automatic defaults.
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.
WIP but currently works to generate a small JSON with L1 deployment info.
We're working on figuring out how to do the mainnet deployment and currently we have manually tracked addresses in several places. I would like to remove opportunities for manual errors.