Human ID primary sources — 2026-05-09

Classification takeaway

Human ID is best cataloged as privacy-preserving identity-verification and compliance-proof middleware rather than as a generic attestation registry or ordinary KYC service. Its core mechanism is a user / issuer / consumer credential flow in which users can prove narrow facts — uniqueness, residency, sanctions status, age, accredited-investor status, and similar properties — without exposing the full underlying identity to the consuming application.

Primary sources reviewed

1. Human ID docs landing page — https://docs.holonym.id/

   • Best concise first-party description of the product.
   • Defines Human ID as a privacy-preserving identity protocol developed by Holonym Foundation and says it uses zero-knowledge proofs to verify facts without revealing the whole identity.
   • Useful for the top-level classification and example proof types.

2. Architecture overview — https://docs.holonym.id/architecture/overview

   • Best source for the core actor model.
   • Explicitly frames the system around three actors: user, issuer, and consumer.
   • Important because it clarifies that Human ID is not just a credential schema; it is an issuance-and-proof workflow with distinct trust anchors.

3. Developer integration guide — https://docs.holonym.id/for-developers/start-here

   • Best source for how apps actually consume the system.
   • Shows the two main integration paths: send users into Human ID issuance flows or embed the Human ID SDK, then read proof/SBT results through the API or older onchain interfaces.
   • Important because it makes clear Human ID is application middleware, not merely a user-facing identity product.

4. Docs Q&A on actors and trust surfaces — https://docs.holonym.id/architecture/overview?ask=What%20are%20the%20main%20actors%20and%20trust%20surfaces%20in%20Human%20ID%20and%20how%20do%20issuers%20and%20consumers%20use%20credentials%3F

   • Useful compact synthesis from the official documentation layer.
   • Highlights issuer trust, KYC-provider visibility, encrypted-data handling, and the role of consumers/verifiers that only need proofs or SBT checks instead of raw credentials.
   • Helpful for locating the real trust surfaces without reading the whole docs tree.

5. human.tech docs landing page — https://docs.human.tech/

   • Useful for locating Human ID inside the broader product and protocol ecosystem.
   • Shows that Holonym is building a broader stack around digital identity, privacy, access, personhood, and key management.

6. Human Passport page — https://docs.human.tech/passport

   • Useful for the neighboring product surface and scale claims.
   • Helps show how Human ID sits near anti-Sybil and funding-protection use cases rather than only compliance/KYC.

7. Human Network page — https://docs.human.tech/network

   • Useful for how the project frames adjacent cryptographic-key and recovery infrastructure.
   • Important as evidence that the broader stack is moving beyond pure credential proving.

8. Human Network README — https://raw.githubusercontent.com/holonym-foundation/human-network/main/README.md

   • Most technical first-party source reviewed in this pass.
   • Describes threshold cryptography, OPRF-based key derivation, privacy-preserving identity verification, and decentralized decryption/access-control ideas.
   • Useful not because it defines Human ID directly, but because it clarifies the broader identity-and-key infrastructure trajectory around it.

Whitepaper / technical-doc status

• No standalone Human ID whitepaper was located during this pass.
• The docs tree plus the Human Network technical README are the main primary-source materials today.

Why it stays in the active corpus

• Strong comparison class for attestation systems, compliance identity stacks, and anonymous-membership tools.
• Useful for separating public schema registry projects from privacy-preserving proof middleware where trust still concentrates in issuers, KYC providers, and verifier policy.
• Helps map how one-person-one-action logic, sanctions gating, and selective disclosure can become application control surfaces even when raw identity data is hidden from the relying app.