> 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-rooftops.md).
# Deploy a Node (Rooftops)
(Images: DAWN Rooftop Antenna Deployments in Ghana)
**TLDR:**
* Deployment includes: aligning a plan → deploy on-site → bring on-chain → register node metadata.
* Before listing offers: run a baseline validation window and keep monitoring enabled.
* Go live by creating your listing (commitments/constraints), then maintain + iterate based on performance.
DAWN rooftop nodes bring real wireless infrastructure online in a way the network can measure, verify, and attribute over time. Rooftop deployments are designed to create real coverage and real subscriber revenue inside a measurable line-of-sight (LoS) footprint.
To deploy a DAWN Rooftop Node, the process is as follows: sign up -> deploy → register → validate → go live → maintain. (See: [Join the Deployer Network](/build/deployer-network.md))
Deploying a node means bringing real wireless infrastructure online in a way the protocol can measure, verify, and attribute over time.
## **What is a Rooftop Node?**
DAWN installs antennas on building rooftops that connect wirelessly to other buildings and antennas. This enables cost-effective internet service to households within line-of-sight of the coverage area.
Rewards depend on:
* Level of support you provide
* Rooftop height / LoS quality
* Population density in the covered area\
### **Hardware overview (fixed wireless rooftop antennas)**
* Long-range gear can send gigabit internet up to \~6km and \~500 Mbps up to \~10km.
* DAWN can work with most local antennas/radios (the key requirement is router configuration + measurability).
Common rooftop antenna types (examples):
* Short range (\~1km)
* Medium range (1–2km per 90° sector)
* Long range (gigabit speeds up to \~6km; \~500 Mbps up to \~10km, per 90° sector)
Physical notes:
* Antennas are roughly \~60cm x 72cm and normally attached to a \~3m pole
* They connect to customer sites using point-to-multipoint connections
* Taller rooftops vs the surrounding area usually means more LoS households covered
### **Step-by-step: Rooftop Deployment**
1. Join the Deployer Network
* See: [Join the Deployer Network](/build/deployer-network.md)
2. Identify the right rooftop sites where:
* LoS to meaningful household density is strong
* You can secure roof access + install permissions
* Power + mounting is feasible
* You can keep the site online reliably
3. Site review + coverage modeling
* Submit your candidate sites to DAWN for coverage and deployment feasibility review.
4. Commercial proposal
* DAWN provides proposed deployment economics, requirements, and next steps.
5. Partnership agreement
* Finalize the applicable deployment agreement with DAWN.
6. Physical deployment
* DAWN creates the deployment plan and aligns on next steps:
* On-site deployment
* Bring the network on-chain
7. Register your node + deployment metadata
* Provide the minimum info needed for the network to treat this deployment as a source of truth:
* Site/deployment identifier
* Location / coverage context
* Hardware class / capabilities
* Operator/owner identity + payout destination
8. Baseline validation + monitoring
* Before listing capacity/offers:
* Run a baseline window (uptime, throughput, latency/loss)
* Enable monitoring and keep it on (time-weighted measurement)
9. Go live
* Once registered and baseline is established:
* Create your listing/offer (service commitments + constraints)
* Start serving subscribers and/or downstream nodes
10. Maintain + iterate
* Monitor performance and uptime
* Fix bottlenecks (interference, backhaul, misconfiguration)
* Expand only where demand is proven
### **Next Steps**
Ready to take your DAWN deployments to the next level?
See: [Service an entire Building](/participate/service-an-entire-building.md)
### **Operational expectations**
* Nodes are expected to remain online consistently.
* Repeated downtime, spoofing, or misreporting reduces attribution and eligibility for incentives.
* DAWN doesn’t require a specific upstream type—only that claimed connectivity is real and provable with measurements.
## **Deployer Network**
Deployers expand DAWN by sourcing locations, coordinating installs, onboarding deployments to operator standards, and ensuring each deployment is measurable and maintainable. (See: [Join the Deployer Network](/build/deployer-network.md))
### **Referral economics (local partner introductions)**
For referrals to local partners, DAWN offers internet revenue share.
When entering a new market, we are searching for real estate partners to generate internet revenue and a local telecoms partner to handle the operational and technical side locally.
DAWN has two main value propositions:
* Allow Real Estate companies to sell Internet directly to tenants inside their property and set up new revenue streams outside their building footprint with rooftop antennas.
* Allow Telecommunications companies to automate payments with blockchain technology and to earn from the downstream revenue share of the last mile