The problem Promise Registry solves

🧩 The Problem It Solves
In our everyday lives, we make countless promises and commitments — to ourselves, to others, and to teams or communities. But:

We often forget them, or lose track of our progress.

There's no accountability or system to remind us or verify our intent.

Commitments are made casually, and it's easy to break them without consequence.

People may want to show that they're serious about a goal, but there's no easy way to prove it.

This platform addresses these pain points by bringing transparency, accountability, and structure to promises — using blockchain technology.

✅ What You Can Use It For
People can use this platform for a variety of personal, professional, or social commitments:

Personal Goals – e.g., “I’ll wake up at 6 AM for 30 days,” or “I will finish reading 10 books this year.”

Habit Tracking – Use it like a public habit journal that keeps you accountable.

Team Agreements – Team members can make signed promises like “I’ll deliver this feature by Friday.”

Social Accountability – Make promises public and verifiable — friends or followers can see your progress.

Self-Improvement Challenges – Join or create challenges where everyone signs and tracks progress.

Reputation Building – Build a verifiable track record of fulfilled commitments.

🔐 How It Works
Every promise is signed with MetaMask, meaning the commitment is tied to your Web3 identity.

All promises are publicly visible and timestamped on the blockchain — making them tamper-proof and trustable.

Users can track progress — see how much of the promise is completed and what’s left.

Optional features could include reminders, social rewards, or penalties for unfulfilled promises.

🎯 Why This Matters
This platform makes existing tasks easier, more transparent, and goal-oriented:

Adds seriousness and commitment to personal and professional goals.

Encourages accountability and reduces procrastination.

Promotes a culture of integrity and self-discipline.

Leverages blockchain to create a trust layer for personal development and group commitments.

Challenges we ran into

🛠️ Challenges I Ran Into
While building this project, I ran into a couple of tricky issues that slowed down development:

1. Dynamic Boxes Reappearing on Page Reload
   One of the main bugs I faced was that dynamic promise boxes were appearing again and again every time the page was reloaded. At first, it was confusing because it looked like the same data was being duplicated without any clear reason.

🔍 Root Cause:
I was using mock data for initial testing, and I forgot to remove it once I connected the frontend to the backend. So every time the page loaded, the mock data was being rendered along with the actual data from the backend.

✅ Solution:
I removed the mock data and made sure the frontend was only rendering data fetched from the backend. This fixed the issue of repeated boxes and made the UI reflect the actual state of the application.

2. Frontend and Backend Linking Issues
   Another challenge was getting the frontend and backend to work smoothly together, especially when dealing with MetaMask integration and data flow between the blockchain and the UI.

🧩 Issue:
There were mismatches between the data structure expected by the frontend and the format returned by the backend APIs.

🛠 Fix:
I updated both sides to use a consistent data model, added error handling in API calls, and ensured that MetaMask-connected users were correctly authenticated and their promises were properly stored and retrieved.

These issues were frustrating at first, but solving them helped me better understand the importance of clean data flow and keeping test data separate from production logic.