> For the complete documentation index, see [llms.txt](https://aetherservice.gitbook.io/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aetherservice.gitbook.io/about/incentive-design-and-network-economics/sustainable-economic-framework.md).

# Sustainable Economic Framework

The economic sustainability of the Aether network is based on the principle that tokens are **not pre-mined** and are created only when **real network value emerges**. This value is represented by confirmed, useful traffic from external consumers via the distributed node network. The core of the system is the **Proof-of-Demand (PoD) mechanism**, which determines issuance volumes in each cycle based on real bandwidth demand, rather than simply the number of connected devices.

### Proof-of-Demand (PoD) Formula

Token emission per epoch is calculated as:

```
Mint_epoch = Σ(Bᵢ × Qᵢ × Sᵢ × DDM_region × DDM_global × K)
```

* **Bᵢ** – confirmed traffic per node, only including validated, legitimate requests, excluding internal noise.
* **Qᵢ** – channel quality factor, accounting for jitter, packet loss, latency, and bandwidth stability. High-quality channels earn proportionally more tokens per byte.
* **Sᵢ** – node uptime stability coefficient, rewarding nodes with consistent operation.
* **DDM\_region / DDM\_global** – regional and global demand multipliers, scaling rewards in areas with high demand.
* **K** – dynamic "token-per-byte" constant, adjusted according to network load and liquidity conditions.

This ensures that **token issuance is strictly proportional to actual network utility**.

### Adaptive Minting Constraint (AMC)

To maintain stability, AMC limits emission changes between **40%–160% of the previous period**, with dynamic elasticity ±15%. This allows the system to respond smoothly to demand fluctuations:

* If demand grows faster than network capacity, K decreases → lower emission per byte.
* If demand drops, K adjusts upward → rewards continue without liquidity shortages.

### Deflationary Pressure System (DPS)

DPS introduces automatic deflationary measures:

* **Overload burn:** 2–7% of tokens burned if network demand exceeds 90% of capacity.
* **Activity burn:** 20% of unused rewards burned if a node remains inactive >45 days.

These mechanisms enforce **natural selection**, distributing tokens only to nodes delivering real value.

### Dynamic Reward Rebalancing (DRR)

DRR redistributes rewards based on network performance indicators:

NSI = (load\_peak / load\_avg) × jitter\_avg × failover\_rate

* High-stability nodes → higher reward coefficients.
* Low-stability/fluctuating nodes → lower rewards.

This prevents inefficient connections from consuming undue token emission.

### Long-term Equilibrium Mechanism (LEM)

LEM monitors moving averages over 90 days for:

* Emission levels
* Token turnover speed
* Network load

LEM dynamically adjusts AMC, DPS, and DRR to maintain **economic balance**, automatically lowering emission when demand is low and triggering burns during overheating.

### Nexus Liquidity Reserve (NLR)

NLR is a liquidity buffer sourced from emission, fees, and corporate payments:

* Smooths market fluctuations
* Ensures liquidity during spikes
* Enables token buybacks
* Protects staking pools

This guarantees network stability during demand volatility.

### Summary

All elements—**PoD, AMC, DPS, DRR, LEM, and NLR**—work together to:

* Regulate token supply growth
* Adjust rewards according to real network load
* Control deflation
* Ensure long-term token sustainability

The Aether token thus becomes a **direct reflection of actual network utility**, ensuring value growth aligns with infrastructure use.


---

# 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:

```
GET https://aetherservice.gitbook.io/about/incentive-design-and-network-economics/sustainable-economic-framework.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.