> 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/token-sales.md). # Token Sales Planned SONIC pre-sale policy for Q4 2026, launchpad selection, sale inventory, pricing, success/failure handling, DEX liquidity activation and risk disclosures. **Stage: PRE-SALE · Target window: Q4 2026 · Status: PLANNED / PRE-DEPLOYMENT** {% hint style="warning" %} No SONIC token sale is Live today. Dates, provider, sale contract, eligibility, contribution limits, soft/hard caps, treasury accounts and production mint remain subject to approval, deployment and independent verification. {% endhint %} SONIC plans a Community pre-sale as a controlled launch stage for early supporters of the creator ecosystem. The sale is intended to fund launch execution and liquidity while preserving a clear boundary between product utility and speculative market activity. ## Planning baseline | Field | Current planning state | | ----------------------------------- | ----------------------------------------------- | | Stage | **Pre-Sale** | | Target window | **Q4 2026** | | Candidate launchpad | **PinkSale or Smithii.io — final provider TBA** | | Sale contract / provider deployment | **Q4 2026 target · address TBA until verified** | | Sale inventory planning envelope | **\~3–5 billion SONIC** | | Approx. share of initial maximum | **\~16.26%–27.11%** | | Initial pre-sale price reference | **\~$0.000002 / SONIC** | | Initial DEX launch-price reference | **\~$0.0000025 / SONIC** | | Production mint | **TBA** | | Soft cap / hard cap | **TBA** | | Accepted contribution assets | **TBA** | | Eligibility / jurisdictions | **TBA** | `~` means a planning reference, not a guaranteed commercial term. Final terms must be published before the sale opens and cannot be silently changed by frontend configuration. ## Launchpad selection The current provider shortlist is: * **PinkSale** — Solana presales support sale configuration and, where selected, automatic DEX-liquidity creation after successful finalization. See the [PinkSale Solana presale documentation](https://docs.pinksale.finance/solana/create-a-presale). * **Smithii.io** — Solana launchpad tooling supports sale/launch pricing, contribution limits, soft/hard caps, whitelist/vesting options and a configurable share of raised funds for liquidity. See the [Smithii Solana launchpad documentation](https://docs.smithii.io/products/tools/solana/token-tools/token-launchpad/create-presale). Provider selection is **not final**. Before activation SONIC must verify Token-2022 compatibility, contract/program identity, administrative authority, refund behavior, fee schedule, liquidity controls, audit/security evidence, data export/reconciliation, operational support and applicable legal/compliance requirements. ## Sale inventory is not a new allocation The planned **\~3–5B SONIC** sale inventory must be sourced from one or more existing approved allocation buckets. It does not increase supply and is not a ninth allocation. ``` sale inventory ⊆ allocated supply locked inventory ⊆ allocated supply sale inventory + other uses must never double-count the same token inventory ``` Final source allocation(s), exact amount and any vesting/lock treatment remain TBA. The canonical distribution table remains the sole allocation source of truth. ## Success definition A sale is not successful merely because a UI displays `success`, a hard cap is approached, or a contribution transaction exists. A successful pre-sale requires the approved success threshold to be met and the following evidence to reconcile: 1. the final sale configuration and provider/contract identity are verified; 2. the minimum/soft-cap rule is satisfied; 3. accepted contributions are settled according to the sale contract/provider; 4. sold and unsold SONIC inventory reconciles to the approved allocation source; 5. contributor entitlements/claims are recorded correctly; 6. treasury proceeds and provider fees reconcile; and 7. required launch liquidity is created and independently verified before SONIC reports the corresponding DEX market as active. If the approved success condition is not met, the sale follows the configured failure/refund policy and must not proceed as though the raise succeeded. ## Post-sale DEX activation The current market plan uses an initial DEX reference of **\~$0.0000025 / SONIC** after a successful sale and verified liquidity bootstrap. Planned venue architecture: * **Raydium** — candidate primary Solana liquidity venue; * **Meteora** — candidate complementary liquidity venue; * **Orca** — candidate venue subject to final Token-2022 and pool-policy verification; and * **Jupiter** — route discovery/aggregation after verified liquidity is available. Jupiter is not treated as a pool listing venue in the same sense as a Raydium, Meteora or Orca pool. Additional DEX venues may be enabled as verified liquidity, holder distribution, route quality and operational demand grow. Venue count is not a launch KPI by itself. ## Liquidity and volatility policy SONIC should prefer meaningful initial liquidity over many thin pools. A larger, well-distributed liquidity base can reduce **trade price impact and slippage**, all else equal, but it cannot control or guarantee market volatility. Liquidity policy should therefore optimize for: * sufficient pool depth relative to expected trade sizes; * transparent treasury/source funding; * appropriate LP lock/management policy; * resilient routing and price discovery; * multiple venues only when fragmentation does not materially worsen execution; * monitoring for abnormal price impact, pool depletion and route failures; and * verified on-chain balances rather than marketing liquidity figures. No SONIC document should promise a stable price, minimum future value, guaranteed liquidity or protection from loss. ## Early supporters and utility-first positioning The pre-sale is intended to give eligible early supporters access to the SONIC ecosystem before broader market availability and to support network launch/liquidity funding. **SONIC is not positioned as a meme token.** It is designed around creator-network utility: creator rewards, supported tokenized-content workflows, Marketplace/Storefront commerce, platform utility, and governance/participation where those capabilities are actually enabled. Product purpose and utility do **not** guarantee token demand, appreciation, liquidity or investment returns. ## Binance / Binance Alpha notice **Binance: TBA. Binance Alpha: TBA.** SONIC must not imply an application, selection, endorsement, Alpha feature or Binance Exchange listing unless it is independently confirmed by Binance and publicly verifiable. Binance states that Alpha highlights early-stage projects and that being featured on Binance Alpha does **not** guarantee a Binance Exchange listing. See [Binance's official Alpha explanation](https://www.binance.com/en/academy/articles/what-is-binance-alpha). ## Risk disclosure {% hint style="danger" %} Digital assets and early-stage token sales are high risk. SONIC can experience substantial price volatility, illiquidity, smart-contract or launchpad failures, DEX/pool risks, routing failures, regulatory restrictions, loss of access and total loss of contributed value. A successful pre-sale does not guarantee a DEX market, a particular launch price, future liquidity, Binance/Alpha support, centralized-exchange listing, utility activation or financial return. This documentation is product/technical information, not investment, legal or tax advice. Participation must be limited to eligible jurisdictions and users under the final sale policy. {% endhint %} ## Activation gate ``` approved sale policy + funded inventory from existing allocations + verified production mint + verified provider / sale contract + security review + legal / jurisdiction policy + published final terms + treasury / refund controls + monitoring and reconciliation = sale may be activated ``` Until that gate passes, the product state remains `PLANNED` or `CONFIGURED_UNVERIFIED`, never `LIVE`. --- # 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/token-sales.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.