How to Implement Post-Quantum Signatures in Solidity

Frequently Asked Questions

01.Can I add post-quantum signatures without redeploying my existing wallet contracts?

Yes, if your wallets use ERC-4337 account abstraction. Validation logic lives inside the smart contract account, so a new validator module can accept ML-DSA signatures alongside ECDSA without changing the wallet address or moving funds. Externally owned accounts cannot be upgraded this way.

02.What's included in the audit cost for a post-quantum signature module?

A typical scope covers the validator contract, key storage or registry pattern, hybrid AND-mode signature logic, and testnet gas benchmarking. Most operators budget an audit tied to the complexity of their existing wallet architecture and whether social recovery is in scope, run alongside a phased mainnet rollout rather than a single cutover.

03.Can I start with an MVP instead of migrating every contract at once?

Yes. Most teams pilot ML-DSA verification on one contract, treasury wallet, or product line first, benchmark gas cost and validation latency, then extend to the rest of the fleet over several weeks. A full-system cutover on day one carries the highest operational risk and is not recommended.

04.Do I need a precompile, or can I verify ML-DSA signatures in pure Solidity?

Pure Solidity verification is possible but gas-expensive because the lattice math involves large polynomial operations. A dedicated precompile handles the heavy computation off the EVM's interpreted opcode path, which is why Ethereum's proposed precompile route is the practical option for production contracts today.