Timelock on mainnet
Most protocol changes go through a ~48 hour timelock on mainnet before they take effect. Proposers schedule a change, the delay passes, then an executor applies it. This gives the community time to review updates to risk settings, oracle wiring, new markets, or contract upgrades before they hit production. Testnet uses a much shorter delay for development only.What requires governance
Typical timelocked changes include:| Area | Examples |
|---|---|
| Markets | Listing new assets, editing LTV and liquidation settings |
| Oracles | Price feed configuration and tolerance bands |
| Infrastructure | Pool deployment, controller upgrades, aggregator wiring |
| Migration | Approving which Blend pools users can migrate from |

