The problem ImpactVault solves

🧩 The Problem It Solves

In today’s DeFi ecosystem, billions of dollars in idle liquidity sit across protocols, earning passive yield for individual users — but very little of that yield contributes to public good.
Projects that depend on grants, donations, or community funding often face sustainability issues because their financial support is manual, unpredictable, and short-lived.

⚙️ What ImpactVault Does

ImpactVault bridges the gap between profit and purpose by turning DeFi yield into automatic, transparent funding for public goods.

Users can:

• Deposit tokens (like mDAI) into a decentralized vault that earns yield.
• Simulate yield and track how their deposits contribute to real-world impact.
• Harvest & Donate their accrued yield directly to verified public-good projects — with on-chain transparency and proof of contribution.

💡 Why It’s Powerful

• Automated Giving: You don’t have to choose between earning and giving — your yield does both.
• Transparency: Every donation is verifiable on-chain through the smart contract.
• Accessibility: Anyone can contribute, from DeFi users to NGOs, without intermediaries.
• Sustainability: Creates a recurring, yield-powered stream of funding for ecosystems, not one-time donations.

🚀 Example Use Cases

• DeFi investors redirecting part of their yield to fund open-source projects.
• DAOs automating community impact programs.
• Hackathon participants testing sustainable treasury models.
• Nonprofits integrating on-chain yield vaults to fund social causes.

Challenges I ran into

⚔️ Challenges I Ran Into

Building ImpactVault was both technically exciting and full of real-world DeFi hurdles.

🧠 1. Network & Deployment Issues

Deploying the contracts on testnets like Base Sepolia and Sepolia (Infura) was tricky — faucets were often delayed or empty, leaving me without test ETH for gas fees.
I overcame this by configuring multiple RPC endpoints (Alchemy, Infura, QuickNode) and switching between them when one was congested.

🧩 2. Smart Contract Debugging

Initially, my MockERC20 and vault contracts failed to deploy due to incorrect payable settings and insufficient minting logic.
After reviewing the OpenZeppelin base contracts and manually adjusting mint permissions, I successfully deployed a working token with mint() support for testing.

💻 3. Frontend Integration with Ethers.js

Connecting the smart contract to the UI through Ethers.js brought its own challenges — especially handling provider states and ensuring smooth MetaMask interactions.
To fix this, I implemented clear connection logic, error handling, and a clean async structure for deposits, yield simulation, and harvesting.

🎨 4. Modern UI/UX Design

Initially, the frontend felt too “flat.”
By introducing dark gradients, animated preloaders, and interactive cards styled with the project’s color palette, I made the dashboard both functional and visually appealing.

⚙️ 5. Data Tracking Logic

Keeping user balances and donation stats updated on-chain and in the dashboard required setting up real-time event listeners (e.g., DonationSent events).
I created lightweight toast notifications and progress bars to visualize these updates dynamically.