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

Act as a Sentinel in the Curator App

A Sentinel is a risk-mitigation role for Morpho Vault V2. It can react quickly to reduce vault risk, but it cannot introduce new risk. The role can revoke pending timelocked actions, decrease caps, and deallocate assets back to the vault's idle balance.

Use the Curator app to perform these actions from a dedicated Sentinel tab on each Morpho Vault V2 page.

Before You Start

  • Open the Curator app and select the Vault V2 you want to monitor.
  • Connect the wallet that has the Sentinel role for that vault.
  • If your Sentinel is a Safe, MPC wallet, or another smart account, make sure the transaction is sent from that exact Sentinel address.

What a Sentinel Can Do

ActionEffectTimelocked?
Revoke a pending actionCancels a submitted timelocked action before it is executedNo
Decrease an absolute capReduces the maximum assets that can be allocated to a risk id (Market, Collateral asset, Adapter)No
Decrease a relative capReduces the maximum % of vault assets that can be allocated to a risk id (Market, Collateral asset, Adapter)No
DeallocateMoves assets from an adapter back to the vault's idle balanceNo

A Sentinel cannot add adapters, increase caps, allocate assets into adapters, change roles, change fees, change gates, change timelocks, or transfer ownership.

Emmergency Sentinel Flows

The emergency flows below can be triggered by the Sentinel role on the Curator App Emergency tab.

  • Close Deposits: Block new deposits by disabling the active liquidity adapter - either zeroing its caps or redirecting it to an idle market.
  • Safe Market Removal: revoke pending cap increases for a market, zero its caps, and safely deallocate any withdrawable funds.
  • Sentinel Lockdown: Execute a full lockdown of the vault, activating all sentinel capabilities.
Emergency flows for the Sentinel

Common Sentinel Flows

The Sentinel common flows are available on the Sentinel tab of your vault.

Revoke a Pending Action

Use this when a pending Curator action should not be allowed to execute, for example an unsafe cap increase, adapter addition, fee change, gate change, allocator change, or timelock change.

  1. In the Sentinel tab, review pending actions for the vault.
  2. Check the target function, parameters, and executable time.
Select pending changes and revoke it as Sentinel
  1. Click on Batch Action and select the action(s) to revoke. You can select several pending changes to revoke it at once.
  2. Sign the revoke transaction.

After the transaction confirms, verify that the pending action no longer appears in the app and that the corresponding revoke(bytes) transaction is visible onchain.

The Sentinel can also see all pending changes and revoke it, on any tab, via the tooltip at the bottom right of the app.

Select pending changes and revoke it as Sentinel

Reduce Exposure to an Unsafe Market or Collateral

Use this when a market or all markets sharing a collateral type are considered too risky, but the adapter is still functioning.

  1. Identify the risk level
  2. Prefer the narrowest safe scope: a market-level for one market, a collateral-level for all markets sharing one collateral (or adapter-level only when the whole adapter should stop receiving liquidity).
  3. Set the relevant absolute and relative caps to 0.
Reduce exposure
  1. Deallocate available assets from the affected market or adapter back to idle by clicking on the "Zero" button and "Save".
Deallocate from a market
Deallocate from a market
  1. If the market is illiquid, repeat the deallocation as liquidity becomes available.

Freeze Risk While a Curator or Owner Issue Is Investigated

Use this when the Sentinel needs to create time for depositors, the Owner, or a replacement Curator to react.

  1. Revoke every suspicious pending action.
  2. Decrease the affected caps to 0. If the risk is broad or unclear, consider setting all relevant caps to 0 until the situation is assessed.
  3. Deallocate assets to idle where possible.
  4. Coordinate with the Owner to replace a compromised Curator or Sentinel if needed.
  5. Coordinate with the Curator for any follow-up cleanup that requires timelocked actions, such as removing an adapter or re-establishing caps.

After Each Sentinel Action

  • Verify the transaction status in the app and on a block explorer.
  • Confirm the vault state changed as expected: pending action removed, cap reduced, or allocation moved to idle.
  • Communicate the action to the Curator and Owner so they can perform any follow-up role, cap, adapter, or liquidity changes.
  • Continue monitoring until the risk is resolved or the vault is fully unwound.

Related Docs