Ethereum Research Daily
Post-quantum account engineering moved quickly in a single day. EIP-8288 merged a fix to the leanSPHINCS public key format, and its batched proof work was folded into a new draft, "Generic Proof Verification and Batching". A new draft, ERC-8499, proposes deriving hash-based signing keys from BIP-39 phrases. Toni says core devs may revisit the Hegotá scope within two weeks and narrow it toward post-quantum, and audit findings on the EIP-8037 and EIP-8038 repricings land on November 16.
Image: Ethereal news
Merged 2026-11-14 04:48. Author VanshSahay notes that EthLib and leanVM both moved leanSPHINCS to the FIPS 205 layout and dropped the old public parameter. He caught the mismatch while implementing the scheme in go-ethereum, where the known-answer tests from both projects only pass with the new order.
Opened by Marchhill on 2026-11-13 19:21 and still being revised at 2026-11-14 05:00. It turns on EIP-8288's reserved LEANSTARK_SCHEME and adds sponsored batch proofs: a sponsor pays once per batch leaf, member transactions pay per claim, and any valid subset can be included without members signing again. Discounted claims go builder-direct only, while ordinary single proofs stay eligible for the public mempool. The PR says every gas value and bound is provisional, and activation requires measured full-block completion time and memory on stated hardware.
Around 2026-11-14 05:28 without merging; its description says the new draft above supersedes it.
Thread opened by johba on 2026-11-13 17:34 (ERC PR #2172 followed at 17:41). It covers leanSPHINCS, SLH-DSA, WOTS, FORS and XMSS. The author lays out today's split: some wallets derive from the BIP-39 entropy with Keccak-256, some run a second PBKDF2, and some apply HMAC-SHA512 to the BIP-39 seed, so one phrase gives different keys in different wallets. A reply at 2026-11-14 02:38 adds that after a parameter-set change, a restoring wallet derives every key type it supports and checks which one the account accepts, and it must keep deriving retired key types because the account address may have come from the old key.
ERC-8499: Hash-Based Key Derivation from BIP-39, thread opened by johba on 2026-11-13 17:34 (ERC PR #2172 followed at 17:41). It covers leanSPHINCS, SLH-DSA, WOTS, FORS and XMSS. The author lays out today's split: some wallets derive from the BIP-39 entropy with Keccak-256, some run a second PBKDF2, and some apply HMAC-SHA512 to the BIP-39 seed, so one phrase gives different keys in different wallets. A reply at 2026-11-14 02:38 adds that after a parameter-set change, a restoring wallet derives every key type it supports and checks which one the account accepts, and it must keep deriving retired key types because the account address may have come from the old key.
At 2026-11-14 03:09 johba asked whether an XMSS seed can be recovered from a mnemonic if the keystore file is lost, the way ERC-2333 works for BLS. ERC-8499 deliberately does not rebuild stateful keys from a phrase.
The EIP-8141 PR adding leanSPHINCS was updated at 2026-11-14 04:20 and is still open. Which post-quantum scheme Frame transactions adopt depends on it.
With a revision pushed at 2026-11-13 13:44 and an author reply to review at 16:00. Background: EIP-8151 makes ecRecover read the recovered address's code, so an EIP-8141 Frame transaction whose validation prefix calls ecRecover can depend on a third-party account. The new rules record each recovered address and its code class (empty or delegated, versus other code) as a signer dependency and revalidate when the class changes. They cap pending transactions per recovered address, with separate shares for the canonical signature hash and other digests, and count pay-frame recoveries once per paymaster.
Pushed 2026-11-13 21:49. EIP-8430 supports 2D nonces where key 0 is the account's normal nonce, and this rule ties in-transaction EIP-7702-style delegation to that main nonce sequence.
Got two revisions at 2026-11-13 17:58 and 19:44 (weighting writers by listing count, proving equivocators). Correction: yesterday's report called this draft EIP-8500. The file in the PR is eip-8497.md, and Ethereal news #47 also lists it as EIP-8497.
Frame Transaction Breakout #8 on November 17 (pm #2295).
2026-11-13 17:00. The question is whether a narrower post-quantum focus would move faster; reconsidering FOCIL and features that scale or shorten slots would be a significant step.
2026-11-13 15:28, cautioning against reading a roadmap proposal as already approved.
Published 2026-11-13, records that Ethlabs withdrew quick slots (EIP-8198) to focus on post-quantum and it is now DFI; that the Mumbai workshops put the Q-day estimate at 2029, down from 2032 a year ago; that Dedaub, ChainSecurity and the EF will present EIP-8037 and EIP-8038 audit findings at ACDT #103 on November 16, with next steps (spec changes or Hoodi scheduling) at ACDE #249 on November 19; and new EIPs including EIP-8487 (separate execution credits and billing credits) and EIP-8488 (versioned opcodes for gas repricing).
Was filed at 2026-11-14 04:28: a post-quantum consensus layer working session, first meeting November 17 at 21:00 for 120 minutes, configured to recur every Tuesday, Wednesday and Friday.
2026-11-13 21:41, pointing to ecrecover, permits and immutable contracts as bigger compatibility problems in a post-quantum migration.
(per Ethereal news #47, 2026-11-13) adds EIP-8038 state access repricing to its experimental Glamsterdam support, so contract developers can estimate post-repricing gas now.
2026-11-14 01:43, with withdrawals to any EVM chain. A privacy tool you can actually use today.
2026-11-13 21:28: the Bermuda Bay team deposits USDC from Ethereum into a private balance on Rollup X, with public and private balances side by side.
2026-11-13 22:17: apps define rules and block builders drop violating transactions during block building; the piece covers the risks and the impact on rollup Stage 1.
Merged 2026-11-14 01:07, a one-sentence spec clarification.
Opened 2026-11-14 07:26.
Another reply at 2026-11-14 01:53 backs Bangkok as unambiguous and ASCII-friendly.
Announced 2026-11-13 19:18.
Clients and security (per Ethereal news weekly #47): Lighthouse v8.3.3 is a high-priority security release; Reth v2.11.0 parallelizes EIP-7702 authorization recovery; Across had its domain hijacked through Namecheap and Gnosis Pay reported a breach of a legacy system, so affected users should check the official notices.
2026-11-14 04:17; Barnabé adds that ethereum:native will be a post-quantum store of value, 2026-11-14 04:25.
Ethlabs collects takes on ETH as a store of value, 2026-11-14 04:17; Barnabé adds that ethereum:native will be a post-quantum store of value, 2026-11-14 04:25.
2026-11-13 23:13, and he argues against a hard-cap security budget.
2026-11-13 21:32, stressing crypto agility.
2026-11-13 20:11.