• Vansh Sahay submitted leanSPHINCS post-quantum signature verification code to Ethereum client Geth on November 15.
• The code assigns leanSPHINCS the signature identifier 0x3 and verifies 32-byte public keys.
• The draft targets the Bogota Devnet 2 testnet and stays unmerged until specifications adopt leanSPHINCS.
leanSPHINCS Signature Verification Reaches Geth
An Ethereum (ETH) developer has written and tested code that lets the network's main execution client verify post-quantum digital signatures, a direct answer to the long-running quantum computer threat. The Ethereum (ETH) price is untouched by the work for now, since nothing ships to the live chain. The change landed in the Geth repository on November 15.
Geth is the most widely used Ethereum execution client, the software that processes transactions and maintains the blockchain's state across the network. Developer Vansh Sahay submitted the change, which implements leanSPHINCS, a post-quantum signature scheme designed to keep working even if a sufficiently powerful quantum computer breaks today's cryptography. The code lets the client verify and process transactions carrying a leanSPHINCS signature under the protocol's new Frame Transaction structure, a separate path from the signing method ordinary Ethereum transactions use today. The implementation assigns leanSPHINCS the signature identifier 0x3 and verifies signatures against a 32-byte public key. Sahay implemented key generation, signing and verification, then modified transaction processing so the client handles the new signature type end to end. The code change's own description states that the work passed unit tests and transaction execution specification tests, and that the existing test suite ran without failures. Digital signatures are the mechanism that confirms a transaction requester's authority and the integrity of what is being sent, the same trust layer that secures every smart contract interaction on the chain.
No Merge Before Spec Adoption
The technology is not live on Ethereum. The change is a draft written against Bogota Devnet 2, a development testnet where engineers trial changes before anything reaches a public network. Sahay's own instructions bar merging the code until leanSPHINCS is formally adopted in the protocol's technical specifications, and the gas fee for verifying the new signatures is only provisionally set, so cost figures stay open until benchmarking settles them.
Today's Ethereum signatures rest on elliptic curve cryptography. The scheme works well and has never been broken in practice, but researchers expect a capable enough quantum computer to break the math beneath it. That possibility, distant as it is, is why post-quantum designs keep entering Ethereum's development pipeline: a signature scheme protects every account and every transfer, so replacing it is planned years ahead rather than rushed after a breakthrough. The submission is also the second step in a sequence. On November 4, Ethereum developers proposed adding the leanSPHINCS signature method to Frame Transactions, a discussion that stayed at the level of technical specifications. The new code takes that proposal into working verification logic, the difference between agreeing on a design and building it. Even so, formal adoption of leanSPHINCS and any schedule for applying it to Ethereum's mainnet remain undecided, and the Geth code itself carries no activation date.
Plumbing Before the Consensus Fight
Our reading: the sequencing matters more than the code. A signature scheme change touches every transaction the network ever processes, so Ethereum's developers stage the engineering first, on a devnet, while the harder question, which post-quantum scheme becomes the standard, is settled in specification discussions. The 0x3 identifier and the provisional gas cost mark this as early scaffolding, not a release. For validator operators and Geth users, nothing changes today and no software update is required. The nearest fixed point ahead is the specification review that decides whether leanSPHINCS is adopted at all, alongside further Bogota Devnet 2 testing of the Frame Transaction path.
