FAQ

Synchronize and Auto-allocate execute the same permissionless plan: realize supported Liquid Lane issuer payouts, finalize ready 3F requests, collect adapter assets, fill withdrawals, then allocate free assets. Liquid Lane usefulness is measured in the issuer payout token, so a claim can matter even when the vault asset balance and account.totalAssets() stay unchanged.

The simulated zero-asset deposit moves no collateral and mints no shares. It runs only when it has a useful effect. If only prerequisites have an effect, only the prerequisites run; if nothing has an effect, nothing is submitted. Unsaved allocation changes or a blocked execution path also disable the action. No owner or allocation role is required.

Auto-allocation fills adapters sequentially in the configured order. Each adapter is filled to the lower of its relative and absolute caps before the next adapter receives assets. Deposits service pending withdrawals before routing the remaining free assets.

Automatic deallocation uses the separate main adapter order. An instant withdrawal first services the pending queue and stops while queue demand remains; otherwise it uses idle liquidity, then deallocates the remaining shortfall in order.

Withdrawal Queue shows ordered positions and currently withdrawable liquidity; fills may be partial. Fill sends the direct zero-deposit action and does not add Liquid Lane or 3F prerequisites. Synchronize can include those prerequisites and allocate remaining idle assets. Withdrawal Queue does not expose depositor request or claim controls.

No. A cap limits exposure; existing assets must be deallocated separately. Effective capacity is the lower of the absolute cap and the relative cap applied to vault total assets. Removal requires zero adapter assets and also clears route membership, roles, and limits.

Use Deallocate for Morpho and Aave liquidity that can return normally. Use Force deallocate for App and Restaking positions: it returns available liquidity, requests the remainder, and lowers the absolute cap to prevent immediate reallocation. Liquid Lane and 3F use their own on-demand redemption lifecycles.

Synchronize can realize supported Centrifuge and Figure issuer payouts and finalize ready 3F requests before vault synchronization. These prerequisites run through strict Multicall3 calls and only when simulation finds them useful. Liquid Lane and 3F cannot join auto-allocation; unclassified Liquid Lane account families are not synchronized automatically.

Create the adapter, whitelist it for the vault, add it with the required role, then set its caps and, where supported, its auto-allocation position. Creation alone does not add or route it. Whitelisting is self-service on Hoodi and Sepolia. For mainnet, contact Symbiotic.

Management fees accrue annually on current assets and are capped at 5%. Performance fees apply to positive asset growth since the accounting checkpoint and are capped at 20%. Each has a separate role and receiver. Accrual mints vault shares directly to the receivers, so there is no manual claim action. Protocol fees are separate.

Claim a supported reward into the adapter, then use an authorized converter to submit the supported CoW conversion into the vault asset. Claiming and conversion are separate actions, and not every adapter supports them. This flow is separate from the disabled Earnings page.

V2 ownership and action roles are separate. Each write requires its specific Vault or Universal Delegator role; ownership does not grant every action. Granting or revoking a role also requires its role-admin permission.

Use the earliest Emergency stage that addresses the incident and review its preview. Adapter or account pauses, Liquid Lane token stops, migrations, and removals have different permissions and preconditions. Available actions reflect the roles held by your address and each configured executor; one owner role may not cover the sequence. Liquid Lane per-token pauses are one-way.

Network Restake uses a network limit plus operator share weights. Full Restake uses a network limit plus per-operator limits. Operator Specific uses a network limit for the delegator's fixed operator. Operator Network Specific fixes both operator and network and is read-only. V1 does not use V2 adapter onboarding, caps, allocation, or deallocation.

These values bound or distribute active stake, not V2 adapter exposure. Network Restake distributes bounded stake by operator shares; Full Restake also applies each operator limit. Network maximum, active stake, and network/operator opt-ins still constrain the effective amount.

Removal saves the corresponding value as zero. It changes delegation configuration; it does not queue V2-style deallocation or withdrawal.

V1 Fees supports default curator and operator fees plus per-network overrides, not per-adapter overrides. Only the current curator can submit changes. Claiming is not currently available here because Earnings is disabled.

Delegation writes require the setter permission for the active delegator type. Fee writes require the submitting address to be the current curator. Neither owner nor curator identity replaces every permission check.

The delegator hook is V1-only. In Roles, an address with the hook-set role can replace it or clear it to the zero address. Saving the current value is not a valid change.

Resolvers is available only for a V1 veto slasher. Only the resolver recorded at the slash request's capture time may veto, and it must still be configured. The deadline is exclusive; completed or expired requests cannot be vetoed. Slash requests and execution remain middleware actions.