I’ve built a small open-source age gate: a website that lets someone prove they are 18 or over, with a phone wallet (ISO mdoc, Longfellow ZK) or a passport (ZKPassport), without the site learning anything else. Visitors can then pay with a shielded Zcash payment through ZecCheckout, which holds only a viewing key. Everything runs on test credentials and testnet.
Before I ask anyone for funding, I’d like someone with security experience to look at it. I’ve tried to make that easy:
- Threat model, with the gaps I already know about: age-gate/docs/THREAT-MODEL.md at main · Mirrorisor/age-gate · GitHub
- The part I’m least sure of, the passport check (about 190 lines of TypeScript plus a few routes), with specific questions: age-gate/docs/REVIEW-PASSPORT.md at main · Mirrorisor/age-gate · GitHub
- What funding would pay for, milestone by milestone: age-gate/docs/ROADMAP.md at main · Mirrorisor/age-gate · GitHub
It runs in Docker, there’s a one-command end-to-end check (scripts/e2e.ps1), and CI builds and tests every part. The payment side is the most Zcash-specific: I’m moving ZecCheckout off a public lightwalletd onto my own Zebra node, and I’d welcome a second pair of eyes on how the site trusts the checkout’s “paid” webhook.
Even an hour and a list of “this worries me” would help. If it’s paid work for you, tell me your rate. Replies here or a DM both work.