Sonic is an EVM-compatible Layer 1 blockchain that uses a unique consensus mechanism designed to support high throughput, security, and scalability. The network is reportedly capable of processing up to 400,000 transactions per second (TPS) with sub-second finality, making it suitable for applications such as decentralized finance (DeFi).
Sonic was launched in December 2024 as the successor to the Fantom Opera network, introducing improvements in both its technical design and branding. As part of the migration, Fantom users could exchange their FTM tokens for Sonic’s native S token on a one-to-one basis. The S token is used for transaction fees, staking, validator operations, and governance participation.
How Sonic Works
Consensus mechanism
Sonic uses a Proof of Stake (PoS) consensus mechanism combined with asynchronous Byzantine Fault Tolerance (ABFT) and a directed acyclic graph (DAG) structure.
Proof of Stake (PoS)
Sonic validators secure the network by staking tokens, which can be penalized if they act dishonestly. They are responsible for collecting transactions, bundling them together, and sharing them with the network.
Asynchronous Byzantine Fault Tolerance (ABFT)
Validators can agree on transactions without confirming them in strict order. Once most validators reach an agreement, the transactions are confirmed, ordered, and added to Sonic’s main blockchain as the permanent record.
Directed Acyclic Graph (DAG)
Instead of processing transactions one block at a time, validators can handle and share multiple groups of transactions in parallel. This non-linear approach increases throughput, allowing Sonic to finalize transactions in about 2 seconds.
Database storage
To manage storage, Sonic uses two types of databases: LiveDB, which stores only the current state of the blockchain, and ArchiveDB, which keeps full historical records. Validators operate using LiveDB, keeping their storage requirements low, while archive nodes preserve the complete history for applications or users who need it.
A process called live pruning automatically removes outdated data from validators as the blockchain grows, helping to reduce storage requirements without compromising accuracy. This ensures the network remains efficient while still providing full historical access when needed.
EVM compatibility
Sonic is fully compatible with the Ethereum Virtual Machine (EVM), allowing applications built for Ethereum to run on Sonic. The network supports both Solidity and Vyper smart contracts, making it easier for developers to build and migrate projects while benefiting from Sonic’s speed and scalability.
Key Features
Sonic Gateway
The Sonic Gateway is Sonic’s native bridge, connecting directly to Ethereum and providing developers and users with access to liquidity across both networks. It is designed for both speed and safety, with a unique fail-safe mechanism that keeps user assets protected.
Transferring assets through the gateway involves three steps:
Deposit: Users deposit tokens into the bridge. Finalization takes about 15 minutes on Ethereum and only 1 second on Sonic.
Heartbeat: Transfers are processed in batches at intervals called “heartbeats.” These occur every 10 minutes from Ethereum to Sonic and every hour in the reverse direction. A Fast Lane option allows users to pay a fee to trigger an immediate heartbeat.
Claim: Once the transfer is complete, users claim their bridged assets on the destination chain and can begin using them in the Sonic ecosystem.
The bridge is designed with strong protections to keep your assets safe. If the gateway is down for 14 days, you can still recover your funds directly on Ethereum. This 14-day window is fixed and cannot be changed by Sonic Labs or any third party, allowing you to remain in control of your assets.
Fee Monetization (FeeM)
Sonic’s Fee Monetization system allows developers to earn 90% of the network fees generated by their applications. This directly rewards builders for the activity they drive and provides a steady revenue stream without requiring extra tokens or separate blockchains.
When a user makes a transaction, the gas fee is paid in S tokens. Validators receive 10% of this fee for securing the network, while the remaining 90% goes to a FeeM smart contract. Off-chain oracles monitor gas usage across applications, confirm the data on-chain, and release rewards once the data is verified. This ensures fees are distributed fairly and transparently, linking developer earnings directly to real application activity on Sonic.
Sonic Token
The S token is the native token of the Sonic network. It’s used within Sonic’s infrastructure and ecosystem for many purposes, including:
Gas fees: S is used to pay for transaction fees when interacting with applications or smart contracts on Sonic.
Staking: Holders can stake S to help secure the network, either by delegating to validators or by operating validator nodes directly.
Validator operations: Running a validator requires locking up at least 500,000 S. Validators earn rewards for confirming transactions, but can be penalized if they act dishonestly or misconfigure their systems.
Governance: S tokens give holders a role in decision-making, allowing them to influence upgrades and future protocol direction.
Ecosystem incentives: Sonic distributes S through multi-season airdrops, rewarding users who provide liquidity and interact with DeFi apps and games.
