EIP-8141's mempool and paymaster sections moved together: svlachakis submitted a mempool lifecycle definition where pending identity is `(sender, nonce)`, replacements must bump both fee fields, and summed pending maximum costs for any payer cannot exceed its balance; he also submitted the transaction log set and unrolled-batch log semantics, and a concrete canonical paymaster implementation. AnkushinDaniil submitted two RFCs, a signature scheme registry and recognizing the canonical paymaster by stable identity. Blob support, direct evaluation of validation prefixes, the APPROVE gas cost and fee field bounds, submitted the day before, merged. zeam announced its EF grant has ended.
(svlachakis), submitted. Replacement: pending identity is `(sender, nonce)`, and signature- or witness-refreshed variants are replacement candidates, which closes signature-malleability churn; replacements must be independently valid, bump both fee fields by a node-configured minimum, and may switch payer, with reservations moving atomically. Payer exposure: the canonical paymaster's reservation accounting generalizes to every payer, so summed pending maximum costs never exceed the payer's balance, preventing one balance change from invalidating many pending transactions at once.
(svlachakis), submitted: the transaction's logs are the frame receipts' logs in frame order, and an unrolled frame's logs are discarded with its state changes; otherwise two clients could agree on the receipt encoding and still disagree on the header `logsBloom`.
AnkushinDaniil submitted two RFCs: recognize the canonical paymaster by stable identity rather than exact bytecode match, meaning an EIP-7702 delegation to a reserved address or a code hash pinned per fork, and formalize the signature scheme table as an in-protocol registry, where a signature scheme is a cryptographic operation the protocol supports in optimized form, not an account.
AnkushinDaniil submitted two RFCs: recognize the canonical paymaster by stable identity rather than exact bytecode match, meaning an EIP-7702 delegation to a reserved address or a code hash pinned per fork, and formalize the signature scheme table as an in-protocol registry, where a signature scheme is a cryptographic operation the protocol supports in optimized form, not an account.
Merged: blob support for frame transactions, direct evaluation of protocol-defined validation prefixes, the APPROVE opcode gas cost, and static bounds on fee fields.
Merged: blob support for frame transactions, direct evaluation of protocol-defined validation prefixes, the APPROVE opcode gas cost, and static bounds on fee fields.
Merged: blob support for frame transactions, direct evaluation of protocol-defined validation prefixes, the APPROVE opcode gas cost, and static bounds on fee fields.
Merged: blob support for frame transactions, direct evaluation of protocol-defined validation prefixes, the APPROVE opcode gas cost, and static bounds on fee fields.
(forshtat), submitted; per Ethereal news #33, EIP-7906 is transaction assertions via a state diff opcode, part of his trustless clear-signing architecture.
16:23: a pre-execution allow/deny interface for autonomous agent actions, with the decision proven in zero knowledge against a policy never disclosed onchain.
