> 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/sonic-token-visual-identity-and-asset-usage.md). # SONIC Token Visual Identity & Asset Usage Canonical SONIC token visual identity, Refined Wave Pillars brandmark, public asset paths, vector/raster usage and pre-mainnet verification boundaries. SONIC uses the **Refined Wave Pillars** mark as the canonical token and application brandmark. The burgundy waveform-pillar monogram replaces the earlier generic waveform treatment across token artwork, app icons, wallet surfaces, documentation and public asset packages. ## Canonical brand system | Element | Canonical treatment | | ---------------- | --------------------------- | | Brandmark | **Refined Wave Pillars** | | Wordmark | **SONIC** | | Tagline | **CREATE A HIGHER REALITY** | | Primary burgundy | `#7A101D` | | Charcoal | `#111111` | | Off white | `#FCFBF9` | | Light gray | `#D9D6D3` | | Mid gray | `#73706D` | The primary token presentation artwork is a premium burgundy circular token with the raised white Refined Wave Pillars mark. The token artwork is a presentation asset; it is not proof of an on-chain mint. ## Public asset repository Canonical source repository: `https://github.com/sonicaiworks/sonic-token-assets` R24 public asset layout: ``` public/ ├── assets/ │ ├── sonic.svg │ └── vector/ │ ├── sonic-brandmark-burgundy.svg │ ├── sonic-brandmark-black.svg │ ├── sonic-brandmark-white.svg │ ├── sonic-brandmark-gray.svg │ ├── sonic-logo-horizontal.svg │ ├── sonic-token-flat.svg │ ├── sonic-app-icon.svg │ └── sonic-favicon.svg ├── icons/ │ └── logo/ │ ├── sonic.svg │ ├── sonic-black.svg │ └── sonic-white.svg ├── images/ │ ├── sonic-token.png │ ├── sonic-token.webp │ ├── sonic-token-512.png │ ├── sonic-token-256.png │ ├── sonic-token-128.png │ └── sonic-brandmark-token-system.webp └── manifest.json ``` ## Vector vs raster usage Use **SVG** for application chrome, website headers, navigation, documentation, favicons and scalable iconography. Use the burgundy SVG mark on light surfaces, the white mark on burgundy or charcoal surfaces, and the black mark only where a monochrome treatment is required. Use **PNG/WebP token artwork** for wallets, token selectors, marketplace cards, metadata presentation, social previews and high-fidelity 3D token rendering. Do not rasterize an SVG when the consuming surface supports vector assets. ## Token icon hierarchy 1. **Primary token** — burgundy metallic token with white Refined Wave Pillars mark. 2. **Flat token** — burgundy circle with white mark for small product surfaces. 3. **App icon** — burgundy rounded square with white mark. 4. **Favicon** — burgundy circle with white mark. 5. **Monochrome mark** — black, white or gray variants for constrained environments. Do not substitute the retired multi-bar waveform as the canonical token mark. ## Token standard and verification SONIC policy specifies a **Solana Token-2022** fungible asset using **9 decimals** and a fixed genesis amount of **18,446,000,000 SONIC**. ``` Solana mainnet-beta + Token-2022 + verified mint + 9 decimals + exact genesis supply + mint authority revoked after genesis + verified registry/release = trusted production SONIC identity ``` The production mint remains **TBA** until mainnet deployment and independent verification complete. ## Fee label rule The canonical token profile does **not** use the Token-2022 `TransferFeeConfig` extension. Ordinary wallet-to-wallet SONIC transfers therefore have **0% SONIC protocol transfer tax**; users still pay the applicable Solana network fee. Product-domain charges such as SONIC Swap's **2% service fee**, marketplace fees, checkout fees or machine-payment fees are quoted and settled by those products. They must never be presented as a native SONIC transfer fee. ## Asset integrity The public asset manifest should include file paths, byte sizes and SHA-256 hashes. Production applications should consume the canonical manifest rather than maintaining unrelated logo copies. Artwork, metadata, symbol and repository assets never establish on-chain identity by themselves. ## Accessibility Use descriptive alt text such as `SONIC token`, `SONIC Refined Wave Pillars brandmark`, `SONIC app icon` or `SONIC horizontal logo`. Do not encode verification, network or financial state through color alone. --- # 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/sonic-token-visual-identity-and-asset-usage.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.