Glossary

Pre-Confirmation Bond

A pre-confirmation bond is collateral staked by a sequencer or proposer to guarantee that a promised inclusion will happen.

Key Takeaways

  • A pre-confirmation bond is collateral that a sequencer or proposer locks up to back a promise of fast transaction inclusion before on-chain settlement.
  • If the provider fails to honor a preconfirmation, its bond is slashed: a portion or all of the collateral is forfeited to compensate the affected user or the protocol.
  • Bond sizing is an open design problem: the collateral must exceed the value a provider could gain by reneging, but setting it too high discourages participation and reduces the pool of available providers.

What Is a Pre-Confirmation Bond?

A pre-confirmation bond is a deposit of collateral that a block proposer or sequencer stakes before issuing preconfirmations to users. Preconfirmations are promises that a transaction will be included in a future block, delivered well before full on-chain finality. Without a bond, these promises are mere assertions: a provider could issue them freely and break them without consequence. The bond transforms a soft promise into a credible economic commitment.

The concept draws on a simple principle from mechanism design: a commitment is only as credible as the penalty for breaking it. If a provider stakes 10 ETH as a pre-confirmation bond, it has 10 ETH at risk every time it promises inclusion. If it fails to include the transaction as promised, the bond is slashed: some or all of that collateral is seized and redistributed. This creates a direct financial incentive to honor every preconfirmation issued.

How It Works

The lifecycle of a pre-confirmation bond follows a deposit, commit, and resolve pattern. The provider locks collateral in a smart contract, issues preconfirmations against that collateral, and either fulfills the promises (keeping its bond) or fails (triggering a slash).

  1. The provider deposits collateral into an on-chain registry or bond contract. This collateral is locked and cannot be freely withdrawn.
  2. When a user submits a transaction, the provider issues a signed preconfirmation: a cryptographic commitment that the transaction will appear in a specific block or time window.
  3. The provider builds and proposes the block, including the promised transactions.
  4. After the block is finalized on-chain, anyone can verify whether the provider honored its commitments by checking the block contents against the signed preconfirmations.
  5. If a preconfirmation was violated (the transaction was not included, was reordered, or failed when success was guaranteed), a challenger submits a proof of the violation to the bond contract, triggering a slash.

Slashing Conditions

Research from the Ethereum community identifies several tiers of preconfirmation guarantees, each with its own slashing trigger:

  • Inclusion guarantee: the provider promises the transaction will appear in a specific block. Slashing is triggered by a proof of non-inclusion.
  • Ordering guarantee: the provider promises the transaction will appear at a specific position within the block. Slashing requires proof that the transaction appeared at a different index or was absent entirely.
  • Execution guarantee: the provider promises that the transaction will not only be included but will execute successfully (not revert). Slashing requires proof that the transaction reverted despite the guarantee.

Stronger guarantees demand larger bonds because the provider takes on more risk. An execution guarantee, for instance, requires the provider to simulate the transaction and account for state changes from other transactions in the same block.

Bond Sizing

The fundamental rule for bond sizing: collateral must exceed the maximum profit a provider could extract by breaking its promises. If a provider can earn 5 ETH in MEV by reordering or excluding a preconfirmed transaction, its bond must be greater than 5 ETH for the guarantee to be credible.

In practice, this is difficult to calculate precisely because MEV opportunities are dynamic and depend on market conditions. Proposed approaches range from fixed floors (some designs use 1 ETH, others argue for more than 32 ETH) to dynamic collateral that adjusts based on the value of transactions being preconfirmed.

// Simplified bond credibility check
function isPreconfCredible(
  bondAmount: bigint,
  transactionValue: bigint,
  estimatedMev: bigint
): boolean {
  // Bond must exceed what the provider could gain by reneging
  const maxGainFromReneging = estimatedMev + transactionValue;
  return bondAmount > maxGainFromReneging;
}

// Example: 10 ETH bond, 2 ETH transaction, 1 ETH MEV opportunity
// isPreconfCredible(10n, 2n, 1n) => true (10 > 3)
// The provider loses more by breaking the promise than by honoring it

Withdrawal Delays

Bond contracts enforce a withdrawal delay to prevent providers from removing their collateral before slashing evidence can be submitted. If a provider could withdraw instantly after breaking a promise, the bond would be meaningless. Typical designs use a delay of one day or longer, giving challengers time to construct and submit proofs.

Collateral Sources

Pre-confirmation bonds can be funded from several sources, each with different trust and risk profiles:

  • Dedicated collateral: the provider deposits fresh capital specifically for preconfirmation bonding. This is the simplest model and carries the least systemic risk, but it is capital-intensive.
  • Restaked collateral: the provider repurposes staked assets (such as ETH already staked for Proof of Stake validation) as preconfirmation bonds through restaking protocols. This is more capital-efficient but introduces correlated slashing risk: a single fault could trigger slashing across multiple protocols simultaneously.
  • Registry-based pooling: a preconfirmation registry contract accepts delegated collateral from multiple depositors, distributing slashing penalties proportionally. This lowers the barrier for individual providers but adds smart contract risk.

Use Cases

Based Rollups

Based rollups derive their sequencing from Ethereum L1 proposers rather than running a dedicated sequencer. Without a centralized sequencer providing fast soft confirmations, based rollups face latency equal to L1 block times (12 seconds on Ethereum). Pre-confirmation bonds solve this: L1 proposers opt into preconfirmation protocols, stake bonds, and issue sub-second inclusion promises to rollup users.

This architecture gives based rollups the best of both worlds: the decentralization and censorship resistance of L1 sequencing, plus the speed of preconfirmed inclusion backed by economic security.

Centralized Sequencer Rollups

Even rollups with centralized sequencers benefit from pre-confirmation bonds. Without a bond, a centralized sequencer's soft confirmations are trust-based: users believe the sequencer will include their transactions because it has historically done so. A bond adds cryptoeconomic enforcement. Prototype implementations, such as the l2beat native rollup demo, use a 10 ETH bond with on-chain slashing by the L1 contract.

Cross-Chain and Bridge Operations

Pre-confirmation bonds enable faster bridge operations. A bridge relayer can accept a preconfirmed transaction on the source chain and release funds on the destination chain before full source-chain finality, knowing that the preconfirmation is backed by slashable collateral. If the preconfirmation turns out to be false, the relayer can claim compensation from the bond.

MEV Protection

Bonded preconfirmations can protect users from certain forms of MEV extraction. A provider that commits to a specific transaction ordering and backs that commitment with a bond cannot profitably sandwich or frontrun the preconfirmed transaction unless the MEV exceeds the bond. This makes bonded ordering guarantees a tool for fair transaction sequencing.

Why It Matters

Pre-confirmation bonds address a fundamental tension in blockchain scaling: users want fast confirmations, but trustless finality takes time. Without bonds, speed requires trusting the sequencer or proposer. With bonds, speed is backed by credible economic penalties, shifting the trust model from reputation to cryptoeconomics.

For rollup ecosystems, this matters because it allows decentralized sequencing (such as based rollups) to compete on user experience with centralized sequencers. It also creates a market for preconfirmation services, where providers compete on bond size, latency, and reliability. The result is faster, more reliable transaction inclusion without sacrificing decentralization.

Layer 2 protocols like Spark approach fast confirmations differently: Spark provides instant finality through its cooperative signing model, eliminating the need for challenge periods or bonded preconfirmation schemes entirely. For systems that do rely on optimistic or based rollup architectures, however, pre-confirmation bonds remain the primary mechanism for delivering credible speed.

Risks and Considerations

Undercollateralization

If the bond is smaller than the profit available from breaking a preconfirmation, the guarantee is not credible. A provider facing a 50 ETH MEV opportunity will rationally sacrifice a 10 ETH bond. This is especially dangerous during periods of high market volatility, when MEV spikes can temporarily exceed bond amounts that are adequate under normal conditions.

Overcollateralization Barriers

Setting bonds very high (above 32 ETH, as some proposals suggest) may exclude smaller providers, leading to centralization among well-capitalized entities. This creates a tension: higher bonds produce stronger guarantees but concentrate the provider set among fewer, wealthier participants.

Correlated Slashing with Restaking

When pre-confirmation bonds use restaked collateral, a single fault can cascade across multiple protocols. If a provider's restaked ETH is slashed for a preconfirmation violation, it may also affect the provider's standing in the base Proof of Stake protocol and any other services using the same restaked capital. This systemic risk has led some researchers to advocate for dedicated, non-restaked collateral.

Front-Running the Withdrawal

A malicious provider might attempt to initiate a bond withdrawal and then break preconfirmations during the withdrawal delay, hoping to exit before slashing is enforced. Bond contracts must account for this by invalidating pending withdrawals when new preconfirmation commitments are active, or by extending the delay beyond the maximum challenge period.

Proof Construction Costs

Slashing requires a verifiable proof that the preconfirmation was violated. Constructing these proofs (particularly for execution guarantees that require replaying state transitions) can be computationally expensive. If the cost of proving a violation exceeds the slashing reward, rational challengers may not bother, undermining the enforcement mechanism.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.