Based Rollups & Preconfirmations: The Complete 2026 Guide

1. The Sequencer Problem No One Talks About

When you send a transaction on Arbitrum, Optimism, Base, or virtually any other Layer 2 today, it doesn't go straight to Ethereum. It goes to a sequencer — a centralized server controlled by the rollup's operator. That sequencer decides the order of your transaction relative to everyone else's, bundles them up, and only then posts a batch to Ethereum.

Technically, this sequencer inherits Ethereum's security for finality (you can always force transactions through the L1 if the sequencer ignores you). But in practice, it creates real risks most users never consider:

The broader Ethereum community has been aware of this problem since the earliest rollup days. The question was always: what do you replace the sequencer with? Running a decentralized sequencer set costs money, introduces latency, and creates governance headaches. Based rollups offer a different answer: don't replace it with a new thing — use the thing that's already there and already proven at scale.

2. What Are Based Rollups?

A based rollup — also called an L1-sequenced rollup — is a Layer 2 where transaction ordering is delegated entirely to Ethereum's own block proposers. There is no separate sequencer. Instead, the next Ethereum L1 validator can, in collaboration with L1 searchers and builders, permissionlessly include the next rollup block as part of the next L1 block.

The key insight is that Ethereum already solves decentralized transaction ordering — it does it for the L1 every 12 seconds. Validators compete to propose blocks, MEV is captured through a competitive market (PBS), and the whole system is secured by hundreds of billions of dollars in staked `ETH`. Why build an entirely new parallel system when you can piggyback on the existing one?

When you use a based rollup, your transaction goes into the same mempool environment as L1 transactions. Ethereum's block builders — the same entities building blocks for Ethereum mainnet today — can include your L2 transaction as part of the next L1 block. The rollup's execution layer processes it, but the sequencing decision was made by Ethereum's existing infrastructure.

3. How Based Sequencing Works

Under the hood, Ethereum already uses a separation between the validator who proposes a block (the proposer) and the entity who builds the block content (the builder). This is called Proposer-Builder Separation, or PBS. Builders compete in a competitive auction for the right to fill a block with the most profitable set of transactions; the proposer simply picks the highest-paying builder.

Based rollups plug directly into this existing PBS market. Builders who are already constructing L1 blocks can additionally include L2 rollup transactions in their block bids. When the proposer selects that block, both L1 and L2 transactions are finalized together in a single atomic operation. The result is that based rollup transactions achieve the same censorship resistance and decentralization as ordinary Ethereum transactions — because they literally go through the same process.

This design has a powerful side effect: synchronous composability. Because L1 and L2 transactions are included in the same block, a smart contract on Ethereum mainnet can atomically interact with a contract on the based rollup in a single transaction. This was impossible with traditional rollups that had their own separate sequencer timing. Think of it like combining two separate call stacks that used to require a multi-block round trip into a single atomic operation.

4. What Are Preconfirmations?

There's an obvious problem with based rollups: Ethereum's block time is 12 seconds. If your transaction is sequenced by an L1 validator, you're stuck waiting up to 12 seconds just to know if it got included. Rollups with their own sequencers can give you a soft confirmation in under a second. That's a brutal UX gap.

Preconfirmations (commonly shortened to "preconfs") solve this. A preconf is an off-chain commitment from an Ethereum validator to a user, promising that a specific transaction will be included in their next block. The validator sends you a cryptographic commitment — essentially a signed IOU — within ~100 milliseconds of receiving your transaction. You now have a reliable guarantee without waiting for block finalization.

Preconfs come in three flavors, depending on how strong a guarantee you want:

Preconfs are enforced through a slashing mechanism. If a validator issues a preconf and then reneges — either by excluding your transaction or by delivering a different execution result — they can be slashed (lose a portion of their staked `ETH`). This economic penalty is what gives preconfs their teeth. A validator making a preconf is putting real money on the line.

Validators who want to issue preconfs opt in to this service. They register their intent to act as preconf providers, and users can choose to route transactions to them (paying a small premium for the speed guarantee). Validators who'd rather not take on slashing risk can stay in their standard role as block proposers.

5. Based Rollups + Preconfs: The Full Picture

Individually, based rollups and preconfirmations each solve different problems. Together they form a coherent solution to Ethereum's scaling challenge:

The combination delivers something no previous L2 design could claim: a rollup with the decentralization and security of Ethereum itself, combined with user-facing speed that approaches centralized competitors. You're not choosing between fast-and-centralized vs slow-and-decentralized. You're getting both.

EIP-7917, which introduces deterministic proposer lookahead, is one of the key infrastructure changes landing in the Ethereum protocol to support this model. It lets validators (and users) know ahead of time which validator will propose the next block — a prerequisite for meaningful preconfs, since you need to know who to request the commitment from.

6. Transaction Flow Visualizer

Select a scenario below to see how a transaction flows through each architecture.

7. Based vs Traditional Rollups: Side-by-Side

8. Who Is Building Based Rollups?

Based rollups are moving from whitepaper to production as of 2026, with several teams in different stages of deployment:

9. Risks & Trade-offs

Based rollups are a genuine architectural improvement, but they come with real trade-offs you should understand before dismissing traditional rollups entirely.

10. What This Means for You as a User

If you're a DeFi user on Ethereum today, here's the practical translation:

The practical timeline: you're unlikely to notice a difference in your day-to-day Ethereum usage immediately. Taiko is live but still growing its ecosystem. As based rollup infrastructure matures over 2026 and into 2027, expect the major rollup teams to at minimum decentralize their sequencers using based or based-adjacent designs, even if they don't go full based immediately.

The long arc here favors based rollups. Centralized sequencers are a liability — reputationally, legally, and technically. The question isn't whether the industry moves away from them; it's how fast.

Related Guides

Frequently Asked Questions