> 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/api-reference/solana-and-sonic-token.md). # Solana & SONIC token Solana network, canonical SONIC Token-2022 policy, 9-decimal accounting, supply and token-registry APIs, deployment verification, transfer-fee configuration, rewards and chain-sensitive activation rul > **Deployment-sensitive surface** — A configured address, metadata document, artwork, token list or product flag does not prove that the production SONIC token is deployed or verified. Live/Verified status is derived from the canonical registry plus observed Solana evidence. All blockchain/RPC providers remain behind the SONIC server boundary. RPC credentials, signer material and privileged configuration never become public client settings. ## Canonical policy ``` Token SONIC Network Solana Standard Token-2022 Token-2022 program TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb Initial maximum supply 18,446,000,000 SONIC Decimals 9 Atomic initial maximum supply 18,446,000,000,000,000,000 Launch transfer-fee rate 2% / 200 bps Maximum transfer-fee rate policy cap 5% / 500 bps Token-2022 maximum fee amount TBA Production mint TBA Quarterly burn 2% — calculation base TBA Streamflow lock 3,000,000,000 SONIC designated ``` The **500 bps rate-policy cap** is distinct from Token-2022's on-chain `maximumFee` absolute token-amount cap. ## Canonical token API ```http GET /api/v1/token/total-supply GET /api/v1/token/circulating-supply GET /api/v1/token/metadata GET /api/v1/token/deployment GET /api/v1/token/verification GET /api/v1/token/status ``` The supply routes distinguish policy maximum from observed production supply. Registry routes project the same policy, deployment registry and verification service. ## Supply model Before deployment: ``` initialMaximumSupply = 18,446,000,000 SONIC totalSupply = unavailable / null circulatingSupply = unavailable / null ``` After a production mint is verified, `totalSupply` is observed from the mint and must never exceed the initial maximum. Circulating supply remains derived from verified exclusion classifications. ## Token Registry authority chain ``` SONIC Tokenomics v1.0.0 ↓ deployment registry ↓ live Solana RPC verification ↓ verified deployment state ↓ product/status projections ``` Configuration is expected state. Verification is observed state. A configured mint may be `MAINNET_CONFIGURED`; only successful required checks may produce `MAINNET_VERIFIED`. ## Deployment verification invariants Production verification includes, at minimum: 1. registry mint equals the live RPC mint; 2. mint account is owned by the Solana Token-2022 program; 3. decimals equal **9**; 4. atomic supply is parseable and does not exceed **18,446,000,000,000,000,000**; 5. mint/freeze authority state matches approved policy; 6. launch transfer-fee rate equals **200 bps**; 7. effective transfer-fee rate remains at or below the **500 bps policy cap**; 8. Token-2022 maximum fee amount matches approved deployment configuration; 9. transfer-fee configuration authority matches the registry; 10. withdraw-withheld authority and withheld-fee handling match the registry; 11. metadata-authority policy matches the registry where configured; and 12. verification records slot/block-time provenance when available. If SONIC is presented as fixed-supply after genesis, production verification must also confirm the intended post-genesis mint-authority state. ## Creator Rewards ``` ESTIMATED → ELIGIBLE → ALLOCATED → CLAIMABLE → SUBMITTED → CONFIRMED → SETTLED → RECONCILED ``` Leaderboard position, social engagement, wallet connection or token ownership alone does not create a claimable entitlement. ## Chain-sensitive actions ``` signed session / auth context → access / entitlement checks → verified wallet where required → quote / policy → TransactionIntent → explicit signature → submission → confirmation → expected-effect verification → settlement → reconciliation ``` A token metadata, supply, deployment, verification or status response is informational state only. It grants no authentication, transaction, governance, reward or administrative authority. --- # 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/api-reference/solana-and-sonic-token.md?ask=&goal= ``` `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.