AA2026-11-17_008

Native Account Abstraction #008

2026-11-17 3 decisions 410 transcript lines

Transcript

At a glance

Signature list will be removed from frames; replaced with a PROOF frame mode forward-compatible with EIP-8288
SPHINCS-to-signature-list PR (lightclient's DevCon sketch) is not the target path; 8288-compatible PROOF frame mode is preferred
Two large spec changes (remove sig list / 8288 compat, and SSZ hashing decision) targeted for resolution within ~one month before end-of-year freeze
Major frame spec changes (8288 compat + SSZ decision) — finalize before end-of-year holidays (~mid December 2026)verify date
leanSPHINCS parameter set finalized — January 2027 deadline (likely earlier per Nico)verify date

Detailed notes

Testing

  • •Mario proposes a new mempool-validation reference test format for clients to regression-test MAX_VERIFY_GAS rules; lukewarm yes from Nethermind, ethrex, Besu00:50:10

Max Verify Gas

  • •EIP-8141 PR #12644 proposes raising MAX_VERIFY_GAS from 100K to 300K; Nethermind benchmarked this as balanced for PQ + DoS safety (initial target was 500K)00:46:09
  • •Toni cautions: MAX_VERIFY_GAS also sets builder critical-path work for FOCIL inclusion-list checks — final number depends on whether FOCIL is in Hegota00:47:32

Spec Priorities

  • •Guru: immediate focus should be frames spec + EIP-8151 (restricted ecrecover) + EIP-8298 (SETCODEFROM); harden PQ readiness before adding more EIPs00:43:38
  • •EIP-8141 PR #12506 (set code from as default in SENDER mode) + EIP-8151 together form the full K1 retirement path alongside 770200:45:47
  • •SSZ serialization/hashing for frame transactions raised at DevCon; lightclient considers it better in isolation but acknowledges large scope; no decision yet00:14:04

Focil Interaction

  • •Daniil raises FOCIL + frames interaction as a risk; spencer and others deferring until ACDE/ACDC clarify whether FOCIL stays in Hegota00:57:33

Pq Signatures And Sphincs

  • •PQ sigs without aggregation: even several hundred SPHINCS sigs/block is only a few MB; aggregation is for efficiency, not security — don't block shipping00:23:03
  • •Proposal: exclude calldata cost from the 100K verify gas mempool limit; large SPHINCS sigs would otherwise consume most of the budget00:30:51
  • •SPHINCS precompile debated; Nico/Sanso prefer EVM execution if leanPCS makes it cheap enough — avoid precompile if possible00:34:03

Eip8288 Forward Compatibility

  • •EIP-8288 (leanPCS): frames must be forward-compatible; primary change is removing the signature list in favor of a PROOF frame mode00:06:13
  • •Goal: users should not need to change wallets again when aggregation (EIP-8288) ships; forward-compat design is the priority over incremental devnet updates00:09:15
  • •lightclient's sketch: new PROOF frame mode where initial content is a regular signature; protocol interprets it per 8288 shape in future forks00:18:05

Action items

  • •Post LeanPCS resources/writeup to ETH R&D so teams can evaluate fit with frames PROOF modeNico
  • •Open draft PR with 8288-forward-compatible dependency frame proposal for async discussionIván | ethrex
  • •Switch leanSPHINCS implementations to new PQ bindings (breaking change in lean-pq-bindings PR #45)All teams using leanSPHINCS

Agenda

From the call issue #2295Show
  • L1 R&D / Devcon event summary - @lightclient
  • new/existing proposal discussions
  • devnet updates
    • current devnet status
    • next devnet planning
      • spec changes
      • test release timeline
    • client team updates
  • call for community feedback, e.g., wallet, tooling, app devs

open threads:

Key decisions

  • Signature list will be removed from frames; replaced with a PROOF frame mode forward-compatible with EIP-8288

    The goal is to ensure users do not need to change wallets again when aggregation (EIP-8288) is implemented; forward-compatibility is the priority.
  • SPHINCS-to-signature-list PR (lightclient's DevCon sketch) is not the target path; 8288-compatible PROOF frame mode is preferred

    The team rejected the SPHINCS-to-signature-list approach in favor of a PROOF frame mode compatible with EIP-8288.
  • Two large spec changes (remove sig list / 8288 compat, and SSZ hashing decision) targeted for resolution within ~one month before end-of-year freeze

    The resolution of major frame spec changes, including SSZ hashing and EIP-8288 compatibility, is targeted for mid-December 2026.

EIPs discussed

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.