Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Emergency pause

Pausing is the last rung. Lowering caps stops growth without touching positions. Lowering a borrow LTV stops new borrowing without changing the liquidation LTV, so nobody is liquidated by it. All three are ordinary changes in Configuration. A governor contract decides whether your wallet may make them.

Pause

Configuration → Hook configuration → Pause every operation on N vaults. It fills the hook configuration of every loaded vault: the hook target cleared to the zero address (replacing any hook contract) and every operation (deposits, withdrawals, borrows, repayments, liquidations, transfers) disabled. Save the entered changes, then review, simulate and sign them like any other change.

Through a timelock, the pause is scheduled, not immediate. An immediate stop needs an account that can act at once, such as a guardian of a governor suite.

Resume

Resume every operation on N vaults fills the fields to clear the pause only on vaults with every operation paused and no hook contract; save the entered changes to stage it. A partial pause or a hook contract is left alone.

What users see

Operations show as disabled by the vault's curator. Labels do not change. Deprecation is a separate step in Labels and metadata.

See also Pause and upgrade mechanisms for the protocol-level pause.