Safety Controls
The V2 contracts have four emergency mechanisms. This page states what each one does to a depositor's position, who can trigger it, and whether it can be undone. The contract-level sequence is on the Emergency workflow page.
Status as of 2026-09-30. Applies to Ethereum Network Lending, AAVE GHO Saving and Hyperliquidity Provider (HLP).
The controls
| Control | Who | What it does | What it means for you | Reversible? |
|---|---|---|---|---|
Pause (pause) |
Guardian | Freezes deposits and withdrawals on one vault. Funds stay exactly where they are — in the vault or in the strategies — and keep earning. | You cannot deposit or withdraw until unpause. Your shares and their value are untouched. | Yes — unpause by the Guardian. |
Exit all strategies (vaultExit) |
Guardian | Recalls every strategy position back to the vault as idle USDC. The vault keeps operating. | Withdrawals become fully liquid from idle USDC; deposits still work. Yield stops until the Keeper re-allocates. | Yes — the Keeper can re-allocate. |
Shutdown (shutdown) |
Guardian | Permanent wind-down: exits all strategies, blocks new deposits and normal withdrawals, and opens emergency redemption. | You call emergencyRedeem to burn all your shares and receive your pro-rata share of the vault's idle USDC. The vault's asset and share token are protected from any privileged sweep for 7 days after shutdown. |
No — one-way. |
Emergency redeem (emergencyRedeem) |
Investor | Available only after shutdown. Burns the caller's shares and pays out pro-rata idle USDC in one transaction. | Your exit path if a vault is ever wound down. No admin action is needed for you to get your funds. | Not applicable — a depositor action. |
| Async vault (HLP) | Guardian / Keeper | Same pause and shutdown controls. Pending redemption batches are settled by the Keeper; claims are blocked while paused. | A pending request is not lost during a pause; it is claimable once the vault resumes. On shutdown, executed requests are claimed first and pending ones return their escrowed shares before the pro-rata payout. | Pause yes; shutdown no. |
What no control can do
None of these functions can move depositor funds to an arbitrary address, change what a share is worth, or add a new destination for capital. Every one of them emits an on-chain event. See What the contracts cannot do.
What they cannot guarantee
- Exit all and shutdown recover what the strategies can return at that moment. A strategy whose underlying protocol is paused, or whose assets are on another chain, may not return funds in the same transaction. For HLP,
HyperStrategy.exitcan only initiate the cross-chain return; funds on Hyperliquid still need the Keeper's return sequence before they are idle on Ethereum. See Exit paths. - Emergency redeem pays from the USDC idle in the vault at the time of the call. Assets not yet returned are not included; handling any later recoveries requires the approved recovery procedure.
emergencyRedeemis gated on the Investor role, so an address removed from the allowlist cannot use it.
When they would be used
| Control | Situation |
|---|---|
| Pause | A suspected issue in King's Vault or in an underlying protocol, pending investigation. |
| Exit all | An underlying venue looks unsafe but the vault itself is fine. |
| Shutdown | A product is being retired. |
How you would know
| Signal | Where |
|---|---|
Paused / Unpaused / VaultShutdown / EmergencyRedeemed events |
The vault contract on Etherscan |
An exit-all: the vaultExit transaction and the USDC transfers from each strategy back to the vault |
The Controller and the vault on Etherscan |
Strategy registry changes (StrategyAdded / StrategyRevoked) and role changes (RoleGranted / RoleRevoked) |
The Controller on Etherscan |
| Portal banner | kingsvault.vip |
| Daily external watch | See Transparency |