The problem DeFi Entiendo solves

Traditional Public Goods Funding Has Three Critical Problems:

Donor Fatigue

• People make one-time donations and stop
• No ongoing engagement or impact tracking
• Communities rely on annual grant cycles that are unpredictable and often insufficient

Lack of User Education & Retention

• DeFi knowledge is fragmented across multiple platforms
• No direct link between learning and contributing to public goods
• Users don't understand how their capital can generate sustainable funding

Principal Risk for Supporters

• Traditional yield farming requires users to risk their capital
• Complex strategies make participation risky for newcomers
• No mechanism to donate yield while protecting principal

DeFi Entiendo Solves This With:

✅ Continuous Passive Funding - Users deposit USDC, their yield automatically flows to public goods forever (no manual intervention needed)
✅ Gamified Education - Learn DeFi through interactive lessons while earning soulbound NFT certificates. Knowledge = Credentials = Impact
✅ Principal Protection - Your deposit stays safe in your wallet. You can withdraw anytime. Only yield is donated (5% APY mock, real yield coming soon)
✅ Transparent Impact - Real-time on-chain tracking shows exactly how much you've funded for public goods. See your impact every single day.
✅ Sustainable Model - Unlike grants, this creates an infinite funding stream. One user = continuous yield stream. 1,000 users = $50K+ annually donated to public goods.

Use Cases:

• Individual Users: Earn returns while funding Ethereum development & open-source tools
• Educational Institutions: Use platform to teach DeFi to students while generating funds
• DAOs: Can deploy treasury to generate yield for member education & public goods
• Projects: Can receive continuous funding through Octant V2 integration

Challenges I ran into

Developing this project helped me understand and grasp more concepts about DeFi, leading to their implementation

Key Learnings:

1. Smart Contract Testing: Mock implementations are valuable for MVP, but need clear path to real integration
2. Frontend Web3: State management is critical - use Wagmi hooks properly with correct dependencies
3. Database Security: RLS policies need balance between safety and usability
4. Deployment: Never commit secrets; use platform env var systems

All challenges were resolved with clean code, thorough testing, and proper architecture decisions.