Choosing between an appchain and a shared L2 mainnet is a fundamental architectural decision that defines your protocol's performance and operational model.
Scroll Appchain excels at providing dedicated, predictable throughput by leveraging the Scroll Stack to create a sovereign rollup. This architecture isolates your application's traffic, eliminating competition for block space. For example, a high-frequency DeFi protocol can achieve consistent sub-2-second finality and scale its TPS independently of the broader Scroll ecosystem, avoiding network congestion from popular NFTs or meme coins.
Scroll Mainnet takes a different approach by offering a shared, highly secure scaling environment for Ethereum. This results in immediate composability with a growing ecosystem of protocols like SyncSwap, LayerBank, and Ambient Finance, but introduces variable performance. While peak throughput can reach 100+ TPS, actual user experience depends on overall network demand, which can increase transaction costs and latency during high-traffic events.
The key trade-off: If your priority is guaranteed performance, customizability (e.g., custom gas token, precompiles), and sovereignty, choose the Scroll Appchain. If you prioritize immediate ecosystem liquidity, developer tooling maturity (like Hardhat & Foundry plugins), and shared security from day one, choose Scroll Mainnet.
Throughput isn't just TPS. It's about predictable performance, cost efficiency, and resource isolation. Here's how the two architectures compare for high-demand applications.
Guaranteed block space: Your application doesn't compete for resources with other protocols like Uniswap or Aave. This provides predictable transaction inclusion and latency, critical for high-frequency DeFi or gaming. You control the gas limit and block time.
Tailored performance: Implement custom precompiles, adjust gas schedules, or modify state access patterns specifically for your application's logic. This can drastically increase effective TPS for specialized workloads compared to the one-size-fits-all mainnet EVM.
Instant composability: Tap into the aggregated liquidity and user base of the entire Scroll ecosystem. Transactions interact seamlessly with native protocols like SyncSwap, Ambient, and LayerBank without bridging, maximizing capital efficiency.
Battle-tested infrastructure: Benefits from continuous, protocol-wide optimizations to the base layer (e.g., zkEVM proof generation, data availability). Handles the aggregate load of all applications, with current peaks exceeding 100+ TPS and a roadmap for multi-threaded provers.
Direct comparison of throughput, cost, and finality for deployment decisions.
| Metric | Scroll Appchain | Scroll Mainnet |
|---|---|---|
Peak TPS (Theoretical) | 10,000+ | 200 |
Avg. Transaction Cost | ~$0.001 - $0.01 | ~$0.10 - $0.50 |
Time to Finality | < 4 sec | ~12 min |
Data Availability Layer | Custom (e.g., Celestia) | Ethereum L1 |
Sequencer Control | Sovereign / Permissioned | Decentralized (Planned) |
Native Gas Token | Flexible (e.g., USDC) | ETH |
Choosing between a dedicated zkEVM appchain and the shared mainnet involves critical trade-offs for transaction speed and capacity. This breakdown focuses on throughput metrics and architectural constraints.
Guaranteed capacity: Your application has exclusive access to the sequencer and block space, eliminating competition from other protocols like Uniswap or Aave. This is critical for high-frequency applications (e.g., on-chain gaming, order-book DEXs) that require predictable, low-latency execution.
Architectural control: As an appchain operator, you can increase the block gas limit and adjust parameters like block time to maximize TPS for your specific workload. This allows for vertical scaling beyond the mainnet's shared constraints, potentially achieving 1000+ TPS for optimized contracts.
Contained failure domain: Network congestion or a gas spike from a popular NFT mint only affects your application's chain, not the entire Scroll ecosystem. This provides operational stability and simplifies capacity planning, but requires you to manage your own validator set and security assumptions.
Settled on Ethereum L1: Every batch of transactions is proven and finalized on Ethereum Mainnet, leveraging its ~$500B+ economic security. This provides strong, verifiable finality for high-value DeFi applications where security is non-negotiable, at the cost of being bound by L1 batch posting intervals.
Instant composability: Your protocol interacts seamlessly with the entire Scroll ecosystem—liquidity from native DEXs, users from major wallets, and assets from bridges. This reduces bootstrap time and is ideal for general-purpose DeFi and consumer dApps that thrive on interconnectedness, not raw isolation.
Constrained by shared resources: Throughput is limited by the mainnet's batch submission speed to Ethereum and competition for block space from all other dApps. During peak demand, TPS is shared, leading to potential latency. This is the core trade-off for using a managed, secure layer-2.
Choosing between a dedicated appchain and the shared mainnet is a critical throughput decision. Here are the key trade-offs for high-volume applications.
Guaranteed block space: Your application does not compete with other protocols for L1 block inclusion. This eliminates non-deterministic finality delays and provides consistent TPS for your specific state transitions. This matters for orderbook DEXs like dYdX or high-frequency gaming where latency spikes are unacceptable.
Direct Ethereum finality: Transactions are finalized upon successful verification on Ethereum L1, providing the highest security guarantee. Throughput is bounded by Ethereum's provenance proof verification speed (~12-15 minutes per batch). This matters for bridges holding >$100M TVL or institutional DeFi where security is non-negotiable.
Verdict: The default choice for broad liquidity and security. Strengths: Direct access to Scroll's native DeFi ecosystem (e.g., Ambient Finance, SyncSwap) and its ~$1B TVL. Inherits Ethereum's security via zkEVM, which is non-negotiable for high-value protocols. Seamless composability with other mainnet dApps. Trade-offs: Subject to network congestion and variable gas fees during peak demand. Throughput is shared across all mainnet applications.
Verdict: Ideal for specialized, high-frequency financial products. Strengths: Guaranteed, dedicated throughput (10k+ TPS) and sub-second finality for order books, perpetuals, or options. Customizable gas token and fee structure (e.g., subsidized transactions). Sovereign control over upgrades and MEV policies. Trade-offs: Requires bootstrapping your own liquidity and validator set. Introduces additional trust assumptions if using a permissioned validator set.
Choosing between a Scroll Appchain and the Scroll Mainnet is a strategic decision between ultimate control and seamless composability.
Scroll Appchains excel at providing dedicated, predictable throughput and minimal latency because they operate as sovereign zkEVM rollups with isolated state. For example, a high-frequency DeFi protocol can achieve sub-second finality and avoid network congestion from unrelated NFT mints, guaranteeing its users consistent performance. This architecture is ideal for applications with extreme performance requirements or those needing custom gas token economics and governance.
Scroll Mainnet takes a different approach by offering shared security and deep liquidity within a unified ecosystem. This results in superior composability—your protocol can interact natively with established DeFi primitives like Ambient Finance or Pencils Protocol without cross-chain bridges—but you accept variable transaction costs and potential throughput contention during peak network activity, as seen in shared L2 block space.
The key trade-off: If your priority is maximum, guaranteed performance and architectural control for a specific vertical (e.g., a high-TPS gaming engine or institutional trading venue), choose a Scroll Appchain. If you prioritize immediate ecosystem access, shared security, and seamless composability with existing DeFi and NFT applications, choose the Scroll Mainnet. The decision hinges on whether isolated optimization or integrated network effects deliver more value to your end-users.
Stop patching. Start engineering. Get a free technical roadmap and a 30min strategy call.