Human Network primary sources — 2026-05-11

Classification takeaway

Human Network is best cataloged as lower-layer threshold-cryptography and programmable-decryption infrastructure rather than as a generic identity app. Its main reusable primitive is a threshold scalar-multiplication network that can operate on masked user inputs, enabling secure key derivation from low-entropy secrets, web-account-derived keys, and conditional decryption workflows without any single node seeing the underlying secret.

Primary sources reviewed

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

   • Best first-party entry point for how the project frames itself.
   • Describes Human Network as the network for Human keys and an AVS secured by EigenLayer and Symbiotic.
   • Useful for positioning it inside the broader human.tech stack.

2. What is Human Network? What are Human Keys? — https://docs.network.human.tech/overview/what-is-human-network-what-are-human-keys.md

   • Best source for the core primitive.
   • Explains that Human Keys are derived from human attributes and other low-entropy inputs, and that the network adds entropy without seeing the sensitive data itself.
   • Important because it clarifies that the product is about cryptographic key derivation and not only about identity verification UX.

3. Methods and their use cases — https://docs.network.human.tech/overview/methods-and-their-use-cases.md

   • Best source for the internal product split.
   • Lists the three main methods: OPRFSecp256k1, JWTPRFSecp256k1, and DecryptBabyJubJub.
   • Important because it makes visible three distinct control planes that would otherwise get flattened together: low-entropy key derivation, web-account-derived keys, and provable encryption / decentralized decryption.

4. Mainnets and Testnets — https://docs.network.human.tech/decentralization/mainnets-and-testnets.md

   • Best source for deployment-mode and decentralization status.
   • Shows the split between Mainnet Alpha / Holesky paths that rely on resharing and a Robustnet mode that remains permissioned because resharing is disabled.
   • Important because it surfaces operator admission and resharing as live governance / trust issues rather than abstract future details.

5. Docs Q&A on mechanism and security layers — https://docs.network.human.tech/welcome-to-human-network.md?ask=What%20is%20Human%20Network%27s%20core%20mechanism%2C%20main%20use%20cases%2C%20and%20what%20roles%20do%20EigenLayer%20and%20Symbiotic%20play%3F

   • Useful compact synthesis from the official docs layer.
   • Summarizes the threshold-network mechanism, major use cases, and the role of EigenLayer / Symbiotic as security layers.
   • Helpful for a quick first-party explanation of why the protocol belongs in identity-and-privacy infrastructure, not just in AVS lists.

6. Docs Q&A on control surfaces — https://docs.network.human.tech/decentralization/architecture.md?ask=What%20are%20Human%20Network%27s%20main%20control%20surfaces%20or%20centralization%20risks%2C%20including%20relayer%2C%20resharing%2C%20permissioned%20modes%2C%20and%20operator%20admission%3F

   • Best concise source for trust and centralization analysis.
   • Highlights the relay node as request ingress, resharing as a major governance surface, Robustnet as a permissioned mode, and operator registration as an admission gate.
   • Important because it identifies where practical authority still sits even though the network is presented as decentralized threshold cryptography.

7. human.tech overview — https://docs.human.tech/

   • Useful for how the foundation frames the larger ecosystem.
   • Places Human Network alongside Wallet as a Protocol and Human Passport, which helps show that Human Network is a substrate beneath broader personhood, wallet, and identity products.

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

   • Useful for the short, product-level summary.
   • Describes the project as a network for creating secure cryptographic keys from familiar authentication methods like web accounts and biometrics.
   • Helpful for comparing the concise marketing surface against the more detailed technical docs.

9. GitHub repository / README — https://github.com/holonym-foundation/human-network and https://raw.githubusercontent.com/holonym-foundation/human-network/main/README.md

   • Most technical first-party material reviewed in this pass.
   • Explains threshold scalar multiplication, DKG, DLEQ proofs, relay coordination, epoch handling, onchain credits, optional semi-trusted nodes, and use cases like private biometrics and programmable decryption.
   • Crucial because it makes the real lower-layer mechanism legible in a way the short docs summaries do not.

Whitepaper / technical-doc status

• No standalone canonical Human Network whitepaper surfaced during this pass.
• The official docs plus the public GitHub README are the main primary-source packet for now.

Why it stays in the active corpus

• It is a strong lower-layer comparison point beneath Human ID, Human Passport, Self Protocol, and related proof systems.
• It helps separate credential issuance and proof UX from the cryptographic service layer that generates keys, nullifiers, or conditional-reveal capability in the first place.
• It introduces distinct control surfaces — relay ingress, operator admission, resharing, optional semi-trusted nodes, and AVS security dependencies — that would be lost if it stayed folded into the broader human.tech brand only.