Skip to main content
OAV contracts are deployed behind upgradeable proxies. Moving an existing OAV from its v1 or v2 implementation to the current OAV v3 implementation is a proxy upgrade yield.xyz performs: the vault’s address, its share token, and user balances are unchanged. Users do not withdraw and redeposit, and you do not need to redeploy or re-point your integration.

What changed since v1

v1 vaults have no reward-claiming mechanism: incentive tokens paid by the underlying strategy accumulate unclaimed unless the vault is upgraded. See OAV v3 for the current fee and reward-handling model, and automatic off-ramping for how reward claiming works once available.

What stays the same for your integration

The ERC-4626 interface (deposit, withdraw, mint, redeem) and the Yield API surface do not change with a vault’s implementation version. If you integrate through the Yield API: An upgrade to a newer implementation changes what the vault can do (for example, whether it can claim reward tokens) but not how you call it.

Requesting an upgrade

Contact yield.xyz to upgrade an existing v1 or v2 vault to the current implementation. Because fee accounting depends on the vault’s recorded asset value at the time of upgrade, yield.xyz performs a one-time reconciliation as part of the upgrade so the next fee calculation does not compute a false gain or loss from the change.

Next steps

OAV v3

Vault mechanics, fees, and reward handling on the current implementation.

Off-the-shelf OAVs

Pre-deployed OAVs already running the current implementation.