-
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
fix(protocol): add 1 to _REENTRY_SLOT in EssentialContract #16593
Conversation
This reverts commit 0523a47.
fix(protocol): add 1 to _REENTRY_SLOT in EssentialContract
🚨 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.
Approved, but we do assume the string being used is unique to already prevent collisions from happening. I guess a good general recommendation to be super super sure, but wouldn't call this an issue.
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.
Emmm looks like we need to upgrade every contract we deployed both on L1 / L2 for this change...
We don't have to apply the change anytime soon. The previous code works fine. |
…tract (#16593)"" This reverts commit fdd6d0303abad7a2fa37366b5ffcd08a61bf975f.
Change _REENTRY_SLOT from
0xa5054f728453d3dbe953bdc43e4d0cb97e662ea32d7958190f3dc2da31d9721a
to0xa5054f728453d3dbe953bdc43e4d0cb97e662ea32d7958190f3dc2da31d9721a + 1
Based on code-423n4/2024-03-taiko-findings#11