Cowrie Research

anon-aadhaar-primary-sources-2026-05-11

3 min read

Anon Aadhaar primary sources — 2026-05-11

Project status in this pass

  • No canonical standalone Anon Aadhaar whitepaper surfaced.
  • The clearest primary materials in this pass were the official docs, the repository README, the protocol walkthrough, and package-level READMEs for contracts and React integration.
  • Those materials consistently frame Anon Aadhaar as a reusable Aadhaar-proof middleware stack rather than as a broad identity wallet.

Primary-source snapshots

1) Official introduction and scope

  • URL: https://documentation.anon-aadhaar.pse.dev/docs/intro
  • Key excerpt:
    • The docs introduce Anon Aadhaar as a zero-knowledge protocol that allows Aadhaar ID owners to prove identity in a privacy-preserving way, with tools to generate proofs, verify them, authenticate users, and verify proofs on-chain.
    • This matters because it places the project at the middleware layer: proof generation plus verifier integration, not only end-user onboarding UX.

2) Core mechanism: UIDAI-signed QR verification inside a zk circuit

  • URL: https://documentation.anon-aadhaar.pse.dev/docs/intro
  • Key excerpt:
    • The docs say the protocol is built around a circuit that takes the RSA signature contained in the Aadhaar QR code and verifies that it was signed by the Indian government public key.
    • This is the strongest mechanism clue in the pass. The key trust surface is not generic “identity,” but government signature verification plus local proof generation.

3) Client-side proving and limited disclosure

  • URL: https://raw.githubusercontent.com/anon-aadhaar/anon-aadhaar/main/README.md
  • Key excerpt:
    • The README says Anon Aadhaar works on the client side and does not require the user to send Aadhaar details to any server.
    • It also frames the verifier as an app or smart contract that can be sure the prover had a valid Aadhaar containing the revealed information.
    • This is important because it clarifies that server-side document custody is not the main model here.

4) Proof inputs, nullifiers, and selective field reveal

  • URL: https://documentation.anon-aadhaar.pse.dev/docs/how-does-it-work
  • Key excerpt:
    • The workflow page says proof generation uses the signed QR data, RSA signature bytes, the UIDAI public key, a signal, and a nullifier seed.
    • It also says the circuit can reveal only four fields if requested: age over 18, gender, state, and pincode; by default it reveals nothing.
    • This is the most useful lower-layer detail in the pass because it shows where application policy enters the system: requested fields, signal choice, and nullifier handling.

5) Package surface as reusable developer infrastructure

6) Onchain verifier contract package

7) React integration and app-facing authentication flow

8) Explicit maturity warning

  • URL: https://documentation.anon-aadhaar.pse.dev/docs/intro
  • Key excerpt:
    • The docs warn that Anon Aadhaar is still under development and should not be used in production without guidance.
    • That warning matters when comparing it to more mature identity products; it reads as a powerful primitive with an unfinished production posture.

Working conclusion

Anon Aadhaar is best cataloged as a narrow Aadhaar-secure-QR proof rail: government-signed document data, client-side zk proving, limited selective disclosure, app-scoped nullifiers/signals, and both offchain and onchain verification. Its usefulness in the corpus comes from how clearly it separates document authenticity, local proof generation, requested-attribute policy, and verifier integration.

Graph View