SOON

SOON Explained: A Decoupled SVM Stack for Ethereum and Other Base Layers

SOON combines an Ethereum-settled Layer 2 with infrastructure for deploying SVM-based chains on different base networks. Its SOON token is presented as a governance, network, staking, and ecosystem-incentive asset, but the system also depends on external settlement, data-availability, messaging, and infrastructure providers.

What SOON is building

SOON describes itself as a stack built around a decoupled Solana Virtual Machine, or SVM. Its main products are SOON Mainnet, SOON Stack, and InterSOON. The project documentation characterizes SOON Mainnet as a general-purpose Layer 2 that settles on Ethereum, while SOON Stack is intended to let developers deploy SVM-based Layer 2 chains on top of other base layers. InterSOON is the project’s cross-chain messaging component for connecting SOON Mainnet, SOON Stack chains, and external networks.

The practical distinction is between an execution environment and the chain that provides settlement or data availability. SOON’s documentation says its execution layer uses a decoupled SVM, while the Stack can use Ethereum as a settlement layer and Avail as a data-availability layer, with infrastructure support from Caldera and AltLayer. These are project-described integrations rather than guarantees that every SOON Chain uses the same configuration.

How the architecture is intended to work

The public Igloo repository provides a more technical view of the design. It describes an OP-style rollup framework whose derivation layer follows Optimism’s design while the execution layer is based on an SVM implementation derived from Agave. The repository separates Layer 1 information, Layer 2 block production, transaction streaming, derivation, data availability, and execution through software interfaces. In plain terms, the design tries to reuse rollup settlement logic while replacing the usual execution environment with an SVM-based engine.

The same repository describes the implementation as a demonstration and educational project, not production software. It also discusses a centralized rollup configuration and identifies peer-to-peer synchronization and multiple sequencers as later work. That makes sequencing and decentralization important questions for users assessing a live deployment: the existence of open-source components does not by itself establish that every production security property is already active.

The role of the SOON token

SOON’s tokenomics documentation presents SOON as the ecosystem’s native utility token. The stated roles include governance, network activity across SOON Mainnet and SOON Stack chains, incentives for builders, and staking. The documentation says holders may vote on protocol upgrades, treasury management, ecosystem development, and reward distribution. These are documented intended functions; their practical scope depends on the governance contracts, voting rules, delegated power, and which decisions have actually been placed on-chain.

The tokenomics page lists an initial supply of 1 billion SOON and describes 3% annual inflation, while also recording a 30 million SOON burn associated with SIP-1. It allocates tokens across community, ecosystem, airdrop and liquidity, foundation and treasury, and team or co-builder categories. Because the page describes future distribution and incentive programs as subject to additional information, readers should treat the allocation table as a policy description and verify current unlocks and circulating balances through project disclosures and explorers.

Governance and staking control

SOON’s documentation assigns governance rights to token holders, including votes on mainnet upgrades and decisions affecting chains built with the SOON Stack. A separate forum discussion for SIP-3 describes a proposal to stake previously unlocked allocations for more than six months, with exceptions for certain ecosystem or community decisions through governance. The discussion shows how token-locking policy has been presented to the community, but it should not be read as proof that all proposed governance powers are fully decentralized or permanently fixed.

The tokenomics documentation also describes a planned validator model in which validators stake SOON and receive staking incentives, including a stated 3% annual token incentive. The exact relationship between this staking model, SOON Mainnet security, and Stack-chain operation requires careful checking of current validator software and governance documentation. The public code organization contains genesis and rollup-related repositories, but the repository pages inspected here do not establish the complete live validator set or its operational independence.

Cross-chain dependencies and intended users

SOON is aimed primarily at developers who want SVM-style execution without building a complete Layer 1 from scratch. The Stack is intended for teams deploying application-specific or general-purpose SVM chains, while SOON Mainnet is positioned as a general-purpose Layer 2. InterSOON is described as the messaging layer connecting these environments, with Hyperlane identified as the underlying cross-chain messaging provider.

This architecture creates dependencies beyond SOON’s own code. A deployment may rely on a settlement chain, a data-availability provider, a rollup infrastructure provider, a messaging system, and bridge or token-contract infrastructure. The official token documentation lists locked token addresses on BNB Chain, Solana, and Base, and public explorers provide separate views of token activity on those networks. Users therefore need to confirm the network and contract context before treating a balance, transfer, or liquidity position as interchangeable across chains.

What remains unproven

The central open question is whether the proposed stack can deliver durable usage across multiple deployments while preserving clear security responsibilities. The documentation names major components and external providers, but it does not by itself demonstrate sustained application demand, independent validator diversity, or the security of every bridge and messaging route. The public GitHub organization shows active infrastructure repositories, including rollup, proving, and genesis-related work, but repository activity should not be confused with production adoption or a completed audit of the full system.

Key takeaways

• SOON is presented as an Ethereum-settled Layer 2 and a toolkit for deploying SVM-based chains on different base layers.
• Its decoupled SVM design separates execution from settlement and data availability, but each deployment may introduce different infrastructure dependencies.
• SOON is documented as a governance, network, staking, and builder-incentive token rather than only a transferable asset.
• The documented token model includes 3% annual inflation, a 30 million SOON burn under SIP-1, and allocations for community, ecosystem, treasury, liquidity, and contributors.
• Governance and staking claims should be checked against live contracts, validator implementation, voting records, and current unlock data.
• The system’s security depends partly on settlement, data availability, messaging, sequencing, bridge, and infrastructure providers outside the SOON token itself.

Risks and open questions

• The public Igloo repository describes a centralized rollup framework and future work toward multiple sequencers; the decentralization status of each production deployment requires separate verification.
• SOON’s stated 3% annual inflation can dilute holders if network demand and staking participation do not grow sufficiently to offset issuance.
• Token allocations, vesting, staking locks, and circulating supply may change through governance, burns, migrations, or additional emissions.
• InterSOON and other cross-chain functions depend on messaging and bridge infrastructure, creating contract, validator, relayer, and integration risks.
• The tokenomics documentation states governance rights, but the inspected sources do not establish the full voting mechanism, voter concentration, quorum rules, or veto powers.
• External settlement and data-availability providers create dependencies that may affect cost, uptime, finality, and recovery procedures for SOON-based chains.