Ethereum EIP Repository Advances Post-Quantum Signature Proposals in November 2026

Three post-quantum proposals advanced in the ethereum/EIPs repository in the first half of November 2026: EIP-8151 added public mempool rules for recovered signers (Nov 16), EIP-8288 pinned the leanSPHINCS public-key format for in-mempool STARK aggregation (Nov 13), and EIP-8355 committed ML-DSA verify vectors and reject cases for its contract precompiles (Nov 7). The article maps what each change actually does, scores the three on a proprietary Quantum Readiness Score, and explains why this quiet standards work matters before the Glamsterdam upgrade ossifies wallet and mempool behavior.

· Updated November 18, 2026 · Zain Tran · 5 min read · 0 total views · 0 today

Categories: technologyEthereum

Futuristic editorial visualization of three post-quantum EIP specification documents advancing through a commit pipeline with ML-DSA and leanSPHINCS signatures flowing into an Ethereum mempool

The commit landed at 23:47 on a Monday.

I was watching the ethereum/EIPs repository when 8194528a2e dropped on November 16 — "Update EIP-8151: add public mempool rules for recovered signers." Not a typo fix. Not formatting. A change that tells every mempool operator on Earth what happens to a transaction signed by a wallet whose keys are already considered burned. Then on November 13, 79e11d2a55 rewrote how EIP-8288 encodes a leanSPHINCS public key. And on November 7, someone committed ML-DSA verify vectors — actual test data — for EIP-8355.

Three post-quantum proposals. One week. The quietest, most important work in Ethereum right now isn't a headline upgrade. It's a standards repo moving.

Key Metrics at a Glance

Metric Value Note
PQ-related EIP commits, Nov 1–17 2026 3 tracked EIP-8151, EIP-8288, EIP-8355
EIP-8151 latest substantive update 2026-11-16 Public mempool rules for recovered signers
EIP-8288 latest substantive update 2026-11-13 leanSPHINCS public key = PK.seed || PK.root
EIP-8355 latest substantive update 2026-11-07 ML-DSA 65/87 verify vectors + reject cases
EIPs referenced 8051, 8141, 8151, 8288, 8355 EIP-8141 = Frame Transaction carrier
NIST lattice scheme in play ML-DSA (FIPS 204) Levels II/III precompiles proposed
Hash-based scheme in play leanSPHINCS Aggregated via recursive STARKs
Current default signature ECDSA secp256k1 Quantum-vulnerable, still ~100% of mainnet txns

What Actually Changed This Month

EIP-8151 governs "account code restricted ecRecover" — the mechanism that lets a contract verify a recovered signer — and the November 16 update added the public mempool rules. In plain English: if your key is compromised and someone recovers your account code, the mempool now has explicit, written rules about whether a transaction from that recovered signer is admissible. That is not plumbing. That is a policy decision about whose transactions count.

EIP-8288 is the aggregation layer. It proposes in-mempool aggregation of signatures and proofs using recursive STARKs, carried inside the EIP-8141 frame transaction. The November 13 change pinned the leanSPHINCS public key format to PK.seed || PK.root — a single canonical encoding, which is exactly the kind of boring detail that decides whether a scheme is deployable or a research toy.

EIP-8355 adds precompiles so contracts can verify ML-DSA (FIPS 204) signatures at NIST security levels. The November 7 commit shipped ML-DSA 65 and 87 test vectors plus negative cases — the difference between "we think this works" and "here is the data that proves the precompile rejects malformed signatures."

Futuristic editorial visualization of three post-quantum EIP specification documents advancing through a commit pipeline, with ML-DSA and leanSPHINCS signatures flowing into an Ethereum mempool

The Post-Quantum Signature Landscape

This is where a lot of coverage stops at "quantum bad, post-quantum good." It's more interesting than that.

Scheme Role in the stack Signature size Key size Verification cost Status
ECDSA secp256k1 Today's default 64–72 B 32 B ~fast (native precompile) Deployed, quantum-vulnerable
ML-DSA (FIPS 204) Contract-verifiable PQ signature ~2.4–4.6 KB ~1.3–2.6 KB Gas-heavy precompile EIP-8355 / EIP-8051, vectors committed Nov 7
leanSPHINCS PQ signature for aggregation ~7–17 KB ~32 B (seed+root) Prover-side, folded into STARK EIP-8288 format pinned Nov 13

The pattern: hash-based signatures (leanSPHINCS) have tiny keys and huge signatures but are conservative and well-understood. Lattice signatures (ML-DSA) have bigger signatures but are NIST-standardized and contract-verifiable via precompile. Ethereum is deliberately not picking one winner — it's building rails for both, with aggregation compressing their cost back down via EIP-8288.

A Proprietary Check: Quantum Readiness Score

I scored each proposal on the November activity using a simple framework I use for standards work — PQ Readiness Score (PQRS) = (Specification maturity × 0.4) + (Test vector availability × 0.3) + (Integration path clarity × 0.3), each 0–10.

EIP Spec maturity Test vectors Integration path PQRS
EIP-8355 (ML-DSA precompiles) 7 (precompile spec, levels defined) 9 (ML-DSA 65/87 vectors + reject cases) 8 (direct precompile call) 7.9
EIP-8288 (mempool aggregation) 6 (leanSPHINCS format pinned Nov 13) 5 (aggregation proofs still maturing) 8 (rides EIP-8141 frame txns) 6.3
EIP-8151 (recovered-signer rules) 8 (mempool rules now explicit Nov 16) 6 (rule sets, fewer raw vectors) 7 (mempool policy, not a precompile) 7.1

The takeaway: EIP-8355 is furthest along because it has real test vectors. EIP-8288 is the scalability play. EIP-8151 is policy — and policy moves slower but binds harder.

Comparison matrix rendering ECDSA, ML-DSA and leanSPHINCS signature sizes and a proprietary PQ Readiness Score gauge for EIP-8151, EIP-8288 and EIP-8355

Decision Framework: What to Watch per Role

Are you a wallet developer?
├── YES → Track EIP-8151 mempool rules; recovered-signer txns may be filtered
└── NO  → Are you a contract developer?
    ├── YES → EIP-8355 precompiles let you verify ML-DSA in-contract today-ish
    └── NO  → Are you a rollup/sequencer?
        ├── YES → EIP-8288 aggregation can shrink PQ signature overhead in frames
        └── NO  → Just hold; no mainnet action required yet

Why This Matters Now

Glamsterdam is the named next upgrade. Every signature scheme decision made in these EIPs has to land before wallet and mempool software ossifies around it. The November commits are the last cheap moment to change the encoding — after that, the format is load-bearing.

The honest caveat: none of this protects your existing ECDSA key from a quantum attacker today. What it does is build the off-ramp — contracts that can verify PQ signatures, mempools that know how to handle recovered signers, and aggregation that makes PQ cheap enough to actually use.

Futuristic editorial illustration of an Ethereum roadmap stretching toward Glamsterdam, with post-quantum signature rails being laid into the protocol ahead of the fork

TL;DR

  • What: ethereum/EIPs advanced three post-quantum proposals in Nov 2026 — EIP-8151 mempool rules (Nov 16), EIP-8288 leanSPHINCS key format (Nov 13), EIP-8355 ML-DSA test vectors (Nov 7)
  • Why: These are the rails that let contracts verify PQ signatures and mempools handle recovered signers before Glamsterdam ossifies wallet behavior
  • Edge: EIP-8355 leads on readiness (7.9/10 PQRS) because it shipped real verify/reject vectors; EIP-8288 is the cost-compression play
  • Watch: Whether EIP-8288 aggregation lands in a Glamsterdam-adjacent frame spec, and whether wallet vendors implement the EIP-8151 mempool filters

Sources


Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter. He writes about Ethereum, ETH, smart contracts, DeFi, Layer 2 networks, staking, validators, and the real-world consequences of technical and financial failure.