01 · The problem
What security problem did Ridham demonstrate?
Today’s wallets are not post-quantum secure, and the blockchain stack is built around how those wallets sign transactions. Once a capable quantum attacker can break those signatures, the attacker could authorize transactions and spend another user’s funds.
- Today’s blockchain wallets depend on signatures that are not post-quantum secure.
- A capable quantum attacker could forge authorization and move another user’s funds.
- Post-quantum signature schemes are still evolving, so a permanent verifier creates migration risk.
02 · The solution
Protect the funds in a contract and make signature verification replaceable.
Instead of keeping funds directly in the wallet, keep them in an on-chain smart contract. A pluggable verifier decides which signatures are valid and when the contract can release the funds.
03 · What was demonstrated
A wallet flow with a pluggable verifier
The talk broke the approach into a practical sequence:
- 1Hold funds in an on-chain contract
- 2Send the proposed signature to a verifier
- 3Release funds only after verification
- 4Swap the verifier as cryptography improves
04 · Technical take
Design for cryptographic change without moving customer funds
Post-quantum signature schemes are still maturing. A swappable verifier allows the cryptography to be upgraded without moving the protected funds or forcing users to migrate their keys.
Separate funds from keys
The contract can protect assets even when the signing method must change.
Build replaceable trust
A pluggable verifier avoids locking the system to one immature scheme.
Minimize migration
Security upgrades are easier when users do not have to move funds or recreate keys.
05 · Continue exploring