Back to all reports

以太坊研究日报

Ethereum Research Daily

chunter-cb submitted and merged four EIP-8130 changes, one of them a security fix: the payer signature hash did not include the payer field, so a signature from one actor could be used to pay from any account that authorized that actor; now the signature is bound to the account being charged. A metadata field was also added. misilva73 submitted an EIP-8037 change that resolves a conflict with EIP-7928 and routes state gas refills to the origin. On encrypted mempools, EIP-8105 and EIP-8184 asked for feedback, and GottfriedHerold published a criticism of LUCID (EIP-8184). julianma argued wallet teams lack the incentive to build gasless payments.

Image for June 16, 2026

Image: ethresear.ch, A Criticism of LUCID and Encryption-Scheme-Agnostic Encrypted Mempool Designs (GottfriedHerold)

The EIP-8130 payer security fix

EIP-8130: bind payer field into payer signature hash

(chunter-cb), submitted and merged. The payer hash (the `AA_PAYER_TYPE` payload) used to exclude `payer`, so a payer authorization was pinned only to the transaction body and the resolved `sender`, not to which account funds it; validation (`actor_config(payer, actorId)` plus PAYER scope) succeeds for any account that authorizes the same actor. Now the payer's signature is bound to the account being charged.

https://github.com/ethereum/EIPs/pull/11808

EIP-8037 state gas accounting

EIP-8037: resolve EIP-7928 conflict and route state gas refills to origin

(misilva73), submitted. First, the account creation portion of `CREATE`/`CREATE2` is charged unconditionally before the create frame and refilled on exit if the target already existed or creation failed, avoiding the target existence read that EIP-7928 defers; `CALL*` keeps its conditional charge. Second, a frame-local record of where state gas came from is added, so refills route to the origin.

https://github.com/ethereum/EIPs/pull/11807

Encrypted mempools and privacy

Wallet experience

Other updates

Community