This prerelease is now available for open review! Try it out, look at the code, and share your feedback.
In addition to all the changes in 4.8.0-rc.0, this new release candidate improves the timelock configuration process and updates part of the documentation.
- ⌛ TimelockController: Add a new admin constructor parameter that is assigned the admin role instead of the deployer account.
- 📖 Some documentation improvements.
Breaking changes
TimelockController: During deployment, the TimelockController used to grant the TIMELOCK_ADMIN_ROLE to the deployer and to the timelock itself. The deployer was then expected to renounce this role once configuration of the timelock is over. Failing to renounce that role allows the deployer to change the timelock permissions (but not to bypass the delay for any time-locked actions). The role is no longer given to the deployer by default. A new parameter admin can be set to a non-zero address to grant the admin role during construction (to the deployer or any other address). Just like previously, this admin role should be renounced after configuration. If this param is given address(0), the role is not allocated and doesn't need to be revoked. In any case, the timelock itself continues to have this role.
See the changelog for all the release details.