> 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/changelog/2026-09-03-token-app-tokenomics-and-deployment-registry.md).

# 2026-09-03 — Token app, tokenomics & deployment registry

## Added

* Canonical 18,446,000,000 SONIC allocation reference with exact allocation amounts.
* Token application MVP status matrix covering policy, deployment registry, production mint, rewards/claims, pre-sale, Raydium/Meteora, Jupiter routing, Streamflow lock, governance and burn.
* Creator Rewards state model: estimated → eligible → allocated → claimable → submitted → confirmed → settled → reconciled.
* Compact SONIC Token Reference implementation map.
* Deployment-controlled token identity and token metadata boundary.
* Expanded SONIC token API contracts for status, deployment, metadata, market, supply and rewards.
* Monorepo token upgrade boundaries for `types/tokens.ts`, token policy, deployment registry, token metadata and `/programs/` scaffolding.

## Security / production truth

SONIC-owned mint and program IDs remain deployment-generated. They must not be invented in source code, documentation or frontend configuration.

Canonical verification:

```
SONIC deployment registry
→ expected mint / token program / decimals / authorities
→ Solana RPC verification
→ product feature status
```

Canonical value-moving flow:

```
session / auth context
→ access / entitlement checks
→ verified wallet where required
→ quote / policy
→ TransactionIntent
→ signature
→ submission
→ confirmation
→ effect verification
→ settlement
→ reconciliation
```

## Production activation invariant

```
policy
+ verified deployment
+ authorized product configuration
+ explicit user intent where value moves
+ chain verification
+ settlement
+ reconciliation
= production-valid token capability
```

The token application remains early-phase until applicable capabilities are explicitly marked Live/Verified.


---

# 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/changelog/2026-09-03-token-app-tokenomics-and-deployment-registry.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.