An Ethereum research proposal aims to improve wallet security against quantum threats while keeping gas costs low.

An Ethereum Research proposal looks into a practical way to verify post-quantum signatures for EVM wallets, using an optimized design based on SPHINCS.

Frequently Asked Questions
Here is a list of FAQs about an Ethereum research proposal aimed at improving wallet security against quantum threats while keeping gas costs low

BeginnerLevel Questions

1 What is a quantum threat to my Ethereum wallet
A powerful quantum computer could in theory break the cryptography that protects your private key This would allow someone to steal your funds by signing transactions as if they were you

2 Why is this proposal different from just using a stronger password
This isnt about passwords Its about changing the underlying math that creates your wallets address and signs transactions A stronger password wont stop a quantum attack

3 How does this proposal keep gas costs low
It uses a clever cryptographic trick Instead of putting a large expensive quantumproof signature into every transaction it hides most of the proof in a separate cheaper data space Your transaction only includes a tiny cheap verification

4 Will this change how I send ETH or tokens
No From your perspective sending ETH would look and feel exactly the same The complexity is handled behind the scenes by your wallet software

5 Is this something I need to do right now
No Largescale quantum computers dont exist yet This is a proactive researchlevel proposal to prepare for a future threat You dont need to take any action today

AdvancedLevel Questions

6 What specific cryptographic change is being proposed
The proposal likely moves away from the current ECDSA toward a latticebased signature scheme like CRYSTALSDilithium These are believed to be resistant to quantum attacks

7 How does the low gas cost trick actually work technically
It uses a technique called signature aggregation or batch verification with a lookup table The bulk of the large quantumproof signature data is stored once onchain Future transactions only need to reference that stored data with a tiny cheap pointer rather than resubmitting the whole signature

8 What is the main tradeoff of this proposal
The primary tradeoff is

Scroll to Top