1. Layer 2: Motivation and Design Principles

Layer 2 (L2) solutions move most activity off-chain while retaining security guarantees anchored in the base layer. Design goals include:

• Higher throughput and lower fees.
• Reduced load on Layer 1.
• Preservation of decentralisation and security properties.

L2 solutions differ primarily in:

• Where computation occurs.
• Where data is stored.
• What assumptions underpin safety (cryptographic proofs vs fraud proofs vs federation trust).

2. Payment Channels and State Channels

Payment channels allow two parties to transact many times off-chain while only using the base layer for:

• Channel opening (funding transaction).
• Channel closing or dispute resolution.

Off-chain, parties exchange signed updates representing the latest balance allocation. Only the final (or disputed) state is settled on-chain.

2.1 Properties

• Near-instant, low-cost off-chain transfers.
• Liveness depends on parties being online or using watchtowers.
• Suitable for repeated interactions among a small set of participants.

3. Channel Networks and Routing

Networks of payment channels (e.g., Lightning Network) enable payments between users without direct channels:

• Multi-hop payments route value via intermediaries.
• Hashed timelock contracts (HTLCs) coordinate conditional transfers.
• Routing algorithms must find paths with sufficient liquidity.

Challenges include liquidity fragmentation, route discovery, and managing channel rebalancing.

4. Sidechains, Plasma and Child Chains

Sidechains are separate blockchains interoperable with a main chain via a bridge:

• Assets are locked or burned on the main chain.
• Representation tokens appear on the sidechain.
• Users rely on the sidechain’s security assumptions.

Plasma-style constructions aim to inherit base-layer security by:

• Committing sidechain state roots to the main chain.
• Allowing users to exit with proofs in case of operator misbehaviour.

5. Rollups: General Architecture

Rollups execute transactions off-chain (on a separate engine or sequencer) and post compressed data and/or proofs to Layer 1. The base layer acts as:

• Data availability layer (for optimistic rollups and many ZK rollups).
• Settlement and dispute resolution layer.

Two major categories:

• Optimistic rollups: assume correctness by default; rely on fraud proofs.
• ZK rollups: provide validity proofs (e.g., SNARKs/STARKs) for each batch.

6. Optimistic Rollups: Fraud Proofs and Challenge Windows

In optimistic rollups:

• Sequencers propose batched transactions and resulting state roots.
• Data (transaction inputs) are posted on-chain for transparency.
• There is a challenge window during which anyone can submit a fraud proof if they detect an invalid transition.

Security is derived from:

• At least one honest party willing to verify and challenge.
• Economic incentives and bonds posted by sequencers.
• Availability of data to reconstruct state transitions.

7. ZK Rollups: Validity Proofs and Cryptographic Guarantees

ZK rollups generate succinct validity proofs attesting that:

• All transactions in a batch were executed correctly.
• State transitions conform to the rollup’s rules.
• No fraud proofs or challenge windows are necessary for correctness (though exits may still be delayed for UX reasons).

Trade-offs:

• Stronger correctness guarantees.
• Higher prover complexity and specialised hardware.
• More complex circuits and proving systems.

8. Bridges and Cross-Chain Interoperability

Bridges connect otherwise independent chains or rollups, enabling asset movement and message passing. Designs vary by trust model:

• Trusted or federated bridges: rely on a set of operators.
• Light-client-based bridges: verify consensus proofs on-chain.
• Hybrid approaches: combine on-chain verification with off-chain committees.

Bridges are a major source of systemic risk, as compromised bridges can lead to large-scale asset theft or mis-accounting.

9. Security and Failure Modes in Layer 2 and Cross-Chain Systems

Key risk categories include:

• Sequencer censorship or downtime.
• Fraud-proof mechanism failures (optimistic rollups).
• Prover bugs or proof system vulnerabilities (ZK rollups).
• Bridge key compromise or incorrect verification logic.
• Economic attacks exploiting liquidity fragmentation across chains.

Robust L2 design requires explicit modelling of these risks and mitigation strategies such as: decentralised sequencer sets, fallback paths, circuit audits, and conservative bridge designs.

10. Module and Course Summary

In this module, we examined Layer 2 scalability patterns: channels, sidechains, Plasma-like constructions, optimistic and ZK rollups, and cross-chain bridges. We discussed their security assumptions, performance characteristics, and common failure modes.

Across the full course, you have developed a systems-level perspective on:

• Blockchain architecture and data structures (Module 1).
• Consensus mechanisms including Nakamoto-style and stake-based protocols (Module 2).
• Classical BFT consensus, finality, and safety arguments (Module 3).
• Layer 1 scalability via sharding, DAGs and protocol optimisations (Module 4).
• Layer 2 scalability and cross-chain systems (Module 5).

This foundation positions you to critically analyse new blockchain designs, understand their consensus and scalability trade-offs, and evaluate their suitability for real-world applications that demand reliability, throughput, and security.