Skip to content

Revoke Strategy

This V2 flow invokes a strategy's exit path and removes it from the Controller registry. It is not a temporary pause, and it does not guarantee that every strategy returns all capital in the same transaction.

  1. The Developer calls Controller.strategyRevoke(vault, strategy, force).
  2. The Controller calls strategy.exit(force).
  3. The Strategy is removed from the registry by swapping it with the last element and popping the array.
  4. The Controller decreases the active book value by the total withdrawn amount.

Cross-chain Limitation

For HyperStrategy, exit(force) only transfers local source-chain assets; it does not unwind remote HyperEVM or HLP positions. Removing a strategy from the registry must not be treated as confirmation of remote recovery.

The handling of remote positions, in-flight transfers, late recoveries, and the associated accounting during revocation requires an engineering-approved procedure. This page does not specify a safe operational ordering for revoking an HLP strategy with outstanding exposure. See cross-chain divestment and emergency limitations.

This Controller-based operation does not describe the separate per-user V3 GHO Staking product.