Back to all reports

Ethereum Research Daily

Ethereum Research Daily

Frame Transaction Breakout #8 was mostly about staying forward compatible with EIP-8288. Iván said on the call he'd open a draft, and afterwards ilitteri submitted an EIP for leanSPHINCS dependency frames, where signatures travel beside the transaction and can later be swapped for an aggregate proof. The call agreed to lock down EIP-8151 and EIP-8298 (SETCODEFROM) first. soispoke published a long post arguing against dropping FOCIL and other features from Hegotá in the name of pqai, and worked out that an unchanged FOCIL could force at most 16 leanSPHINCS transactions into a block. ACDE #249 meets tomorrow at 21:00 to cover Glamsterdam and Hegotá.

Image for November 18, 2026

Image: LambdaClass blog

Frame Transaction Breakout #8: forward compatibility with EIP-8288 and a draft for leanSPHINCS dependency frames

recording

The Frame Transaction Breakout #8 summary went up at 23:06 on 2026-11-17 (an auto-generated Zoom summary that mangles names like Hegotá, Besu and leanSPHINCS), along with the recording. Key points:

https://youtu.be/K7LSqIMjo2w

Verification gas and FOCIL: two constraints on bringing frame transactions into Hegotá

AnkushinDaniil's reply

At 04:24 on 2026-11-18 brought Nethermind measurements. The builder used to execute every IL entry, VERIFY included. Under EIP-7805's byte limits (16 ILs × 8 KiB, 2,624 minimal frame transactions per slot), going from a 100k to a 300k cap took per-slot time from 223 ms to 670 ms with a cheap loop, or from 3.2 s to 9.7 s with KECCAK256 over 4 KiB. Running only the entries EIP-8369's fill rule admits brings the worst case to 0.20 to 0.29 s per slot, and it no longer grows with the cap. He's still worried that tail truncation can leave a transaction unprotected even though it's in an IL.

https://github.com/ethereum/EIPs/pull/12644#issuecomment-6961426269

draft EIP PR #12663: FOCIL omission witnesses for frame transactions

Discussion on draft EIP PR #12663: FOCIL omission witnesses for frame transactions: at 16:16 on 2026-11-17 soispoke suggested simply pointing to EIP-8369's notion of "position-stable" transactions, and warned that with a shared paymaster a builder can send its own sponsored transactions first and drain the balance. At 03:13 AnkushinDaniil proposed that the paymaster keep a "released" counter that only goes up, stored in the upper 96 bits of slot 0 so no new storage slot is needed.

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

EIPsInsight recap

The FOCIL Breakout #46 summary went up at 22:07 on 2026-11-17 (EIPsInsight recap at 23:06): consensus-specs PR #5769 got the green light, with a merge planned for the next call; the group discussed IL timing, the retention window (#5785 extends it from 2 to 3 slots) and proposer deadlines. Next week's FOCIL Breakout #47 (11-24) is dedicated to PQ FOCIL.

https://x.com/EIPsInsight/status/2122723180662104229

FOCIL Breakout #47

The FOCIL Breakout #46 summary went up at 22:07 on 2026-11-17 (EIPsInsight recap at 23:06): consensus-specs PR #5769 got the green light, with a merge planned for the next call; the group discussed IL timing, the retention window (#5785 extends it from 2 to 3 slots) and proposer deadlines. Next week's FOCIL Breakout #47 (11-24) is dedicated to PQ FOCIL.

https://github.com/ethereum/pm/issues/2308

Post-quantum accounts and validator migration: ERC-8403 ships permission tiers, PQ material registration

replied at 01:39

Magicians: an independent check of ERC-8403 at 20:54 on 2026-11-17. it44 recomputed the SLOTS16 leaf, node and root vectors with a separate keccak256 implementation and every one matched, but found the reference account was missing the authorityRoot() function and AuthorityStateChanged event the spec requires. The author replied at 01:39 that both are now added, with a test.

https://ethereum-magicians.org/t/erc-8403-account-authority-lifecycle/29570/15

EIP-8483, post-quantum material registration (PR #12609)

Got a review at 17:32 on 2026-11-17. The EIP lets a validator's withdrawal address register 32 bytes of PQ material, stored in the beacon state for a future migration fork. The reviewer pointed out that whoever owns the withdrawal address often isn't the operator (contracts, custodians, delegated staking) and suggested adding a path triggered by the BLS key. Otherwise contracts need upgrades, custodians need to support a new transaction, and delegators need to coordinate with operators, all of which would slow the migration.

https://github.com/ethereum/EIPs/pull/12609#discussion_r4598334944

Other updates

EthSystems explained

Ethereum.org launched an institutional privacy guide at 19:04 on 2026-11-17, and EthSystems explained at 18:22 that it grew out of the EF's institutional privacy task force. Institutions that need to keep data confidential while staying compliant can start there and contact the team directly.

https://x.com/eth_systems/status/2122651553261867456

X post

LambdaClass: what a cryptographic break would mean for Ethereum (X post at 03:48 on 2026-11-18), the second post in its post-quantum series. Neither hardware wallets nor multisigs stop a quantum attacker, and it covers how ethrex and ethlambda are testing the migration.

https://x.com/class_lambda/status/2122794143852179674

Community

Mozilla's analysis

Vitalik urges opposition to Canada's C-22 bill at 17:43 on 2026-11-17, linking Mozilla's analysis. He argues that AI is making this a hard period for cybersecurity, which makes it even more important to cut backdoors and mass data collection. In a reply at 18:29 he notes that senators use Signal too, and whoever controls the backdoors could selectively expose people's secrets.

https://blog.mozilla.org/netpolicy/2026/10/08/canadas-bill-c-22-threatens-encryption-users-privacy-and-the-security-of-digital-economies/

a reply

Vitalik urges opposition to Canada's C-22 bill at 17:43 on 2026-11-17, linking Mozilla's analysis. He argues that AI is making this a hard period for cybersecurity, which makes it even more important to cut backdoors and mass data collection. In a reply at 18:29 he notes that senators use Signal too, and whoever controls the backdoors could selectively expose people's secrets.

https://x.com/VitalikButerin/status/2122653327595020572