6. Proposal Queuing & Execution
After a DIP has passed, any address can call the queue method to move the proposal into the timelock queue. A DIP can only be queued if it has passed.
Parameter | Description | Short Timelock Executor | Merkle-Pauser Executor | Long Timelock Executor | Starkware Executor |
---|---|---|---|---|---|
Timelock Delay | After a proposal passes and is queued, delay before the proposal is executed | 2 days | 0 days | 7 days | 2-9 days |
Execution Grace Period | The time after which a proposal becomes executable, during which it must be executed. | 7 days | 7 days | 7 days | 7 days |
Minimum Timelock Delay | Minimum delay before a proposal is executed (after queuing) | 1 day | 0 days | 5 days | 4 days |
Maximum Timelock Delay | Maximum delay before a proposal is executed (after queuing) | 7 days | 1 day | 21 days | 21 days |
As soon as the voting period ends and a proposal has succeeded, anyone can call queue to begin the timelock delay.
For the Starkware priority timelock executor, it has a priority period of 7 days out of the 9 day timelock delay. This means that after 9 days anyone can execute a proposal, but within days 2-9 (the priority period) Starkware has the option to execute the proposal.
In practical terms it's:
Days 0–2: No one can execute
Days 2–9: Only Starkware can execute
Days 9: Anyone can execute
Last updated