The short answer
Dogecoin and Litecoin both sign with ECDSA on secp256k1, inherited from Bitcoin, and neither has an adopted post-quantum plan. On Dogecoin the question was formally raised in its own issue tracker in June 2021 and closed without an implementation. As of August 2026 we found no dated commitment for either.
What we checked, and how
This piece makes a negative claim, and negative claims deserve more care than positive ones. We are not saying these chains have no post-quantum plan. We are saying something narrower and checkable: that on 12 August 2026, a review of each project's reference client repository, its issue tracker and its published materials did not turn up an adopted post-quantum proposal, an implementation, or a dated commitment to produce one.
That is a statement about what a careful search found on a particular day. If you can point us at something we missed, send it with the link and we will publish the correction, because being corrected in public is the job.
What these chains sign with
Both are Bitcoin derivatives, and both inherited its cryptography. Transactions are signed with ECDSA over secp256k1, the same curve and the same hard problem, and therefore the same exposure to Shor's algorithm.
They also inherited Bitcoin's better habit. An address is a hash of a public key, so a coin sitting in an address that has never been spent from has not published the key that protects it. That is a genuine buffer, and it is doing quiet work on every one of these chains.
What the buffer does not coverThe moment you spend, the public key is published and stays published. For anyone who has used the same address more than once, which is most people, the protective hash is already behind them.
Dogecoin: asked in 2021, closed without an answer
Dogecoin is the more interesting of the two, because the conversation is not absent. It is on the record and it went nowhere.
From Dogecoin's own issue tracker.
- An issue titled "Update Dogecoin to be Post Quantum Resistant" is opened on the Dogecoin Core repository, arguing that elliptic-curve cryptography will become vulnerable and proposing the adoption of a NIST competition finalist. The issue is now closed, with no implementation, no branch and no accompanying proposal. source
There have been later community discussions too. What there has not been is a maintainer-adopted design, a specification, or a date. Saying nobody has raised it would be wrong. Saying nobody has answered it is fair.
Litecoin: capable of changing, and not changing this
Litecoin is the harder case to be sympathetic about, because it has demonstrated the exact capability that would be needed. It designed, implemented and activated MWEB, a substantial consensus change, across a live network. Whatever you think of that feature, shipping it proves Litecoin can coordinate a soft fork when it decides something matters.
Applying that same capability to signatures is a decision nobody appears to have made. Our search found no post-quantum roadmap, improvement proposal or research programme specific to Litecoin.
This matters more than it does for a small chain precisely because Litecoin is not small. Capability without a decision is a different failure from lacking the capability at all, and it is the more frustrating one.
Where this leaves them
Neither chain is in danger this year. No quantum computer exists that can derive a private key from a published one, and the honest estimates for such a machine are still measured in years. The rating is about preparation, and the absence being measured here is an absence of published intent rather than an absence of time.
For context, here is the whole of that rung as it stands today, rendered live from the index. We have made the dated search described above for Dogecoin and Litecoin specifically. The others are rated on their own evidence, which you can read on each profile.
- DashDASHHardy 16.5ECDSA on secp256k1 for coins on Dash Core; BLS12-381 threshold signatures for masternode quorums, ChainLocks and InstantSend; RedPallas for spends in Dash Platform's shielded pool
- SonicSHardy 14.5ECDSA on secp256k1 for account transactions and for validator event signatures
- Terra ClassicLUNCHardy 14.5ECDSA on secp256k1 for accounts; Ed25519 for validator consensus keys
- Ethereum ClassicETCHardy 13.0ECDSA on secp256k1 for account transactions; proof of work for block production
- FlareFLRHardy 13.0ECDSA on secp256k1 for C-chain and P-chain transactions; validator block signatures with the staking certificate key (ECDSA on P-256 by default); ECDSA signatures from data providers to finalise Flare Systems Protocol results
- Internet ComputerICPHardy 13.0BLS for consensus, certification and randomness; threshold ECDSA over secp256k1 and threshold Schnorr over bip340secp256k1 and ed25519 for chain-key signatures; Ed25519 or ECDSA for user identities
- TONTONHardy 11.0Ed25519, verified inside wallet smart contracts
- DecredDCRHardy 10.5ECDSA on secp256k1 by default, with Ed25519 and EC-Schnorr-DCRv0 on secp256k1 available through OP_CHECKSIGALT; Schnorr signatures by Politeia keys for treasury spends; hybrid proof of work and proof of stake, with ticket votes signed like ordinary spends
- IOTAIOTAHardy 10.5Ed25519 (EdDSA over Curve25519) by default for layer-1 transactions; ECDSA over secp256k1 and secp256r1 also accepted
- LitecoinLTCHardy 10.5ECDSA on secp256k1, inherited from Bitcoin
- MidnightNIGHTHardy 10.5Schnorr over secp256k1 (BIP-340) for unshielded spends, including NIGHT on Midnight; shielded spends by Plonk proofs with KZG commitments over BLS12-381; sr25519 block authoring and Ed25519 GRANDPA finality for validators
- QtumQTUMHardy 10.5ECDSA on secp256k1 for spends and for proof-of-stake block signatures; Schnorr on secp256k1 for Taproot outputs since the 2022 hard fork
- KaiaKAIAHardy 10.0ECDSA on secp256k1 for every account key type and for validator committed seals; BLS12-381 signatures by block proposers for on-chain randomness
- VaultaAHardy 10.0ECDSA on secp256k1 (K1), ECDSA on P-256 (R1) or WebAuthn P-256 (WA) for account permissions; secp256k1 for block producer signatures; BLS12-381 for Savanna finalizer votes
- DogecoinDOGEHardy 9.0ECDSA on secp256k1, inherited from Bitcoin
- 0G0GHardy 8.5ECDSA on secp256k1 for accounts; BLS12-381 for validator consensus votes
- AIOZ NetworkAIOZHardy 8.5ECDSA on secp256k1 (eth_secp256k1, Ethereum-style keys) for accounts; Ed25519 for validator consensus keys
- Akash NetworkAKTHardy 8.5ECDSA on secp256k1 for accounts; Ed25519 for validator consensus keys
- ArweaveARHardy 8.5RSA-PSS with 4096-bit keys and SHA-256 by default for wallets and block signing; ECDSA on secp256k1 accepted for wallets and miners since the 2.9 hard fork
- AvalancheAVAXHardy 8.5ECDSA on secp256k1 across the C-Chain, X-Chain and P-Chain
- Bitcoin SVBSVHardy 8.5ECDSA on secp256k1 for transactions; proof of work for block production
- CelestiaTIAHardy 8.5ECDSA on secp256k1 for accounts; Ed25519 for validator consensus keys
- Chiliz ChainCHZHardy 8.5ECDSA on secp256k1 for accounts and validator block seals; P-256 verification available to contracts
- ConfluxCFXHardy 8.5ECDSA on secp256k1 for Core Space and eSpace accounts; BLS12-381 for proof-of-stake finality votes; ECVRF on secp256k1 for committee election; secp256r1 verification available to contracts
- dYdX ChainDYDXHardy 8.5ECDSA on secp256k1 for accounts and permissioned keys; Ed25519 for validator consensus keys
- eCashXECHardy 8.5ECDSA and Schnorr on secp256k1 for spends; Schnorr on secp256k1 for Avalanche stake proofs, delegations and votes; proof of work for block production
- FilecoinFILHardy 8.5ECDSA on secp256k1 for f1 and Ethereum-compatible f410 accounts; BLS on BLS12-381 for f3 accounts, block signatures by storage providers' worker keys and F3 finality votes
- GateChainGTHardy 8.5Ed25519 for native and vault accounts; ECDSA on secp256k1 for EVM accounts; an elliptic-curve VRF for committee selection
- Gnosis ChainGNOHardy 8.5ECDSA on secp256k1 for accounts; BLS12-381 for beacon chain validators; P-256 verification available to contracts since Fusaka
- InjectiveINJHardy 8.5ECDSA on secp256k1 (eth_secp256k1, Ethereum-style addresses) for accounts and validator operators; Ed25519 for validator consensus keys
- KCC (KuCoin Community Chain)KCSHardy 8.5ECDSA on secp256k1 for accounts and validator block seals
- KiteKITEHardy 8.5ECDSA on secp256k1 for accounts; BLS12-381 keys registered for each validator on the Avalanche P-Chain
- Mina ProtocolMINAHardy 8.5Schnorr signatures over the Pallas curve for accounts; a Pallas-based VRF for block-producer election; Kimchi proofs with Pickles recursion over the Pasta curves for the succinct chain and zkApps
- MultiversXEGLDHardy 8.5Ed25519 for account and guardian signatures; BLS multisignatures on BLS12-381 for validator consensus
- Polygon PoSPOLHardy 8.5ECDSA on secp256k1 for accounts, Bor block seals, Heimdall validator consensus and checkpoint signatures; P-256 verification available to contracts
- Provenance BlockchainHASHHardy 8.5ECDSA on secp256k1 for accounts; Ed25519 for validator consensus keys
- Theta NetworkTHETAHardy 8.5ECDSA on secp256k1 for accounts, native and EVM transactions, and enterprise validator votes; BLS on BLS12-381 for aggregated guardian votes
- THORChainRUNEHardy 8.5ECDSA on secp256k1 for RUNE accounts; Ed25519 for CometBFT validator consensus; GG20 threshold ECDSA (secp256k1) and threshold EdDSA (Ed25519) for the Asgard vaults that hold assets on other chains
- VeChainVETHardy 8.5ECDSA on secp256k1 for transactions and VIP-191 gas-payer co-signatures; secp256k1 block-header signatures with an ECVRF proof for the VIP-214 random beacon
- WEMIXWEMIXHardy 8.5ECDSA on secp256k1 for account transactions and fee-payer signatures, and for block producers' header signatures
- WhitechainWBTHardy 8.5ECDSA on secp256k1 for account transactions and for Clique block seals
- BeldexBDXHardy 7.5CLSAG linkable ring signatures, stealth addresses and Bulletproofs+ over the Ed25519 group, inherited from Monero; Curve25519 and Ed25519 keys for master nodes
- Ozone ChainOZOHardy 7.5ECDSA on secp256k1 for accounts and for QBFT validator signatures, through stock Hyperledger Besu
- CronosCROHardy 7.0ECDSA on secp256k1 for EVM accounts, Cosmos SDK secp256k1 for native accounts, Ed25519 for validator consensus identities
- MemeCoreMHardy 7.0ECDSA on secp256k1, inherited from Ethereum Virtual Machine compatibility
- HyperliquidHYPEHardy 5.5ECDSA on secp256k1, via EIP-712 typed-data signing
What this means if you hold either
Nothing to do today, and one thing to watch for. The signal that would change this rating is not a price move or an announcement about adoption. It is a specification: a named scheme, a proposal number and a date.
Until one of those exists, the useful posture is the boring one. Assume the address you have spent from has a public key on the record, prefer fresh addresses where your wallet makes that easy, and treat any claim that these chains are quantum-safe as something to check rather than something to accept. On the evidence we can find, they are not, and nobody involved is currently saying otherwise.
Where to go next
- Dogecoin: the full rating Every dimension score, with the source behind each one, and what the rating means if you hold it.
- Litecoin: the full rating Every dimension score, with the source behind each one, and what the rating means if you hold it.
- Is my crypto safe from quantum computers? If you have seen the scary headlines about quantum computers and crypto, here is the calm version. What is true, what it means for the coins you hold, and what is worth doing about it.
- How to protect your crypto from quantum computers If you hold crypto and the quantum headlines have been bothering you, this is the practical version. Four steps, in order, with the limits of each one stated.
Sources
Every dated event above carries its own primary source. These are those sources, each checked on the date shown.
- Update Dogecoin to be Post Quantum Resistant (issue 2241) Dogecoin Core · primary · checked 12 August 2026
- Dogecoin Core reference client Dogecoin Core · primary · checked 12 August 2026
- Litecoin Core reference client Litecoin Project · primary · checked 12 August 2026
- BIP-360: Pay-to-Merkle-Root (P2MR) Bitcoin Improvement Proposals · primary · checked 12 August 2026
This is a security-readiness assessment, not investment advice.