preconfirmations-primary-sources-2026-05-11

Preconfirmations primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

• https://github.com/cairoeth/preconfirmations
  • Public project repository landing page
  • Used to confirm the project’s self-description, component layout, and linked design materials
• https://raw.githubusercontent.com/cairoeth/preconfirmations/main/README.md
  • Canonical project README
  • Used to confirm the system’s claimed architecture: preconf-share matchmaker, preconf-operator EigenLayer AVS role, wallet-facing rpc wrapper, Relic-backed proof path, Flashbots-derived middleware lineage, and the sub-second preconfirmation framing
• https://ethresear.ch/t/towards-an-implementation-of-based-preconfirmations-leveraging-restaking/19211
  • Linked Ethereum Research post from the project README
  • Used as the project’s own higher-level design context for the restaking-based based-preconfirmation implementation
• https://raw.githubusercontent.com/cairoeth/preconfirmations/main/contracts/src/PreconfChallengeManager.sol
  • Raw onchain challenge-manager contract
  • Used to confirm the reviewed implementation’s actual enforcement flow: EIP-712-style signed preconfirmations, target-block and challenge-window logic, Relic prover integration, operator recovery from signed commitments, and service-manager freeze calls
• https://raw.githubusercontent.com/cairoeth/preconfirmations/main/contracts/src/PreconfServiceManager.sol
  • Raw service-manager contract
  • Used to confirm that the slashing / freezing path described in the README is not yet fully wired in the reviewed code because freezeOperator is still left as a TODO

Notes

• Preconfirmations is analytically valuable because it separates four layers that later projects often flatten together: user request routing, operator matching, economic security via restaking, and post-hoc proof-based enforcement.
• The Flashbots lineage matters. preconf-share is described as a fork of MEV-Share and rpc as a fork of the Flashbots RPC endpoint, so the project sits between private order-flow infrastructure and proposer-commitment infrastructure rather than cleanly inside only one category.
• The raw contracts surfaced the most important caveat in this pass: the README’s slashing story is stronger than the currently reviewed service-manager implementation, which still leaves the actual freeze call as a TODO.
• This entry belongs in the active corpus because it is a useful comparison point for Bolt and adjacent preconfirmation / sidecar systems: the control surface here sits less in proposer-side PBS constraints and more in the user-to-operator matchmaker, wallet abstraction, and challenge proof pipeline.