FAQs
Network Extensions (NEs) expand Solana’s execution capabilities while staying integrated with its base layer. Rollups are a subset of NEs that process transactions off-chain and post proofs back to Solana.
While all rollups are NEs, not all NEs are rollups, some function as standalone modules that scale specific parts of an application.
How does sequencing work?
Sequencers are not required for NEs. Transactions can still be ordered, but execution can happen without a strict sequencing model.
Rollups use sequencers to order transactions in a block before submitting them to Solana. Sequencing is mandatory and can be centralized or permissionless (with staking for security).
How does block building happen?
NEs don’t create blocks in the traditional sense. Instead, they execute transactions off-chain and submit final results (state updates or proofs) to Solana.
Rollups batch transactions into blocks, compute the state changes, and submit the block state root to Solana.
How does L1 ↔ NE message passing work?
NEs don’t need bridges for Solana-native interactions. Instead, they use direct state reading/writing (e.g., SVM Engine can pull Solana state and update it later).
Rollups use bridges (e.g., Hyperlane) to pass messages between Solana L1 and the rollup.
How does existing infra (stables, RPCs, etc.) connect with NEs?
NEs stay on Solana, no bridges are required. Stablecoins and tokens remain native, and RPCs can query both L1 and NE execution layers.
Rollups are required to bridge stablecoins and assets since they operate in a separate execution environment.
TL;DR:
Rollups require sequencers, bridges, and block-building logic.
Termina’s NEs are modular and don’t need sequencers or bridges, reducing complexity.
NEs interact directly with Solana L1, keeping liquidity and composability intact.
Last updated