IVaultCore

The vault tracks "idle" assets (held in this contract) vs "allocated" assets (held by registered external strategies managed by the StrategyManager).

Will be 0 when no strategy manager is set. Reverts with VaultCoreStrategyNavUnavailable, like totalAssets(), when the manager's totalAllocated() read fails.

Never blocked by the old manager. Swapping away from a manager that is latched, still reports allocations, or cannot answer either read latches deposits on the vault until the admin calls IVaultCoreRecovery.clearManagerSwapLatch() (#305). The swap skips the latch only when the old manager reports depositsLatched() == false and totalAllocated() == 0. Reaching zero can take more than zero targets and rebalance(): some adapters hold legs a rebalance never recalls (the UniswapV3 adapter's position exits only through its admin's emergencyWithdraw; the Lido adapter's staked and queued legs need requestWithdrawal/claimWithdrawal).

Only callable by the configured strategy manager.

Only callable by the configured strategy manager.

Emitted when the strategy manager address is updated.

Emitted when assets are pushed from the vault to a strategy.

Emitted when a strategy recall is acknowledged (assets return via separate transfer).

Emitted when yield is harvested and totalAssets is updated.

Reverts when a caller other than the configured strategy manager calls a manager-only function.

Reverts when attempting to set an invalid manager address (e.g., address(0)).

Reverts when a share-price-sensitive entry point (deposit/mint/withdraw/redeem) is called while the configured strategy manager is mid-rebalance(). During a rebalance the vault's idle balance and the strategies' reported balances are transiently inconsistent, so totalAssets() (and therefore the share price) cannot be trusted. Blocking these entries defeats read-only reentrancy via a strategy callback.

Reverts from totalAssets() when the configured strategy manager's totalAllocated() read fails (e.g. a registered strategy's totalAssetsManaged() reverts). The vault's NAV is then unknown, so share pricing fails closed: totalAssets(), the converters and the previews revert, the ERC-4626 max* views return 0 and every entry and exit reverts. Recovery: the manager admin force-removes a strategy whose read reverts (see IStrategyManager.removeStrategy); if none can be removed (e.g. a well-formed balance that overflows the sum), the vault admin calls setStrategyManager with a fresh manager. Either way the affected strategies' funds leave the NAV, and returning them later moves their value to whoever holds shares at that moment. Both routes therefore latch deposits closed (VaultCoreDepositsLatched), so no new depositor shares in returned funds; they accrue to whoever still holds shares when they return (a holder who exits while latched is priced on the idle-only NAV). A force removal latches the manager until the manager admin clears it. The setStrategyManager route latches the vault itself (IVaultCoreRecovery): the old manager still reports allocations (here up to type(uint256).max) or cannot answer, so deposits stay closed on the fresh manager until the vault admin calls clearManagerSwapLatch() (#305).

Reverts from deposit/mint while deposits are latched closed. manager names the latch holder, whose clear reopens deposits:

• this vault, while its manager-swap latch is set (IVaultCoreRecovery.managerSwapLatched()): a setStrategyManager swap away from a manager that was latched, still reported allocations, or could not answer. Cleared by the vault admin's clearManagerSwapLatch(); it survives later swaps.
• otherwise the configured strategy manager, while it reports depositsLatched() (IStrategyManagerRecovery), set by a strategy force removal. Cleared by the manager admin's clearDepositLatch(). A swap away from that manager carries this latch over to the vault. maxDeposit/maxMint return 0 while either latch is set; withdrawals and redemptions stay open, capped at idle.