> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/sonic-tokenomics.md).

# SONIC Tokenomics

Canonical SONIC v1.0.0 pre-deployment economic-policy index for Token-2022 supply, distribution, token sales, fees, markets, locks, burns, Creator Rewards and deployment verification.

**Version `1.0.0` · PRE-DEPLOYMENT · Solana Token-2022**

{% hint style="warning" %}
This section is the canonical economic-policy source. Policy and planning values are not deployment proof. Production mint, authorities, sale provider/contract, Token-2022 `maximumFee`, Streamflow positions, market pools and burn execution remain unavailable until independently verified.
{% endhint %}

SONIC is designed as the utility token of SONIC NETWORK for creator rewards, ecosystem participation, supported tokenized-content workflows, platform utility and creator commerce. Token utility does not guarantee market value or investment return.

## Policy at a glance

| Policy                            |                                 Canonical / planning value |
| --------------------------------- | ---------------------------------------------------------: |
| Initial maximum supply            |                                   **18,446,000,000 SONIC** |
| Decimals                          |                                                      **9** |
| Launch Token-2022 transfer fee    |                                           **2% / 200 bps** |
| SONIC transfer-fee policy ceiling |                                           **5% / 500 bps** |
| Token-2022 `maximumFee`           |                                                    **TBA** |
| Quarterly burn policy             |                              **2% · calculation base TBA** |
| Streamflow lock designation       |                           **3,000,000,000 SONIC / 16.26%** |
| Creator Rewards allocation        |                              **10% / 1,844,600,000 SONIC** |
| Pre-sale stage                    |                               **Q4 2026 target · planned** |
| Pre-sale price reference          |                                    **\~$0.000002 / SONIC** |
| Pre-sale inventory                | **\~3–5B SONIC planning envelope; source allocations TBA** |
| Initial DEX reference             |                                   **\~$0.0000025 / SONIC** |
| Production mint                   |                                                    **TBA** |

## Read by domain

* **Distribution** — the one canonical allocation table; no pie-chart duplicate.
* **Supply Accounting** — maximum, minted, allocated, locked, circulating and burned states.
* **Token Sales** — Q4 2026 pre-sale planning, PinkSale/Smithii.io evaluation, success/refund logic and risk disclosures.
* **Markets & Liquidity** — Raydium/Meteora/Orca pool policy, Jupiter routing and liquidity-depth controls.
* **Transfer Fees** — 200 bps launch setting, 500 bps policy ceiling and fee-domain separation.
* **Rewards & Claims** — funded eligibility, claims, settlement and reconciliation.
* **Governance, Strategic Lock & Burn** — authority, Streamflow and burn boundaries.
* **Deployment & Verification** — evidence required before product activation.

## Supply invariant

```
Initial Maximum Supply
→ Allocated Supply
→ Locked / Unlocked Supply
→ Circulating Supply
→ Burned Supply
```

`lockedSupply ⊆ allocatedSupply` and `saleInventory ⊆ allocatedSupply`. Neither the Streamflow designation nor sale inventory creates additional supply.

## Sale and market boundary

```
planned sale terms
→ approved source inventory
→ verified sale provider/contract
→ successful or refunded sale outcome
→ verified liquidity bootstrap
→ factual DEX routing
→ reconciled market state
```

A planned price is not a price floor. A successful pre-sale does not guarantee liquidity, a DEX route, Binance/Alpha support, a centralized-exchange listing or future value.

## Canonical implementation boundary

```
approved tokenomics policy
→ shared/token/*
→ /api/v1/token/* and /api/v1/token-sales/*
→ Token page / Dashboard / Storefront / SDK / Docs
→ deployment registry
→ finalized Solana verification
```

Amounts use decimal-safe strings or integer/bigint atomics. **Lamports are SOL units only**; SONIC uses 9-decimal token atomic units.

## No duplicated specification

Detailed technical/deployment fields live in **Token Reference**, **Deployment & Verification**, **Tokenomics Architecture & Trust Model**, and developer program documentation. Distribution values live only on **Distribution**.


---

# 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, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/sonic-tokenomics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.