Start here · What is at risk? · Crypto project tracker · Wallets · Banks & the world · What you can do · What happens next?

Start here: the two-minute explanation

A quantum computer uses a different way of processing information. It is not simply a faster laptop, and a demonstration of many physical qubits is not proof that it can break a cryptocurrency key. The security concern is a future, sufficiently capable machine that can defeat certain widely used mathematical protections. There is no reliable public countdown to that capability. NIST explains the problem and the response.

Encryption keeps information confidential. Digital signatures let a system check that a transaction or update was authorized. A powerful quantum attack could undermine some current public-key methods used for those jobs. Post-quantum cryptography, or PQC, uses replacement mathematics designed to resist such attacks and can run on ordinary computers. “Post-quantum” does not mean you need a quantum computer to use it. Read NIST’s introduction.

Why care now? Replacing security across networks, devices, companies and old accounts takes years. Sensitive encrypted information may also be collected today for attempted decryption later. That confidentiality problem—“harvest now, decrypt later”—is distinct from forging a blockchain transaction signature. NIST’s migration guidance explains why preparation starts before the attack machine exists.

What are projects trying to protect?

• Your authorization: a wallet’s private key authorizes spending. A quantum-vulnerable signature scheme may need replacement even when the key is stored offline.
• Network agreement: validator signatures and related mechanisms help participants agree on valid history. Protecting a user account alone does not automatically protect consensus.
• Connections between systems: bridges, oracle operators, exchange custody, administrator keys and applications can introduce separate dependencies.
• Private information and trusted updates: bank messages, identity records, web connections and firmware signatures need their own migration plans.

Hashing, encryption and signatures are different tools. Do not assume that a claim about a strong hash function proves a wallet’s signatures are quantum-resistant. Hedera’s technical overview explicitly distinguishes these layers. See the cryptographic breakdown.

The challenge is migration—not just picking an algorithm

Engineers must manage larger keys and signatures, verification costs, limited device memory, audits, network capacity, old accounts and compatibility. Operators need ways to upgrade without locking users out or breaking recovery. “Crypto agility” means designing systems so their cryptographic components can change. Ethereum’s protocol work and BIS payment-system experiments illustrate why this is an ecosystem project.

Crypto project tracker: what is actually being done?

Status key: “Deployed component” describes a specific reported feature; “Roadmap” means work remains; “Draft” is a proposal; “Research” is not a retail recommendation. No label here certifies an entire ecosystem or predicts token performance. Project statements are attributed to their issuers and have not been independently audited by Crown & Ledger.

Algorand (ALGO) & Pera — deployed account features; broader migration remains

Algorand reports that native Falcon-1024 post-quantum accounts went live on mainnet in August 2026 with the v5.0.0 upgrade, with support in Pera Wallet and developer tools. Its state-proof work also uses Falcon. These are separate protections for account authorization and verifiable chain history.

The same roadmap still includes additional work on post-quantum multisignatures and consensus-related mechanisms. Therefore, “Falcon account support exists” is more precise than “everything on Algorand is quantum-proof.” An existing account is not automatically converted just because a wallet offers a new account type. Check current official instructions and recovery support before considering any change.

Algorand’s current deployment and roadmap · Falcon technical specification · Pera rollout report

Bitcoin (BTC) — draft protocol changes, not an activated migration

BIP 360, Pay-to-Merkle-Root, is listed as a Draft in the Bitcoin proposals repository. It addresses long-exposure public-key risk; it is not a complete replacement for quantum-vulnerable transaction signatures. A published BIP number does not establish network acceptance, wallet availability or mainnet activation. Future signature upgrades and user migration are separate questions.

Read BIP 360 and its status.

Ethereum (ETH) — coordinated protocol roadmap

The Ethereum Foundation’s post-quantum site describes work across execution, consensus and data. It includes account-authentication migration, replacement validator signatures and related infrastructure. Its schedule and milestones are explicitly subject to research and governance; targets are not proof that today’s ordinary account signatures have already changed. An application or layer-2 feature alone does not certify all of Ethereum.

Follow the maintained Ethereum PQ roadmap.

Hedera (HBAR) — published migration path, not full present immunity

Hedera’s April 2026 technical article says existing elliptic-curve signature methods require migration. Its path covers network communications and signature changes, alongside implementation and performance constraints. Strong hash functions or a distributed-consensus design should not be confused with post-quantum protection for every spending key.

Read Hedera’s technical assessment and roadmap.

Quantum Resistant Ledger (QRL) — specialist research to examine

QRL provides documentation centered on quantum-resistant cryptography and XMSS tooling. Treat it as a research example, not a recommendation to buy its token. A signature design must also be assessed alongside software quality, state management, wallet recovery, liquidity, governance and service availability. This page has not verified a QRL financial product’s eligibility for New York residents.

Explore the project’s technical documentation.

Chainlink, XRP, Stellar, Solana, Avalanche & USDC — assess the complete stack

These are also on our research watchlist. This review does not establish complete, deployed post-quantum protection across their networks, wallets and applications. That means not verified here, rather than “no work is being done.” For a token such as USDC, examine the issuing network, issuer-controlled permissions, custody and transfer route. For interoperability, examine both networks and the systems connecting them. One protected component does not automatically protect the whole route.

Explore the ecosystem connections on our homepage.

Wallets: what does “quantum-ready” really protect?

Ask four separate questions: device authenticity, trusted firmware updates, transaction signing, and network acceptance. A device can improve one layer while the asset’s blockchain still relies on a different signature scheme. Cold storage protects keys from many online threats; it does not change the mathematics accepted by a network.

Ledger — SDK capabilities are not automatic asset protection

Ledger reports adding ML-KEM and ML-DSA capabilities to its developer SDK. These address different cryptographic jobs. The article also describes hardware-resource limits and implementation caveats, including physical-attack protection work. This is evidence of developer capabilities, not a guarantee that every device, installed app, blockchain or existing account has migrated.

Our Ledger Atom preorder is not a hands-on review. We have not tested its post-quantum behavior and do not certify it as an end-to-end quantum solution.

Ledger’s SDK technical article · Our product research standards

Trezor Safe 7 — distinguish device protections from coin signatures

Trezor documents post-quantum mechanisms for parts of its boot/update trust chain and device authentication. Those protections do not, by themselves, replace Bitcoin’s or another network’s transaction signatures. We have not personally tested this device. Read exactly what the manufacturer’s claim covers rather than treating “quantum-ready” as universal asset insurance.

Trezor’s explanation of its design choices.

Before downloading, buying or migrating: request the exact device model, firmware/app version, supported account type, network rules, recovery method, audit scope and known limitations. Never enter a recovery phrase into a “quantum upgrade” website. A brand name, secure chip or new wallet address is not enough evidence.

What are banks, governments and the wider world doing?

United States — standards and migration planning

NIST published ML-KEM, ML-DSA and SLH-DSA standards in 2024. Key establishment and digital signatures are different functions, so institutions need the right replacement for each use. Its transition guidance supports migration planning and priorities, including protecting information with a long confidentiality lifetime. Government planning dates are not predictions of when a quantum attack becomes possible, nor a universal deadline for every consumer wallet.

NIST’s standards publications · Current transition guidance

Central-bank payment systems — BIS Project Leap experiments

BIS reports that Project Leap Phase 2 tested replacement signatures in a payment-system test environment. It found migration feasible while highlighting performance costs and changes across system components. This is an experiment with a defined scope, not evidence that every bank or live payment rail is already quantum-safe. It illustrates why institutions must coordinate technology, testing and operations.

Read BIS Project Leap and its reports.

Gold and tokenization — HSBC’s reported pilot

HSBC announced a quantum-safe technology pilot involving tokenized gold in September 2024. It is a useful example of financial institutions testing protections around digital representations of traditional assets. A pilot announcement does not certify every HSBC product, the gold market or a public cryptocurrency network.

Read HSBC’s original pilot announcement (PDF).

For stocks, bonds, real estate and bank money, the shared issue is the digital infrastructure used to authenticate instructions, protect records and operate settlement. Replacing cryptography does not automatically turn these assets into cryptocurrencies, require a particular token, or guarantee a profitable “quantum” investment.

What you can do now—without buying anything

• List the networks, wallet models, apps and custodians you depend on. Keep private keys, seed phrases, passwords and balances out of anything you submit to this site.
• Bookmark official release notes. Separate what a vendor has shipped from what it plans to ship.
• Keep supported software updated through verified official channels. Maintain a private recovery plan and understand it before making changes.
• Before a future migration, confirm network support, device support, recovery and the complete transfer process. Do not experiment with savings or rush because of a social-media deadline.
• For New York readers, verify the exact financial service and current eligibility independently. A technical feature, downloadable wallet or U.S. marketing claim is not a New York authorization.

Practice wallet separation · Learn to avoid costly mistakes · Compare wallet and yield risks

Practice: check a quantum claim in three minutes

Fictional reader Sam sees: “Our wallet uses post-quantum firmware checks, so every coin is protected forever.” On paper, identify the protected layer, the unproven leap and the evidence still needed. Answer: a firmware check is a device-update protection. Sam still needs evidence about transaction signing, network acceptance, recovery and other dependencies. “Forever” is not a defensible guarantee. No purchase, download or wallet connection is needed.

What is going to happen? Scenarios, not a countdown

• Preparation succeeds: networks and institutions deploy replacements, users migrate supported accounts, and operations adapt. Watch actual releases and adoption—not only announcements.
• Migration is uneven: old devices, dormant accounts and incompatible services remain. Recovery, cost, coordination and treatment of legacy funds can become difficult.
• Capability advances faster than expected: emergency changes and disruption become possible. Their timing and market effects cannot be predicted reliably here.

Quantum technology may also create useful research opportunities. That is a separate question from whether a retail product delivers an advantage. This page does not claim quantum computers can reliably predict prices, guarantee trading profits, or make a token valuable.

Definitions to keep handy

• Qubit: a unit of quantum information. Physical-qubit counts alone do not establish useful attack capability.
• CRQC / Q-day: shorthand for a quantum computer capable of a relevant cryptographic attack, and the point that capability is reached—not a known calendar date.
• PQC: cryptography designed to resist quantum attacks while running on conventional systems.
• ML-KEM: a standardized way to establish a shared secret; it is not a blockchain spending signature.
• ML-DSA / SLH-DSA / Falcon: different signature approaches. Check the exact standard, parameter set, implementation and supported use.
• Hybrid protection: combining classical and post-quantum components; its security depends on the exact construction.
• Quantum key distribution: a separate approach using quantum communication properties. It does not automatically replace wallet transaction signatures.

Terminology and algorithms: NIST PQC introduction and standards directory.

How this research page will be maintained

Last review: October 27, 2026. This is an editorial snapshot, not an automatically updating certification. Future revisions should record the source date, exact deployment or proposal, affected layer, limitations, and what changed. Official project statements are useful primary evidence but can contain marketing language; we narrow claims to what the evidence actually establishes.

Have a source or a question? Send a question or email crownandledger.com@gmail.com. Do not send account credentials, recovery phrases or private financial information.

Educational scope: David is not a financial adviser. This is general technology and financial education for New York and U.S. readers, not personalized investment, financial, tax or legal advice, a security audit, or a product endorsement. No return, immunity from loss or attack date is promised.