Integrated recommendationsJudge-ready proof boardThreat-aware aid privacy

Competitive Edge Package

This page packages the strongest ideas from current public Stellar ZK projects into AidShield’s own lane: private humanitarian aid claims with accountable donors, vendors, issuers, and incident controls.

AidShield before
88%
AidShield after
96%
Readiness growth
+8%
Current lead range
+5% to +14%
New judge story layer

Crisis Aid Mission Demo

AidShield now has a clearly labeled synthetic flood-relief mission: NGO operator issues an encrypted QR, beneficiary claims privately, approved vendor can receive voucher payment, replay fails, and donors audit aggregate settlement without seeing PII. This keeps the demo honest while making the real-world use case concrete.

Open Mission

Judge Proof Board

A compact view of what succeeds and what must fail before a reviewer trusts the system.

Open Contract
CaseResultEvidenceLayer
Valid private claimExpected passGroth16 proof verifies, claimant signs, nullifier unused, escrow pays once.ZK circuit + Soroban
Replay claimExpected failThe same nullifier is already persisted and blocks cash-plus-voucher reuse.Soroban nullifier set
Wrong walletExpected failCredential leaf binds the claimant address field, so another wallet cannot claim it.ZK public input binding
Expired credentialExpected failThe claim public input carries expires_at and the contract rejects stale credentials.Soroban policy
Revoked issuerExpected failIssuer key id must be active before the proof can release funds.Issuer registry
Unauthorized vendorExpected failVoucher route only pays active vendor addresses.Vendor registry
Emergency pauseExpected failOperators can pause claims during incident response without revealing beneficiary data.Governance control

Selective Disclosure Panel

Donor

Shown: Campaign funded amount, remaining escrow, number of claims, payout size, contract ids.

Hidden: Beneficiary name, ID, credential secret, Merkle path.

Regulator

Shown: Nullifier count, approved issuer keys, vendor approval status, settlement hashes.

Hidden: Aid-list membership and private eligibility witness.

Field operator

Shown: Credential hash, keyed wallet identifier, expiry, delivery mode, issuer key id.

Hidden: Raw identity documents and unencrypted beneficiary credential.

Proof Telemetry

Circuitaidshield-groth16 / Circom
CurveBLS12-381
Proof size384 bytes
Public inputs6 field elements
Verifier contractCAD7QR…DEJ2KG
Disbursement contractCARYQO…5D3CZD
Merkle root337334…d6d5ad
VK hashc243d169dcf3...77d4d128
Verification anchor

Disbursement 176bc0…d25922 uses issuer key 0096e9…4ddc1c and admin anchor GC7HI6…2OVYVJ.

No-Wallet Judge Mode

01
Read

Open Judges or Edge page and inspect contract anchors without connecting a wallet.

02
Issue

Use prepared sample credential or admin-issued QR payload from the local demo pack.

03
Prove

Generate the browser proof and inspect proof/public-input telemetry.

04
Verify

Show that invalid routes are rejected by tests, simulation, or replay after first claim.

Threat Simulator

Forged proof
Blocked

Verifier rejects proof that does not match the committed Merkle root.

Credential leak
Blocked

Wallet-bound leaf prevents a different Freighter account from claiming.

Double spend
Blocked

Nullifier prevents cash and vendor routes from both succeeding.

Compromised vendor
Contained

Admin can revoke vendor and keep direct cash route available.

Compromised issuer
Contained

Issuer key can be revoked and campaign can be rotated.

Underfunded campaign
Visible

Escrow health and remaining claim capacity are visible to auditors.

Integrated Advantages

Judge Proof Board: valid claim, replay, wrong wallet, expired credential, revoked issuer, unauthorized vendor, and pause controls.
Selective Disclosure Panel: donor and regulator facts without beneficiary names, IDs, credential secrets, or Merkle paths.
Proof Telemetry Panel: circuit, proof size, public inputs, verifier, root, VK hash, and expected proof lifecycle.
No-Wallet Judge Mode: a guided demo path for reviewers who do not have Freighter ready.
Threat Simulator: attack cases mapped to the exact layer that blocks or monitors them.
Escrow Health Attestation: live reserve, payout amount, remaining claim capacity, and public settlement anchors.
Mobile Field Officer Flow: QR credential delivery stays first-class instead of becoming a future-only claim.
Competitive Positioning: AidShield is framed as humanitarian privacy plus accountability, not generic private payments.

Competitive Readiness Growth

ProjectFocusBeforeAfter AidShield EdgeAidShield LeadWhat changed
ZK AidShieldPrivate humanitarian aid claims88%96%+8% internal growthRecommendations are now packaged as visible product surfaces.
TukarConfidential remittance corridor93%91%+5%AidShield now matches its selective disclosure and negative-proof clarity while keeping a stronger humanitarian workflow.
NebulaConfidential token infrastructure92%90%+6%AidShield now adds comparable proof telemetry and contract evidence, then leads on real field operations.
Open Stellar PassportZK passport for agent payments90%88%+8%AidShield now mirrors the no-wallet judge path and replay/tamper evidence while staying closer to real-world aid payments.
x402 ZK MeshPrivate AI-agent task marketplace87%84%+12%AidShield now turns zero-trust controls into a simpler threat simulator judges can verify quickly.
AuspexProof-of-solvency and risk attestation85%82%+14%AidShield now borrows reserve-health language while proving a more complete user-facing payout system.

These percentages are strategic readiness estimates, not official hackathon scores. They measure clarity, real-world fit, ZK load-bearing value, Stellar integration, demoability, and threat posture.

Open Judge BriefOpen Mission DemoOpen Threat DashboardOpen Audit Evidence