4 Dec 2020 — Yearn V2 website call 2

--- tags: brand --- # 4 Dec 2020 — Yearn V2 website call 2 x48, Eric Juta, Klim, WrongNebula What was discussed: **A. Swap into vaults** Exploring way for users to swap into vaults. We initially wanted to call it "Zap" but "x48: most new users dont know what is zap", abstract away concept of "zap", would prefer just "deposit" Mockup of that UI is in the Figma file Button will remain "Deposit" but user will be presented with ways to either deposit correct asset, or to swap existing assets (limitations applies) Options: 1. use Curve swap (allow only BUSD, DAI, USDC, USDT, TUSD, Compound.curve.fi, usdt.curve.fi, y.curve.fi, busd.curve.fi) 2. Use Zapper.fi contracts 3. Use Banteg versions of Zapper.fi contracts (best) Note: need to show disclaimer, preview of slippage, slippage tolerance settings (in the global user settings UI panel) *MVP will NOT have swap, only deposits!* **B. Cover** Cover (=yCover) will be located under main nav, Products. UI will be minimal, inspired by https://yinsure.finance Anton is working on a UI? Beside the standalone UI under main nav, Products, Cover will also be accessible directly from two other places in the website: 1. From the yVaults, there will be indicators if for example the user has 5000 USDT deposited in USDT vault but no cover for it. CTA that will direct to the yCover standalone page, field pre-filled for 5000 USDT. 2. From the Stats dashboard, there is an overview of the user yVaults positions, there we'll have a visual indicator of which ones are covered, maybe this can also be a link to the yCover standalone page. 3. Could be possible to use the Verbose splash page, if a user has a large un-Covered position, put a disclaimer there (that you can close), could be text, could be a block etc... Important, we decided that we don't incentive users to buy a new COVER every single time they make a deposit in a vault. We only incentive them AFTER they have positions in vaults. **C. Standalone yVaults pages** *MVP will NOT have standalone yVaults pages, only full v2 will have!* List of yVaults (Accordion view, like currently on v1 and v2) Pros: same way to display information than on v1, users are not lost, good if > 30 different vaults, alread implemented by x48 Cons: performance issues with many vaults, no way to link directly to a vault (no specific URL for each vault) Standalone yVaults pages (like on https://delphi.akropolis.io/vault) Pros: better performance, more space to display informations/stats/transactions history, better for SEO (each vault being a page, with proper hierarchy H1 H2, keywords, text content etc..), more space to do things like swapping into vaults, swapping between vaults etc.. Cons: more clicks, require new design --- Priorities for x48 - Governance Staking UI - Nav - Splash overview - yCover UI Priorities for Eric: - Components - Nav - Governance Staking UI cards - Info cards - Search - User settings panel - etc.. - Tailwind css - SEO? Priorities for Nebula: - Splash page + Overview finalized in Figma - yCover standalone UI in Figma - User settings panel in Figma (the panel that include dark/light mode switch, language switch, slippage etc...) - Final footer in Figma - Finish mockups for all specific vaults like veCRV Backscratcher, zLOT vault, Hegic El Calfos vault etc... in Figma