The problem Split Bill Dapp solves

💡 The Problem It Solves
Managing group expenses is often chaotic — from tracking who paid what, to calculating who owes whom, and making sure everyone settles fairly. Traditional methods like spreadsheets, manual calculations, or central payment apps lack transparency, are prone to disputes, and often rely on one trusted party.

Our DApp brings a decentralized solution to this problem.

📊 Tracks individual contributions: Each participant enters their own expense and wallet address.

🤝 Eliminates trust dependencies: Smart contracts calculate fair settlements automatically.

✅ On-chain verification: Payments are made directly on Ethereum, ensuring transparency and traceability.

💸 Real-time settlement: Users can pay their exact share instantly from the UI.

🔐 No centralized control: Funds aren’t held by a middleman — everything happens on-chain.

Whether it's for friends splitting dinner, flatmates dividing rent, or teams sharing travel costs — this DApp makes group expense management fair, transparent, and trustless.

Challenges we ran into

🧩 Challenges We Ran Into
🧠 Designing a fair settlement algorithm: It was tricky to compute how much each person owed or was owed, especially when everyone spent different amounts. We had to carefully handle rounding issues and optimize logic for Ethereum's gas limits.

⛓️ On-chain payment tracking: Ensuring that each participant's payment status was correctly stored and reflected on the blockchain required structuring mappings and storage efficiently.

🔄 Syncing UI with contract state: Keeping the frontend reactive to blockchain events and dynamically updating paid statuses, history, and live settlements was a challenge with asynchronous web3 interactions.

💥 MetaMask integration issues: We ran into issues with wallet permissions, user transaction confirmation delays, and multiple pending requests — especially while testing rapidly.

🧪 Testing locally with realistic data: Simulating multiple users, wallets, and transactions in a local Hardhat environment to validate payment logic and status tracking required detailed mock scenarios.

💻 Remote & local setup difficulties: Since our team worked entirely online, we faced issues syncing local blockchain networks (Hardhat), managing shared contract changes, and dealing with missing dependencies or mismatched environments. Debugging Solidity and frontend integration over screen-sharing was time-consuming, but taught us a lot about remote collaboration.