IStrategyManager

The StrategyManager maintains a list of registered yield strategies for a single vault, tracks allocation targets (in basis points), and orchestrates rebalancing.

Trust assumption: strategies are trusted to report accurate balances. Reverts if any strategy's read reverts or the sum overflows, which makes a VaultCore vault's totalAssets() revert (fail closed).

Reverts with StrategyManagerStrategyNotEmpty if the strategy already reports a balance, and bubbles the revert if its totalAssetsManaged() read fails.

Reverts with StrategyManagerStrategyStillAllocated while the strategy reports a balance. A strategy whose totalAssetsManaged() read fails is force-removed instead, emitting StrategyForceRemoved; any funds it still holds leave the vault's NAV. The force removal latches the vault's deposits closed (IStrategyManagerRecovery): exits reopen, capped at idle, while deposit/mint stay closed until the admin calls clearDepositLatch, so no new depositor shares in funds the strategy returns in the meantime. Those funds accrue to whoever still holds shares when they return; a holder who exits while latched is priced on the idle-only NAV and gives up their share of the stranded funds. The strategy cannot be re-added while it reports a balance.

Anyone can call; does not move funds. Useful for off-chain indexers.

Pushes or recalls assets to/from strategies, then calls deploy() on each strategy that advertises IProtocolAdapter and holds idle asset. Anyone can call. A recall that loses value beyond a fixed rounding tolerance reverts with StrategyManagerWithdrawShortfall; an honest partial recall emits StrategyPartiallyRecalled; a failing deploy emits StrategyDeployFailed. Allocations are capped at the vault's actual idle balance.

Emitted when the associated vault address is set.

Emitted when a new strategy is registered with a target allocation.

Emitted when a strategy is removed from the registry.

Emitted (before StrategyRemoved) when removeStrategy drops a strategy whose totalAssetsManaged() read fails. Any funds it still holds leave the vault's NAV; if they are later returned to the vault, they accrue to whoever holds shares then. The removal also latches the vault's deposits closed (IStrategyManagerRecovery.DepositLatchSet follows this event) until the admin calls clearDepositLatch, so no one can enter at the lower NAV and capture those funds.

Emitted when a strategy's target allocation (in bps) is updated.

Emitted after a harvest sweep of all strategies.

Emitted after a rebalance operation completes.

Emitted when rebalance() recalls less than it requested from a strategy that still reports the undelivered part (an honest partial recall, e.g. a Lido buffer that is short, or an Aave or Compound market whose cash is borrowed out). The strategy stays over its target until a later rebalance recalls the rest.

Emitted when rebalance() calls a protocol adapter's deploy() to put its idle to work and the call reverts (e.g. the adapter or its protocol is paused). The idle stays in the adapter, still counted in its NAV, and the rebalance completes.

Reverts when the vault has not been set and a vault-dependent operation is called.

Reverts when an invalid strategy address is provided (e.g., address(0)).

Reverts when attempting to add a strategy that is already registered.

Reverts when a strategy address is not found in the registry.

Reverts when adding/updating a strategy would push total allocation above 10 000 bps.

Reverts when a strategy's underlying asset does not match the vault's asset.

Reverts when a rebalance recall loses value: the strategy's reported balance drops by more than the vault actually received, beyond a fixed rounding tolerance (slippage, an exit fee, or a strategy that writes off more than it pays). An honest partial recall does not revert.

Reverts when attempting to remove a strategy that still holds vault assets. Recall assets first via rebalance() (set the target to 0, then rebalance). Only a strategy whose balance read fails is removed without this check (see StrategyForceRemoved).

Reverts when adding a strategy that already reports a balance. A new strategy must start empty so that adding it cannot step the vault's NAV up, e.g. re-adding a force-removed strategy that still holds the stranded funds, which would hand them to whoever deposited after the removal.

Reverts when adding a strategy would exceed the MAX_STRATEGIES cap.