StarkWareQuantum Hub

Learn

Starknet and quantum security

Explore articles, podcast conversations, definitions and primary sources on quantum threats, post-quantum cryptography and Starknet.

Articles & podcasts

Quantum library

Showing 6 of 18 items.

  1. The first quantum-safe Bitcoin transaction has been mined

    Avihu Levy’s QSB method has been executed on Bitcoin mainnet, moving coins into quantum-resistant storage with no soft fork or change to consensus rules.

  2. Top 5 Quantum Computing Myths, Answered

    Can quantum computers break crypto wallets? Not yet, and not the way most coverage suggests. Five quantum computing myths, answered with dated evidence.

  3. What is Q-Day?

    Q-Day is the day a quantum computer breaks public-key cryptography. No one knows the year, but the migration deadlines already exist.

  4. Understanding the Quantum Threat

    Maps quantum attacks to signatures, encryption, hashing and five blockchain migration surfaces.

  5. Quantum security for everyone: the Starkware Quantum Hub is now live.

    The StarkWare Post-Quantum Hub is live: Starknets migration, technical advancements, and post-quantum research all in one place.

  6. StarkWare and Bitcoin Journalist Pete Rizzo Launch the Quantum Bitcoin Countdown Podcast

    StarkWare and Pete Rizzo launch Quantum Bitcoin Countdown, a podcast asking whether Bitcoin can survive the quantum computing threat.

Selected answer

Selected answer: Is Starknet quantum-resistant?

The system claim

Is Starknet quantum-resistant?

No. Not as a single system-wide claim.

A. PQ-friendly architecture. STARK proving does not depend on elliptic-curve hardness.

B. Cryptographic agility. Native account abstraction allows account-level signature verification to change.

C. Migration status. Some parts of Starknet still need migration, particularly existing deployments and Ethereum-facing dependencies.

Open Migration

Public-key systems

What does Shor’s algorithm change?

ECDSA and KZG.

Shor’s algorithm threatens discrete-log public-key systems. In this Hub, that maps to account signatures and Ethereum-facing dependencies. Shor’s algorithm does not target the assumption behind StarkWare’s hash-based STARK proofs.

Hash functions

What does Grover’s algorithm change?

Security margins.

Grover’s algorithm gives a quadratic speedup for unstructured search, which affects parameter choices and hash-preimage margins. Grover’s algorithm does not break hash functions.

Post-quantum standards

Which standards matter?

Three NIST standards anchor this vocabulary: ML-KEM (FIPS 203), ML-DSA (FIPS 204) and SLH-DSA (FIPS 205).

NIST’s standards define particular key-establishment and signature schemes. They do not certify StarkWare’s STARK proofs or BLAKE2.

The stack

Where does each risk sit?

Migration

What does migration mean here?

Component by component.

Each Migration status identifies what is live, what remains, who controls the next change and which public evidence supports the status.

Compare all five surfaces

Reference term

Post-quantum cryptography (PQC)

Cryptography designed to resist known attacks from classical and quantum computers. The claim must name the primitive or system boundary it covers.

Reference term

STARK proof

A transparent proof of computation whose cryptographic commitments use hash functions rather than elliptic-curve hardness assumptions.

Reference term

Proof system

A proof system verifies computation. It is separate from the signature scheme that authorizes an account transaction.

Reference term

Account signature

The cryptographic signature an account uses to authorize a transaction. A post-quantum proving layer does not migrate account signatures by implication.

Reference term

Elliptic-curve cryptography and ECDSA

ECDSA is an elliptic-curve signature scheme. Shor’s algorithm threatens the discrete-log assumption that supports its security.

Reference term

KZG

A pairing-based polynomial-commitment scheme used by Ethereum’s blob path. It is an Ethereum-facing dependency, separate from StarkWare’s hash-based STARK proof layer.

Reference term

BLAKE2

A hash function already used for compiled class hashes and Starknet OS program hashes. That deployed scope does not migrate account authorization.

Reference term

Native account abstraction

Starknet accounts are contracts that define transaction validation. A new account implementation can choose different signature verification logic.

Reference term

Cryptographic agility

The ability to replace a cryptographic primitive without redesigning the system around it.

Reference term

Harvest now, decrypt later

A confidentiality risk in which encrypted data collected today is decrypted after quantum hardware improves. Public blockchain state is not secret, so the primary risk is signature forgery rather than decrypting public data.

Selected answer

The system claim

Is Starknet quantum-resistant?

No. Not as a single system-wide claim.

A. PQ-friendly architecture. STARK proving does not depend on elliptic-curve hardness.

B. Cryptographic agility. Native account abstraction allows account-level signature verification to change.

C. Migration status. Some parts of Starknet still need migration, particularly existing deployments and Ethereum-facing dependencies.

Open Migration

Primary sources

Foundational references

Papers, standards and protocol documentation. These sources are separate from the editorial content above.

Last updated: 27 August 2026.