-
Notifications
You must be signed in to change notification settings - Fork 268
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 #526 - add upgrade mechanism to registry #625
Conversation
5901aee
to
284b5a5
Compare
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.
Minor nits on naming.
284b5a5
to
3dd7525
Compare
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.
Needs some natspec for all the functions in Registry
03a80c4
to
2b4f183
Compare
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.
More consistency on @notice
then good to go.
2b4f183
to
329e2d0
Compare
Description
Per our slack discussion of registry snapshotting issue, currently, rollup/inbox/outbox just call the latest version of each other. So we aren't really handling forks for now. I have therefore created #624 for when we reach consensus on how to handle forks for L1<>L2 communication.
Fixes #526
Checklist: