Ethereum’s scaling roadmap has long revolved around roll-ups, but a newer design known as the based roll-up is attracting growing attention. The concept is being discussed as a possible improvement over traditional Optimistic and ZK roll-ups, particularly in the way transactions are sequenced and committed back to Ethereum.
The source article frames the discussion in a highly opinionated way, but its core contribution is educational: it outlines how based roll-ups work, why they were proposed, and what trade-offs they introduce for users, developers, and the broader Ethereum ecosystem.
Why roll-ups became central to Ethereum scaling
Roll-ups emerged because Ethereum mainnet can become expensive and congested under heavy usage. Rather than processing every transaction directly on Layer 1, roll-ups execute activity on Layer 2 and then post bundled transaction data back to Ethereum. This design seeks to preserve Ethereum’s security while reducing costs and increasing throughput.
Until now, two categories have dominated the landscape: Optimistic roll-ups and ZK roll-ups. Optimistic systems assume transactions are valid by default and rely on fraud proofs to catch invalid activity after the fact. That approach can reduce Layer 1 computation, but it also creates delays in areas such as withdrawals because time is needed for dispute windows.
ZK roll-ups take a different route. They bundle transactions off-chain and return them to Ethereum with cryptographic validity proofs, often using SNARKs or STARKs. These proofs act as evidence that state transitions are correct, which can significantly improve efficiency and throughput. However, the engineering burden and system complexity tend to be higher.
The sequencing problem behind current roll-ups
According to the source material, one of the biggest shared issues across both optimistic and ZK designs is the sequencing layer. In many existing roll-ups, sequencing is controlled by dedicated entities or specialized infrastructure. That can raise concerns around centralization, downtime, censorship risk, and operational complexity.
This is the gap that based roll-ups aim to address. Rather than depending primarily on a roll-up-controlled sequencer, the design moves sequencing closer to Ethereum itself. In other words, it attempts to leverage the base layer’s existing infrastructure rather than replicating similar functions at the Layer 2 level.
What makes a roll-up “based”
The article attributes the concept of based roll-ups to Ethereum researcher Justin Drake, who proposed the idea in March 2023. In this model, transaction sequencing is handled on the base layer—Ethereum Layer 1—instead of by an independent Layer 2 sequencer.
That distinction is the defining feature. By relying on Ethereum’s existing network participants—such as searchers, builders, and proposers—a based roll-up seeks to improve decentralization, reliability, and security. The article argues that anyone with visibility into the roll-up mempool could potentially participate in sequencing, making the process more permissionless and less dependent on a single operator.
Another implication is architectural simplicity. Instead of building and maintaining a fully separate sequencing stack, based roll-ups reuse Ethereum’s underlying machinery. The source presents this as a meaningful advantage over more complex L2 sequencing systems.
How the architecture is described
The source breaks based roll-ups into four layers: the consensus layer, data availability layer, execution layer, and settlement layer. Of these, the consensus, data availability, and settlement functions are anchored to Ethereum Layer 1, while the execution layer remains the responsibility of the roll-up itself.
This means the roll-up still handles execution logic off-chain or in its own environment, but much of the trust and coordination framework is inherited from Ethereum. In theory, this can reduce design overhead and align the roll-up more tightly with Ethereum’s security assumptions.
How transaction sequencing works in a based roll-up
The source outlines a four-step transaction lifecycle. First, L2 searchers bundle together user transactions originating on the roll-up. Second, L1 searchers and L2 builders collaborate to sequence these transactions into full L2 blocks. Third, L1 searchers submit the completed L2 blocks to L1 block builders. Finally, L1 block builders package the data into Layer 1 blocks and pass them to L1 validators, who process them as they would normal Ethereum transactions.
The article emphasizes that this process is permissionless, meaning no special authorization is required for a roll-up block to be included in an Ethereum block. In principle, that should reduce censorship concerns and improve resilience because inclusion depends on Ethereum’s broader infrastructure rather than a dedicated sequencer run by the roll-up itself.
Potential benefits: decentralization, simplicity, and lower overhead
Several advantages are highlighted. The first is greater decentralization, since sequencing is tied to Ethereum’s open block-building and proposing environment instead of a roll-up-specific operator. The second is reliability, because the design leans on Layer 1 validators and existing Ethereum infrastructure, which may reduce downtime risk.
The third claimed benefit is lower cost. The article says gas overhead can be reduced by removing the need for sequencer signature verification associated with some other roll-up designs. In practical terms, that could translate into a more efficient cost structure for users and builders, though real-world outcomes would still depend on implementation details and market conditions.
Finally, the piece argues that based roll-ups are simpler to build because they eliminate a number of moving parts associated with bespoke L2 sequencing and consensus systems. For developers, fewer custom components can mean a cleaner design surface and potentially lower operational complexity.
The role of pre-confirmations
One notable feature discussed in the article is the use of pre-confirmations. These are commitments that allow transactions to be acknowledged before final on-chain inclusion. If executed well, pre-confirmations could significantly improve user experience by making transactions feel much faster.
However, the source also notes that these commitments come with stronger accountability. Proposers may face increased slashing penalties if they fail to honor pre-confirmation promises when the transaction is supposed to be included on-chain. This creates a mechanism intended to enforce reliability, but it also adds economic and operational pressure to participants making those promises.
The trade-offs: MEV capture and reduced flexibility
The article is clear that based roll-ups are not a universal solution. One major drawback is economic. In roll-ups that use their own sequencer, the system may be able to retain more of the MEV associated with transaction ordering. In a based roll-up, by contrast, sequencing occurs on Layer 1, so that value is more likely to be captured by Ethereum’s own block production pipeline rather than by the roll-up.
There is also a flexibility trade-off. Builders of traditional roll-ups can experiment more freely with sequencing rules and infrastructure in pursuit of speed or efficiency gains. Based roll-ups surrender some of that optionality because they are more constrained by the design and limits of Ethereum Layer 1. In effect, part of the roll-up’s scalability and sequencing behavior is now subject to the base layer’s own rules and bottlenecks.
How this fits into the broader Ethereum roll-up race
The source places based roll-ups within Ethereum’s ongoing competition among Layer 2 scaling models. It notes that Optimistic roll-ups still dominate much of the current market and says only Arbitrum and Optimism have reached stage 1 status among the projects referenced in the piece.
The article also cites a September 2024 statement from Vitalik Buterin indicating that, starting the following year, he planned to publicly mention only Layer 2s that had reached stage 1+, with perhaps a short grace period for genuinely new and interesting projects. That remark is presented as evidence that Ethereum’s scaling discussion is shifting away from early-stage experimentation and toward more mature, hardened designs.
Projects mentioned in the based roll-up category
To illustrate where development may be happening, the article names several projects exploring the based roll-up arena: Taiko, Espresso, Fairblock, Sorella, and Chainbound. It does not provide comparative metrics or implementation status for each, but it presents them as examples of teams working in or around this design space.
That is an important nuance. The based roll-up idea is still part of a broader evolution in Ethereum scaling rather than a fully settled end state. Different teams may interpret or implement the concept differently, and the practical value of the approach will depend on how these systems perform under real usage, how incentives are aligned, and how closely they integrate with Ethereum’s roadmap.
Final takeaway
Based roll-ups represent an attempt to keep the benefits of roll-ups while improving one of their most controversial components: sequencing. By moving sequencing closer to Ethereum Layer 1, they aim to deliver stronger decentralization, simpler architecture, lower overhead, and better reliability. At the same time, they may sacrifice MEV revenue, customization, and some sequencing flexibility.
That makes them neither a guaranteed replacement for Optimistic or ZK roll-ups nor a purely theoretical experiment. Instead, they appear to be a serious design alternative in Ethereum’s ongoing search for scalable infrastructure. Whether based roll-ups eventually become dominant will likely depend on execution quality, user experience, economics, and the extent to which developers and the Ethereum ecosystem embrace the trade-offs they require.