# $OPN Tokenomics

With a **fixed supply**, transparent distribution model, and strong utility across staking, rewards, and reputation-building, $OPN is designed to power the Internet of People - not inflate and fade.

***

### Total Supply

**Total Max Supply**:\
&#x20;**25,000,000,000 OPN** (25 Billion tokens)

This is the **maximum supply cap** - no more tokens will ever be created. $OPN is deflationary over time due to the burn mechanics built into rewards redemption.

***

### Token Distribution

| Category            | Allocation    | Purpose                                                                 |
| ------------------- | ------------- | ----------------------------------------------------------------------- |
| **Presale**         | 2,000,000,000 | Sold via Manager contract in transparent batch pricing ladder           |
| **Public Sale**     | 5,500,000,000 | Reserved for future ecosystem expansion and public onboarding           |
| **Staking Rewards** | 2,500,000,000 | Used to reward long-term token lockups and loyalty participants         |
| **Validator Round** | 2,500,000,000 | For securing the OPNChain network and incentivizing node operation      |
| **Foundation**      | 1,250,000,000 | Managed by the IOPn Foundation to support ecosystem development         |
| **Team & Advisors** | 3,750,000,000 | Vested long-term to align contributors and builders with the protocol   |
| **Marketing**       | 1,750,000,000 | Campaigns, brand partnerships, ambassador programs                      |
| **Liquidity**       | 2,500,000,000 | DEX and CEX liquidity provisioning                                      |
| **Ecosystem**       | 1,750,000,000 | Strategic partnerships, grants, integrations                            |
| **Treasury**        | 1,500,000,000 | Protocol-managed for reserves, future governance, and ecosystem support |

***

### Vesting & Controls

* **Team/Advisor tokens** are on **long-term vesting schedules**
* **Validator incentives** and **staking rewards** are distributed programmatically
* All major categories are governed by **multisig or DAO-controlled wallets**
* The **presale and staking mechanisms** are fully on-chain and transparent

> No backdoors. No silent unlocks. Full transparency from day one.

### Emission Schedule

<figure><img src="/files/pTgvumwrGnYA5mPz52DH" alt=""><figcaption></figcaption></figure>

***

### Deflationary Pressure via Burning

A unique aspect of $OPN is its **redemption-based burn model**:

* When users redeem merch, NFTs, or visa access via their **NeoCard**, they must **burn OPN tokens**
* This rotates the tokens back to the treasury.
* Over time, this creates **natural deflation**, increasing scarcity as adoption grows

Every burn is **on-chain, trackable, and tied to identity-based actions** - reinforcing reputation and long-term value.

***

### Utility-Backed, Not Speculation-Driven

$OPN is not built for hype cycles - it's built for:

* Loyalty rewards (NeoPoints)
* Stake-based yield
* Reputation and identity (NeoCard + NeoID)
* On-chain governance (coming soon)
* Real-world perks (merch, events, residency)
* In-game and app-layer utility across IOPn partners

This **multi-utility structure** ensures $OPN is used, not just traded.

***

### Security & Governance

* Pricing logic, referrals, and NeoPoint issuance are handled by **auditable smart contracts**
* Future governance proposals will be **token-weighted**, empowering the community to shape protocol upgrades, funding, and priorities

***

***


---

# 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://iopn.gitbook.io/iopn/usdopn-the-fuel-of-iopn/usdopn-tokenomics.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.
