Sonic (S)
Unlock Schedule
Sonic (S) Token Unlock & Vesting Schedule
The unlock chart above provides a clear visual overview of the Sonic (S) token release schedule, showing when and how tokens enter circulation across investor, team, treasury, and community allocations. Understanding these tokenomics dynamics is critical for evaluating potential supply pressure, inflation impact, and market liquidity over time — key factors that can influence S price performance.
Each color segment in the chart corresponds to a specific allocation group described in the Allocations section below. Underlying assumptions and data models used to reconstruct this schedule are explained in detail under Assumptions, while broader utility insights and token use cases are covered in Tokenomics & Utility.
Tokenomics & Utility
Roles of the S token
The S token serves four core roles:
- Pay gas for transactions and smart contracts
- Stake to secure the network and earn rewards
- Run validators (with an on‑chain minimum bond)
- Vote in governance on upgrades and funding proposals (docs.soniclabs.com)
Supply, issuance, and burns
At Sonic mainnet launch, S mirrored the FTM supply with an initial total of roughly 3.175 billion. Subsequent governance approved limited, time‑bound issuance to support institutional expansion (ETF exploration, a Nasdaq vehicle, and the Sonic USA entity). Issuance schedules are public, and unused allocations from the yearly issuance are burned to reduce inflation. As part of gas‑economy design, fees on non‑FeeMonetization transactions can include a burn component, while apps enrolled in FeeM receive the bulk of fees generated. (binance.com)
Staking and validators
Token holders can delegate to a validator from within the MySonic app and withdraw with a 14‑day unbond period. To operate a validator, nodes must bond a significant amount of S, which aligns incentives and helps defend against Sybil attacks. Rewards are paid from network emissions and block rewards that migrated from legacy Opera to Sonic. (docs.soniclabs.com)
Fee Monetization (FeeM) and developer rewards
Sonic’s FeeM program directs up to 90% of user‑paid gas fees to the apps that actually consumed that gas. Validators receive 10% of fees. Off‑chain oracles attribute gas usage across contracts in a transaction and settle rewards back on‑chain, preventing double counting. This design encourages builders to bring traffic, rather than forcing them to launch a separate app chain. (docs.soniclabs.com)
Airdrops and Gems
Sonic’s airdrop strategy assigns approximately 200 million S to community programs. Sonic Gems are season‑based points earned by apps for driving real activity; apps can redeem Gems for S and then distribute tokens to their users under their own rules. (docs.soniclabs.com)
Assumptions
- Supply is uncapped; validator rewards transition to ongoing inflation after the first 4 years.
Docs specify migrated Opera rewards for 4 years, then new S issuance at 1.75%/year for validator rewards.
- PoS post-2028 emissions modeled for 10 years at a fixed 1.75% of an estimated 2028-12-18 supply baseline.
Exact annual base can vary with burns, future issuances, and market conditions. We used a reasonable estimate to enable monthly charting; real emissions may differ.
- Airdrop Season 1 unlocks assume full vesting amounts enter circulation over 270 days without netting early-claim burns.
Early claims burn part of the vested allocation; exact burn volume is unknown. Modeling uses the program’s stated vesting mechanics.
- Ongoing Funding mints the full 47,625,000 S each year for six years; any unused portion may be burned later.
Issuance is on-chain and scheduled; burns depend on program usage and occur after each year.
- Genesis supply of S equals FTM total supply (3,175,000,000) at launch via a 1:1 upgrade.
Official migration and upgrade materials specify 1:1 conversion, and Fantom’s total supply is 3.175B.
- 1. https://docs.soniclabs.com/sonic/s-token
- 2. https://docs.soniclabs.com/funding/sonic-airdrop
- 3. https://blog.soniclabs.com/sonic-mainnet-launch-evm-compatible-verifiable-10-000-tps-and-sub-second-finality/
- 4. https://docs.fantom.foundation/sonic-migration/overview
- 5. https://fantom.foundation/ftmToken
- 6. https://sonicscan.org/tx/0xd0d0148b527c9c60373e73ce9320925146cbdb466356b92a4d153c3a9111ccf6
- 7. https://sonicscan.org/tx/0x0550080bece31fabecbd52a224b2a7bc15c70151bf55b08417113e6b44c16878
- 8. https://sonicscan.org/tx/0xce8078a6e5c44630f86868034df50d8e08b18e3f405d912696a7e745c40d7508
- 9. https://sonicscan.org/tx/0x2acf561539705b8d0004da7aaa5e8ee2971e34fdbca0e017ac753761e862ae2c
Allocations
Description
#250
Sonic (ex. Fantom) is a decentralized platform for smart contracts and digital assets that aims to be faster, cheaper and more secure than Ethereum. Fantom uses a Proof-of-Stake network with thousands of validator nodes and transactions per second.
| Sector: | Layer 1 |
| Blockchain: | Sonic |