What Are Preconfirmations? Faster L2 UX Explained

A preconfirmation is a fast promise from a sequencer (or, in some designs, an L1 block proposer) that a specific transaction will be included and processed in a particular way, given to a user before that transaction has actually reached hard, base-layer finality — designed to give users near-instant certainty about their transaction's outcome without waiting through the chain's full finality timeline.

The problem preconfirmations address

As covered in our piece on transaction finality, L2 transactions typically reach a fast "soft" confirmation quickly, followed by a much slower "hard" finality once settled on the base layer — a gap that can range from minutes on a ZK-rollup to about a week on an optimistic rollup. Soft confirmations already give users a reasonable degree of confidence, but they're an implicit assumption based on how sequencers normally behave, not an explicit, accountable commitment.

Preconfirmations try to make this more concrete and, in some designs, more accountable: instead of an implicit assumption, the sequencer (or proposer) makes an explicit, often economically backed promise about a transaction's treatment, sometimes with real financial consequences (like slashing) if that promise is broken.

Where preconfirmations become especially relevant

This concept has become particularly important in the context of based rollups and shared sequencing designs, where transaction sequencing is tied to Ethereum's own L1 block proposers rather than a dedicated L2 sequencer. Because L1 block times are relatively slow compared to what users have come to expect from centralized L2 sequencers offering near-instant soft confirmations, based rollups risk feeling slower to use unless something fills that gap. Preconfirmations are one proposed solution: a proposer commits, ahead of actually building their L1 block, to specific transaction inclusion and ordering guarantees, giving users fast feedback despite the underlying L1 block cadence.

What a preconfirmation actually guarantees, and what it doesn't

It's worth being precise here. A preconfirmation is a promise, and depending on the specific design, that promise may or may not carry real economic consequences for being broken. Some proposals tie preconfirmations to staked collateral that gets slashed if the promise isn't honored, making the guarantee meaningfully stronger than a purely reputational commitment. Others rely more on reputation and expected future behavior, which is a weaker guarantee, closer in spirit to the soft confirmations users already get from centralized sequencers today.

Regardless of design, a preconfirmation is still not the same as base-layer hard finality. In an extreme scenario — a chain reorganization at the L1 level, for instance — a preconfirmed transaction could theoretically still fail to materialize as promised, even under an economically backed design, though well-designed slashing conditions are meant to make this costly and therefore rare.

Preconfirmations compared to existing confirmation types

Confirmation type	Speed	Guarantee strength
Soft confirmation (typical sequencer)	Seconds	Implicit, based on normal sequencer behavior
Preconfirmation (economically backed)	Seconds	Explicit promise, backed by slashable stake
Hard (base-layer) finality	Minutes to ~7 days	Strongest — settled on base layer

What this means for users today

Preconfirmations are still an emerging piece of infrastructure, most relevant to newer sequencing designs like based rollups rather than something available uniformly across all L2s today. For most current everyday use, the practical guidance remains the same as for any soft confirmation: fine for typical transactions, but worth understanding the specific chain's finality timeline before treating a large transfer or withdrawal as fully settled.

Slashing as the mechanism that gives preconfirmations teeth

The most credible preconfirmation designs tie the promise to collateral that the proposer or sequencer has staked and that can be automatically slashed if the promise isn't honored. This is what separates a genuinely accountable preconfirmation from a purely reputational one: if breaking a promise costs the promiser real, material capital, they have a strong, aligned incentive to honor it even when doing so might otherwise be inconvenient or less profitable in a given moment. Designing these slashing conditions correctly is technically challenging, since they need to reliably distinguish between a proposer genuinely breaking a promise versus a promise becoming impossible to keep for reasons outside the proposer's control (like an unrelated network-wide disruption), without either over-punishing honest actors or under-punishing genuine bad behavior.

Why this matters beyond based rollups specifically

While preconfirmations are especially relevant to based rollups and shared sequencing designs, the underlying idea — giving users faster, more explicit, and ideally economically accountable guarantees about pending transactions — has broader applicability across the L2 landscape generally. Even chains with traditional centralized sequencers could, in principle, adopt more formal preconfirmation mechanisms to make their existing soft confirmations more accountable, rather than relying purely on informal trust in the operator's normal behavior. Whether this becomes a widely adopted practice across the whole ecosystem, or remains mostly associated with newer, more decentralized sequencing designs specifically, is still an open question.

Bottom line

Preconfirmations aim to give users fast, explicit inclusion guarantees from sequencers or L1 proposers before a transaction reaches full base-layer finality, addressing a UX gap that's especially relevant for based rollups and other designs tied closely to Ethereum's own block timing. The strength of the guarantee depends heavily on the specific implementation — an economically backed, slashable promise is meaningfully stronger than a purely reputational one — but neither replaces true hard finality for transactions where irreversibility genuinely matters.