> For the complete documentation index, see [llms.txt](https://deepnode.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deepnode.gitbook.io/docs/ecosystem/incentive-mechanism/validators.md).

# Validators

Validators secure DeepNode’s execution layer by verifying miner outputs, enforcing model correctness, and ensuring that all tasks in the network meet the required quality thresholds.

The flow below outlines how validators participate in the incentive loop:

<figure><img src="/files/vbMiJXW8DrRk0T4GPJJh" alt=""><figcaption></figcaption></figure>

***

### **1. Role of Validators**

See [Roles](/docs/platform/roles.md#validators) for a more in depth description.

***

### **2. Incentive Flow**&#x20;

The validator incentive system works through a structured pipeline:

#### **Step 1: Tasks Enter the Domain**

Consumers generate model request via the platform or API.

#### **Step 2: Miners Process Tasks**

Miners perform the compute work and submit their results.\
These results are forwarded to validators for auditing.

#### **Step 3: Validators Run Verification**

Validators check whether miners outputs are correct.

* **If validation is correct:**\
  → The task is approved\
  → Rewards are emitted to all relevant actors (miners, validators, creators/backers)
* **If validation fails:**\
  → Miner trust score is reduced\
  → Validators notify the domain\
  → The task may be reassigned or penalized depending on severity

#### **Step 4: Reward Emission**

When validators approve a task, the reward engine triggers:

* Miners receive their utility-weighted reward
* Validators receive their share of emission
* Stakers receive a share proportional to their stake
* The domain receives its revenue allocation
* Model owners/backers receive their configured share

#### **Step 5: Staking and Delegation**

Validators are strengthened by stakers who delegate their $DN to validator operators.\
Delegators earn a percentage of validator rewards, and validators accumulate trust and influence proportional to delegated stake.

This ensures:

* long-term alignment
* economic security
* a robust and decentralized validator set

***

### **3. Fee Routing**

As shown in the diagram:

* A portion of revenue (y%) flows into Fees & Payment Processors
* A portion of fees may route to Variable Burn (d%) depending on network governance

{% hint style="info" %}
For a complete overview of fees in the network see: [Fees](/docs/ecosystem/fees.md).
{% endhint %}

***

### **4. Why Validators Matter**

Validators:

* ensure correctness
* maintain economic sustainability
* prevent manipulation
* preserve model integrity
* protect users from malicious outputs
* participate in governance

They are the backbone of the entire $DN incentive mechanism.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://deepnode.gitbook.io/docs/ecosystem/incentive-mechanism/validators.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
