0x3d2668ca3d26…3d2668cd
Ethereum Developer Drafts Native leanSPHINCS Checks for Frame Transactions
Developer ilitteri's Nov. 17 draft would have Ethereum nodes verify leanSPHINCS post-quantum signatures alongside frame transactions before execution, per EIP-8141.

Outputs
Ethereum developer ilitteri submitted the draft on Nov. 17, 2025, without an assigned EIP number.
The proposal applies leanSPHINCS, a hash-based post-quantum signature scheme, to frame transactions defined by EIP-8141.
Signatures would travel alongside transactions through the mempool and be verified by nodes before execution.
The earlier draft EIP-8288 would use the same interface for aggregation, reserving leanSTARK for future use.
The draft does not change the Ethereum network; its full technical specification remains to be written.
Ethereum developer ilitteri submitted a draft proposal on Nov. 17 to add native leanSPHINCS signature checks to frame transactions, marking a further step in the protocol's post-quantum planning. The draft specifies how nodes would verify post-quantum signatures before a transaction executes, although it carries no EIP number and leaves its full technical specification unwritten.
The proposal does not change the Ethereum network today. It is a design document, and its route to activation runs through the standard EIP process — assignment of a number, a completed specification, client-team review and eventual inclusion in a fork. For practitioners, the more immediate question is what the draft changes about how signatures would move through the system.
How would the signature scheme work?
leanSPHINCS is a hash-based signature scheme, a family resistant to attack by quantum computers. The draft applies to frame transactions as defined by EIP-8141, the structural proposal that introduces a dependency verification frame. That frame would declare which signature a transaction requires.
The design separates the signature from the transaction itself. Under the draft:
- Signatures would not form part of the transaction.
- They would travel alongside it through the mempool, where pending transactions circulate.
- They would be included with the transaction in a block.
- Nodes would verify them before executing the transaction.
This accompanying-signature architecture matters operationally. Mempool operators, block builders and wallet developers would all need to handle a second object per transaction, and node software would perform an additional verification pass before execution — a cost measured per transaction across every node in the network.
What does this change for post-quantum planning?
The draft builds on earlier work. A previous Ethereum draft, EIP-8288, covers both leanSPHINCS and leanSTARK and would use the same dependency-verification interface for signature aggregation. EIP-8288 reserves leanSTARK — a STARK-based verification path — for future use, while the new submission describes individual signature verification rather than aggregated checks.
The relationship between the two drafts suggests a staged approach: define per-transaction verification first, then layer aggregation on top through EIP-8288 once the interface exists. Aggregation matters because hash-based signatures are large relative to the elliptic-curve signatures Ethereum uses today, and batching verification is one way to contain the per-block cost.
The unnumbered status signals early-stage work. Nothing in the draft alters consensus rules, client behavior or transaction formats until it advances through Ethereum's standards process — a timeline historically measured in months to years for proposals touching transaction structure.
What this changes for practitioners is preparation, not action. Client developers now have a concrete architecture to evaluate; infrastructure operators can begin assessing mempool and block-propagation implications of accompanied signatures; and security teams gain a reference point for how post-quantum verification might reach mainnet. The next observable milestone is the assignment of an EIP number and publication of the full specification, after which the proposal enters technical review.
via tokenpost.com (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles