What Is a Based Rollup? L1-Sequenced Scaling Explained

A based rollup is a layer-2 design where transaction sequencing is handled directly by Ethereum's own layer-1 block proposers, rather than by a separate, dedicated sequencer operated by the rollup's own team. This removes an entire piece of centralized infrastructure that most rollups currently depend on, at the cost of tying the rollup's transaction timing more closely to Ethereum's own block production.

The problem based rollups are trying to solve

As covered in our piece on evaluating L2 decentralization, one of the biggest centralization points across most rollups today is the sequencer: a single operator, usually the founding team, responsible for ordering every transaction on the chain. This creates a single point of failure and a meaningful concentration of power, including the ability to reorder transactions for MEV extraction or, in a worst case, censor specific users or transactions.

Decentralizing sequencing has proven to be one of the harder problems in the rollup design space — building an entirely new, robust, decentralized sequencer network from scratch is a significant undertaking with its own risks.

The based rollup approach: reuse Ethereum's proposers

Based rollups sidestep building new sequencer infrastructure entirely by having Ethereum's existing layer-1 block proposers include and order the rollup's transactions as part of their normal Ethereum block production duties. Since Ethereum's proposer set is already reasonably decentralized (any staked validator can be selected to propose a block), a based rollup effectively inherits that same decentralization for its own transaction sequencing, without needing a separate mechanism.

This means a based rollup doesn't have a special, privileged sequencer operator at all — inclusion of a rollup transaction into the next L2 block is tied directly to whichever validator is proposing the next Ethereum L1 block.

The trade-off: less flexibility, tighter coupling to L1

This design has a real cost. Because sequencing is tied to Ethereum's L1 block proposers, a based rollup can't offer features that depend on having its own dedicated, specialized sequencer — such as sub-second soft confirmations decoupled from Ethereum's own block time, or custom ordering rules a project might want for its specific application. Based rollups trade away some of this flexibility and potential performance in exchange for meaningfully stronger, more credibly neutral sequencing decentralization from day one.

Based rollups vs. typical sequencer models

Aspect	Typical single-operator sequencer	Based rollup (L1-proposer sequencing)
Decentralization of ordering	Low — one operator	High — inherits Ethereum's proposer set
Soft confirmation speed	Fast, independent of L1 block time	Tied to Ethereum's own block timing
Custom ordering/features	Flexible, sequencer-specific	Limited by L1 proposer behavior
New infrastructure needed	Yes — dedicated sequencer	No — reuses existing L1 proposers

Where this fits in the broader decentralization conversation

Based rollups are one of several approaches — alongside shared sequencers and other decentralized sequencing proposals — attempting to solve the same underlying problem: reducing or eliminating the centralization risk that comes from a single entity controlling transaction ordering on a rollup. It's a genuinely different philosophy from shared sequencer networks, which build new, separate coordination infrastructure, whereas based rollups deliberately avoid building anything new by leaning entirely on Ethereum's existing validator set.

What this means for evaluating a rollup

If a rollup describes itself as "based," it's making a specific, checkable claim: that its sequencing is directly tied to Ethereum L1 proposers rather than a separate centralized operator. This is generally a meaningfully stronger decentralization claim than most current L2s can make, but it's still worth checking the specific implementation details and how mature and tested the design actually is, since this remains a newer approach relative to the dominant single-sequencer model most rollups still use today.

The role of preconfirmations in making based rollups feel fast

Because Ethereum's L1 block times are noticeably slower than the near-instant soft confirmations users are accustomed to from centralized L2 sequencers, based rollups face a real user-experience challenge: without some additional mechanism, transactions might feel slower than on a typical L2, even though the underlying security and decentralization is stronger. Preconfirmations are the primary proposed solution to this gap — an L1 proposer commits, ahead of actually building their block, to including and ordering specific transactions in a particular way, giving users fast feedback despite the slower underlying block cadence. This pairing of based sequencing with preconfirmations is central to making the based rollup model practically competitive with the user experience offered by traditional single-operator sequencers.

Current adoption and maturity

Based rollups remain a newer design relative to the traditional single-sequencer model that most major L2s still use today. A small number of projects have implemented or are actively developing based rollup architectures, but it hasn't yet become the dominant sequencing approach across the broader L2 landscape. As with any newer infrastructure design, it's worth watching how these implementations perform under real, sustained usage and adversarial conditions over time, rather than assuming the theoretical decentralization benefits automatically translate into a flawless practical experience from day one.

Bottom line

Based rollups remove the need for a dedicated, centralized sequencer by having Ethereum's own layer-1 block proposers handle transaction ordering directly, inheriting Ethereum's existing validator decentralization instead of building new sequencing infrastructure. This offers a meaningfully stronger decentralization guarantee than the single-operator sequencer model most rollups use today, at the cost of some flexibility and performance tied to Ethereum's own block timing. It's a promising direction, but still newer and less widely adopted than traditional sequencer designs.