# Utility-Driven Demand & Built-In Scarcity

The $COR token is more than just a medium of exchange. Its design ensures **continuous demand** while embedding **structural scarcity** into the network. This balance drives sustainable tokenomics and aligns incentives across developers, miners, and users.

***

### 1. Developer Staking for Free Quotas

* Developers can **stake $COR** to unlock free inference quotas for their applications.
* The more $COR staked, the more free calls an application can make.
* **Additional usage** beyond the free quota requires either increasing the stake or paying in a **pay-as-you-go** model.
* Each new application effectively **locks more $COR out of circulation**, directly tying network growth to token demand.

***

### 2. Miner Staking & Burn Mechanics

* **Node operators** are required to stake $COR, with **higher-capacity nodes** demanding larger stakes.
* **Usage and gas fees** collected in $COR are partially burned, permanently reducing circulating supply.
* This mechanism introduces **deflationary pressure** that scales with network activity.

***

### 3. Compounding Scarcity

The combined effects of staking and burning create a **compounding scarcity cycle**:

* **Developer Staking** → locks tokens for application quotas.
* **Miner Staking** → locks tokens for capacity provisioning.
* **Burns from Usage** → remove tokens from circulation permanently.
* **More Apps → More Usage → Faster Supply Reduction**.

This dynamic ensures that **network adoption directly amplifies token scarcity**.

***

### Activation Timeline

* These mechanics are **fully activated at L3 mainnet** launch.
* Early effects are already observable in **testnet environments**, as developer and miner staking begins to shape token flows.

***

### Key Takeaway

$COR is designed as both a **utility token** (fueling AI tasks and sessions) and a **scarcity-driven asset** (through staking and burns). This dual role ensures that **growth in network usage directly strengthens token value fundamentals**, anchoring Cortensor’s long-term sustainability.


---

# Agent Instructions: 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://docs.cortensor.network/community-and-ecosystem/ecosystem-flow/utility-driven-demand-and-built-in-scarcity.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.