New Ethereum Research the proposal is to put post-quantum wallet security in the background, describing a reliable way to verify signatures that are not related to the amount of EVM without requiring a complete upgrade of the protocol.
The idea, published by Ethereum researcher nicocsgy, explores an EVM-optimized version of SPHINCS + stateless post-quantum digital signatures. This design aims to prove that quantitative authentication is more effective in wallet use cases by adapting the scheme to Ethereum’s execution style.
TL; DR
- Ethereum Research proposal suggests a post-quantum signature verification method for EVM.
- Its architecture is based on SPHINCS+ but optimized for Ethereum systems.
- This proposal uses KECCAK256 instead of SHAKE256 to better match the EVM value.
- It can give wallets and smart accounts a flexible way to migrate before a threat escalates quickly.
Why Quantum Security Is Back in the Ethereum Discussion
Quantum computing does not threaten Ethereum wallets today, but developers are already thinking about what the migration path will look like if cryptographic concepts change.
Most blockchain wallets rely on a private network. If future computers become powerful enough to break commonly used signatures, wallets and protocols will need other ways to securely verify ownership.
This does not mean that Ethereum is facing an imminent crisis. It means that the environment needs reliable ways to increase the risk before it occurs.
Ethereum Research’s opinion is interesting because it does not wait for a complete overhaul of the infrastructure. Instead, it examines whether post-quantum signature verification can be useful within the EVM itself.
How SPHINCS-Based Design Works
SPHINCS+ is a post-quantum signature system developed by NIST. The problem is that post-quantum signatures can be large and expensive to verify on-chain, especially if the design doesn’t scale well with Ethereum’s value.
This proposal modifies the concept by replacing the SHAKE256 hash pattern with KECCAK256, which is derived from the EVM. This is important because Ethereum already supports KECCAK256 well, making it a reliable rebuild for the machine.
The author also focuses on the design of the wallet instead of trying to cover every use case. That exchange is important. If the goal is to provide users with a reliable way to protect money, the solution should be affordable to use, not just academically efficient.
The report estimates the gas leak to be between 127,000 and 150,000. This is still more expensive than standard signature verification, but it’s low enough to be discussed as useful for wallet security and smart account design.
What This Could Mean For Wallets
The most useful part of the concept is the idea of a non-elevating method. If smart accounts or wallet contracts can verify the post-quantum signature at the request level, users will not have to wait for Ethereum itself to change its signature.
This can be important for long-term holders, managers, and organizations. These operators are less concerned with making the entire transaction as cheap as possible and more concerned with ensuring that large scales can be secured over long distances.
A practical solution may include smart accounts that support recovery, migration, or spending. Users can move money in wallets that are hard to attack under future cryptographic concepts as the main Ethereum protocol continues to evolve.
Still Early, But Worth Watching
This is still a research, not a finished level of the wallet. There are trade-offs around signal strength, gas costs, installation complexity, and user experience. Any manufacturing model may need to be carefully evaluated before you start relying heavily on it.
Even so, the advice is important. Crypto security can’t wait until quantum computers are powerful enough to create a crash. The best way is to test the migration tools early, while there is still time to practice slowly.
For Ethereum, post-quantum preparation will be slow. Ideas like this show how the first steps can be done in a wallet and a smart account instead of using one big switch in the network.
