Timelocks and execution state
Timelocks add a delay between proposal approval and execution. They give operators time to notice and respond to risky approved actions.
Why use a timelock
- Treasury transfers above an internal threshold.
- Program upgrades.
- Member removals.
- Emergency authority rotations.
- Any action where delayed execution improves review.
State meanings
| State | Meaning |
|---|---|
| Active | Voting or execution is still pending. |
| Approved | Threshold rules are satisfied. |
| Waiting | Approved, but timelock has not elapsed. |
| Executed | The governed action has run. |
| Rejected | Rejection policy made the proposal fail. |
| Cancelled | An authorized cancellation stopped the proposal. |
Operational guidance
Use timelocks for actions whose blast radius is larger than the cost of waiting. For small routine actions, a timelock may add unnecessary friction.
Timelock is not review by itself
A timelock creates time for review. Your team still needs a process for alerts, escalation, and cancellation.