Rollup Transaction Lifecycle: A Visual Technical Guide

Data availability (DA) is identified as the next major bottleneck after execution scaling. Ethereum's EIP-4844 upgrade introduced blob space for Layer 2s, with initial implementation providing 384 kilobytes per block. The roadmap progresses through phases: first, Proto-Danksharding reduces node storage requirements from perpetual to 17 days; second, full Danksharding implements two-dimensional data availability sampling, enabling sublinear scaling where adding more nodes or blobs means each node does less work. This progression supports Base's goal of scaling to 1 gigagas per second or higher. For Base specifically, staying connected to Ethereum's DA layer maximizes trust, while other teams may experiment with alternative DA solutions at L3 for different trust-security trade-offs.

Ethereum's scaling roadmap progresses through Proto Danksharding (200 TPS), Full Danksharding (50,000 TPS), and EigenDA (500,000+ TPS, targeting 50 million TPS). In the rollup-centric vision, L2s inherit security but require proof verification (ZK rollups) or fraud proof adjudication (optimistic rollups), plus posting data to a DA service. DA systems function as high-availability bulletin boards, not long-term storage, with data expiring after ~2 weeks. Data blobs attach via transactions with fingerprints, using EIP-1559-style fee mechanics (131,072 gas per blob). Full Danksharding increases capacity from 3 to 128 blobs (43x increase) through data sharding across 32 subnets. Erasure coding treats blobs as polynomial points where any 50% can reconstruct the whole, enabling robust sampling. KZG commitments provide cryptographic verification. EigenDA achieves horizontal scaling (adding machines increases capacity) unlike Ethereum's vertical scaling, using 4.54:1 erasure coding and dispersing data proportionally to restaked ETH. This enables 500,000-600,000 TPS now, targeting 1 GB/second (40-50 million TPS) for applications like MegaETH (100,000 TPS) and global financial systems.

Ethereum's data availability layer is evolving from a monolithic architecture where all nodes download the entire chain to a rollup-centric model using EIP-4844's blob data resource (128KB chunks with their own fee market and 18-day expiry), which increases capacity by approximately 5x. The next phase, Danksharding, introduces data availability sampling using erasure coding, where any 50% of data can reconstruct the full blob, enabling nodes to verify data availability by sampling only a few points rather than downloading everything. This sampling approach, combined with subnet-based data distribution, could increase block capacity from 3-6 blobs to 32-64 blobs per slot (10x increase) or potentially 256 blocks with 2D construction, fundamentally changing how Ethereum handles data availability at scale.

Cheap DA unlocks new blockchain applications: central limit order books with fraction-of-penny fees, on-chain games, deep learning networks, and smoother social media. Rollups select DA providers based on live status, infrastructure maturity, security trade-offs, cost economics, and ecosystem alignment. Projects like Eclipse chose Celestia initially for being the only live verifiable DA layer besides Ethereum. Ethereum's EIP-4844 (Proto-Dank Sharding) introduces blobs per block to reduce DA costs, but full Dank Sharding targeting 10,000 TPS may still fall short of demand. The choice between Ethereum-native DA and alt-DA involves balancing immediate practicality against long-term strategic considerations of security, cost, and ecosystem alignment.

Proto-dank sharding is being proposed as a key first step toward full dank sharding implementation. It comes with Ethereum Improvement Proposal 4844, authored by Ethereum researcher Dank Rad Feist and co-founder Vitalik Buterin. The proposal involves adding a new transaction type called blob-carrying transactions to Ethereum. Currently, Ethereum blocks can carry 50-100 kilobytes of data, but under proto-dank sharding, they'll be able to carry closer to one megabyte—a 10 times increase in data availability. While this is less than the 16 megabytes projected under full dank sharding, it should significantly decrease the cost of using roll-ups and pave the way for cheaper, quicker layer 2 networks.

Maximal Extractable Value (MEV) represents the amount of money extractable from blockchain systems through strategic transaction manipulation. Originally termed 'miner extractable value' in the 2019 Flash Boys 2.0 paper, it evolved to generalize beyond miners to any account. The term emphasizes extractability over actual extraction, serving as a scientific tool for analyzing incentives. MEV drives blockchain centralization through multiple vectors: barrier to entry increases as sophisticated actors with PhD teams, low-latency infrastructure, and capital advantages dominate; infrastructure centralization emerges through shared stake token infrastructure and block builder monopolies; latency advantages create exclusive order flow access. Proposer-Builder Separation addresses this by separating sophisticated building from simple proposing, keeping proposers unsophisticated while maintaining permissionless market competition. MEV operates through a pipeline: Users → Wallets → Searchers → Builders → Relays → Proposers, with each actor having conflicting incentives. L2 blockchains like Arbitrum and Optimism use centralized sequencers preventing sandwich attacks but creating trade-offs: decentralized sequencing would enable market-based MEV dynamics but reintroduce sandwiching risks. Encrypted ME pools protect users by hiding transaction contents through three main technologies: Suave using hardware enclaves (Intel SGX/AMD SEV), threshold encryption with federated committees, and delay encryption relying purely on cryptography.

MEV (Maximal Extractable Value) is the ability to manipulate transaction ordering to extract value, such as front-running trades or arbitrage opportunities. Decentralizing sequencers is crucial because centralized sequencers can manipulate economics significantly. The challenge is that decentralizing sequencers introduces complexity and may reduce the benefits of removing consensus overhead from the base layer.

A rollup sequencer receives transactions, determines order, provides soft confirmations, executes state transitions, and posts results to L1. This centralizes ordering authority, creating censorship risks absent in L1 consensus. Decentralizing sequencers requires applying L1-style consensus (like Tendermint) to the sequencer role, creating validator sets that rotate leadership and inherit censorship resistance. This improves real-time guarantees while maintaining faster L2 block times. Shared sequencer models allow multiple rollups to use common sequencing infrastructure, either through pure fork-choice approaches inheriting L1 guarantees or more sophisticated models separating ordering from execution. Cross-domain MEV can be achieved economically without shared sequencing through sophisticated actors who understand risk and execute across domains, relying on trustless settlement through oracles reporting state changes.

Sequencer design involves fundamental trade-offs between performance and decentralization. Shared sequencing creates centralization risks and social coordination challenges, with every large chain incentivized to build its own sequencer. MEV attribution presents critical challenges requiring careful redistribution mechanisms to ensure dApps capture value rather than users or sequencers. The base rollup philosophy accepts certain trade-offs (block time, latency) in exchange for avoiding shared sequencer complexity, prioritizing execution environment innovation when app chain incentives are eliminated through proper incentive alignment. Wallet compatibility issues also present security challenges requiring chain ID differentiation solutions.

Centralized L2 sequencers fundamentally contradict the vision of censorship-resistant blockchain infrastructure. With $38 billion secured across all L2s, users currently depend on trust-based relationships with central entities controlling transaction ordering, state reporting, and inclusion guarantees. This creates vulnerabilities where sequencers can lie about transaction status, prioritize certain transactions, and experience liveness failures lasting hours or days. As crypto adoption grows, the probability of a central entity sharing users' values diminishes, increasing censorship risks. Forced inclusion is often mistaken for decentralization—it functions like a traffic jam, working under normal conditions but failing during congestion. True decentralized sequencing ensures all transactions have equal properties for censorship resistance and liveness. The core argument is that L2s must inherit Ethereum's censorship resistance, liveness, and safety properties through decentralized sequencer design rather than relying on trust-based relationships.

With shared sequencers, transactions for multiple rollups can be submitted in bundles, but atomic execution is challenging due to lazy execution. For atomic execution, transactions must be placed at the top of the block after simulation. Design builders are rollup nodes that simulate execution to ensure atomic cross-rollup transactions, similar to flashbots models. Bridging from sequencer to rollup involves users submitting lock transactions that rollup nodes identify and mint corresponding funds. Bridging from rollup to another chain involves state root posting with optimistic or ZK proofs, validated by rollup state root trackers.

Cross-rollup transactions require safety guarantees comparable to normal transactions. Rollup transactions settle when validity proofs are verified by Ethereum L1. NEBRA's approach aggregates all validity proofs from different rollups with safety proofs for cross-rollup transactions into a single proof settling on Ethereum, using L1 security for safety. The shared sequencer approach enforces atomic composability early, while NEBRA's settlement layer approach enforces it later, providing more flexibility and sovereignty to rollups. NEBRA OS (Open Stack) provides an integrated stack for deploying ZK rollups, enabling one-click or permissionless deployment without business negotiations with oracles and bridges. The stack is open source from day one and designed for interoperability with other stacks like OP stack, ZK stack, and Polygon AggLayer. NEBRA views this as a collaborative space rather than zero-sum competition, aiming to fulfill the vision of putting a ZK rollup on every desk and phone.

EigenLayer partnered with Near Protocol to create bridges between L2s using Near as a data availability layer. The speaker argues cross-rollup interoperability is an engineering problem, not a deal-breaker, as users have not complained about composability issues. Data availability networks compete on security and cost, with the gold standard being Ethereum layer one. This reflects broader ecosystem dynamics where interoperability challenges are solved through engineering rather than representing fundamental architectural limitations. The narrative that interoperability is a deal-breaker doesn't reflect actual user needs or technical solutions available.

Layer 2 success depends on network effects and liquidity. Arbitrum captured the perpetual DEX sector by providing composable infrastructure that other platforms could build on. Successful Layer 2s distribute tokens to users and platforms, creating sticky liquidity and capital. The challenge is maintaining user and liquidity stickiness after initial rewards end. Bridges are evolving from simple mint-burn mechanisms to their own execution layers. Modularization enables executing smart contracts on one chain while settling on another. Projects like Gravity Bridge and Axelar offer modular stacks for cross-chain execution. Liquidity porting systems allow moving assets across chains without manual bridging. The goal is seamless token movement and execution across chains within the same transaction. Roll-Ups tethered to Ethereum can use it to prove state changes between chains. Account abstraction enables transactions to route through multiple roll-Ups with proofs between each step. This creates tightly coupled systems using shared tokens for gas, eliminating bridge problems. The end goal is seamless bridging between roll-Ups through shared standards, enabling atomic cross-chain transactions without manual bridging or gas token issues.

Modern rollup platforms provide end-to-end tooling for institutional actors to launch rollups with minimal effort (one-click deployment). ZK proofs are essential for scaling, enabling both execution efficiency and future link consensus improvements. Interoperability between rollups is essential for asset movement and cross-chain communication. Synchronous composability allows faster message passing (seconds/minutes) compared to optimistic rollups (7 days). Design choices like frequent L1 state checks and shared proofs enable faster settlement and cross-rollup communication. The ecosystem continues evolving toward more open solutions for bridging and cross-chain contract calls.