
L2 preconfirmer and provide the service of preconfirmation to users.L1 Proposers can opt-in to additional slashing conditions and be Enforcers . Their job will be to enforce the inclusion of a preconfirmed transaction. For the sake of this flow EigenLayer-like opt-in scheme is assumed.Preconfirmers. Preconfirmers simulate and validate the user transaction and PR.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.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.Enforcers request/enforce inclusion from L1 builders through a slightly modified MEV-boost pipeline. L1 builders include the preconfirmed transactions.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.Preconfirmer staked balance.preconfirmer PER bid goes from their staked balance to the Includer . The Includer is likely the L1 builder or vertically aligned with them.L1 Builder would be able to offer higher MEV bid to the L1 Proposer (the Enforcer) that is the actual payment to the L1 Proposer.With the flow above the following was achieved: