[PRC #1] Allow Stewards to use PWN timelocks

Governance
1

TL;DR

Allow Stewards to call any selector on PWN timelocks.

Voting

Mode: Stewards
Duration: 3 days
Veto threshold: 10%

Proposal

This proposal aims to expand the capabilities of the Steward governance plugin by updating the DAOExecuteAllowlist. The update will permit the plugin to call any selector on both the PWN Protocol and Admin timelocks. The DAOExecuteAllowlist serves as an authorization module for Stewards governance, controlling what can be executed through this governance mechanism.

PWN currently operates with two timelocks:

  • Protocol timelock: Owns PWNHub, PWNConfig, and MultiTokenCategoryRegistry
  • Admin timelock: Administers the PWNConfig proxy.

By implementing this proposal, Stewards will gain the ability to:

  • Update PWNHub tags
  • Register new MultiToken categories
  • Modify PWNConfig values
  • Upgrade the PWNConfig proxy implementation
  • Schedule operation on timelocks
  • Grant and revoke timelocks roles
  • Adjust the minimum delay for timelocks

This change will significantly enhance the Stewards’ governance capabilities, allowing for more comprehensive management of the PWN protocol.

On-chain actions

  1. call DAOExecuteAllowlist function setAllowlist(address,bytes4,bool) with protocol timelock address, ANY_SELECTOR constant, and true value.
  2. call DAOExecuteAllowlist function setAllowlist(address,bytes4,bool) with admin timelock address, ANY_SELECTOR constant, and true value.

Contract addresses

  • DAOExecuteAllowlist: 0xa7abafd48372560f35D599a36D729B0dce143856
  • Protocol timelock: 0xd8dbdDf1c0FDdf9b5eCFA5C067C38DB66739FBAB
  • Admin timelock: 0xd57e72A328AB1deC6b374c2babe2dc489819B5Ea
3 Likes
2

Stewards proposal created: PWN DAO Governance