# What is the zkProofer Node

The zkProofer Node is one of the core components of Humanity's decentralized identity verification infrastructure. It serves as the verification engine that powers the network's trust layer.

### Network Architecture

Humanity's verification infrastructure consists of three fundamental components:

**Issuers** Trusted entities—such as governments, universities, or organizations—that create and sign Verifiable Credentials (VCs) for users. Issuers provide cryptographically secure, tamper-proof digital representations of user claims.

**zkProofer Nodes** Lightweight verification workers that validate credentials and proofs on behalf of requesting applications. They ensure the integrity, validity, and privacy of Verifiable Credentials without accessing underlying personal data.

**DApps / Verifiers** Applications that request verification of user attributes, define verification policies, and pay verification fees to the network.

## What zkProofer Nodes Are

zkProofer Nodes are **lightweight verification workers** powering Humanity's decentralized trust network. They are **not blockchain validators** and do **not** produce blocks or maintain chain state.

Instead, zkProofer Nodes:

* Receive verification requests from applications
* Validate cryptographic proofs and credential policies
* Return signed verification results
* Earn rewards and fees for correct participation

In the fully ZK end state, zkProofer Nodes verify zero-knowledge proofs using public parameters—confirming claims (e.g., "user is over 18") without accessing any underlying personal data.

## Key Responsibilities

**Credential Verification** Execute cryptographic checks to validate the digital signature on a Verifiable Credential, confirming it was issued by a legitimate and authorized Issuer.

**Status Checking** Verify the current status of a credential by checking against revocation lists to ensure it has not been revoked by the Issuer.

**Condition Evaluation** Process and evaluate custom verification policies set by DApps (e.g., "Is the user over 18?") and return a binary result (True/False).

**Consensus Participation** Work collaboratively with other randomly selected zkProofer Nodes to reach consensus on the validity of a credential, ensuring the decentralized trust model.

### Why zkProofer Nodes?

Humanity is the **trust layer of the internet**—enabling applications to verify facts about users without relying on centralized authorities or exposing personal data. zkProofer Nodes are the mechanism that decentralizes this trust across many independent operators.

### Smart Contracts

* Node License NFT Contract: \[Address TBD]
* Sale Contract: \[Address TBD]
* Treasury Contract: \[Address TBD - multi-sig]
* Reward Distribution Contract: \[Address TBD]
* Audit Status: \[TBD - Firm name, completion date]

\
\
[Node Reward Distribution](/zkproofer-node/what-is-the-zkproofer-node/node-reward-distribution.md)


---

# 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://docs.humanity.org/zkproofer-node/what-is-the-zkproofer-node.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.