YOLO Protocol
The Ultimate Hook for DeFi Degens
About
The problem it solves ### A. Introduction **** YOLO Protocol is a modular DeFi engine built on top of Uniswap V4, combining the various functionalities of blue-chip protocols - such as ****MakerDAO, Synthetix/Mirror, and Gearbox**** - into a single Uniswap V4 Hook.  **** ### B. Imagine if you can... **** 1. Trade and speculate on shares directly inside Uniswap 2. Even better, being able to execute leveraged tradings with 100X leverage on shares on-chain 3. Unleash the liquidity of your favourite yield-bearing tokens (be it PT-USDe, Beefy LP, CurveLP, LST ETH) by executing 20X leveraged yield looping ****YOLO Protocol make this possible!**** **** ### C. Problems **** 1. **Underutilized Yield-Bearing Tokens (YBTs)**: Traditional DeFi protocols failed to unlock the full capital efficiency of YBTs, leaving substantial yield opportunities untapped. 2. **Lack of on-chain synthetic asset exposure**: There was no frictionless way to mint and trade synthetic assets tracking real-world prices like gold, gasoline, NVIDIA, or JPY in a decentralized environment. 3. **Poor liquidity for synthetic assets**: Fragmented liquidity across different DEXes made it difficult to access deep and efficient markets for synthetic asset trading. 4. **Inaccessible high-leverage strategies**: Existing protocols struggled to offer secure, high-leverage yield farming without exposing users (and protocols themselves) to significant liquidation risk. **** ### D. Our Vision **** Our vision is to build an onchain version of eToro/Plus500, providing a seamless web2 leveraged trading & yield-looping experience to DeFi degens. **** ### E. Background **** We have won Hackathon with an earlier version of this project, back then it was just a rough idea. Since then we have been building relentlessly, and integrated rich features including frontend, stable math, cross-chain functionality with CCIP, innovative hybrid oracle powered by Chainlink Functions, Circle USYC's rehypothecation. 
How it's made
Challenges we ran into In our journey of building this project, we have faced several significant challenges: **** ****Code Complexity****: Since we have been adding more and more interesting features into the protocol, the codebase has become very complicated, and harder to maintain. Trimming / breaking code to conform to 24KB contract size limitation of EVM is a pain and took several days. Should I have the chance to re-build it from scratch, I will not use a Proxy-Implementation pattern, and will rather choose an EIP-2535 mechanism instead. ****Time Constraint****: Since we are currently joinimg Uniswap V4 Hook Incubator and Incubase at the same time, there are lots of commitments we need to fulfil, render us having less time to code. ****