The de-risk sequence

1
Detection
Hypernative, Blockaid or your own source reports an exploit, a depeg or a health issue on the strategy or its dependencies.
2
Pause
A pre-signed pause stops the vault, typically within seconds. No funds move.
3
Exit
Your approved signers deallocate the strategy’s position back to idle in the vault, typically within minutes. How much can exit depends on the strategy’s available liquidity.
4
Optional fallback
Funds can be deployed into a pre-approved fallback strategy, such as a wrapped Aave v3 market, so yield continues during the incident, and the vault unpaused.
5
Recovery
Once the strategy is confirmed safe, capital goes back into it. The primary strategy can also be replaced for good.
On-chain controls
These are the same functions every Meta Vault has; see Roles & signing. A fallback strategy can sit in the vault’s list at zero weight, so moving into it needs no change to the list during an incident.
Compared with a single-strategy OAV and a multi-strategy Meta Vault
Integration
A Sentinel Vault integrates like any Meta Vault: through the Earn API as a yield ID, or directly through the standard ERC-4626 functions. Yield.xyz deploys and operates the contract. You request one in the dashboard.Next steps
Security & monitoring
From a risk signal to a pause, an exit and a redeploy.
Meta Vaults
The multi-strategy vault a Sentinel Vault runs on.

