Summary: Humanode is best cataloged as a biometric-sybil-resistance blockchain rather than as a generic identity project or another Substrate-based chain. Its primary-source surface centers on a privacy-preserving “one human = one node” validator model, with Bioauth and related biometric enrollment/authentication flows gating consensus participation. The whitepaper, validator docs, and GitHub surfaces jointly show a network that is trying to replace capital- or hardware-weighted validator admission with biometric uniqueness, while still exposing practical developer surfaces such as EVM compatibility, Substrate tooling, launcher-based node management, and a biomapper SDK.
What it does:
Runs a blockchain where validator participation is tied to biometric uniqueness instead of proof-of-work hardware spend or proof-of-stake capital concentration
Uses biometric enrollment and recurring authentication flows through Bioauth so a validator node can be linked to a single living human and kept active over time
Provides validator-facing tooling including a launcher app, node software, validator guides, wallet setup instructions, and biometric enrollment/authentication flows
Exposes developer-facing surfaces including EVM compatibility, Solidity smart-contract support, Substrate-oriented tooling, JSON-RPC access, and a biomapper SDK
Maintains open-source node code and supporting tooling through a public GitHub organization centered on Rust/Substrate infrastructure
Key claims:
The official whitepaper frames Humanode as a response to the way PoW and PoS systems reproduce resource-based inequality, and describes its alternative as Proof-of-Biometric-Uniqueness (PoBU)
The whitepaper abstract says Humanode ties each validator node to a single, verified, living human through privacy-preserving cryptobiometric verification, creating a network where “one human equals one node, and one vote”
The whitepaper also claims the mainnet launched in 2022, has run without downtime for over 2.5 years, and currently hosts over 1,800 human validators with equal weighting
The official docs say someone becomes a validator by running a node, enrolling biometrically, authenticating with their phone, and then waiting for the next session to appear in the validators list
The validator/Bioauth docs emphasize that biometric verification is not a one-time marketing claim but an ongoing gate on consensus participation: one human can only run one participating node, authentication expires after a period, and going offline can void Bioauth early
The docs and GitHub surfaces show that Humanode is not only a consensus experiment: it also exposes an EVM-compatible development surface, launcher UX, node software, and biomapper tooling for applications
Whitepaper: Humanode maintains an official whitepaper at https://whitepaper.humanode.io/. In practice, the clearest current source of truth is the combination of the whitepaper, validator/Bioauth docs, developer docs, and GitHub organization; see ../whitepapers/humanode-primary-sources-2026-04-28.md.