Documentation

Timelock

The 48-hour delay that protects users from sudden protocol changes.

Every administrative action in Yield Forge goes through a timelock — a mandatory waiting period between proposing a change and executing it.

How It Works

  1. Propose — the admin queues a transaction on-chain (e.g., upgrading a facet)
  2. Wait 48 hours — the transaction sits in a public queue, visible to anyone
  3. Execute — after the delay, the transaction can be applied
  4. Expires — if not executed within the grace period, it automatically expires

Why This Matters

The timelock is your safety net:

  • Transparency — you can see exactly what changes are coming before they happen
  • Exit window — if you disagree with a pending change, you have 48 hours to withdraw your funds
  • No surprises — the admin can't make instant changes, even in their own interest

What Goes Through the Timelock

All administrative actions go through the 48-hour timelock, including facet upgrades, adapter approvals, quote token changes, and fee recipient updates.

Emergency actions (protocol pause and pool bans) skip the timelock by design — you need to be able to stop things quickly when something goes wrong.