Organization / Reviewer POV
Operations
- Create Incident: Set Title, Radius (km), Latitude, Longitude, and a short description.
- Publish Incident: Share incident ID/QR with affected area.
- Monitor Intake: Open Review & Payout → see incoming requests.
- Verify & Gate: Confirm Geofence = Inside and ZK ✓ before approval.
- Approve & Pay: Trigger USDC payout (mock now; swap to Circle/Arc in prod).
- Recordkeeping: Export approvals & notes for reconciliation and audit.
- Close Incident: When relief window ends, set status to closed (future toggle).
Data Needed
- Incident center (lat/lng) & radius, internal reference code
- Per-request: wallet address, requested amount, reason, geofence verification, ZK proof hash
Victim / Applicant POV
Submission
- Select Incident: Choose the relevant relief incident from the list.
- Verify Location: Share approximate location and click Verify Location.
- Generate ZK: Create proof of presence without revealing exact coordinates.
- Request Funds: Enter Name, Wallet (0x…), Amount, and Reason.
- Submit: The request appears in the reviewer’s queue.
- Track Status: Approved requests display a transaction link once paid.
Tips
- Make sure the wallet address starts with
0x and is valid.
- If you’re outside the radius, verification will fail—move closer to the affected area.
Production Integration Guide (Minimal)
Next Steps
- Replace fakeSDK with Circle/Arc wallet + USDC transfer SDKs; store TX IDs.
- Replace geofence placeholder with Mapbox/Leaflet and a ZK/attestation kit.
- Add role-based access (multi‑sig, approver roles) and a secure backend for persistence.
- Log events to your SIEM (e.g., Splunk) and export CSVs for finance reconciliation.