Overview

This is a collection of resources that aim to be an introduction to how yVaults V3 works.

Introduction

The architecture of V3 is an improved version of V2, with increased customization and features. For a complete intro guide of V2 see here.

Yearns V3 system is designed to be an un-opinionated and customizable infrastructure for anyone to easily build on, making generating yield safely and efficiently as easy as possible for all parties involved.

V3 is built in the hopes of opening up the gates to allow anyone and everyone who wants to build a strategy or manage vaults to be easily able to do so. It allows for a more decentralized suite of yield-generating products that fit any needs.

So whether you are a full-blown gas golfing expert, a degen looking to codify your personal yield farming, or just an average crypto user looking to earn passive yield on your magical internet tokens, V3 is for you.

Definitions

• Vault: A vault or "Allocator Vault" in V3 refers to an ERC-4626 compliant contract that takes in user deposits, mints shares corresponding to the user's share of the underlying assets held in that vault, and then allocates the underlying asset to a range of different "strategies" that earn yield on that asset.
• Strategy: A strategy in V3 refers to a yield-generating contract added to a vault that has the needed ERC-4626 interface. The strategy takes the underlying asset and deploys it to a single source, generating yield on that asset.
• TokenizedStrategy A technical implementation of a Strategy that is also a stand-alone ERC4626 compliant Vault. These are the yield generators in the V3 ecosystem. This pattern can be used so that either Allocator Vaults or individual users can deposit directly into and receive shares in return.
• Vault Factory: A factory contract deployed by Yearn Governance that all Allocator Vaults of a specific version can be easily and trustlessly deployed from.

Get started

• Building your own V3 Strategy
• Deploying and managing a V3 Vault
• Protocol Fees

Contract Addresses

*Deployments are done using create2 factories and should be stable across all EVM chains the protocol has been deployed on.

Core

VERSION 3.0.1:

• Vault BluePrint: 0xDE992C652b266AE649FEC8048aFC35954Bee6145

• VaultFactory: 0xE9E8C89c8Fc7E8b8F23425688eb68987231178e5

• TokenizedStrategy: 0xDFC8cD9F2f2d306b7C0d109F005DF661E14f4ff2

• Periphery Address Provider: 0xB1662c1E500610F5D14B8041FD5306bbD3D8EdEe

If a contract has not been deployed on a specific chain it can be done permissionlessly using the scripts in the relevant GitHub repo. Or reach out to a Yearn contributor for help.