Scaffold a starter age-gate circuit in Noir and integrate it into a Next.js login flow.
Compare the Circom and Noir versions of an anonymous voting template side by side.
Use the proof of reserves template as the basis for an exchange transparency report.
Generate a private allowlist claim circuit and wire it up to an Ethereum verifier contract.
Templates are explicitly marked as unaudited starter material and require an external Noir or Circom toolchain to compile.
This project is a starter kit for teams building apps with zero-knowledge proofs. A zero-knowledge proof is a way to prove something is true without revealing the underlying data, for example proving you are over 18 without showing your birthday. The library gives a shared catalog of common proof patterns, each one documented with its inputs, security notes, and starter circuit files. The first version covers five patterns that come up often in privacy apps: an age gate, group membership, anonymous voting, private allowlist claims, and proof of reserves. The README is clear that every template is marked as starter material. They are not audited production circuits, so the team should treat them as scaffolds and review checklists rather than finished code. The library ships with a command line tool and a JavaScript API. You can list every template, show details for one, or scaffold a starter circuit into a folder using either the Noir or Circom proof system. Examples in the README show commands like list, show group-membership, and scaffold anonymous-vote with a chosen system and output path. The JavaScript API exposes the same actions as importable functions. Each template entry in the catalog file records an ID, title, summary, category, supported systems, descriptions of public and private inputs, the proof statement in plain language, the constraints the circuit must enforce, security notes, and references to starter files. A JSON schema defines the shape. A GitHub Pages workflow builds a static catalog site from the source folder on every push to main. The production checklist warns implementers to replace placeholder hash functions with audited primitives, add positive and negative tests, bind proofs to a specific verifier and chain to prevent replay, version every circuit, and get independent security review before shipping anything real.
Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.