nixorokish: AA update, the Frame Transactions EIP was moved today to Scheduled for Hegotá
00:04. It was proposed as a headliner and moved to Considered in March, and there was strong consensus that shipping AA in Hegotá matters.
After the SFI: what is settled for 8141 and what is not
Derek Chiang: Frames (8141) was SFI-ed only to signal that Ethereum will ship AA in Hegotá
00:21; it does not mean Frames as written, or even the final EIP number, is set in stone, and he pushed back at ACDE against making the SFI decision now.
nero_eth: one overlooked aspect of EIP-8141 is privacy
14:59. Frame transactions let privacy pools sponsor withdrawals directly from the withdrawal amount, removing the relayer needed today; the next step is STARK aggregation, which can push the cost of privacy pool interactions close to zero.
EIP-8141: an opcode and frame-mode registry for the frame transaction family
(AnkushinDaniil), submitted. The 8141 family (8141, 8250, 8272, 7906, 8288, 8312) allocates opcodes and frame modes per draft, which has already caused two collisions: `0xB5`, assigned by EIP-8272 to `RECENTROOTREFLOAD` and later used by 8141 for `SIGDATACOPY`; and frame mode `3`, assigned by EIP-7906 to `POST_TX` and also claimed by EIP-8312 (UTXO). 8141 would hold the authoritative allocation that dependent EIPs draw from.
EIP-8037: restore a frame's state gas on rollback
(chfast), submitted: the "state gas charged within the frame" in the rollback rules has no counter; it is `L0 - L1 + S1`, and `L0` was never defined.
Post-quantum migration: ecrecover
ethresear.ch: proposed PQ upgrade for ecrecover
22:08 (mirabelenkiy-circle). Many contracts verify ECDSA signatures with ecrecover and are exposed to quantum attacks; rather than disable it, ecrecover could read post-quantum signatures from EIP-8141 frame transactions, with the 65-byte `(v, r, s)` encoding lookup values and a sentinel value triggering the new path. The aim is a graceful migration for immutable contracts, not a fix for EOAs themselves. The author notes the EVM defines ecrecover as a pure function, so any public key lookup raises backward compatibility questions.
Other updates
Ethereal news #37
20:50: Glamsterdam repricing impact for contract developers, the Revolut euro stablecoin rolling out, and native AA scheduled for Hegotá. Security: about $8.5M drained in the Term Finance governance incident, a roughly $1.5M Sandbox bridge exploit, and a Ledger clear signing flow bug fixed in the Ethereum app.
EIP-4444: move to Draft
Submitted and merged, aligning the execution layer block retention window with the consensus layer's; move to Review, submitted.
move to Review
EIP-4444: move to Draft, submitted and merged, aligning the execution layer block retention window with the consensus layer's; move to Review, submitted.
EIP-8298: clarify code lifecycle and gas pricing
Submitted and merged, aligning `SETCODEFROM` gas costs with Glamsterdam pricing.
EIP-7773: move to Review
Merged; abcoathup submitted EIP-7773: call out the Glamsterdam headliners (ePBS, BALs) and EIP-8081: call out the Hegotá headliners (FOCIL, Frame transactions).
EIP-7773: call out the Glamsterdam headliners
EIP-7773: move to Review, merged; abcoathup submitted EIP-7773: call out the Glamsterdam headliners (ePBS, BALs) and EIP-8081: call out the Hegotá headliners (FOCIL, Frame transactions).
EIP-8081: call out the Hegotá headliners
EIP-7773: move to Review, merged; abcoathup submitted EIP-7773: call out the Glamsterdam headliners (ePBS, BALs) and EIP-8081: call out the Hegotá headliners (FOCIL, Frame transactions).
ERC-7730: define wallet behavior for non-zero native value
(soyrubio), submitted, since function selectors encode parameter types but not payability.
Magicians: Sordino, a trust-minimized encrypted mempool for the OP Stack
01:24: transactions are threshold-encrypted before reaching the sequencer, and t-of-n keypers release decryption shares only after ordering is fixed.
Community
binji: if Ethereum protocol development does not work closely with the app layer, we are cooked
14:05; the network must not become an art project people like but no one uses.
Péter Szilágyi: Fable introduced a regression into one of his crypto libs (from a dependency), and after his fuzzer flagged it, Fable refused to touch it
20:27.