-
Notifications
You must be signed in to change notification settings - Fork 17
docs: bold upgrade guide #35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: gzeon <hng@offchainlabs.com>
godzillaba
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should not be merged without #36
|
|
||
| 7. Run the prepare script, this will deploy the actions. L1_PRIV_KEY does not need to be the chain owner. | ||
| ``` | ||
| $ L1_PRIV_KEY=xxx INFURA_KEY=xxx ETHERSCAN_API_KEY=xxx yarn script:bold-prepare --network {mainnet|arb1|base|arbSepolia} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this script will deploy ETH versions of the inbox,outbox,bridge. we need to update it to handle ERC20 versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pushed this commit to disable custom fee token chain upgrade for now be1c247
update bold guide
* chore: update v3.0.0 meta * feat: add any * docs: comments * chore: add rei hashes * fix: type * feat: check fee token * feat: v3 upgrade check * docs: bold upgrade draft * Update scripts/foundry/contract-upgrades/3.0.0/README.md Co-authored-by: gzeon <hng@offchainlabs.com> * readme tweak * Update scripts/foundry/contract-upgrades/3.0.0/README.md * fix: disable custom fee token chain support for v3 for now * update guide * merge main * restore v3 metadata hashes * restore 2.1.2 and 2.1.3 hashes * fix target versions descending * fix target versions descending * set bold prereqs same as 7702 patch prereqs * allow multiple upgrade paths * update versions in readme * set tag * Revert "allow multiple upgrade paths" This reverts commit c3688df. * special case for 2.1.3 and 3.0.0 * only L2 can upgrade to v3 * add comment and L1 sepolia exception * chore: use v3.1.0 --------- Co-authored-by: Henry <11198460+godzillaba@users.noreply.github.com>
BLK-275