> 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/distribution.md).

# Distribution

The single canonical SONIC v1.0.0 allocation table. No pie chart, no double-counting of Streamflow locked supply, and sale inventory must come from existing allocations.

**Version `1.0.0` · PRE-DEPLOYMENT**

This page is the **single source of truth for SONIC allocation percentages and amounts**. Other pages should link here rather than copy the complete distribution table.

## Canonical distribution

| Allocation             |    Share |              SONIC | Release model    |
| ---------------------- | -------: | -----------------: | ---------------- |
| Ecosystem & Community  |  **20%** |  **3,689,200,000** | Programmatic     |
| Protocol Treasury      |  **20%** |  **3,689,200,000** | Controlled       |
| Core Contributors      |  **15%** |  **2,766,900,000** | Vesting          |
| Creator Rewards        |  **10%** |  **1,844,600,000** | Reward programs  |
| Liquidity & Markets    |  **10%** |  **1,844,600,000** | Liquidity policy |
| Strategic Partners     |  **10%** |  **1,844,600,000** | Vesting          |
| Community Distribution |  **10%** |  **1,844,600,000** | Programmatic     |
| Foundation & Grants    |   **5%** |    **922,300,000** | Milestone-based  |
| **Total**              | **100%** | **18,446,000,000** |                  |

## Reconciliation invariant

```
Σ allocation percentages = 100%
Σ allocation amounts = 18,446,000,000 SONIC
```

{% hint style="info" %}
**3,000,000,000 SONIC / 16.26%** is designated for Streamflow-based lock/vesting infrastructure. This amount is contained within existing allocations. It is **not** an additional allocation and must not be added to the total above.
{% endhint %}

## Token-sale funding overlay

The Q4 2026 pre-sale currently uses a **planning envelope of \~3–5 billion SONIC**. That amount is **not a new allocation**. Before sale activation, governance/policy must identify exactly which existing allocation(s) fund the sale and how much each contributes.

```
saleInventoryAtomic
≤ funded amount from approved existing allocations
```

The final sale mapping must satisfy all of the following:

* total allocation remains **100% / 18,446,000,000 SONIC**;
* the same inventory cannot be counted simultaneously as sale inventory, liquidity inventory, reward inventory or another funded use unless the state model explicitly shows the transition;
* Streamflow locks remain a supply-state overlay and may overlap an allocation only when the exact locked position is identified;
* unsold sale inventory returns to an approved allocation/custody state under the final sale policy; and
* changing source buckets or their percentages requires a versioned Tokenomics policy update rather than a hidden sale configuration change.

## Visualization policy

The canonical docs intentionally use a **table and textual summary rather than a pie chart**. Any future visualization must render from the same machine-readable distribution data and must not become an independent source of values or imply circulation/unlock state.

## Release-state rule

Allocation does not imply custody, unlock, circulation, sale availability or claimability. See **Supply Accounting** for state semantics, **Token Sales** for the planned sale overlay and **Deployment & Verification** for production evidence.


---

# 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/distribution.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.