Termina
  • Overview
    • Introduction
    • Quickstart
  • Solana Primer
    • Solana Virtual Machine (SVM)
    • Existing Scaling Solutions
    • Why Termina
  • Network Extension Stack
    • Overview
    • FAQs
    • NE Modules
      • SVM Engine Module
        • Engine Internals
        • Launching an Instance
      • zkSVM Prover Module
        • Prover Mechanics
        • Leveraging the zkSVM
      • Data Module
    • Rollups
  • Socials
    • Twitter
    • Discord
    • Website
Powered by GitBook
On this page
  1. Solana Primer

Existing Scaling Solutions

PreviousSolana Virtual Machine (SVM)NextWhy Termina

Last updated 4 days ago

While Solana’s core infrastructure provides high speed and composability, the growing complexity and diversity of SVM dApps requires tailored solutions to provide congestion resistance, enhanced privacy, and advanced data processing.

One common misconception is that Solana doesn’t need L2s when in fact the ecosystem already has a number of notable L2 projects. Please see this blog for a high-level exploration of these dApps. The scaling solutions that have emerged can be organized into three main categories: rollups, batchers, and Solana Permissioned Environments (SPEs). However, each of these present a unique set of tradeoffs and often diverge from Solana’s vision of a globally unified state machine and its commitment to preserving liquidity and interoperability.

Type
How It Works
Tradeoffs
Examples

Rollups

Executes transactions off-chain and sends state summaries to Solana, secured by fault proofs

Can fragment state & liquidity

Zeta’s Bullet L2 (perpetuals DEX)

Batchers

Combines transactions off-chain and re-executes the net transactions on Solana

Adds delay before execution

Code (P2P payments), Cube (hybrid CEX/DEX)

Appchains / SPEs

Uses its own validator set and operates independently from Solana mainnet

Separate trust model & liquidity

Pyth (oracle network), Spherenet (merchant payments)