> 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/tokenomics-architecture-and-trust-model.md). # Tokenomics Architecture & Trust Model Canonical SONIC tokenomics architecture connecting approved v1.0.0 policy, product UI, APIs, deployment registry, Token-2022 verification, Streamflow state, market data and final on-chain truth. This page defines how SONIC tokenomics information moves from approved policy and verified external state into product surfaces without allowing the UI, API or market providers to become the source of token truth. > **Pre-deployment rule** — A designed screen, API route, configured provider, token artwork, market quote or tokenomics document does not by itself prove production deployment. Deployment-sensitive facts remain subject to the deployment registry and verified Solana state. ## Canonical policy inputs ``` Token standard Token-2022 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 until deployment Quarterly burn 2% — calculation base TBA Streamflow lock designation 3,000,000,000 SONIC Production mint TBA until deployment Authorities TBA until deployment ``` The **500 bps rate-policy cap** is distinct from Token-2022's on-chain `maximumFee` absolute token-amount cap. ## Canonical architecture ```mermaid flowchart TD P[SONIC Tokenomics v1.0.0 Policy] P --> UI[Product UI] P --> DATA[Data Domain] P --> TRUST[Trust Layer] UI --> API[SONIC API /api/v1] DATA --> API TRUST --> API API --> CONFIG[Deployment / Token Config] API --> RPC[Solana RPC] API --> MARKET[Market Providers] CONFIG --> VERIFY[Token-2022 Verification] RPC --> VERIFY VERIFY --> CHAIN[Trusted SONIC Production State] MARKET --> API ``` The architecture separates policy, presentation, calculation, deployment verification and external market observations. ## 1. Product UI The Product UI owns **presentation and user action**, not token truth. | Surface | Responsibility | Must not do | | ----------------- | -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | Tokenomics | Present approved policy and verified live state with provenance | Convert policy values into fabricated live metrics | | Supply | Distinguish initial maximum, observed minted, locked/unlocked, circulating and burned supply | Label the initial maximum as live total supply before deployment | | Rewards | Display eligibility, allocation, claim and settlement state | Convert engagement into automatic entitlement | | Wallet / Checkout | Quote applicable fee domains separately before signature | Collapse token, service, network and provider fees into one percentage | | Governance | Present verified proposal/voting state where enabled | Treat token ownership as automatic administrative authority | ## 2. Data Domain | Domain | Canonical responsibility | | -------------- | ---------------------------------------------------------------------------------------- | | Metadata | Name, symbol, Token-2022 policy fields, presentation metadata and registry version | | Supply | Initial maximum, observed minted, verified locked/unlocked, circulation and burned state | | Allocation | Approved v1.0.0 distribution buckets | | Lock / Vesting | Streamflow and other approved schedules, beneficiaries and release state | | Rewards | Eligibility, funded allocation, claims, settlement and reconciliation | | Fees | Token-2022 transfer fee, Marketplace, Swap, network/priority and provider fee separation | | Burn | Scheduled through reconciled quarterly-burn execution evidence | ``` allocation ≠ custody ≠ locked ≠ unlocked ≠ circulating ≠ claimable ≠ burned ``` ## 3. Supply publication ```http GET /api/v1/token/total-supply GET /api/v1/token/circulating-supply ``` Before deployment, the approved policy value is `initialMaximumSupply = 18,446,000,000 SONIC`; observed `totalSupply` remains unavailable until a production mint exists and is verified. Circulating supply is derived from verified state: ``` circulatingSupply = observedMintedSupply - verifiedLockedSupply - vestingExcludedSupply - treasuryExcludedSupply - reserveExcludedSupply - otherApprovedNonCirculatingSupply ``` The **3,000,000,000 SONIC Streamflow designation** is not automatically a verified lock exclusion. ## 4. Trust Layer The Trust Layer determines whether token data is sufficiently verified to publish or activate. Production verification should confirm: * Solana network/cluster; * production mint identity; * Token-2022 account ownership; * observed decimals equal **9**; * observed supply relative to the initial maximum; * mint/freeze authority state; * active **200 bps** launch TransferFeeConfig; * active transfer-fee rate at or below the **500 bps policy cap**; * Token-2022 maximum fee amount; * transfer-fee configuration authority; * withdraw-withheld authority and withheld-fee handling; * metadata authority where configured; and * slot/block-time provenance. If SONIC is represented as fixed-supply after genesis, the intended post-genesis mint-authority state must also be verified. ## 5. SONIC API `/api/v1` The API is the stable publication boundary between product surfaces and underlying data/trust systems. Response principles: * policy maximum and observed supply use distinct fields; * public quantities use decimal-safe strings; * atomic amounts use the canonical **9-decimal** scale; * precision-sensitive calculations use integer/arbitrary-precision arithmetic; * unavailable state is null/unavailable, never a fabricated zero; * provider/RPC credentials remain server-only; * public read-only token endpoints require no wallet connection; and * deployment-sensitive fields include explicit status/provenance. ## 6. Token / Deployment Config Configuration may contain: * approved Token-2022 standard; * canonical **9 decimals**; * **200 bps** launch transfer-fee rate; * **500 bps** maximum transfer-fee rate policy cap; * expected Token-2022 maximum fee amount once configured; * expected production mint once configured; * initial maximum supply policy; * allocation classifications; * Streamflow/vesting registries; * treasury/account classifications; * fee-authority configuration; * product feature gates; * market-source registry; and * version/integrity metadata. Configuration cannot self-declare production verification. ## 7. Solana RPC Solana RPC is the primary source for chain-observable facts such as mint existence/ownership, supply, token accounts/balances, authority state, Token-2022 extensions, transaction signatures, confirmations and provenance. ## 8. Market providers Market APIs provide factual price, liquidity, pool, route and volume observations where available. They do not define SONIC mint identity, monetary policy, allocation, circulation methodology, governance authority or treasury authority. ## 9. Source precedence ``` 1. verified Solana state for chain-observable facts 2. approved SONIC Tokenomics v1.0.0 for economic policy 3. approved deployment/allocation/lock registries for classifications 4. deterministic SONIC domain calculation 5. factual external market provider for market observations 6. SONIC API projection 7. Product UI presentation ``` ## Failure behavior | Condition | Required behavior | | ------------------------------------------------------ | ----------------------------------------------------------------------- | | RPC unavailable | Return unavailable/error; do not fabricate chain data | | Observed supply violates policy | Raise monitoring/review state; do not silently publish | | Launch TransferFeeConfig differs from 200 bps policy | Keep production verification failed / requires review | | Effective transfer-fee rate exceeds 500 bps policy cap | Keep production verification failed / requires review | | Token-2022 maximum fee or fee authority unknown | Keep field TBA/unverified | | Streamflow schedule unverified | Do not report designated amount as verified locked supply | | Burn base unresolved | Do not activate or calculate the quarterly burn | | Market provider unavailable | Keep market fields unavailable/stale; do not substitute planning prices | | Allocation registry invalid | Fail dependent calculations rather than guessing | ## Production invariant ``` approved policy + deterministic data model + verified deployment registry + Token-2022 chain verification + verified provenance + canonical API projection + factual external state where required = trustworthy SONIC tokenomics experience ``` --- # 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/tokenomics-architecture-and-trust-model.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.