Timelock Queue Executor

WHAT IT DOES

This tool queues, executes, and cancels operations in a timelock controller contract. It reads and displays the timelock queue status (idle, active, or paused), queued operations, operation delay (waiting period), operation execution time (when the operation becomes executable), operation status (pending, ready, executed, or cancelled), account balance, chain ID, and execution history. Beyond read-only access, the tool lets you execute the five key actions: queue an operation in the timelock, execute a ready operation after the delay has passed, batch execute multiple queued operations in one transaction, cancel a queued operation, and claim execution confirmation.

HOW TO USE

Connect your wallet and select the network. Enter the timelock contract address, operation ID, target contract address, calldata (hex), and optional value (ETH). Click "Load State" to fetch the queue status, operation status, delay, execution time, and queued operations list. Review the operation status and queue status. Enter the target and calldata, then click "Queue Operation" to add the operation to the timelock. After the delay has passed, click "Execute" to execute the operation. To execute multiple operations at once, click "Batch Execute." Click "Cancel" to cancel a queued operation, or "Claim" to confirm execution. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM

The tool interacts with a timelock controller contract that manages time-delayed operations. The queue() function adds an operation to the queue with the current timestamp plus the delay. The execute() function executes a queued operation after its execution time has passed. The operationStatus() function returns the current state (0 = pending, 1 = ready, 2 = executed, 3 = cancelled). Batch execution uses executeBatch() with an array of operation IDs. The tool fetches queued operations via queuedOperationAt() and execution history via executionHistory().

WHAT IT CANNOT SEE

Cannot verify that the queued operation is correct or that the execution is appropriate. Relies entirely on the timelock contract's verification and the destination chain's final state. Cannot detect if the calldata is malicious, if the delay is too long, or if the execution will fail due to state changes.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The timelock contract must implement queue(), execute(), executeBatch(), cancel(), queueStatus(), operationStatus(), operationDelay(), executionTime(), queuedOperationAt(), and executionHistory(). The tool is read-write: it signs transactions for queuing, execution, batch execution, cancellation, and claiming. Always verify the contract address and operation details before submitting.