Skip to content

Exit Paths

For a depositor the only question that matters in the end is: how do I get my USDC back, and who has to do something for that to happen? This page answers it for each product under four conditions. "Needs" names the party whose transaction is required; "nobody" means the depositor can complete the exit alone.

Status as of 2026-09-27, describing the contracts and strategies currently deployed.

Ethereum Network Lending (KingsVaultV2)

Condition What happens Needs
Normal withdraw / redeem pays from the vault's idle USDC in the same transaction. Nobody (depositor's own transaction).
Idle USDC insufficient The vault calls the Controller's liquidity waterfall; AaveV3Strategy and SteakhouseStrategy withdraw the shortfall from Aave V3 / Morpho Steakhouse in the same transaction. Nobody, provided Aave and Steakhouse have liquidity.
Underlying protocol illiquid or paused The waterfall skips a strategy that reverts and retries the others. If no strategy can serve the request the withdrawal reverts with InsufficientStrategyAssets and no shares are burned; if the strategies respond but return less than the shortage, the withdrawal settles for the amount actually recovered (fundReplenishOnlyForVault returns min(actualWithdraw, shortage)) and the requested shares are burned. Smaller withdrawals within available liquidity are unaffected. Nobody for the retry; a Keeper fundDivest later if liquidity has to be sourced over time.
Operator absent Deposits already in Aave / Steakhouse remain withdrawable through the waterfall without any Keeper action. Idle USDC is not re-deployed. Nobody.
Vault shut down by Guardian Normal deposit and withdrawal stop. emergencyRedeem burns shares for a pro-rata share of the USDC then idle in the vault. Requires the Investor role. Guardian to trigger shutdown; then nobody.

AAVE GHO Saving (KingsVaultV2)

Condition What happens Needs
Normal Pays from idle USDC in the same transaction. Nobody.
Idle USDC insufficient The waterfall calls replenish on every attached strategy pro rata to its assets: the GhoSavingFluidStrategy deployments redeem sGHO to GHO and sell GHO for USDC on the Fluid GHO/USDC pool, with a minimum output of the 1:1 amount minus the slippage bound (currently 1%); the legacy GhoSavingStrategy converts through the Aave GSM. Nobody, provided the Fluid pool fills within the bound (and, for the legacy share, the GSM holds inventory).
A route cannot fill (pool price outside the bound, or GSM inventory empty) That strategy's replenish reverts and the Controller drops it from the attempt, retrying the remaining strategies. The withdrawal reverts whole with InsufficientStrategyAssets only when no strategy can serve it. A Keeper for the part that could not be served: fundDivest once conditions allow, or on the GSM route pre-fill the GSM and fundDivest in one transaction through the GhoGsmLiquidityHelper. The interface states "instant within available liquidity; larger amounts up to 24 hours".
Operator absent Withdrawals succeed only up to idle USDC plus whatever the Fluid pool (within the bound) and the GSM can convert. Beyond that, funds stay in sGHO until a Keeper acts. Keeper.
Vault shut down by Guardian As for Lending: emergencyRedeem against idle USDC, Investor role required. Assets still in sGHO are not included until converted. Guardian; then Keeper for anything not yet idle.

Hyperliquidity Provider (KingsVaultV2Async)

Condition What happens Needs
Normal withdraw / redeem escrows shares and records a redemption request. A Keeper calls executeRedeem() once the vault holds enough idle USDC; the depositor then calls claim(). The interface estimates 96 hours. Keeper to execute the round; depositor to claim.
Idle USDC insufficient The Keeper must first bring USDC back from Hyperliquid: fundDivest → redeem message to the Allocator → router steps out of HLP (subject to HLP's 4-day lock from its last deposit) → CCTP burn and mint → completeDivest. Then executeRedeem(). Keeper, for every step.
Underlying (HLP) locked or illiquid Requests remain pending until HLP releases funds and the Keeper completes the return. Pending requests earn or lose with the vault until executed; the preview is not a locked amount. Keeper.
Operator absent Pending requests stay pending. Cross-chain messages can only be completed through Keeper-gated functions, so funds on Hyperliquid cannot be returned by a third party. Keeper. There is no permissionless fallback in the deployed contracts.
Vault shut down by Guardian shutdown triggers HyperStrategy.exit, which can only initiate the cross-chain return; funds already on Hyperliquid still require the Keeper sequence above before they are idle on Ethereum. emergencyRedeem then pays pro-rata from idle USDC, Investor role required. Guardian; then Keeper.

Summary

Lending GHO Saving HLP
Can a depositor exit with no King's Vault action? Yes, while Aave / Steakhouse are liquid Only within idle USDC + what the Fluid pool fills inside the 1% bound (+ GSM inventory on the legacy share) No
Single point on the exit path External protocol liquidity Fluid GHO/USDC pool liquidity and the GHO price; Keeper for larger amounts Keeper
Lock-up imposed by King's Vault None None None (HLP's own 4-day lock applies)
emergencyRedeem after shutdown Idle USDC, pro-rata, Investor only Same Same

Two points follow from the table and are stated plainly. First, the HLP product's exit depends entirely on the Keeper; the contracts do not provide a route around an absent operator. Second, emergencyRedeem is gated on the Investor role, so an address removed from the allowlist cannot use it.