Add timelocks to migrations and upgrades #223
Labels
needs discussion
This issue needs more discussion before its implementation
security
This issue impacts security assumptions
solidity
Issues related to the solidity contracts
type: feature
Feature request
Description
Support for contract upgradability by a proxy admin was added in #188 and support for light client migrations was added in #196. In both cases, we have not included any timelocks on said upgrades/migrations.
A timelock is a delay between the admin broadcasting a proposal and the execution of that proposal, allowing users to see the upcoming changes and potentially migrate their funds if they believe their funds to be at risk.
Discussion
Openzeppelin has a very useful TimelockController contract which is intended to be owned by a multisig.
This gives us two options:
TimelockController
(in this case we close this issue as not planned)TimelockController
for the admins ourselves and require them to use it.For Admin Use
The text was updated successfully, but these errors were encountered: