Timelock Transaction Builder

Generate queue and execute data for timelock-controlled governance transactions

Target Contract Address

Address of the contract to call

Function Signature

Function signature without 'function' keyword

Parameters (comma-separated)

Function parameters separated by commas

Value (ETH)

Amount of ETH to send with transaction (usually 0)

Delay (Days)

Delay (Hours)

Minimum delay before transaction can be executed (typically 2-7 days)

1. What is a Timelock?

A Timelock contract is a governance mechanism that enforces a delay between proposing and executing transactions. This gives the community time to review and potentially veto malicious actions.

2. How does it work?

Timelock Workflow

Queue: Propose a transaction with future execution time (ETA)
Delay: Wait for minimum delay period (typically 2-7 days)
Execute: Execute the transaction after ETA within grace period
Cancel: Can be cancelled before execution by admin

Security Benefits

Timelocks provide transparency and security for DeFi protocols. Users can monitor queued transactions and exit positions if they disagree with proposed changes before they take effect.

3. Examples

Aave Parameter Update

Target: 0x464C71f6c2F760DdA6093dCB91C24c39e5d6e18c
(Aave Governance)
Function: propose(...)
Delay: 1 day (after voting)

Compound Interest Rate Change

Target: 0x6d903f6003cca6255d85a0ab1e340961c0632049
(Compound Governor Bravo)
Function: executeTransaction(...)
Delay: 2 days

OpenZeppelin Timelock Usage

Target: 0xe8FdA5c7d3bBf167dB058e91C147e9e76e7F49d0
(Timelock Controller)
Function: execute(target, value, data, salt)
Delay: 3 days minimum