Coin Brief ENDE

EIP-8151 adds mempool rules for addresses that ecRecover reads

An update to EIP-8151 merged on 16 November adds a "Public Mempool" section. Under this EIP, ecRecover reads the raw code of the address it recovers, so the validation prefix of an EIP-8141 frame transaction that calls it depends on the code of every recovered address - which may belong to a third party rather than the sender. The new rules apply only to public mempool validation and do not affect consensus.

The text defines a "code class": permitted (empty code or an EIP-7702 delegation indicator) or rejected (any other code). Switching between empty code and a delegation indicator keeps the class. While simulating the validation prefix, a node should record each recovered address and its class as a "signer dependency", except tx.sender, and revalidate the transaction when the class of a dependency changes at a new head, in either direction and after a reorg. A block that touches the address without changing its class does not trigger revalidation.

Nodes should also cap how many pending transactions may depend on one recovered address, so that a single code adoption - for example through SETCODEFROM in EIP-8298 - cannot invalidate an unbounded number of them. The cap is split by digest: recoveries over the transaction's own canonical signature hash get a reserved share, and recoveries over any other digest a smaller one, where nodes may keep the highest-fee transactions. The EIP explains why: anyone holding an old signature, or knowing a public key, can build an input that recovers an address without the private key, but not for this transaction's own signature hash.

EIP-8151 adds mempool rules for addresses that ecRecover reads
EIP-8151 adds mempool rules for addresses that ecRecover reads — Coin Brief

Why it matters

The rules move a denial-of-service concern out of consensus and into mempool policy. The split by digest is what keeps a stranger from filling the queue with transactions tied to someone else's address.