Timelock

The definition above treats the delay as protection for users. The mechanism is a contract that sits between governance and the protocol it controls. An approved action is queued with an earliest execution time, published on chain, and can only be executed once that time has passed. Because the queued call is public, anyone can read exactly what will change before it does.

That protection depends on what the timelock actually covers. Many protocols route parameter changes through it while keeping a separate guardian role or admin key that can pause contracts or act immediately. A timelock in front of an upgradeable contract only matters if the timelock itself holds the upgrade authority, rather than a multisig sitting beside it.

A notice period before a change in terms is the TradFi equivalent, and it holds on purpose: counterparties get time to leave. It breaks on who can use that time. Exit requires watching the queue, decoding the call and withdrawing before execution, and a delay shorter than the protocol's own withdrawal process protects nobody.

The practical decision is to compare the length of the delay with the time it takes to exit a position, and to confirm that no privileged role can bypass the queue.