Why a DAO Treasury Transaction Was Reverted by the Timelock
A DAO treasury transaction can be reverted by the timelock if the timelock contract’s own governance logic - or a guardian or multisig with override authority - cancels the queued transaction before the execution delay expires. The timelock does not revert transactions on its own; a reversion means something or someone with the power to intervene used that power.
How the Timelock Normally Processes a Treasury Transaction
In most DAO frameworks, a treasury transaction follows a standard pipeline:
- Proposal passes on-chain - The vote meets quorum and approval thresholds.
- Transaction is queued - The passed proposal’s calldata (the specific function call, recipient, and amount) is submitted to the timelock contract. The timelock records it and starts a mandatory delay timer.
- Delay elapses - After the configured delay (commonly 24 to 48 hours), the transaction becomes eligible for execution.
- Execution - Anyone can call the timelock’s
executefunction to send the transaction.
If step 4 fails - the transaction reverts - the problem is not the timelock itself. The timelock either refused to execute because of a cancellation, or the target contract rejected the call.
Common reasons a timelock transaction reverts
1. The Timelock Was Bypassed or Cancelled by a Guardian
Many DAOs grant a guardian role (a multisig, a veto contract, or a single admin address) the authority to cancel queued transactions. If the guardian called the timelock’s cancel function before execution, the transaction is removed from the queue. Any subsequent attempt to execute it will revert because the timelock no longer recognizes that transaction ID.
This is not a bug - it is a deliberate safety mechanism. The guardian may have detected a malicious proposal, a technical error, or a governance attack (such as a minority quorum capture) and acted before the delay expired.
2. The Target Contract Reverted the Call
Even if the timelock approves the execution, the destination contract (e.g., a token swap, a transfer to a multisig, or a lending protocol interaction) might reject it. Common reasons:
- Insufficient balance - The treasury didn’t have enough tokens to send.
- Revert due to slippage - If the transaction was a swap on a DEX, the price moved beyond the allowed slippage tolerance.
- Blocked recipient - The recipient address was blacklisted by a token contract (e.g., USDC or USDT).
- Out-of-gas - The execution call ran out of gas, though modern timelocks handle gas limits explicitly.
When the target contract reverts, the timelock itself does not revert - the internal call fails, and the timelock propagates that revert to the caller. The transaction remains queued. The DAO can retry if the underlying issue is fixed (e.g., by funding the treasury or adjusting the swap parameters).
3. The Timelock Delay Was Changed or Expired
Some timelocks allow the delay to be updated via governance. If the delay was extended after the transaction was queued, the transaction might no longer be eligible for execution until the new, longer delay passes. Attempting to execute early causes a revert.
Alternatively, some timelocks have an expiration period. If no one executes the transaction within a set window after the delay, the transaction expires and becomes unexecutable. Trying to execute an expired transaction reverts.
4. The Proposal Was Overridden by a Later Governance Action
A DAO can pass a new proposal that explicitly cancels or replaces a previously queued transaction. For example, if the timelock supports a cancel function callable by the DAO itself (not just a guardian), a subsequent vote can revoke the earlier one. The original transaction will revert if anyone tries to execute it.
How to Diagnose a Reverted Timelock Transaction
If you see a revert on a treasury transaction, check these on-chain details:
- Etherscan or block explorer - Look at the transaction that attempted execution. The revert reason is often included in the
revertfield. Common strings:"Timelock: transaction not queued","Timelock: transaction not ready", or the target contract’s own error message. - Timelock contract events - Most timelocks emit
CallQueued,CallExecuted, andCancelledevents. Search for aCancelledevent with the same transaction ID. - Guardian activity - If the DAO has a guardian multisig, check whether that multisig submitted a
cancelcall around the time of the revert. - Target contract state - Verify the target contract’s balance, allowances, and any blacklist status.
What Happens Next
- If a guardian cancelled the transaction - The treasury does not move. The DAO can propose a new transaction, possibly with corrections or a different recipient.
- If the target contract reverted - The transaction remains queued. The DAO needs to fix the underlying issue (e.g., add funds, adjust parameters) and then call
executeagain. Some timelocks allow the proposer to cancel and re-queue. - If the delay changed - Wait for the new delay to expire, or cancel and propose with updated timing.
Reverts are not necessarily failures. They are the system’s way of stopping an action that would have been invalid or harmful. The timelock’s design - delayed execution with cancellation capability - exists precisely to give the DAO time to catch problems before funds move.
Not financial advice. teslaai2023.site publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.