# Humanode

Dato Kavazi, Victor Smirnov, Sasha Shilina, MOZGIII, Dmitry Lavrenov, and the Humanode Core

## Abstract

The global race toward decentralized financial infrastructure has produced countless innovations - but it remains haunted by a paradox. Despite a desire for decentralization, most networks reproduce the very power structures they aim to dismantle. Whether through Proof-of-Work (PoW) or Proof-of-Stake (PoS), validator access is gated by computational or financial capital, favoring those with the most resources and replicating systemic inequality.

Humanode introduces a radically different model: a biometric-based consensus mechanism known as Proof-of-Biometric-Uniqueness (PoBU). Instead of requiring wealth or hardware, Humanode ties each validator node to a single, verified, living human being - achieved through privacy-preserving cryptobiometric verification.

This creates a Sybil-resistant, egalitarian, and capital-agnostic decentralized network, where one human equals one node, and one vote. The system is designed to preserve privacy, eliminate validator monopolies, and offer a new standard for decentralized governance.

Launched in 2022, the Humanode mainnet has been running without downtime for over 2.5 years, currently hosting over 1,800 human validators, with all nodes weighted equally.&#x20;

This whitepaper describes the philosophical foundation, architecture, consensus design, governance mechanisms, and long-term vision of Humanode - a decentralized financial system powered not by machines or capital, but by the human beings themselves.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.humanode.io/whitepaper/untitled-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
