Someone searching for a quantum-resistant cryptocurrency is really asking about the network underneath it. A token is only as quantum-safe as the blockchain that secures it. Very few networks qualify, because quantum resistance requires two separate layers to hold up: the cryptography that verifies the network, and the cryptography that secures user accounts. However, it is precisely in these areas that Starknet has structural advantages.
Starknet covers both layers that determine a chain’s quantum exposure. Its STARK proofs are post-quantum secure by mathematical construction. Its native account abstraction means quantum-resistant wallets can deploy today, without a fork or a migration event. Working Falcon-512 (a post-quantum signature scheme) account implementations already exist, published by S2morrow and OpenZeppelin. Starknet has less remaining work than other major chains to complete that transition, and a committed, inspectable roadmap for finishing it. As an Ethereum Layer 2, Starknet’s full-stack quantum safety depends on Ethereum completing its own transition.
Quantum resistance depends on two central tech layers
Searches for quantum-proof crypto usually turn up lists of niche coins built around a single post-quantum signature scheme. That framing asks the wrong question. What actually faces a quantum adversary is the blockchain underneath, and a blockchain’s quantum exposure is easiest to understand through two tech layers:
- The verification layer: the cryptography the network itself relies on to prove that state transitions are valid. For most modern scaling infrastructure, that means proof systems.
- The account layer: the signature scheme that authorizes transactions from users’ wallets.
A quantum computer running Shor’s algorithm (a quantum algorithm for finding an integer’s prime factors) breaks elliptic-curve cryptography (ECC), which exists at both layers of most chains. ECDSA signatures secure most Bitcoin and Ethereum accounts, and elliptic-curve pairings sit inside most SNARK-based rollups. A chain that fixes one layer and neglects the other stays exposed.
Starknet starts from a post-quantum-compatible position at both layers: STARK proofs are hash-based, and account abstraction allows post quantum wallets without a protocol fork.
The verification layer: Are STARKs quantum-resistant?
Yes. STARKs are the foundation of Starknet’s entire post-quantum position.
STARKs (Scalable Transparent Arguments of Knowledge) rely only on post-quantum secure hash functions for their cryptographic commitments. There is no known quantum attack that breaks hash functions. The best-known quantum attack, Grover’s algorithm, merely speeds up brute-force guessing, an advantage that is eliminated by using slightly larger hash parameters. That reliance on hash functions is what makes STARKs post-quantum secure, a mathematical consequence of how they’re built.
In contrast, SNARKs, the proof system behind most competing rollups, rely heavily on elliptic-curve cryptography, which Shor’s algorithm can break. When practical quantum computers arrive, elliptic-curve-based proof systems will need to be restructured from the ground up.
Because STARKs rely on hash functions and mathematics rather than quantum-vulnerable cryptographic assumptions, Starknet’s verification layer, which secures all value on the network, has no known quantum vulnerability.
The account layer: native account abstraction
Crypto assets are guarded by a user account’s signature scheme. The industry standard is ECDSA, and on most chains, it’s hardwired into the protocol. As a result, making Bitcoin or Ethereum accounts quantum-resistant requires a hard fork at the protocol level and a coordinated migration, where every holder moves assets to new post-quantum address types by a governance-set deadline.
Starknet works differently because of native account abstraction. Every Starknet account is natively a smart contract, and account abstraction is the only account model. Each account defines its own transaction validation logic, including which signature scheme it accepts. That has four concrete effects:
- Signature schemes are swappable at the protocol level. An account can verify post-quantum signatures because validation is just contract code.
- No hard fork is needed. Adopting post-quantum signatures doesn’t affect the protocol.
- No migration is required. Upgrades happen account by account at the wallet level, according to each owner’s schedule, not network-wide.
- Built-in upgradability. Post-quantum standards are evolving. Starknet accounts can swap their verification logic in place, with the same address and same assets, so adopting post-quantum security now doesn’t lock you into standards that could change in the future.
Quantum-resistant wallets exist today on Starknet
S2morrow has demonstrated a working post-quantum account on Starknet, with its own Falcon-512 implementation written in Cairo. Falcon (FN-DSA, draft FIPS 206) is a lattice based, post-quantum signature scheme in NIST’s post-quantum cryptography standardization track.
OpenZeppelin, among the most established names in smart contract security, has published deployable post-quantum account contracts for Starknet. The work includes Falcon-512 verifiers using three different hash functions: one variant that follows the official Falcon specification and is interoperable with any compliant signer, and two additional variants that are post-quantum safe and significantly cheaper. The repository ships account contracts that can be deployed today, including on testnet and through a browser wallet.
Two caveats:
- The OpenZeppelin contracts are early implementations and haven’t been audited yet. Treat them as a demonstrated capability, not audited, production-ready code for safeguarding client assets.
- Post-quantum signatures cost more per transaction than classical ones today, with active optimization work underway.
How the two layers reinforce each other
The two layers reinforce each other:
- A quantum-resistant wallet on a chain with a quantum-vulnerable proof system is like a steel lock on a cardboard box. With Starknet’s STARK foundation at the verification layer, account-level protection actually protects.
- Similarly, a post-quantum proof system on a chain with fork-dependent accounts is also insufficient, leaving holders dependent on governance decisions. Starknet’s native account abstraction means individuals and institutions act on their own timelines.
- And because STARKs efficiently prove heavy computation, Starknet is structurally suited to absorb the higher verification cost of post-quantum signatures.
What about Ethereum underneath?
As an Ethereum Layer 2, Starknet’s proofs settle on Ethereum, and bridged assets are held in Ethereum contracts, which are still quantum-vulnerable. Ethereum has its own post-quantum migration ahead, and until then, no L2 can claim complete, full-stack quantum safety. Our companion piece, Starknet’s Post-Quantum Security Roadmap, covers this dependency and our remaining forward- and backward-compatibility efforts in more detail.
That dependency isn’t uniform across Layer 2s, though, and the differences are where Starknet’s edge becomes concrete. Ethereum’s long-term roadmap also calls for hash-based, STARK-friendly cryptography, which aligns with Starknet’s post-quantum foundations.
Implications for holders and institutions
For crypto holders, the “harvest now, decrypt later” threat, by which adversaries record chain data today and use that data to crack keys with quantum computing in the future, means quantum exposure exists before quantum computers do. With Starknet, moving to a quantum-resistant wallet is a deployment choice for individuals, not a fork decided by a governance vote.
For users and institutions, the difference lies in who controls the timeline for the layers that can be secured today. On most chains, that’s protocol governance. On Starknet, it’s the account owner.
With NIST post-quantum cryptography standards finalized or in draft and government migration mandates underway, quantum readiness is becoming a compliance conversation. Starknet turns it from a dependency on someone else’s roadmap into a path you control yourself.
The bottom line
“Quantum-resistant cryptocurrency” usually describes a future state, contingent on forks, governance votes, and coordinated migrations. At its core, it’s a claim about the underlying network. Starknet’s claim already holds for the two layers that define a chain’s core quantum exposure: a STARK proof system that’s post-quantum secure by design, and native account abstraction that lets holders deploy quantum-resistant wallets on their own schedule. The remaining dependency, Ethereum’s own post-quantum transition, is one every L2 shares. Starknet will arrive at it with less work left than other major chains. For holders, that’s protection you can act on today. For institutions, it’s quantum readiness you can plan for ahead of time.
To learn more about StarkWare’s plan for Starknet’s post quantum security, read the Roadmap. _________________________________________________________________
FAQ
Which cryptocurrencies are quantum-resistant?
A cryptocurrency is only as quantum-resistant as the blockchain securing it, and very few networks hold up once you weigh both the verification layer and the account layer. Starknet stands out on both counts. Its network is secured by STARK proofs, which are hash-based and post-quantum secure. Its native account abstraction enables post-quantum signature schemes at the account layer, with working implementations already published.
Are STARKs quantum-resistant?
Yes. STARKs rely only on hash functions for their cryptographic commitments, and hash functions have no known quantum vulnerability comparable to Shor’s algorithm against elliptic curves. SNARKs, by contrast, generally depend on quantum-vulnerable elliptic-curve cryptography.
Is Bitcoin or Ethereum quantum-proof?
No. Both use ECDSA signatures, vulnerable to Shor’s algorithm, and post-quantum protection would require protocol changes plus a coordinated migration of assets. Most SNARK-based Ethereum Layer 2s also add elliptic-curve exposure at the verification layer.
Are quantum-resistant wallets available today?
On Starknet, yes, as a demonstrated capability rather than a finished product. S2morrow has shown a Falcon-512 account in Cairo, and OpenZeppelin has published deployable Falcon-512 account contracts, including an official-spec variant, with measured costs that fit Starknet’s validation limits. These are early-stage, pre-audit implementations, but they work today.
What’s the difference between quantum-proof cryptography and quantum-resistant cryptography?
“Quantum proof crypto” is a common search phrase, but cryptographers prefer “quantum-resistant” or “post-quantum secure,” since security claims are always stated relative to known attacks. By that standard, hash-based systems like STARKs sit in the strongest category recognized today, the same family of assumptions behind NIST’s standardized post-quantum schemes.
As an Ethereum L2, doesn’t Starknet depend on Ethereum’s quantum security?
Yes. Two Starknet surfaces depend on Ethereum’s migration: the bridge’s messaging layer and data availability layer, both of which rely on elliptic-curve cryptography. Ethereum is actively researching post-quantum security and has released a multi-year migration plan, laying out its dependencies on elliptic-curve cryptography across several layers of its tech. Starknet’s edge lies in everything above that shared dependency: its post-quantum proof system, and its accounts layer, which can adopt post-quantum signatures today. Once Ethereum migrates, Starknet will have less remaining work than other major L2s.
When should holders and institutions start preparing?
Now. Quantum risk precedes quantum hardware: adversaries can record encrypted data today and decrypt it once the hardware matures, and NIST has already directed organizations to begin transitioning to post-quantum cryptography standards. For holders, preparation means understanding your chain’s migration path before it becomes urgent. For institutions, it means incorporating quantum readiness into platform due diligence while it’s still a planning decision, not an incident response. With Starknet, that preparation can start immediately, since migration doesn’t require a hard fork or network event.
