cLabs and the community are planning to propose 5 governance proposals simultaneously this coming week. By maximizing the overlap of the voting period, we hope to reduce voter fatigue. The first proposal will reduce the quorum required for passing all subsequent proposals. Due to a dequeue limit of 3 proposal/day, the next 4 proposals are spread over the following two days.
The tentative proposal timeline is as follows:
Batch 1: Tuesday, Jan 5
Batch 2: Wednesday, Jan 6
Batch 3: Thursday, Jan 7
- Batch 1: Tuesday, Jan 5
- Batch 2: Wednesday, Jan 6
- Batch 3: Thursday, Jan 7
- Batch 1: Wednesday, Jan 6
- Batch 2: Thursday, Jan 7
- Batch 3: Friday, Jan 8
- Batch 1: Thursday - Tuesday (Jan 7-12)
- Batch 2: Friday - Wednesday (Jan 8-13)
- Batch 3: Saturday - Thursday (Jan 9-14)
- Batch 1: Tuesday, Jan 12
- Batch 2: Wednesday, Jan 13
- Batch 3: Thursday, Jan 14
Impact of Governance Voting Vulnerability
A recently discovered vulnerability in the governance voting process allows voters to vote twice on a proposal. The condition can occur only if there are simultaneous proposals in the referendum (voting) stage which have their referendum stages end at times differing greater than 3 days (the amount of time to unlock and lock gold in another account). In other words, proposals that are proposed between 3-5 days apart introduce this risk.
A fix has been made and will be deployed in the contracts release 2 updates (end of January). For these proposals, proposers will submit them less than 3 days apart so that this vulnerability can not be exploited. Approvers have been notified to be aware of proposals entering on this cadence.
CGP # + Onchain ID Alignment
It has continued to be difficult to maintain alignment of the CGP document number and the onchain ID which is based on the order of the proposal. While having them match leads to less confusion for proposal reviewers, changing the CGP to match the onchain ID breaks URL links that have been referenced in existing documents and posts. For the proposals here, the CGP number and onchain IDs will not all match.