> For the complete documentation index, see [llms.txt](https://docs.infrastructure.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infrastructure.finance/participate/validate-the-network.md).

# Validate the Network

Validation is how DAWN prevents spoofed coverage and claims-based rewards. Validators measure real-world performance and attest to it over time so rewards and settlement track delivery, not promises.

## **How Validation works**

* Validation is time-weighted: persistent contribution over time is more important than single tests.
* DAWN supports multiple validator surfaces, ranging from lightweight to high-reliability hardware validation.<br>

### **What you’re doing when you validate**

You are contributing to DAWN’s Proof of Bandwidth: verifying that claimed service is real and sustained, and that performance is consistent across time and independent measurement surfaces. <br>

### **Choose your validation surface**

1. Chrome Extension: Lightweight endpoint validation during normal usage.
2. Desktop App: More persistent monitoring.
3. Black Box validation: Stable hardware layer that improves measurement consistency.
4. Black Box 2U (serious validators): Higher uptime expectations and higher reward ceiling.&#x20;

### **How to validate**

1. Install + authenticate on your chosen surface.
2. Keep a stable network environment

* Avoid VPN/proxy setups that distort routing/latency.
* Avoid changing networks/devices if you want consistent scoring.

3. Stay online consistently

* Validation is time-weighted; consistency beats occasional bursts.

4. Let measurements run over time

* The goal is confidence over windows, not one speedtest.

5. Track your validator score + rewards dashboard

* Rewards are driven by uptime, reliability, and consistent measurement contribution over time.

### **Validator operational expectations**

* Meet minimum uptime requirements
* Keep software updated
* Don’t attempt to manipulate measurements (anti-spoofing and misreporting controls apply)

### **Best practices**

* Keep your validator online consistently.
* Avoid setups that distort measurements (unstable routing / configurations that artificially change latency).
* Focus on reliability: the system values consistent contribution.&#x20;

### **How rewards are determined**

Rewards are determined by:

* Uptime + reliability&#x20;
* Consistency of measurement contribution over time
* Meeting minimum operational requirements