Syrax

Products

Payments Exchange Intelligence Vault Syrax Chain SRX Token Tokenisation Rewards Sentinel

Solutions

All industries

Developers

Syrax Chain for builders Faucet Governance

Company

Insights About Careers Compliance Security Labs Quant
Open the app
Insights · Technology

Layer 1 vs Layer 2 Blockchains

The base layer secures; the second layer scales. Here is how they fit together.

A Layer 1 (L1) is a base blockchain that provides security and final settlement; Ethereum is the best-known example. A Layer 2 (L2) is a network built on top of an L1 to increase speed and reduce cost, while relying on the L1 for security.

The base layer

A Layer 1 maintains its own validators, its own consensus rules and its own record of transactions. Ethereum, BNB Chain and Solana are all Layer 1s, each with different design choices on speed, decentralisation and cost.

Base layers prioritise security and decentralisation. Every validator must be able to check every transaction, and that requirement limits how many transactions the network can process per second. When demand rises, users compete for limited space and fees climb. See understanding gas fees for how that works.

The trade-off is often described as a trilemma: it is hard to maximise security, decentralisation and scalability all at once. Layer 1 chains choose different balances. Layer 2 networks are one way to improve scale without rewriting the base layer's priorities.

Why Layer 2 exists

L2s process transactions off the base chain and post compressed proofs or data back to it, scaling capacity without sacrificing the L1's security properties. Users get faster confirmation and lower fees, and the L1 remains the final judge of what is valid.

The central idea is to move the heavy work away from the base layer while keeping a verifiable link to it. Hundreds or thousands of transactions are bundled into one batch, so the L1 handles one submission rather than many.

What happens to a transaction

  1. The user sends a transaction to the Layer 2 network.
  2. A sequencer orders it and executes it quickly, giving fast confirmation.
  3. Transactions are bundled into a batch.
  4. The batch, with its proof or data, is posted to the Layer 1.
  5. The Layer 1 records the outcome as final once the rules for that rollup are satisfied.

Costs are shared. The fee to post one batch to the base layer is split across every transaction in it, which is why fees on a rollup can be a fraction of the base-layer cost.

Rollups

  • ZK rollups post a cryptographic validity proof for each batch.
  • Optimistic rollups assume validity and allow a challenge window.

How they differ in practice

ZK rollupOptimistic rollup
CorrectnessProven mathematically per batchAssumed, then open to challenge
Withdrawal to L1Can finalise once the proof is verifiedWaits for the challenge window to close
Main costGenerating proofs is computationally heavyRelies on someone watching and disputing errors

The proof system behind ZK rollups is explained in zero-knowledge proofs explained.

Other scaling approaches exist, such as sidechains and state channels, which run with their own security rather than inheriting it from the base layer. Rollups are generally considered the strongest option for inheriting security because they publish the data needed to reconstruct their state on the Layer 1.

Proof-based designs add a further benefit: a batch that carries a valid proof cannot contain an invalid state transition, so the base layer can accept it without waiting for a dispute.

Trade-offs to weigh

  • Security inheritance. An L2 is only as secure as its connection to the L1, including how data is made available and how exits work.
  • Liquidity. Assets and applications can be spread across several networks, which fragments liquidity.
  • Bridging. Moving assets between layers adds steps and, if poorly designed, risk. See cross-chain interoperability.
  • Operator design. Some L2s rely on a single sequencer to order transactions, which affects censorship resistance and uptime.

Exit assumptions deserve particular attention. The user should be able to withdraw assets to the base layer even if the Layer 2 operator is unavailable, and the mechanism for doing so should be documented and tested.

Why institutions care

Regulated activity needs predictable cost, fast confirmation and a clear settlement assurance. A Layer 2 can offer the first two and inherit the third from its base layer, which is the combination institutional markets look for. Cost matters most for high-volume use such as payments, where a fee of even a small amount per transaction becomes significant at scale.

Auditability is the other half. Because a Layer 2 posts its results to the base layer, an auditor or supervisor can check the record against an independent public ledger, without depending only on the operator's own reporting.

Predictable fees are valuable in their own right. A finance team can budget for transaction costs far more easily when they stay low and stable than when they swing with congestion on the base chain. This is a large part of why payments and trading, which involve many small transactions, are natural candidates for a rollup.

Choosing between layers

There is no universally right layer. The answer depends on what the application needs.

  • An application that moves large values rarely and needs maximum assurance may settle directly on a Layer 1.
  • An application with many small, frequent transactions, such as payments or trading, usually benefits from a Layer 2.
  • An application with users on several networks needs a plan for bridging and for the liquidity spread between them.

Many designs combine the two: activity runs on a Layer 2 for speed and cost, and final settlement and high-value movements rely on the base layer.

Where Syrax sits

The Syrax chain is designed as a zero-knowledge Layer 2, built for high throughput and low cost, with settlement anchored to Ethereum. It is built to post validity proofs for its batches, so that the base layer can verify them rather than take them on trust.

The wider ecosystem targets Ethereum, BNB Chain, Solana and ZKsync, and core logic is designed to work across all four. Terms are defined in the glossary.

Settlement on an established base layer is also relevant to custody and audit. A record that is anchored to Ethereum can be checked by any third party, regardless of who operates the Layer 2.

For the technology that makes the design possible, read zero-knowledge proofs explained. Each regulated Syrax service will launch only upon receipt of the applicable licences.

This article is for information only and does not constitute financial, legal or investment advice. Each regulated Syrax service will launch only upon receipt of the applicable licences.