Right now, the mapping between timelock and governor needs storage, for the following:
- timelock address
- operationID (for each operation)
So, the storage is manipulated directly in the example contract. However, a timelock extension for example, could have handled these low-level storage manipulations, and the users won't have to think about / deal with the storage themselves.
Although this is not a bug, I believe it is good to have for Developer Experience in general.
Assigned both of us, because this is still in discussion phase, and we may decide to abandon the idea, or change it.
Right now, the mapping between timelock and governor needs storage, for the following:
So, the storage is manipulated directly in the example contract. However, a timelock extension for example, could have handled these low-level storage manipulations, and the users won't have to think about / deal with the storage themselves.
Although this is not a bug, I believe it is good to have for Developer Experience in general.
Assigned both of us, because this is still in discussion phase, and we may decide to abandon the idea, or change it.