YieldLock+

Demo

About

The problem it solves 🔍 The Problem: DeFi Isn’t Built for Real People In traditional finance, people save money for real-world needs: rent, school fees, emergencies, or a new laptop. But in decentralized finance (DeFi), that human element is missing. Users are expected to: Choose from dozens of complex protocols (Aave? Compound? GMX?) Monitor gas fees, APR fluctuations, and chain risks Understand liquidity, slippage, and smart contract risk And still somehow trust their money is growing securely This creates a huge gap: 🎯 People have real-world goals, but DeFi offers abstract tools, not human-first solutions. 😩 Who’s Affected? 🧑‍🎓 Students trying to save for tuition 👩‍👧 Parents saving for rent or school books 👷‍♂️ Workers trying to build an emergency fund 🌍 Users in high-inflation countries who want yield, but not risk Right now, these people: Miss out on DeFi's benefits Or worse, lose money from misuse or hacks They don’t need a protocol — They need a savings experience they trust. 🧠 YieldLock+: The Human-Centered Solution YieldLock+ helps users save for goals, not just chase yield. It solves the problem by: Letting users name real goals (e.g. “Pay rent in Sept”) Automatically applying AI-recommended DeFi strategies Locking funds in smart vaults, with Chainlink-powered automation Returning yield at maturity, or with a fee if broken early It’s like a time-locked DeFi piggy bank — powered by smart contracts, but designed for people. 🔗 Why It Matters YieldLock+: Makes DeFi approachable and meaningful Reduces risk by automating strategy selection Builds healthy savings behavior onchain Gives Chainlink real-world impact — not just data, but decisions and automation that matter

How it's made

Challenges we ran into 🧩 Challenges We Ran Into 🔐 1. Understanding Chainlink Functions Architecture We initially struggled to grasp how Chainlink Functions works under the hood — especially how offchain data could securely trigger onchain logic. It took time to configure the router address correctly and simulate AI responses in a meaningful way. 💡 Solution: We studied Chainlink Functions examples and adapted the offchain script to output a strategy string encoded directly into our contract logic. 🔁 2. Triggering Real Onchain State Changes Chainlink’s core rule is that its services must trigger state changes, not just be read by the frontend. We had to carefully architect our smart contract so that the result of a Chainlink Function call would affect vault configuration and behavior. 💡 Solution: We stored the strategy output in the contract and made sure it affected logic around vault unlocking and user decisions. ⏰ 3. Automation Timing Logic Creating a system that accurately checks when vaults should unlock was harder than expected. We needed to use Chainlink Automation to scan multiple vaults and trigger payouts without bloating gas costs. 💡 Solution: We optimized the upkeep function to iterate through vaults with minimal gas and trigger payouts only when necessary. 🧪 4. Local Testing of Chainlink Services Chainlink Functions and Automation are powerful, but hard to test locally without the full environment. We had to simulate offchain behaviors and carefully mock automation to test real outcomes. 💡 Solution: We built a mock CLI testing loop and wrote fallback strategies to validate logic. 🎨 5. Balancing UX with Onchain Security We wanted YieldLock+ to feel like a real savings app — not a DeFi toy. But designing a UI that’s simple while handling gas, vault IDs, lock periods, and withdrawal rules was a UX/UXD balancing act. 💡 Solution: We stripped the frontend down to the essentials: goal name, amount, and duration — and made sure the backend handled the complexity. ✅ Bonus: Time Pressure With only a short deadline, we had to prioritize features that showed off Chainlink’s power, even if it meant deferring bells and whistles like multi-chain bridging or full frontend dashboards. 💬 TL;DR We faced technical, architectural, and UX challenges — but each one helped us better understand how to build real-world DeFi apps using Chainlink. And we’re proud of how far we’ve pushed this project in just a few days.