> 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/allocation-and-supply-states.md).

# Supply Accounting

Canonical SONIC supply-state model separating intended maximum, allocation, custody, locks, unlocks, circulation, claims and burns.

## Source of truth

The exact distribution percentages and amounts live only on SONIC Tokenomics & Distribution. This page defines **state semantics** and intentionally does not duplicate the distribution table or pie charts.

## Canonical supply sequence

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

A token can remain in the same economic allocation while changing operational state. Allocation therefore does not prove custody, lock status, unlock state or circulation.

## State model

| State                  | Meaning                                                       | Production evidence                                  |
| ---------------------- | ------------------------------------------------------------- | ---------------------------------------------------- |
| Initial maximum supply | Approved genesis maximum of **18,446,000,000 SONIC**          | Policy + verified mint state                         |
| Allocated              | Assigned to an approved economic bucket                       | Versioned tokenomics policy                          |
| Custodied              | Held by an identified treasury, program or controlled account | Verified account ownership + balance                 |
| Locked / vesting       | Restricted by an enforceable lock/vesting schedule            | Verified Streamflow or other approved schedule state |
| Unlocked               | No longer restricted by the applicable schedule               | Verified release state                               |
| Liquidity              | Intentionally committed to verified market liquidity          | Verified pool/account state                          |
| Claimable rewards      | Funded allocation approved for a specific eligible recipient  | Reward ledger + eligibility + funding                |
| Circulating            | Supply meeting the approved circulation methodology           | Reconciled chain/account data                        |
| Burned                 | Supply permanently removed under approved burn policy         | Verified burn transaction + supply reconciliation    |

## Streamflow locked supply

Policy designates **3,000,000,000 SONIC**, equal to **16.26%** of the initial maximum supply, for Streamflow-based locking.

This is a **supply state, not an extra allocation**. Source allocation(s), beneficiaries, lock/vesting type, dates, cadence and Streamflow identifier remain TBA until approved and verified.

## Reporting rules

* Do not infer circulating supply from allocation percentages.
* Do not report the 3,000,000,000 SONIC as verified locked supply until Streamflow state is verifiable on-chain.
* Do not count a reward estimate as allocated or claimable.
* Do not infer burned supply from the 2% policy; reconcile actual burn transactions.
* Do not treat a treasury address as funded custody without balance and authority verification.
* Do not publish a distribution visual that implies live circulation when the underlying values are policy-only.

```
allocation ≠ custody ≠ unlocked ≠ liquidity ≠ circulating ≠ claimable ≠ burned
```


---

# 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/allocation-and-supply-states.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.