-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
feat(protocol): allow resetting genesis hash on L1 before 1st block is proposed #17078
Conversation
feat(protocol): allow resetting genesis hash on L1 before 1st block is proposed
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
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.
I think it makes sense, but only in case if we want to deploy all contracts while still being able to do last minute change - which we should not imo at this point.
My .02: we should have a process for upgrading, and documented. we cannot do these kind of random, rushed merges/changes at mainnet either. We should practice some relax.
We need to reset genesis in TaikoL1 on Ethereum to indirectly upgrade its L2 contracts