Skip to content

Strategy Divest

This operation requests assets from a registered strategy. Whether the assets return in the same transaction depends on the strategy.

Synchronous Strategies

For strategies supporting synchronous divestment, subject to external liquidity and execution restrictions:

  1. The Keeper calls Controller.fundDivest(vault, strategy, amount).
  2. The Strategy withdraws from the external protocol back to the vault receiver.
  3. The Strategy returns the actual withdrawn amount.
  4. The Controller decreases the active book value by the actual amount withdrawn.

For GHO Saving, any required sGHO-to-GHO-to-USDC conversion affects the net recoverable amount. Aave/GSM route costs are separate from the current 0% King's Vault Performance Fee. See GHO Saving withdrawals.

HyperStrategy: Asynchronous Return

HyperStrategy.divest(amount) sends a remote redemption request and returns 0 in the initiating transaction. This is not confirmation that USDC has arrived in the Ethereum vault.

Remote collection, CCTP processing, and completeDivest(message, attestation) are separate stages. The source-chain asset return and accepted remote state must be confirmed; the synchronous four-step sequence above must not be used as a complete HLP procedure. See the cross-chain flow.

The initial fundDivest transaction alone does not establish a completed book-value adjustment or a claimable user redemption. User claims depend on the Ethereum vault's redemption execution round.