Cowrie Research

preconfirmations

3 min read

Preconfirmations

  • Name: Preconfirmations
  • URL: https://github.com/cairoeth/preconfirmations
  • Category: based preconfirmation middleware / proposer-promise matching layer / EigenLayer AVS challenge-and-slash prototype
  • Tags: ethereum-ecosystem
  • Summary: Preconfirmations is best understood as a restaked matchmaker-plus-operator stack for based preconfirmations, not merely as a fast-confirmation wallet RPC. The repository describes a system where users request sub-second inclusion promises, preconf-share gossips hints and ranks operator responses, EigenLayer AVS operators issue signed promises, and an onchain challenge path is meant to slash violated commitments using Relic proofs. The reusable mechanism insight is that this design decomposes preconfirmation infrastructure into four distinct control surfaces — user-to-matchmaker request routing, operator admission through restaking, proof-based challenge resolution, and wallet-facing RPC abstraction — which is a useful comparison point against Bolt’s proposer-constraint path and Flashbots-era private order-flow middleware.
  • What it does:
    • Lets users request signed preconfirmation promises for Ethereum transactions with target-block preferences and tips
    • Uses preconf-share as a middleware matchmaker that receives user requests, gossips hints to operators, and ranks returned promises according to user validation preferences
    • Runs preconf-operator as EigenLayer AVS software for operators that are expected to be block proposers capable of including the promised transactions
    • Exposes a wallet-oriented rpc wrapper so clients do not need to speak the lower-level preconfirmation interfaces directly
    • Includes onchain manager contracts intended to let challengers prove a violated promise and trigger operator slashing / freezing via Relic-backed proofs
    • Makes the fast-confirmation claim legible as an offchain promise market plus an after-the-fact dispute system, rather than as native Ethereum consensus finality
  • Key claims:
    • The repository README says the protocol allows users to get sub-second transaction confirmations on Ethereum and frames preconfirmations as signed proposer promises about inclusion and execution timing
    • The README says the system uses EigenLayer as the security layer for preconfer guarantees, with operators subject to onchain slashing when promises are not fulfilled
    • The README and contract structure make the control split unusually clear: preconf-share handles user request intake and operator matching, preconf-operator handles AVS-side service provision, rpc packages the flow for wallets, and the contracts handle post-hoc challenge resolution
    • The raw PreconfChallengeManager.sol contract shows the reviewed implementation is specifically challenge-window based: challengers can raise and resolve a claim after the target block, prove non-inclusion through a prover interface, recover the operator from the signed preconfirmation, and call the service manager to freeze that operator
    • The same reviewed contract also reveals an important caveat: while the README talks about slashing guarantees, the raw PreconfServiceManager.sol implementation currently leaves freezeOperator as a TODO, so the enforcement path surfaced in this pass looks prototype-grade rather than fully implemented production slashing
    • The project README explicitly says preconf-share is a fork of Flashbots’ MEV-Share node and rpc is a fork of Flashbots’ RPC endpoint, which makes this a useful bridge case between private-orderflow middleware and proposer-commitment systems
    • The strongest comparison frame is not generic “faster confirmations.” It is “a restaked proposer-promise marketplace with a matchmaker, wallet wrapper, and proof-based challenge path,” which makes it a strong comparison point for Bolt, Commit-Boost-adjacent sidecars, Flashbots Auction / MEV-Share, and other preconfirmation designs
  • Whitepaper: No standalone canonical whitepaper or litepaper surfaced in this pass. The strongest primary materials were the project README, the linked Ethereum Research design post, and the raw challenge / service manager contracts collected in ../whitepapers/preconfirmations-primary-sources-2026-05-11.md.
  • Sources:

Internal linkages

  • Best upward reads: puffer-preconf, bolt, and mev-share.

  • Keep this note on the matchmaker / operator / challenge split. Do not let it turn into a generic preconfirmation or MEV middleware hub.

  • Last reviewed: 2026-06-01 UTC

Graph View