Market Updates - Alternate Governance Track

Proposals
4

Hi Compounders. Unfortunately, an update of the Configurator contract will not solve the problem, because after the update of the Configurations, should be called deployAndUpgradeTo method at ProxyAdmin admin (Mainnet example of ProxyAdmin contract) which could be called only by Timelock. An update of Timelock seems like not the best solution because the contract is not upgradable and critical for the whole DAO infrastructure. Also, there should be an updated Configurator on 6 networks.

What WOOF! team suggests

Update only Governor Bravo implementation on Mainnet.

  1. Add an array of fast executors. (farther FE)
  2. Add method to whitelist FE
  3. Add method to de-whitelist FE
  4. Update propose method:
    4.1 If the proposal is created by FE address, then the review takes 20 hours, instead of 44 hours.
    4.2 If the proposal is created by FE address, then voting time takes 1 day, instead of 3 days and 100-200K quorum, instead of 400K quorum.
  5. Update queue method
    5.1 If the proposal is created by FE address, then the queue takes 24 hours instead of 48 hours.
  6. Also, we can update active proposals for FE members from 1 active proposal to 2-3 active proposals.

Current changes will decrease the proposal pipeline’s lifetime for Mainnet updates from 7 days to 3 days and for L2 updates - from 8 days to 4 days.

Note: New variable constants are example ones and can be changed.
Note 2: The solution is the draft one and can require adding/updating additional constants/methods

As security measures, the discord bot for the governance feed can be updated and notify if FE address proposed not only updates of Configurator for faster delegators reaction.

The scope of updates is not only new Governor bravo implementation, tests and deployment scripts, but also requires the update of scenarios in the Comet repository.

2 Likes