The timelock is designed to enforce a minimum delay between governance proposal approval and execution, ensuring users have time to react to critical changes.
The system allows multiple governance actions to be executed atomically within a single transaction, enabling a sequence where the timelock is modified (or weakened) and immediately relied upon within the same execution context, effectively bypassing its protective delay.
Likelihood:
Occurs during standard multisig governance workflows that batch or chain executions
Common when governance tooling executes multiple queued transactions sequentially
Impact:
Timelock delay guarantees are bypassed without violating explicit access control
Enables immediate execution of sensitive governance actions (upgrades, signer changes, fund transfers)
The timelock enforces delay between scheduling and execution, but not between state transitions inside the same transaction. Once the delay is reduced mid-execution, subsequent actions inherit the weakened state.
Enforce transaction-scoped timelock invariants so that timelock configuration changes only take effect in a future block or epoch.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.
The contest is complete and the rewards are being distributed.