Skip to content
C

CrowdFund

Blockchain Based Crowdfund Platform

Created on 15th December 2025

C

CrowdFund

Blockchain Based Crowdfund Platform

The problem CrowdFund solves

Crowdfunding today is largely based on trusting intermediaries and individuals, which creates several real-world problems:

Donors cannot be sure whether their money is securely held.

Campaign owners may withdraw funds even if goals are not fully achieved.

Refunds are often manual, delayed, or not guaranteed.

Fund handling happens off-chain, making misuse difficult to verify.

Users must trust platforms and organizers instead of enforceable rules.

This lack of transparency and automation discourages participation and reduces trust in crowdfunding systems.

How our project helps

Our project provides a blockchain-based crowdfunding platform that makes fundraising safer, more transparent, and automated.

People can use it to:

Create fundraising campaigns for medical aid, education, emergencies, or community causes.

Donate to campaigns with confidence, knowing funds are protected by smart contracts.

Track all donations, withdrawals, and refunds publicly on the blockchain.

Ensure funds are released only when predefined conditions are met.

What makes it easier and safer

Smart contract escrow
Funds are locked inside a smart contract, not held by the platform or campaign owner.

Automatic rule enforcement

If the funding goal is reached before the deadline → withdrawal is allowed.

If the goal is not reached → donors can claim refunds automatically.

On-chain transparency
All financial actions are publicly verifiable and immutable.

Proof of utilization (prototype)
Campaign owners upload utilization proofs stored on IPFS, allowing donors to see how funds were used.

In short, the platform replaces trust in people with trust in code, making crowdfunding more reliable and secure.

Challenges I ran into

  1. Understanding smart contract fund locking

One of the initial challenges was understanding how funds can be securely locked without relying on a central wallet.
I solved this by designing the smart contract to act as an automated escrow, where ETH is stored directly in the contract balance and can only be moved through predefined functions.

  1. Ensuring safe withdrawals and refunds

Handling withdrawals and refunds safely was critical.
I had to ensure:

Only campaign owners could withdraw.

Withdrawals were allowed only after successful funding.

Refunds were available only when campaigns failed.

This was solved by carefully structuring require conditions and using a reentrancy guard to prevent common attack patterns.

  1. Integrating IPFS for proof of utilization

Adding proof uploads introduced challenges around:

File handling in the frontend

IPFS uploads

Environment variables in deployment

Locally everything worked, but deployment failed because the IPFS API key was missing in the hosting environment.
I resolved this by correctly configuring environment variables in Vercel and improving error handling to catch such issues early.

  1. Deployment and environment mismatches

Another hurdle was inconsistent behavior between localhost and the deployed version due to caching and environment configuration differences.
This was resolved by forcing clean redeployments and ensuring all environment variables were correctly set in production.

What I learned

Smart contracts require minimal and precise logic to remain secure.

Blockchain applications demand careful handling of deployment environments.

Building trustless systems means thinking defensively and anticipating edge cases.

These challenges helped me better understand real-world blockchain development beyond just writing code.

Tracks Applied (1)

Ethereum Track

ETHIndia

ETHIndia

Cheer Project

Cheering for a project means supporting a project you like with as little as 0.0025 ETH. Right now, you can Cheer using ETH on Arbitrum, Optimism and Base.

Discussion

Builders also viewed

See more projects on Devfolio