> 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/deploy-a-node-in-home.md).

# Deploy a Node (In-Home)

**TLDR:**

* Easiest way to start: bring a real connection online with standard hardware + keep monitoring on.
* Great for first deployments, neighborhood sharing, and building history before rooftops.
* Requirements: Black Box-family hardware + any real upstream + safe stable placement + stay online consistently.

\
In-home nodes are the easiest way to start deploying with DAWN. You bring a real, measurable internet connection online using DAWN’s standard hardware, register it, and keep monitoring enabled so performance can be verified over time.

\
In-home deployments are ideal for: 

* Starting small with your first deployment
* Local sharing / neighborhood distribution
* Building measurable performance history before expanding to rooftops

## **What you need:**

1. Hardware: A device from the Black Box Family as your routing + measurement layer.
2. An upstream connection: A node can get internet from many sources (home broadband, business broadband, fiber handoff, fixed wireless, etc.). Any source is acceptable as long as it is real and provable with measurement.
3. Basic install readiness: Reliable power, safe placement (ventilation, stable location), and ability to keep it online consistently.

 

### **Step-by-step:**

1. Acquire hardware: Purchase through the official store: [shop.dawninternet.com](https://shop.dawninternet.com/)
2. Install + safety checks: 

* Set up your device and confirm stable power, safe placement, proper ventilation (avoid enclosed heat), and consistent location (don’t move it around to ensure stable scoring)  

3. Register your node + deployment metadata

* Provide the minimum information the network needs to represent your node as a source of truth:
  * Site/deployment identifier
  * Location / coverage context (where applicable)
  * Hardware class / capabilities
  * Operator/owner identity and payout destination

4. Run baseline validation

* Before listing capacity/offers, run a baseline window so the system can establish an initial performance profile:
  * Uptime consistency
  * Throughput under normal conditions
  * Latency and loss stability

5. Enable monitoring

* Monitoring must remain on so performance is time-weighted and auditable rather than one-off speed tests.

6. Go live

* Once the node is registered and baseline performance is established:
  * Create your listing/offer (service commitments + constraints)
  * Start serving traffic (subscribers and/or downstream nodes)

7. Maintain + iterate

* Reliable operators win over time:
  * Monitor performance
  * Fix bottlenecks (backhaul, interference, misconfiguration)
  * Expand where demand is proven (add capacity, densify, or extend coverage)

### **Best practices (in-home)**

* Consistency beats bursts: staying online reliably matters more than occasional high speeds.
* Avoid measurement distortions: VPN/proxy setups and unstable routing can hurt consistency.
* Don’t game measurements: spoofing or misreporting reduces eligibility and attribution.