chore: reproduce deployment broadcast files from on-chain data #204
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.
Description
When I deployed and executed the governance proposal for Mento Governance, I made the immense mistake of not committing the broadcast files to Github. A few days later my macbook went belly up and I lost all the data. Sigh.
This PR uses an archive node (quicknode) and some manual data to reconstruct the Foundry broadcast files. This is useful to have in conjunction with the rest of our tooling which depends on broadcast files. It would have been very useful a few months ago because it makes it really easy to verify contracts on
celoscan
, I used it to verify a few remaining proxies.The script to generate this is a one-off script (famous last words), but I thought it made sense to put it in there in case we ever need something similar, but it shouldn't really be reviewed thoroughly.
Other changes
N/A
Tested
Verified broadcast script manually and tried it out with the cleoscan verification script.
Related issues
N/A
Backwards compatibility
Precisely
Documentation
N/A