# InvestDEFY Yearn v3 Vault *draft 0.2 — 12 June 2023* ## Summary InvestDEFY will develop and deploy their [STACC yield generation program](https://www.investdefy.com/stacc) as a strategy built on Yearn's pending v3 vaults protocol. ## Resources - Presentation on v3 strategy writing from Strategist standup https://docs.google.com/presentation/d/1ZLeDC-jn4utGh_gnQiv8Kvk3uz8nwRl1K3AxPwcgENE/edit?usp=sharing - Vault Core: https://github.com/yearn/yearn-vaults-v3 - Tokenized Strategy Core: https://github.com/yearn/tokenized-strategy - Yearn 4626 Router: https://github.com/Schlagonia/Yearn-ERC4626-Router - Ape Strategy Mix: https://github.com/Schlagonia/tokenized-strategy-ape-mix - Foundry Strategy Mix: https://github.com/Schlagonia/tokenized-strategy-foundry-mix - strategy Periphery: https://github.com/Schlagonia/tokenized-strategy-periphery ## Vault Design To be discussed on our call, after further review we now believe a more simplified approach will be best that builds as much as possible on the standard implementation. All thoughts here are tentative and will evolve through implementation and discussion. ### Implementation Overview In the v3 vaults platform it's possible to deploy direct-deposit strategies that can run independently of a vault, but as management fees are handled at the vault level, it makes more sense to deploy two vaults: one for ETH and one for BTC. Each vault would run a single, exclusive strategy. Additional strategies can be added later to handle TVL that may exceed a single strategies capacity. The strategies would essentially operate in the same way as STACC or STACC-prime do now, except via smart contract and decentralized options protocols such as Lyra. One gnosis multisig safe with multiple public and trusted signers should administer most permissions on the vault and strategy. Additional permissioned roles can be created as needed, for instance trusted entities executing weekly reports and/or trades. The v3 platform doens't have an opinion on how to set parameters, timing, or permissions for a trade so it can be custom tailored to strategists needs. Two common patterns Yearn has used for trade logic are: 1) to do it atomically in the same txn as the report (harvest), or 2) asychronously via a trade handler contract which has been given token approvals by the strategy.