From hackathon demo to real-world aid protocol.
This board shows the seven production credibility layers behind AidShield: external review readiness, trusted setup posture, pilot operations, durable issuance, threat response, privacy boundaries, and live proof evidence. Some items are fully implemented; external audit and real pilot execution remain outside the repo and are clearly labeled as next operational actions.
Independent security review
Ready to requestAudit scope is packaged for circuits, Soroban contracts, issuance, witness handling, Redis ledger, admin controls, and frontend trust boundaries.
Trusted setup path
Ceremony plan documentedGroth16 demo setup is disclosed, with a production ceremony checklist covering contributors, transcript verification, toxic-waste handling, and artifact hashes.
Real pilot package
Pilot-ready planField runbook defines NGO operator, field officer, beneficiary, vendor, auditor, data-retention rules, offline QR handling, and incident escalation.
Production issuance backend
Control model definedDurable Redis reservations, non-PII ledger, admin auth, rate limits, issuer revocation, delivery events, and audit trails are mapped as deployable controls.
Threat actor hardening
Operational playbooksThreat cases now include malicious operators, stolen QR credentials, compromised frontend, phishing, vendor abuse, coercion, and emergency pause.
Privacy disclosure clarity
Explicit boundaryThe project clearly separates hidden eligibility data from public settlement metadata so judges see exactly what privacy is and is not promised.
Live proof evidence
Verification labJudges can inspect contract anchors, public proof inputs, verifier key hash, receipt transaction checks, nullifier replay posture, and explorer links.