Skip to main content
A Meta Vault’s strategy set is not fixed at deployment: strategies can be introduced, removed, or replaced as the opportunity set changes. Composition changes (which strategies are whitelisted) and capital movement (where deployed funds actually sit) are separate on-chain actions, gated by separate roles, so a strategy change is reviewable in two clearly distinct steps instead of one opaque transaction. Steps below name the role whose purpose covers each action (see Roles and signing models); yield.xyz performs them.

​
Add a strategy

1

Whitelist the strategy

The strategist adds the strategy to the vault’s set.
2

Assign a target weight

The rebalancer sets its target weight, adjusting other weights and the idle target as needed.
3

Fund it

A rebalance deploys capital into the new strategy to reach its target weight.
A strategy can be whitelisted with a zero weight; that is expected during rollout, before capital is committed to it.

​
Remove a strategy

1

Exit funds

The rebalancer pulls capital from the strategy back to idle.
2

Remove it from the set

The strategist removes the strategy from the whitelist.
3

Redeploy

Remaining weights are updated and a rebalance realigns the rest of the portfolio.
Exit a strategy’s funds before removing it from the whitelist. Leaving a meaningful balance behind a removed strategy risks stranding it outside the vault’s normal accounting.

​
Replace a strategy

Replacement combines the two flows: exit the old strategy’s funds, update the whitelist to drop the old strategy and add the new one, set weights that include the replacement, then rebalance to deploy into it. Each step is a separate, role-gated transaction, so a signer reviewing the change sees exactly what moved and when, and the sequence lines up with the audit trail any automated rebalance run also produces.

​
Next steps

Allocation and rebalancing

The weight and rebalance primitives these flows compose.

Roles and signing models

How strategist and rebalancer actions get signed.