> 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/application-and-website/tokenomics-and-wallet-experience.md).

# Token Application & Wallet Experience

Token and wallet product UX that consumes canonical token policy, verified wallet identity, transaction intent and settlement without duplicating allocation policy.

Token and wallet surfaces are **transparency, identity and execution interfaces**, not a second tokenomics source of truth. Creation remains the primary SONIC product; token utility is optional and feature-gated.

{% hint style="info" %}
Allocation, sale, liquidity, lock, burn and Creator Rewards policy live in [SONIC Tokenomics & Distribution](/sonic-networks-docs/documentation/sonic-tokenomics.md). This page intentionally does not repeat the allocation table.
{% endhint %}

## Current status

| Area                         | Status                                             |
| ---------------------------- | -------------------------------------------------- |
| Tokenomics policy            | **Defined**                                        |
| Deployment registry contract | **Defined**                                        |
| Production SONIC mint        | **TBA / unverified until deployment verification** |
| Production decimals          | **TBA**                                            |
| Production token program     | **TBA**                                            |
| Token application            | **In progress**                                    |
| Rewards / claims             | **Program-dependent**                              |
| Pre-sale                     | **Planned**                                        |
| Liquidity venues             | **Planned**                                        |
| Governance                   | **Planned**                                        |

The UI must never infer **Live**, **Verified** or **Active** from a design, endpoint, metadata document, source scaffold, symbol, logo, assigned program ID or permissionless pool.

## Token identity

```
SONIC policy
→ deployment registry
→ expected mint / token program / decimals / authorities
→ finalized Solana verification
→ product capability status
```

Metadata is presentation data. Name, symbol, icon, coin artwork, image URI or metadata URI never replace mint/program/decimal verification.

## Wallet state

The authenticated account may have an embedded SONIC Wallet and zero or more externally linked Wallet Standard wallets.

```
authenticated session
→ SONIC identity
→ verified wallet ownership where required
→ wallet permission
→ policy / risk
→ TransactionIntent
```

Wallet connection does not authorize arbitrary transactions and does not replace SONIC authentication.

## Supply UX

Allocation is not circulating supply. Until chain-backed methodology is available, minted, circulating, locked and burned values should remain **Unavailable / TBA** rather than being displayed as zero or inferred from policy.

## Creator Rewards and claims

```
program policy
→ eligibility
→ funded allocation
→ reward ledger
→ claimable
→ claim intent
→ wallet verification / signature where required
→ chain verification
→ settlement
→ reconciliation
```

Leaderboard position, engagement, token ownership or community participation alone does not create financial entitlement.

## Fee domains

Marketplace fees, SONIC Swap fees, Solana network/priority fees, DEX/provider fees and any token-level transfer fee are separate domains. The application must quote them independently and never combine them into an undocumented percentage.

## AI Credits remain separate

AI Credits are SaaS consumption units. They are not SONIC, SOL, USDC, USDT or another wallet asset and must never be rendered as a crypto balance.

## Transaction boundary

```
session
→ access / entitlement
→ verified wallet
→ quote / policy
→ TransactionPlan
→ expected effects
→ user authorization
→ signature
→ submission
→ confirmation
→ indexer
→ reconciliation
```

For economic policy use [SONIC Tokenomics & Distribution](/sonic-networks-docs/documentation/sonic-tokenomics.md). For deployment truth use [Deployment & Verification](/sonic-networks-docs/documentation/sonic-tokenomics/deployment-and-verification.md).


---

# 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/application-and-website/tokenomics-and-wallet-experience.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.