-
Notifications
You must be signed in to change notification settings - Fork 147
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
Configurator #160
Configurator #160
Conversation
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.
Awesome work getting this started 💪
Added some changes to improve the upgradeability of the There is now a separate |
I've updated the configurator flow to be simpler based on a discussion with Geoff. Instead of sharing one customized proxy, the configurator and Comet will now both have their own un-modified OZ proxies. |
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.
Think this is making good sense!
Added the |
37d0a1b
to
26984c6
Compare
5413447
to
81dac52
Compare
b184010
to
f85e276
Compare
Rebased on top of main (which has the recently merged #208). |
c497808
to
9efa9e0
Compare
…backs to for admins
…ple Timelock as admin
…oxyAdminAdmin contract (#212)
…DME with info on these changes
f8518a1
to
381ed9d
Compare
This is an implementation of the advanced architecture described in RFC 021, but with some changes to enhance upgradeability, namely a separate
Configurator
contract that is upgradeable. The overall system looks something like:Timelock
is an admin ofProxyAdmin
, which is an admin of the two proxies.Timelock
is also anadmin
ofConfigurator
, meaning only theTimelock
can set parameters inConfigurator
.