# SNS Roadmap

SNS is being deployed in structured phases to ensure modular scalability, ecosystem alignment, and long-term sustainability.

#### 💥 Phase 0: SNS Token Launch

**🔥 0.1 Burn-to-Mint on WigoSwap**

* **Timeline**: ✅ Completed
* **Platform**: WigoSwap (Fantom)
* **Mechanism**: Users burned WIGO tokens to mint SNS tokens
* **Purpose**: Establish early token distribution while supporting WIGO ecosystem
* **Impact**: Bootstrapped SNS token holders with value-aligned users

**🚀 0.2 SNS Token IDO on Fantom**

* **Timeline**: ✅ Completed (post burn-to-mint)
* **Platform**: Fantom
* **Mechanism**: Initial DEX Offering (IDO) for SNS token
* **Token Symbol**: `SNS`
* **Utility**: Governance, staking, participation in protocol fee distribution
* **Result**: SNS token entered public circulation and core protocol holders were established

**🚀 0.3 Migration**

* **Timeline**: ✅ Completed
* **Platform**: WigoSwap (Fantom) & Defive (Sonic)
* **Result**: Users migrated their SNS tokens on Fantom to SNS tokens on Sonic

#### 🔒 1. Private Domain Reservation

* Reserved `.s` domains for core contributors, partners, and protocol-aligned teams
* Each reserved name is tied to a specific address and **can only be registered by that address**.
* These domains are not pre-minted — they are locked until claimed by their rightful owners during public registration.
* Ensures that premium, protocol-critical, or identity-sensitive names (e.g., `team.s`, `sns.s`, `rex.s`) are protected from front-running or squatting.

***

#### 🌍 2. Public Domain Reservation

* Open reservation of `.s` root domains for the community
* Each reserved name is tied to a specific address and **can only be registered by that address**.

***

#### 🏛️ 3. DAO Governance Launch

* SNS holders will govern:
  * Fee multipliers
  * Module parameters
  * Revenue distribution mechanics
* `RevenueDistributor` feeds community earnings into DAO-based claiming
* DAO tools will be integrated via Snapshot or custom veSNS model

***

#### 🧩 4. Reseller Dashboard & SDK Activation

* Activate `ResellersHub` for commission tracking and payments
* Build dashboard for monitoring reseller stats and balances
* SDKs available for 3rd-party storefronts, wallets, and app integrations
* Balance tracking and claiming is fully on-chain and non-custodial

***

#### 🚀 5. Core Launch on Sonic Mainnet

* Launch of all SNS core contracts on **Sonic**:
  * `DotS`, `Ledger`, `Caster`, `ListController`, `FeeController`, `ReferralHub`, `ResellersHub`, `RevenueDistributor`
* Public `.s` registration goes live
* UI, APIs, and contract SDKs available for integrators

***

#### 🧠 6. Standard Resolvers Go Live

* `Pointer` module enables resolution to:
  * Wallets, contracts, apps, subgraphs
* Pluggable record types, pointer type registry, and optional reverse records

***

#### 🧬 7. Subdomain Activation

* Launch of `SubdomainHub`:
  * Assign roles for subdomain managers
  * Dynamic virtual ownership (not NFTs)
  * Usage-based subdomain limits (some free, some paid)
  * Custom logic per domain (e.g. `free.rex.s`, `pro.rex.s`)

***

#### 🔗 8. Ecosystem dApp Integrations

* `.s` names usable in:
  * Wallets
  * DEX frontends
  * Governance tools
  * Social protocols
* Integration SDKs and incentives for protocols adopting SNS resolution

***

#### 🌐 9. Web2 & DNS Bridge Research

* Researching `.s` ↔ Web2 integrations:
  * HTTP resolution and forwarding
  * `.s` as pseudo-DNS namespace
  * Email routing and traditional domain functionality
* Goal: make `.s` domains usable across Web2 and Web3

***

#### **Stay Informed**

Our roadmap is constantly evolving, and we will keep the community informed with the latest updates and progress. Make sure to follow our channels for key announcements and new developments. The future of decentralized name services is just around the corner, and we can’t wait to launch the Sonic Name Service!


---

# Agent Instructions: 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:

```
GET https://docs.sns.net/intro/sns-roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.