Based Rollups, Explained: Ethereum L1 Sequencing Architecture
A based rollup delegates transaction sequencing directly to Ethereum base-layer validators, removing centralized sequencer bottlenecks, restoring synchronous composability, and redirecting maximal extractable value to Layer 1.
Key points
- Based rollups delegate transaction ordering entirely to Ethereum Layer 1 block proposers, eliminating centralized sequencer single points of failure.
- Synchronous composability allows based rollup transactions and Ethereum Layer 1 transactions to execute within the same block atomically.
- Sub-second execution speeds are achieved through preconfirmations, where upcoming Layer 1 proposers stake collateral to promise transaction inclusion.
- Sequencer MEV and priority revenue flow directly back to Ethereum Layer 1 validators via existing builder auction mechanisms rather than staying with a private operator.
A based rollup is a Layer 2 scaling system that outsources its transaction ordering directly to the Layer 1 base blockchain rather than operating an independent sequencer. Under this architecture, the Ethereum block proposer for any given slot determines the sequence of Layer 2 transactions alongside base-layer transactions. This design eliminates the centralized operational dependencies common to standard rollups while inheriting the base layer's censorship resistance and liveness guarantees.
Traditional Layer 2 networks process transactions off-chain and post compressed state updates back to Ethereum. To achieve low latency, nearly all production rollups rely on a single operator, known as a sequencer, to order incoming user actions. While effective for throughput, this centralized sequencer introduces single points of failure, extraction of transaction ordering value, and regulatory vulnerabilities. Based rollups invert this structure by treating Ethereum's consensus layer as the sequencing engine itself.
The Centralized Sequencer Problem
To understand based architectures, one must first isolate the structural tradeoffs of modern scaling engines, as detailed in our guide on Layer 2s and Rollups, Explained: How Blockchains Scale. In standard optimistic and zero-knowledge rollups, the centralized sequencer acts as a private mempool and exclusive transaction sorter. The sequencer receives transactions from end users, establishes their linear execution order, executes them against the current Layer 2 state, and issues an immediate soft confirmation to the client.
This setup delivers sub-second confirmation times and cheap execution. However, it introduces acute operational risks. If the centralized sequencer experiences infrastructure outages or cloud downtime, the entire Layer 2 halts user submissions until the sequencer recovers or an emergency escape hatch activates. Furthermore, the single sequencer wields monopoly control over priority ordering, allowing it to extract arbitrage value, front-run user swaps, or selectively delay transactions without violating cryptographic proofs. Alternative sequencing models attempt to resolve this through distributed committees, an approach examined in Rollup Sequencers Explained: Centralized vs Decentralized Sequencing, but these introduce separate consensus overheads and token security models.
How Based Sequencing Works
In a based rollup, anyone can bundle Layer 2 transactions and submit them to the active Ethereum Layer 1 block proposer. The Layer 1 proposer serves as the sequencing coordinator. Ethereum validators do not need to execute the Layer 2 code or verify complex state transitions; their sole responsibility is to finalize the deterministic sequence of Layer 2 transaction batches on the base layer.
The mechanics integrate cleanly into Ethereum's modern block-building supply chain. In Ethereum's standard operational model, external entities known as block builders assemble proposed blocks from base-layer transactions and pass them to proposers. Under a based architecture, Layer 2 searchers and builders compile Layer 2 bundles. These builders submit their bundles directly to Ethereum Layer 1 block builders, who include them inside the broader Ethereum Layer 1 block payload. The Layer 1 validator signs and proposes the combined block, cementing the ordering of the Layer 2 transactions on the settlement layer.
Because ordering rights defer entirely to Ethereum Layer 1, a based rollup inherits the complete economic security and censorship resistance of the underlying validator set. An actor attempting to censor a specific Layer 2 transaction must censor that transaction on Ethereum Layer 1 itself, facing the total economic weight of the network's consensus protocol.
Synchronous Composability and Cross-Layer Execution
A primary architectural advantage of based sequencing is synchronous composability with Ethereum Layer 1. On standard rollups, interactions between Layer 1 and Layer 2 are strictly asynchronous: moving assets or triggering logic across layers requires multi-block waiting periods, bridge confirmations, and external relayers. Atomic cross-layer transactions are impossible because the Layer 1 block proposer and the Layer 2 sequencer operate on independent, uncoordinated clocks.
Because the Ethereum block proposer assembles both the Layer 1 transactions and the based rollup batch within the exact same block, operations on both layers can be linked conditionally. A smart contract on Ethereum Layer 1 and a smart contract on the based Layer 2 can execute within a unified atomic workflow. If the Layer 1 portion of the trade fails—such as an automated market maker flash loan or liquidation—the associated Layer 2 execution can be made to revert simultaneously.
This composability eliminates cross-domain arbitrage inefficiencies. Arbitrageurs can settle price discrepancies between a Layer 1 decentralized exchange and a based Layer 2 liquidity pool in a single atomic bundle. The capital risk of one leg executing while the other fails is completely eliminated.
Preconfirmations: Resolving the Latency Tradeoff
The fundamental limitation of standard based rollups is latency. Ethereum processes blocks in deterministic 12-second intervals, known as slots. If a based rollup relies exclusively on the Layer 1 block proposal for user confirmations, end users must wait up to 12 seconds for basic transaction certainty—an unacceptable degradation compared to the 200-millisecond response times of centralized sequencers.
Based rollups solve this latency challenge through preconfirmations (often termed "preconfs"). A preconfirmation is a cryptographically binding promise issued by an upcoming Ethereum Layer 1 proposer guaranteeing that a user's transaction will be included in their designated slot at a specific position.
To issue credible preconfirmations, Ethereum validators opt into a specialized commitment framework, often collateralized via staking protocols. The workflow operates as follows:
- A user submits a transaction directly to the lookahead proposer—the validator scheduled to propose an Ethereum block in the next slot.
- The proposer verifies the transaction validity and signs an off-chain receipt promising inclusion in the upcoming block.
- The user receives this receipt within hundreds of milliseconds, providing immediate economic finality.
- If the validator fails to include the transaction as promised when their slot arrives, the validator's posted collateral is slashed via automated slashing contracts.
Through preconfirmations, based rollups decouple user transaction speed from the underlying 12-second consensus interval while maintaining full Layer 1 sequencing authority.
Value Flow and Fee Sharing: A Worked Example
Centralized sequencers capture two primary revenue streams: base execution fees and maximal extractable value (MEV). In traditional rollup setups, the operating entity retains these revenues, leaving the Ethereum Layer 1 protocol to collect only the minimal blob data or calldata posting fee. Based rollups rewire these economic incentives by returning transaction ordering value directly to the Ethereum validator ecosystem.
This economic dynamic links directly to Ethereum's structural block auction market, detailed in Proposer-Builder Separation (PBS) on Ethereum, Explained. Layer 2 searchers capture MEV—such as arbitrage and liquidations—on the based rollup. To ensure their profitable bundles are included, searchers bid fees to Layer 2 block builders. These builders, in turn, package Layer 2 blocks and bid in the Layer 1 PBS auction to convince the Ethereum Layer 1 proposer to select their combined block.
Consider a hypothetical single-block economic scenario to illustrate this fee distribution. Assume a based rollup generates user activity within a single 12-second slot under the following parameters:
- Aggregate Layer 2 user execution fees: 0.15 $ETH
- Total Layer 2 MEV extracted across automated market makers: 0.35 ETH
- Total gross value generated by the Layer 2 batch: 0.50 ETH
- Cost to post data availability blobs to Ethereum Layer 1: 0.05 ETH
In this environment, Layer 2 builders compete to have their batch selected. Due to competitive builder bidding dynamics, builders bid the majority of their extractable margin to the Layer 1 block builder. Assume the winning builder retains a 0.02 ETH operating margin and incurs the 0.05 ETH base layer data availability cost. The builder forwards the remaining balance to the Layer 1 proposer:
$$\text{Proposer Fee} = 0.50\text{ ETH (Gross Value)} - 0.05\text{ ETH (Data Cost)} - 0.02\text{ ETH (Builder Margin)} = 0.43\text{ ETH}$$
Under this model, 0.43 ETH flows directly to the Ethereum Layer 1 validator who proposed the block, while 0.05 ETH is paid to the protocol's data availability market (where base portions are burned according to fee mechanics). In a centralized sequencing framework, the 0.43 ETH margin would remain entirely with the rollup operating company. Based sequencing realigns the economic incentives between the rollup scaling layer and the base security layer.
Common Misconceptions
"Ethereum nodes must run Layer 2 virtual machines to sequence based rollups." Ethereum Layer 1 validators do not execute Layer 2 transactions, calculate state roots, or verify zero-knowledge proofs during the sequencing phase. Validators simply order opaque transaction bundles. The execution and cryptographic validation of those transactions remain entirely isolated to Layer 2 nodes and dedicated provers.
"Based rollups are inherently slow because Ethereum has a 12-second block time." While settlement finality adheres to Ethereum's block intervals, user-facing latency is mitigated through proposer-signed preconfirmations. By utilizing opt-in slashing collateral, lookahead validators can offer sub-second transaction guarantees that hold equivalent economic finality to traditional sequencer soft confirmations.
"Based rollups eliminate maximal extractable value." Based sequencing does not eliminate MEV; it democratizes and redirects it. Instead of a single rollup operator extracting and retaining ordering arbitrage, the extraction mechanism shifts to open competitive markets (searchers and builders), with the ultimate economic rent captured by the decentralized Ethereum validator base.
How This Connects to the Market
As the decentralized finance ecosystem matures, the structural divergence between rollup architectures carries direct market implications. Institutional capital frequently cites the governance and technical centralization of Layer 2 sequencers as a principal custody and liveness counterparty risk. A rollup operator capable of halting block production or altering sequencing poses distinct legal and operational challenges for high-value settlement.
Based rollups address this concern by anchoring operational availability to Ethereum's decentralized validator set, eliminating the single-operator failure vector. However, this model introduces competitive trade-offs. Scaling teams that adopt based architectures voluntarily forfeit monopoly sequencer revenues, relinquishing high-margin cash flows to the Ethereum base layer. Market participants monitoring rollup development should observe the evolution of validator opt-in rates for preconfirmation protocols, the integration of based bundle endpoints within major MEV-Boost relays, and the ongoing fee dynamics between Layer 2 execution margins and Layer 1 validator yields.
Questions this story raises
- What is the primary difference between a based rollup and an optimistic or ZK rollup?
- A based rollup is defined by its sequencing mechanism, not its proving mechanism. A based rollup can use either optimistic fraud proofs or zero-knowledge validity proofs; its distinguishing feature is that it relies on Ethereum Layer 1 validators to order transactions instead of using an independent, centralized sequencer.
- Does a based rollup increase hardware requirements for Ethereum validators?
- No. Ethereum Layer 1 validators only order the data bundles within standard block limits. They do not execute the transactions or compute Layer 2 state transitions, meaning validator hardware requirements do not change.
- What happens if a validator signs a preconfirmation but fails to include the transaction?
- Validators that issue preconfirmations must opt into a slashing contract with staked collateral. If a validator issues an authorized preconfirmation receipt and fails to deliver the transaction in their assigned slot, their collateral is slashed programmatically.
- Why don't all rollups use based sequencing?
- Centralized sequencers provide rollup development teams with lucrative revenue streams from transaction ordering fees and internal MEV capture. Transitioning to based sequencing redirects these cash flows to Layer 1 validators and requires advanced infrastructure like preconfirmation networks.
References
- [1] Proposer-Builder Separation — Ethereum Foundation
- [2] Based Rollups — Ethereum Foundation
- [3] Consensus Specifications — Ethereum Foundation
Evergreen explainer written by Basis Desk's system and checked by an independent model pass for factual errors and advice language. Figures, fees and rules change — the references above are where to verify current specifics. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.