Governance
The settings are controlled by the people who lock the token, and by nobody else.
Votes
- Only locked tokens vote. Unlocked tokens count for nothing, and the dev holds none.
- A lock starts voting when it is 7 days old. Its weight is tokens times 1.0, 1.5 or 2.5 for a 7, 30 or 90-day lock.
- Votes are counted as they stood when a proposal was created, so buying and locking after the fact changes nothing.
- Creating a proposal takes 0.5% of all voting power.
Two kinds of proposal
| Track | Needs | Used for |
|---|---|---|
| Standard | 8% of all votes taking part, and more than half in favour | Moving a setting inside its allowed range, venues, the fee split, pauses, attester penalties, reversing a flag. |
| Supermajority | 15% taking part, and at least 66.7% in favour | Moving a range itself, changing the voting rules, or replacing one of the supporting contracts. |
From vote to effect
- 1 dayNoticeThe proposal is public before voting opens.
- 5 daysVotingLockers vote for or against.
- 48 hoursWaiting roomA passed proposal sits in the timelock. The Guardian can cancel it during its first 180 days.
- ThenTakes effectAnyone can execute it.
Limits on the voters themselves
- A proposal can only call functions on a fixed list. Anything not on the list cannot even be put to a vote.
- Every setting has a hard range written into the code. A vote cannot go outside it.
- Each setting can change at most once every 14 days. Pauses are the exception.
- Changes to rates and caps apply only to new locks.
- A pause can stop new locks or new claims. It can never stop a withdrawal or a payout already under way.