Second V3 Protocol Team

[Schlagonia]

Scope

For reference the first V3 BR: https://github.com/yearn/budget/issues/120

Funding for the continued development, testing and deployment of the Yearn V3 system.

For a more detailed description of the vision and end goal of V3, please review the V3 Pitch.

Initial development of the core vault and strategy contracts as well as initial versions of all periphery contracts has been completed and were deployed by the date specified in the initial budget request of July 1st 2023.

This budget request is focused on the initial launch phase of the V3 system as well the continued development of periphery contracts and other needs to make the full system function properly.

Components:

1. Maintain and update Vault and Strategy core contracts as needed.
2. Maintain and add to periphery contracts and strategy mixes as needed.
3. Develop more complex periphery contracts.
4. Support all Yearn teams to that start building on and with the V3 stack.
5. Build guides and easy templates for 3rd party developers to get up to speed and integrated with the V3 stack.
6. Support new 3rd parties as they begin to integrate with the V3 system.
7. Continue support for new chains (Polygon, ARB, OP, Scroll, Mainnet etc.)
8. Implement governance systems into the V3 stack.

Status based on previous budget request goals.

• The Vault core has completed its first audit and second audit
• The Strategy Core has completed its first audit and second audit.
• Initial periphery contracts including a Router, Registry, Accountant, and Report Triggers have been developed and deployed.
• A ape and foundry strategy mixes are available to strategists to build on.
• Ape tax strategies and Vaults have been deployed and are being tested with the full stack of contracts.
• Prod version of all of these contracts have been deployed.

Plan

• Continue live testing of strategies, vaults and periphery contracts.
• Work with all other Yearn teams to fully develop the system.
• Work with external teams to build on top of the system.
• Apply for further grants in order to bootstrap the ecosystem on new chains.
• Launch on more sidechains/L2's.
• Develop novel periphery contracts and expand on existing versions.

Goals

• Full Launch on at least 2 chains.
• Develop and deploy Junior Tranches.
• Develop and deploy permissionless debt allocator.
• Implement EIP-1271 in Vaults and strategies

Deadline

2023-10-31

People

Core V3 protocol Team

Money

General

Category	Encompasses	Total
Audits	External audit for high risk periphery contracts. (ex: Router, accountant, debt allocator)	$40k DAI
Audits	Third External audit for vault and strategy core contracts.	$65k DAI
Totals	n/a	$105K DAI

Any funds not spent at the end of the period will be transferred back to the yBudget team or considered for the next period.

NOTE: The V3 team still has $25K DAI from the previous request designated for testing that will be rolled over to continue support testing as well as initial bug bounty programs. We expect for most or all of these funds to still be available by the end of this budget request period.

Comp

Base Pay

Base pay includes pay for core contributors and budget for outside contributors.

Monthly: $40k DAI + 1.5 YFI Total: $120k DAI + 4.5 YFI

NOTE: Pay for outside contributors will be given as seen fit by the V3 core team to any non-yearn contributors to the V3 stack and any unused funds will be rolled over to the next budget request or returned.

Rev Share

Revenue for V3 team is classified as all funds earned from the "protocol fees" through both vaults and strategies across all chains V3 has been launched on.

Protocol fees are the gov set amount that is charged across all vaults and strategies based on the amount of fees that are charged by the vaults management.

Because the protocol fee is a new fee that was not applicable in V2 that allows Yearn to serve as the core infrastructure. And can make revenue on vaults and strategies it doesn't run we classify it as a "new revenue stream".

In the current state the expected rev share once protocol fees are turned on is 12.5% based on current revenue share model.

• "Is this a new revenue stream?" - Yes, protocol fees are a new fee type that gives the ability to earn revenue that was not available in V2. +3
• "Is this a new vertical for Yearn?" - No, it is a new revenue stream on a pre-existing product. +2
• "Does Yearn pay contributors?" - Yes. +0
• "Is it profitable all time?" - No +0
• Multiplier of 2.5

Current Total == 12.5%

TVL that is currently already held in a V2 vault and simply migrated to V3 would not classify under the "new revenue stream" classification. In order to not overcompensate for existing TVL, when V3 is launched on mainnet, a custom protocol fee will be set for the new V3 versions of existing V2 vaults. The custom protocol fee will be used to make the effective revenue share equal to not classifying protocol fees as a new revenue source.

EX:

• Default protocol fee = 10%
• V3 revenue share = 12.5%
• non-new revenue stream share = 5%

Yearn deploys and manages the equivalent of yvWETH on mainnet. The yvWETH V3 vault will have a custom protocol fee of 10 * 5 / 12.5 = 4% set.

Amount

One time: $105k DAI, Monthly: $40k DAI & 1.5 YFI

Wallet address

TBD

Reporting

Once

[Schlagonia]

Updated 7/18:

Main changes include:

• 3 month scope with amounts and goals updated accordingly
• Removal of the strategy fee section
• Removal of the performance bonuses

[Schlagonia]

Update 7/28

Included in the Rev share the model to handle the migration of existing vault on mainnet which includes setting a lower custom protocol fee to account for it not classifyng as a new revenue stream