The problem DRCP (Disaster Response Coordination Protocol) solves

The Humanitarian Crisis

Disaster relief in Southeast Asia faces a 72-hour latency gap - funds take 3+ days to reach victims while intermediaries extract hidden fees. Traditional NGOs operate as "black boxes" where donors have no visibility into fund allocation.

DRCP solves this by:

🔹 Instant Parametric Relief - Funds are automatically allocated when disaster data (BMKG seismic, PetaBencana floods) triggers DAO governance votes

🔹 Radical Transparency - Every Rupiah is tracked on-chain via The Graph. Donors can audit the entire fund flow in real-time

🔹 Trustless Execution - Smart contracts eliminate intermediary corruption. No admin can secretly divert funds

🔹 Volunteer Reputation System - Impact NFTs (Soulbound) create verifiable "Resilience Resumes" for local heroes

Use Cases:

• Donors: Transparent giving with full audit trail
• NGOs: Governance tools to coordinate multi-org responses
• Volunteers: Build portable, verified reputation
• Governments: Real-time disaster fund monitoring

Challenges I ran into

Technical Challenges

1. RPC Rate Limiting

Problem: Free-tier Alchemy endpoints throttled getLogs requests, causing 400 errors on transparency dashboard.
Solution: Implemented paginated chunk fetching (2000 blocks per request) with error handling fallback.

2. Subgraph Indexing Lag

Problem: The Graph took 30-60 seconds to index new transactions, causing stale UI data.
Solution: Built optimistic UI pattern - show pending transactions immediately while background sync catches up.