CrowdFUNding
Make Giving Addictive
About
The problem it solves **CrowdFUNding** tackles the "Philanthropy Dilemma," helping the world's most generous nation overcome financial friction and trust deficits. We leverage the Base blockchain to build a donation platform that is **Borderless**, **Cheap**, and **Transparent**, . ### Borderless: Solving the Velocity Problem Traditional financial rails isolate local causes from global capital. Sending emergency aid from abroad can take **7-14 days** via SWIFT, and even local transfers can lag by 3-5 business days. - **The Solution**: By utilizing the **Base network** and **IDRX** stablecoin, we enable **instant global settlement**. A donor in New York can support a cause in Jakarta instantly, bypassing the slow machinery of legacy banking. ### Cheap: Eliminating the "Middleman Tax" Approximately **12.66%** of donation value is lost to bank transfer fees and payment gateway markups, making micro-donations (under $50) financially impossible. - **The Solution**: We cut out the intermediaries. By facilitating direct peer-to-contract transactions, we ensure that nearly 100% of the donated value reaches the cause, maximizing the impact of every cent. ### Transparent: Restoring Trust through Code Lack of transparency alienates younger generations (Gen Z/Alpha) who demand proof, not promises. Traditional "black box" charities often leave donors wondering where their money went. - **The Solution**: We replace opaque manual audits with immutable **Smart Contracts**. Every donation creates an on-chain record that serves as undisputed proof of impact, making fraud mathematically impossible. ### Key Features: Making Philanthropy Easier & Safer **CrowdFUNding** combines the familiarity of Web2 with the power of Web3 through five core features designed to maximize velocity and retention: - **Seedless Access**: We make **onboarding safer and easier** by eliminating the Web3 barrier. Users log in instantly using their **Google account** via Base OnchainKit, removing the risk and complexity of managing seed phrases. - **Instant Fiat Gateway**: We make **local donations easier** by integrating with standard banking apps. Donors simply scan a **QRIS code** (GoPay, OVO, BCA), allowing them to support causes without navigating complex crypto exchanges. - **Borderless Liquidity**: We make **global support easier** by automating currency conversion. Global supporters donate **USDC**, and the protocol auto-swaps it to **IDRX** instantly, removing the need for manual exchanges and protecting recipients from volatility. - **Dynamic Proof of Impact**: We make **engagement easier** through automated gamification. Contributors receive a **Digital Pet** on Base that evolves on-chain, providing verifiable feedback and "Proof of Impact" without requiring extra user effort. - **Automated Bank Settlement**: We make **accessing funds easier** for campaign creators. The "last mile" is solved by allowing direct transfers of IDRX funds from the smart contract to **local bank accounts**, unifying Web3 with the real world.
How it's made
Challenges we ran into The most significant hurdle we faced during development was **integrating the Frontend with the Backend in a live environment**. We encountered a persistent and frustrating issue where the **Backend became accidentally unreachable from the Frontend**. Despite seemingly correct configurations locally, the communication would breakdown in the deployed environment. **The specific issues included:** - **CORS Configuration:** Our cross-origin resource sharing policies were initially too restrictive, blocking valid requests from our frontend client. - **Network Isolation:** There were disconnects between our containerized services, preventing them from "seeing" each other properly. **How we overcame it:** Debugging this required a deep dive into our network architecture. We had to drastically refine our server configuration to ensure API endpoints were correctly exposed. We methodically tested the handshake between the client and server, adjusting headers and allowed origins until we established a stable, secure connection. This process taught us valuable lessons about the nuances of deploying full-stack Web3 applications versus running them in a local testnet environment.