> 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/deployment-and-verification.md).

# Deployment & Verification

Production deployment and verification requirements for SONIC Token-2022 fixed-supply genesis, authority revocation, approved extensions, assets and signed activation.

## Pre-deployment state

| Field                             | Current policy / status          |
| --------------------------------- | -------------------------------- |
| Network                           | **Solana mainnet-beta**          |
| Token standard                    | **Token-2022**                   |
| Fixed genesis supply              | **18,446,000,000 SONIC**         |
| Decimals                          | **9**                            |
| Atomic genesis supply             | **18,446,000,000,000,000,000**   |
| Production mint                   | **TBA**                          |
| Token-2022 transfer-fee extension | **Disabled**                     |
| Mint authority after genesis      | **None / permanently revoked**   |
| Freeze authority after genesis    | **None / permanently revoked**   |
| Metadata identity                 | **Refined Wave Pillars / SONIC** |
| Genesis allocation root           | **TBA until ceremony**           |
| Signed activation release         | **Required**                     |

## Genesis sequence

```
PREPARE
  ↓
create approved Token-2022 mint
  ↓
initialize approved metadata extensions
  ↓
mint exactly 18,446,000,000 SONIC
  ↓
verify exact atomic supply
  ↓
revoke mint authority permanently
  ↓
revoke freeze authority
  ↓
verify finalized chain state
  ↓
publish genesis manifest + hashes
  ↓
independent verification
  ↓
sign production activation release
  ↓
ENABLE SONIC rail
```

Distribution may occur after genesis finalization. The mint authority must not remain active merely because treasury allocation or vesting distribution requires multiple transactions.

## Production verification gate

Production activation requires finalized evidence for:

1. intended `mainnet-beta` cluster;
2. approved mint keypair/address from the ceremony;
3. Token-2022 program ownership;
4. observed decimals equal **9**;
5. exact genesis supply of **18,446,000,000,000,000,000** atomic units;
6. mint authority equals `None`;
7. freeze authority equals `None`;
8. approved extension fingerprint and absence of the Token-2022 transfer-fee extension;
9. canonical metadata pointer and SONIC metadata identity;
10. canonical public asset manifest and metadata hashes;
11. treasury/allocation root and relevant vault registry;
12. genesis transaction evidence;
13. independent verification report; and
14. signed production activation release.

Any failed or unresolved check keeps `SONIC_MAINNET_READY=false`.

## Fixed-supply rule

Token-2022 does not provide a separate native `maxSupply` field. SONIC's fixed supply is enforced by minting the exact genesis amount and then permanently revoking mint authority.

A burn can reduce outstanding supply but cannot create permission to remint burned SONIC.

## Asset publication

The canonical public asset source is:

`https://github.com/sonicaiworks/sonic-token-assets`

The Refined Wave Pillars artwork, token image, metadata JSON and SHA-256 manifest must be versioned and published independently from private deployment keys. Do not place signing keypairs, RPC secrets or production credentials in the public asset repository.

## Publication rule

No TBA value may be silently replaced with a mock mint, devnet mint, guessed authority, placeholder transaction or frontend-only configuration. Mainnet activation is fail closed.


---

# 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/deployment-and-verification.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.