> 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/network-architecture/the-new-protocol-stack.md).
# The New Protocol Stack
**TLDR:**
* DAWN’s “consensus” is agreeing on service delivery quality instead of block ordering.
* Four roles coordinate the system: Operators, Deployers, Subscribers, Validators.
* Two loops drive everything: service loop (connectivity → measurement → verification → attribution) and growth loop (cashflows → financing → more deployments).
* “Proof of Bandwidth” = sustained, real service verification to prevent spoofed listings and reward delivery.
* Sequencing is staged: Network → Capital (USD.infra Vault) → Token layer.
DAWN is building a new protocol stack designed from the ground up for open-air media, autonomous resource allocation, and the cryptographic protection necessary for a network built without trust.
At a high level, DAWN turns real-world connectivity into verifiable delivery so the network can coordinate supply, measure performance, and settle incentives and payouts based on what was actually delivered and not just what was promised.
## **Protocol Design**
DAWN’s protocol design is organized around roles that produce, consume, and verify service:
* Operators provide real wireless connectivity and publish offers to serve traffic.
* Deployers expand coverage by installing hardware and onboarding new locations.
* Subscribers purchase service and generate recurring telecom cashflows.
* Validators measure performance and attest to delivery over time.
These roles form two reinforcing loops:
1. Service loop: connectivity → measurement → verification → attribution
2. Growth loop: proven deployments + recurring cashflows → scalable financing → more deployments
The USD.infra Vault is the capital layer that accelerates the growth loop by routing capital into deployments through the Vault and SPVs, then returning contracted cashflows back into the Vault for all participants.
## **Consensus Mechanism**
Rather than block ordering, DAWN’s consensus is about converging on a high-confidence view of service delivery so the protocol can differentiate reliable supply from spoofed or degraded supply.
In practice, this relies on:
* Multi-surface measurement (user endpoints + dedicated validator surfaces).
* Time-weighted performance (performance over windows, not one-off tests).
* Sybil resistance and anti-spoofing assumptions.
* Penalties / reduced attribution for sustained poor performance or misreporting.
## **Tokenomics**
DAWN’s sequencing is intentionally staged:
Network → Capital → Token layer
* **Network layer:** deployments + subscribers + measurable service delivery.
* **Capital layer (USD.infra Vault):** digital infrastructure-native stable asset + shared vault + SPVs + transparent exchange rate and liquidity management.
* **Token layer:** longer-term incentive and coordination surfaces once unit economics and verification are proven.
## **Proof of Bandwidth**
Proof of Bandwidth is sustained, real service verification that prevents spoofed listings and rewards consistent delivery (further explanation can be found in the [Validators section](/connectivity/validators.md)).
The protocol coordinates four roles — Operators, Deployers, Subscribers, and Validators. Each plays a distinct part in turning real-world connectivity into verifiable service.
