High-level Flow Overview

MEV-generalization-Preconfirmations.drawio.png

  1. Users submit preconfirmation requests (PR) - containing PR tip - to one or multiple Preconfirmers. Preconfirmers simulate and validate the user transaction and PR.
  2. Preconfirmers through a p2p messaging channel broadcast preconfirmation enforcement requests (PER) containing enforcement bids they are willing to spend. Enforcers notice these PERs and the bids.
  3. Enforcers commit to valid PERs - ones signed by a valid staked Preconfirmer . The commitment is known as PERCom. Sane Enforcers commit to the highest bid. Enforcers can replace commitment for a certain PER via nonce. Enforcers cannot cancel PER once committed to one.
  4. Enforcers request/enforce inclusion from L1 builders through a slightly modified MEV-boost pipeline. L1 builders include the preconfirmed transactions.
  5. As part of the newly sequenced L2 transaction list (therefore block) an Includer submits the PERCom and disburses the various fees. The preconfirmation of the earliest slot is considered valid. In other words the earliest Enforcer wins the PER tip. If the commitment is not honoured the Enforcer is slashed.
  6. The fees are disbursed as:

Outcomes

With the flow above the following was achieved: