Why a proposal is a state transition, not a headline
Who Gets to Change the Protocol?
Turn community governance into a replayable state machine: who proposes a change, who can vote, when it can execute, and how an emergency cancel protects the treasury.
Follow one proposal through snapshots, quorum, delegation, a timelock, a treasury ledger, and an emergency cancel path.
- PProposer: turns an intention into an exact action
- VVoters: bring snapshot power and participation
- TTimelock: exposes the operation before execution
- GGuardian: can stop an unsafe transfer before it runs
One question per lesson
The lessons are ordered so that each one uses concepts introduced earlier.
- 01PROPOSAL · TARGET · ACTION12 MIN
A Proposal Is a Pending State Change
KEY QUESTIONA proposal gets 99% YES. Why might the protocol remain unchanged?
Turn “change the fee” into a target, action, parameter, and pre-execution state so everyone votes on the same operation.
→ - 02SNAPSHOT · DELEGATION · QUORUM14 MIN
How Much Does One Vote Count?
KEY QUESTIONCan borrowed tokens seize a vote after it starts?
Delegate Alice’s power to Bob, freeze the snapshot, and compare participation with quorum and support.
→ - 03QUEUE · TIMELOCK · EXECUTION13 MIN
Why Can’t a Passed Vote Execute Immediately?
KEY QUESTIONDoes a two-day timelock guarantee a malicious proposal cannot hurt the protocol?
Queue a passed proposal behind a timelock, wait until it becomes ready, and replay every event before execution.
→ - 04TREASURY · GUARDIAN · RISK13 MIN
A Treasury Is Not an ATM
KEY QUESTIONAn emergency multisig can save a protocol. Why is it also a risk?
Execute a grant, switch to low quorum, and cancel an unsafe operation to compare capital efficiency with attack surface.
→
Questions covered in this course
How delegation and snapshots prevent the same power being counted twice
Why quorum, majority, and timelock are separate boundaries
How treasury conservation and emergency cancellation change risk