"./yieldGhoVault"
{"title": "\"./yieldGhoVault\"", "logoImg": "bafkreihn2t3thaw3xw3ew7jxojkkwrisuuudvwrcqjnsce5tbg3olkkuti", "website": "https://github.com/Kanoopz/lfghoHackathon", "bannerImg": "bafkreihfzycawlmeu74shagvdqq3twqmwwafbninuy6munbvkfjc6e44ta", "createdAt": 1714077470672, "userGithub": "Kanoopz", "credentials": {}, "description": "\nThe \"./yieldGhoVault\" project aims to revolutionize the concept of stablecoin yield generation, addressing the current limitations of projects like USDC and USDT. While these stablecoins generate significant revenue from fiat collateral through treasury bond investments, they typically do not distribute these profits to their web3 users.\n\nOur platform offers a solution by providing three distinct avenues for yield generation, all stemming from the collateral used to issue the GHO stablecoin, with a 1 GHO: 1.5 USD value ratio. Firstly, users benefit from yield by supplying collateral to the Aave protocol, ensuring returns simply by holding the GHO stablecoin. Secondly, users can leverage their borrowing power through off-chain legal agreements, earning fees for lending.\n\nLastly, users have the option to leave their GHO stablecoin in the vault, where they can earn additional fees for providing liquidity for flash loans. Alternatively, they can utilize their holdings across various protocols, not limited to a single chain, thanks to Chainlink's Cross-Chain Interoperability Protocol (CCIP). This flexibility opens up a multitude of possibilities within the decentralized finance ecosystem.\n\n\n**The general flow and arquitecture is as follows:**\n\n- emailBased abstractedAccounts are used to onboard web2 traditional investors so they dont have to go through the hassle of understanding the concept of gas, signing, etc.\n\n- ghoInvestmentVault to manage internally the investments collateral that go to suppluy aave´s pool. It also provides infrastructure to offer flashloans.\n\n- debtVault to manage the debt of offChain legalAgreements for lending the investors borrowingPower.\n\n- Aave protocol to generate yield.\n\n- CCIP to let the investor and borrower use their gho stablecoin on any external crossChain deFi protocol on any evmCompatibleChain.\n\n![alt text](https://i.ibb.co/pntnByY/111.jpg)\n\nTo simplify the onboarding experience to the web2 traditional users we implemented abstractedAccounts with emailAuthentication and a creditCard ramp to supply liquidity as collateral for issuing gho with fiat.\n\nEVEN THOUGH THE FOCUS IS ON WEB2 TRADITIONAL USER, THE PROTOCOL CAN BE INTERACTED WITH ANY WEB3 NATIVE WALLET (METAMASK, RABBIT, ETC.)\n\n![alt text](https://i.ibb.co/KV7ZzCs/222.jpg)\n\n![alt text](https://i.ibb.co/BGfFhsb/333.jpg)\n\n![alt text](https://i.ibb.co/7jVmnDr/444.jpg)\n\nThe vault supplies the provided amount of collateral to the aaveProtocol and issues the gho stablecoin to a ratio of 1 GHO : 1.5 USD in value.\n\n![alt text](https://i.ibb.co/8s2b83P/555.jpg)\n\nOnce the investors collateral has been supplied to aave, if he reaches a legal agreement, he can apply the second type of yield: lending his borrowing power to a delegatee. This type of yield is done using the debtVault that manages all the logic and the process.\n\n![alt text](https://i.ibb.co/BjrgZVg/666.jpg)\n\nThe last step is to use the issued gho to generate a third type of yield; either with the same investment vault to gain fees on flashloans or to use it on external deFi protocols in the same chain or on any other crossChain deFi protocol thanks to chainlinks CCIP.\n\n![alt text](https://i.ibb.co/w45Z45n/777.jpg)\n\nHere's a condensed version of the roadmap for the \"./yieldGhoVault\" project:\n\nPhase 1: UX/UI Design\nObjective: Revamp user interface and experience.\nTimeline: Months 1-2\n\nPhase 2: UX/UI Implementation\nObjective: Implement the new UX/UI designs.\nTimeline: Months 3-4\n\nPhase 3: Web 2.5 Tools Implementation\nObjective: Enhance platform accessibility with mail wallets and non-KYC fiat on-ramps.\nTimeline: Months 5-6\n\nPhase 4: Security Audit\nObjective: Perform comprehensive security checks.\nTimeline: Month 7\n\nPhase 5: L2 Mainnet Deployment\nObjective: Launch on a Layer 2 mainnet for improved efficiency.\nTimeline: Months 8-9", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "lfghoHackathon", "projectTwitter": "eth_mty"}