Hardy Index Quantum readiness, rated and tracked

Changelog

Changelog

Every score change, methodology revision and correction, newest first. A benchmark that cannot show what it changed and why is an opinion with a number attached.

  1. Development

    Bittensor release 487 bundled ML-DSA-65 and Falcon wallet code, disabled by default

    On 5 November 2026 the RaoFoundation subtensor repository opened release pull request 3294, which carries PR 3220: ML-DSA-65, Falcon-512 and Falcon-1024 wallets plus optional rotating accounts for sr25519 and ed25519, integrated with transfers, staking, proxies, multisig, EVM calls, the Python SDK and the CLI. The code ships switched off: post-quantum and hashed-account authorisation is controlled by a sudo flag that defaults to disabled, so no TAO is protected by a post-quantum key and existing sr25519 coldkeys and hotkeys are unchanged. The release notes state plainly that hashing and rotation do not make classical signatures quantum-resistant, and they name no activation date, no single chosen scheme and no migration route for existing accounts. For the rating to move, Bittensor would need the flag enabled on mainnet so ordinary holders can hold TAO under a post-quantum key, plus a published, dated route off sr25519 and independent cryptographic review of the implementation.

    Bittensor source ↗

  2. Development

    Bittensor runtime 488 release included quantum-resistant wallet code

    On 5 November 2026 the RaoFoundation subtensor repository published runtime release v488, whose changelog lists pull requests 3291 and 3294 carrying "Quantum Resistant Wallets" out of the integration branch where the ML-DSA-65 implementation was merged in October. The release notes do not say the feature is switched on: the underlying work was merged as a disabled candidate with its switches defaulting to off and independent cryptographic review still required, and no activation date or route for existing sr25519 coldkeys has been published. Funds on Bittensor are still protected by sr25519 alone. For the rating to move, the chain would need to show the post-quantum account type enabled on mainnet and usable by ordinary holders, together with a published migration route for existing accounts.

    Bittensor source ↗

  3. Development

    Akash governance approved the migration of the Akash protocol to Solana

    Proposal 346 passed on akashnet-2 on 2 November 2026 with about 97 per cent of votes cast in favour. It approves moving Akash from its sovereign Cosmos chain to Solana under AEP-79, and launching AKT as a Solana token through a one-way migration portal, open for two years, once the token and portal audits are complete. It sets no cutover date: leases, staking and governance continue on akashnet-2 until a separate cutover proposal passes. Akash stays in the index while it runs its own consensus, and its rating is unchanged, because neither the chain it runs today nor the destination keys it describes use post-quantum signatures. When the cutover takes effect, Akash leaves the index's scope and the removal will be logged here.

    Akash Network source ↗

  4. Score change

    Bittensor: tier 5 to 4, after ML-DSA-65 wallet code reached its own repository

    On 18 October 2026 an ML-DSA-65 wallet implementation was merged into the codex/hashed-accounts integration branch of RaoFoundation/subtensor, the Bittensor node. Its description calls it a disabled protocol candidate, not production activation, and says independent cryptographic review is required before it is switched on. That is post-quantum work on the chain's own signatures documented by people with authority over it, which meets Tier 4, Debating. It goes no further: the code is not on the main branch, protects no funds, and has no activation date or route for existing accounts.

    Three dimensions move with the evidence. Deployment rises from 1 to 2 with the tier. NIST alignment rises from 0 to 5, because the one candidate is a specific parameter set of the final FIPS 204 standard, the same placement Cosmos Hub receives for ML-DSA-65 code that has not been selected for activation. Verification rises from 2 to 3, the floor of the band for a merged implementation nobody outside the authoring team has reviewed. Signature, migration and exposure are unchanged. The Hardy Score rises from 8.5 to 19.

    Bittensor source ↗

  5. Development

    NEAR shipped nearcore 2.14.0 with on-chain ML-DSA-65 verification for contracts

    nearcore 2.14.0, released on 26 October 2026, added an ml_dsa_verify host function so smart contracts can verify FIPS 204 ML-DSA-65 signatures on-chain, added SHA-3 digest host functions, stabilised universal accounts under a single post-quantum-safe derivation, and corrected how ML-DSA-65 gas keys are priced. It does not make post-quantum keys mandatory: Ed25519 and secp256k1 remain valid account schemes and no sunset date for them has been published, so accounts that have not rotated are still protected by classical signatures. It also adds no independent review of NEAR's ML-DSA integration, which remains reviewed only by the nearcore maintainers. A published deprecation schedule for classical account keys, or a named external audit of the ML-DSA code, is what would move the rating.

    NEAR Protocol source ↗

  6. Development

    Draft EIP 8425 filed proposing quantum freeze and recovery for unmigrated Ethereum accounts

    A pull request opened against the ethereum/EIPs repository on 24 October 2026 adds a draft EIP, numbered 8425, setting out a minimal framework for freezing legacy ECDSA authorisation and recovering accounts that have not moved to post-quantum keys. It follows a community thread on Ethereum Magicians and is unmerged, unnumbered in the official index and unadopted by core developers. It does not deploy anything, does not commit Ethereum to freezing any account, and does not change the signature scheme protecting funds on mainnet. For the rating to move, this or a successor proposal would have to be accepted by the EIP process and scheduled into a named network upgrade, or a post-quantum account type would have to go live on mainnet.

    Ethereum source ↗

  7. Development

    Draft EIP filed to add a post-quantum validator key registry to Ethereum's beacon state

    On 21 October 2026 a draft Core EIP, numbered 8450, was opened against the ethereum/EIPs repository proposing that each validator register a two-layer leanXMSS public key over Keccak-256 in the beacon state, authorised by its BLS signing key or its withdrawal address and carrying a proof of possession. The registered keys would stay dormant, with a later fork switching validator duties to them and the registered stake acting as a readiness signal. It does not deploy anything: the EIP is unmerged, its leanXMSS parameters depend on an unmerged branch of the leanVM specification, no discussion thread is open, and account signatures protecting user funds are untouched. The rating would move when a post-quantum signature is live and usable on Ethereum mainnet, not when a draft is filed or scheduled.

    Ethereum source ↗

  8. Coverage

    The scale re-check adds four layer 1s

    The first re-check of the seventy-five under the monthly rule. Counting every in-scope layer 1 by market capitalisation, including chains that market-data sites leave out of their layer-1 lists, found four that were not rated, each checked against the methodology by a reviewer that did not write it. All sit in Exposed: Terra Classic 14.5, GateChain 8.5, KCC (KuCoin Community Chain) 8.5, Whitechain 8.5.

    Three are run by or for exchanges, which the index rates on the same footing as BNB Chain and Cronos when they run their own consensus. Each profile says who controls block production: a single signer on Whitechain, a concentrated set of nodes on GateChain, and an admin contract over validator admission on KCC. Whitechain has said it will become a layer 2 this autumn; it is rated while it runs its own consensus and leaves the index when that stops. Terra Classic has a post-quantum roadmap posted by a core contributor for discussion, which names ML-DSA but has not been put to governance, so it stays in Exposed.

    Kava, Dusk and ZetaChain, which a narrower list had suggested, rank just outside the seventy-five once all layer 1s are counted, and are watched for the next re-check on 1 November.

    Terra Classic GateChain KCC (KuCoin Community Chain) Whitechain source ↗

  9. Coverage

    The scale test is re-checked on the first of each month

    The seventy-five largest layer 1s are now re-checked on the first of each month, against that day's market capitalisations, rather than whenever the index updates. Any new entrant that passes is added. A chain admitted on scale stays in, and is removed only if it falls outside the hundred largest layer 1s and meets neither the position test nor the deployment test. The aim is a list that does not churn with daily price moves. The rule is published on the about page.

    This changes no score. Separately, the guides now apply a track-record rule: they name a chain as the leader, or as a place to move funds, only once it has run on mainnet for twelve months. Every profile now records when its current mainnet began, and newer chains appear in every ranking with their age shown. The ranking itself is the rubric's and is unaffected.

    source ↗

  10. Coverage

    Five post-quantum chains from outside the seventy-five added; Arc held back

    Five chains that rank outside the seventy-five largest layer 1s join on the deployment test, because each has a post-quantum signature running on its mainnet. We checked each chain was live and read its signatures from mainnet transactions before drafting, and a reviewer that did not write the profiles checked each against the methodology. Size plays no part in a Hardy Score.

    In Native: Quantus Network 94.0, Dilithion 93.5, Tidecoin 89.0. In Shipping: QoreChain 84.5, Nexus 73.0.

    Two of the five now rate above QRL, and both are young. Quantus began producing blocks on 9 September 2026 and Dilithion's current chain on 28 January 2026, after a reset that invalidated the coins of an earlier soft launch. Their profiles say so, and say what holds their scores down: on Quantus, an audit of an earlier revision of its ML-DSA library and only a draft review of the zero-knowledge path that carries most new coins; on Dilithion, no outside review at all. Both give a small group strong control: ten members seeded at genesis govern Quantus, and Dilithion's own seed nodes admit new miners.

    Nexus accepts Falcon-512 on mainnet, but defaults every account to Brainpool ECDSA, and its "Quantum Resistant" headline describes a classical curve, so it carries the "Claims unverified" flag. QoreChain requires an ML-DSA-87 signature on every transfer, but about half its supply sits in accounts that can still register a post-quantum key with a classical signature alone, which keeps it in Shipping. The registry gains ECDSA on brainpoolP512t1 and on sect571r1, both used by Nexus.

    Arc, Circle's layer 1, is held back. A precompile that verifies SLH-DSA-SHA2-128s signatures is live on its mainnet, which rules out the rungs for chains with nothing post-quantum live, but no released software lets a holder put coins behind it, which rules out Shipping. It is listed on the about page with the reason, and its post-quantum roadmap page is watched.

    Quantus Network Dilithion Tidecoin QoreChain Nexus source ↗

  11. Correction

    Scope correction: Qubic removed, because it has published no post-quantum position

    Qubic was added on 22 October under the position test, on the understanding that it markets a quantum-resistance claim. It does not. Qubic ranks outside the seventy-five largest layer 1s, so the position test was its only route in, and that test needs a position the chain itself has published: a claim to be quantum-safe, a roadmap, an improvement proposal or a funded research programme. Qubic's own article on quantum threats says its documentation makes no post-quantum claim. The quantum-resistant label it carries comes from market aggregators and from a third-party article reposted on its press page, and neither is Qubic's position, by the same rule that keeps a vendor's announcement out of a chain's plan.

    The row is removed rather than rescored. Our assessment stands: Qubic signs with SchnorrQ on the FourQ curve, which Shor's algorithm breaks. It is listed on the about page as assessed and out of scope, and the draft is kept so it can return if Qubic publishes a position or enters the seventy-five.

    Qubic source ↗

  12. Correction

    Polkadot and Bittensor: exposure 3 to 2, the score every address-is-the-key chain receives

    A Polkadot or Bittensor address is an SS58 encoding of the public key itself, so every account's key is readable from its address before it ever signs. The rubric's bottom exposure band, 0 to 2, covers chains where public keys are exposed for effectively all accounts, and Solana, Kaspa, Stellar, Algorand, Hedera, MultiversX and Mina, whose addresses are also the key, all score 2. Polkadot and Bittensor were placed at 3, the floor of the band above, on the ground that no measured share of exposed supply had been published. That misplaced them: the band is met on structure alone, and Polkadot's own note already described the structural position in the bottom band's terms.

    Both move to 2. Polkadot's Hardy Score falls from 37.5 to 36.5 and Bittensor's from 9.5 to 8.5. No tier changes.

    Polkadot Bittensor source ↗

  13. Coverage

    Coverage widened to the seventy-five largest layer 1s: twelve more chains added

    The fourth batch under the seventy-five scale test, each profile checked against the methodology by a reviewer that did not write it. All twelve sit in Exposed: Qtum 10.5, Vaulta 10.0, 0G 8.5, AIOZ Network 8.5, Chiliz Chain 8.5, dYdX Chain 8.5, eCash 8.5, Mina Protocol 8.5, MultiversX 8.5, Qubic 8.5, WEMIX 8.5, Ozone Chain 7.5.

    Ozone Chain markets itself as a quantum-resistant blockchain, but its mainnet runs an unmodified Hyperledger Besu client that signs with ECDSA on secp256k1; its quantum features are random-number generation and planned encryption between nodes, neither of which protects funds. It is placed on the rung its live signature supports and carries the "Claims unverified" flag. Qubic signs with SchnorrQ on the FourQ curve, which Shor's algorithm breaks. It is labelled quantum-resistant by market aggregators, but its own documentation makes no post-quantum claim, so it does not carry the flag.

    The cryptography registry gains two schemes: Schnorr signatures on the Pallas curve, which Mina uses, and SchnorrQ on FourQ, which Qubic uses. Several of the twelve give one key or a small group control over minting, fees, contracts or the validator set, and each profile says where.

    Qtum Vaulta 0G AIOZ Network Chiliz Chain dYdX Chain eCash Mina Protocol MultiversX Qubic WEMIX Ozone Chain source ↗

  14. Methodology

    Clarification to v1.8: what the "Claims unverified" flag says

    The flag's definition said we could not confirm a flagged chain's deployed scheme against a primary source. That misdescribed the case it exists for, which the methodology already sets out: a chain that markets itself as quantum-safe, whose live scheme is confirmably still vulnerable. In that case the deployed scheme is confirmed; what no primary source confirms is the post-quantum claim. The definition now reads: "This chain markets itself as quantum-safe, but no primary source confirms a post-quantum scheme protecting its funds."

    This is a clarification, not a change: it moves no score and no tier. The flag still requires the chain itself to market a quantum-safe claim, so a chain labelled quantum-resistant only by third parties does not carry it. Ozone Chain, added the same day, carries it.

    source ↗

  15. Coverage

    Coverage widened to the seventy-five largest layer 1s: ten more chains added

    The third batch under the seventy-five scale test, each profile checked against the methodology by a reviewer that did not write it. All ten sit in Exposed: Decred 10.5, Kaia 10.0, Akash Network 8.5, Arweave 8.5, Bitcoin SV 8.5, Conflux 8.5, Gnosis Chain 8.5, Kite 8.5, Theta Network 8.5, THORChain 8.5.

    None of the ten has a post-quantum signature live on mainnet or a plan from its own authority. Where something nearby exists, the profile says so and why it does not move the tier. BTQ Technologies has announced a commercial agreement with the Kaia DLT Foundation that names no scheme and leaves holders' signatures unchanged. Decred's mixing uses a post-quantum key exchange, which protects privacy rather than funds. Theta's chief technology officer co-wrote research on the cost of attacking secp256k1, which sets no plan for Theta. Bitcoin SV has an application-level notarisation standard offering ML-DSA, which does not sign spends.

    Arweave signs with RSA by default, so the cryptography registry gains an RSA-PSS entry: Shor's algorithm breaks it as it breaks elliptic curves. Two chains have voted or planned to stop running their own consensus: GnosisDAO approved turning Gnosis Chain into a rollup, and Akash's roadmap aims to leave its own chain by the end of 2026. Both still run their own consensus today, so both are rated, and each leaves the index's scope when that changes. Kite is rated as a layer 1 because it runs its own validator set as an Avalanche L1.

    Decred Kaia Akash Network Arweave Bitcoin SV Conflux Gnosis Chain Kite Theta Network THORChain source ↗

  16. Correction

    Bitcoin and Bitcoin Cash: Glassnode's 1.92 million BTC is not a pay-to-public-key count

    Both profiles described Glassnode's figure of 1.92 million BTC of structural exposure as coins in pay-to-public-key outputs. Glassnode's own definition is wider: early pay-to-public-key outputs, plus legacy bare multisig and Taproot outputs. The Bitcoin profile now says so. The Bitcoin Cash profile had used the figure as a count of the pay-to-public-key coins it inherits, which overstated what Glassnode measured and included Taproot outputs, which never existed on Bitcoin Cash; it now rests on Deloitte's count of about 2 million pay-to-public-key coins.

    Neither exposure score moves: both rest on the share of supply with a visible key, which the corrected wording does not change.

    Bitcoin Bitcoin Cash source ↗

  17. Methodology

    Clarification to v1.8: "publicly available tools" means released software

    Methodology v1.8's definition of "usable by ordinary holders" asks that a holder can put their own coins behind the post-quantum signature with publicly available tools. The definition now says what that means: released software a holder can install, a published release or package, not code that is unmerged or unreleased.

    This writes down a reading the index already applies. Pearl is held back on it: its XMSS spend path is live on mainnet, but the wallet code that signs those spends is an open pull request, not a release. It is a clarification, not a change: it moves no score and no tier.

    source ↗

  18. Coverage

    Coverage widened to the seventy-five largest layer 1s: ten more chains added

    The second batch under the seventy-five scale test, each profile checked against the methodology by a reviewer that did not write it. All ten sit in Exposed: Dash 16.5, Flare 13.0, Midnight 10.5, Celestia 8.5, Filecoin 8.5, Injective 8.5, Polygon PoS 8.5, Provenance Blockchain 8.5, VeChain 8.5, Beldex 7.5.

    None of the ten has a post-quantum signature live on mainnet or a plan from its own authority. Where something nearby exists, the profile says so and says why it does not move the tier. Flare Research published a 2022 paper proposing hybrid Dilithium signatures for EVM chains, never adopted for Flare. A Dash organisation document names ML-DSA and SLH-DSA for its Platform shielded pool, deferred to 2035 or later. Injective has said on X that quantum resistance is in development, without naming a scheme, a proposal or a date. Midnight has a problem statement asking that a future light-client design be quantum-secure. Celestia closed an ML-DSA pull request that concerned other chains' validator keys, not its own.

    Polygon PoS is rated as a layer 1: its own validators run its consensus, and Ethereum checkpoints do not validate its state. Midnight's row covers Midnight's own ledger, though most NIGHT is still held on Cardano. Pearl joins the held-back list: its XMSS spend path is live on mainnet, but no released software lets a holder use it, and the index is watching the pull request that would.

    Dash Flare Midnight Celestia Filecoin Injective Polygon PoS Provenance Blockchain VeChain Beldex source ↗

  19. Correction

    Aptos: AIP-137 is accepted, not proposed; and NIST alignment of 9 needs the scheme in use on mainnet

    Aptos. The profile described AIP-137, which adds SLH-DSA-SHA2-128s accounts, as a proposal awaiting adoption. It was accepted on 7 April 2026, after its last call, and its implementation is merged into aptos-core and enabled on devnet, though not on testnet or mainnet, and no mainnet date has been published. That is an adopted improvement proposal by the core team naming the scheme, so Aptos stays in Committed, and its caveat now says why. Existing accounts can rotate to an SLH-DSA key in place, keeping their address, so migration rises from 6 to 7.

    NIST alignment. The 9 to 10 band is for a scheme in use that a final NIST standard covers; a final-standard scheme named but not yet deployed belongs in 6 to 8, which is where Stellar and Hedera already sit. Four profiles scored 9 for a scheme that is not in use on mainnet: Aptos, with SLH-DSA enabled on devnet only; Sui, whose ML-DSA-65 is not yet deployed; the XRP Ledger, with ML-DSA on AlphaNet; and Tezos, with ML-DSA-44 built into the protocol but switched off on mainnet. Each moves to 8. Taken with the migration rise, the Aptos score is unchanged at 39.0; Sui moves from 43.5 to 42.0, the XRP Ledger from 44.5 to 43.0 and Tezos from 39.0 to 37.5. No tier changes.

    Aptos Sui XRP Ledger Tezos source ↗

  20. Coverage

    Coverage widened to the seventy-five largest layer 1s: the first nine chains added

    The scale test now covers the seventy-five largest layer 1s by market capitalisation rather than twenty-five. Applied against live market caps, it brings 41 chains into scope that the index did not rate, plus Qubic under the position test. They are being added in batches of ten, each profile checked against the methodology by a reviewer that did not write it.

    The first nine, chosen because each has published something about the quantum threat or sits at the top of the new range: Tezos 39.0 (Committed), Sei 24.5 (Debating), Cosmos Hub 23.5 (Debating), Kaspa 20.5 (Debating), Monad 20.0 (Debating), XDC Network 20.0 (Debating), Neo 17.0 (Debating), Sonic 14.5 (Exposed), Ethereum Classic 13.0 (Exposed). A tenth, Pearl, is held back while one question about its post-quantum wallet is settled.

    Tezos has ML-DSA-44 accounts built into the protocol mainnet runs, switched off there. Sei, Monad, Kaspa and Neo each have a draft proposal or an open research item, XDC has an unmerged Falcon branch written by a core contributor, and Cosmos Hub runs a framework whose current release adds ML-DSA-65 keys the Hub has not yet adopted. Sonic and Ethereum Classic have named schemes only in a blog post and an outside draft, which is why they sit in Exposed.

    The about page also gains a scope line on Polkadot parachains, which are excluded because Polkadot's validators finalise their blocks, and five more chains held back because their deployed schemes could not be confirmed from a primary source: Pi Network, Stable, Plasma, Onyxcoin and Ultima.

    Tezos Sei Cosmos Hub Kaspa Monad XDC Network Neo Sonic Ethereum Classic source ↗

  21. Development

    Sui testnet release registered ML-DSA-65 as a signature scheme in RPC and SDK

    Mysten Labs published testnet-v1.82.2 on 20 October 2026, adding SignatureScheme::MLDSA65 = 7 so that ML-DSA-65 signatures and multisig members can be submitted through ExecuteTransaction and checked by VerifySignature, with matching GraphQL types and a Rust SDK bump. This is client and interface plumbing on the testnet release line: it does not put post-quantum account authentication on mainnet, and it does not show ML-DSA-65 accounts enabled for ordinary users on the public test network. The rating would move when ML-DSA-65 accounts are enabled by protocol flag on a persistent public network and usable by holders, and further when the scheme reaches mainnet or draws independent review outside Mysten Labs.

    Sui source ↗

  22. Methodology

    Methodology v1.8: verification and NIST alignment re-anchored to the signatures that protect funds

    Methodology v1.8 is in force from 21 October 2026, and every score on the site is now calculated under it. It also ends the 30-day notice period v1.7 introduced: a change to the rubric now takes effect when it is published, with every chain's score either side recorded in the changelog the same day.

    Four changes. The Shipping and Committed tiers are reworded so that each tests what it is named for: Shipping no longer also asks for a migration, which the migration dimension already scores, and Committed asks for a plan from the chain's own authority naming a post-quantum scheme or a funded programme to select one, rather than for public dates, which the commitments tracker records. No chain changes tier. Solana's caveat about migration goes, because its placement no longer contradicts the definition; a narrower judgement call stays, because its post-quantum wallet is reached through a command-line tool rather than a mainstream wallet. Usable by ordinary holders means any holder can put their own coins behind the signature with publicly available tools, a command-line tool included.

    Verification is re-anchored to the post-quantum component that protects funds, so the openness of classical code no longer earns it, and a chain with no such component sits in the bottom band. Public review means review by people outside the team that wrote the component. NIST alignment counts only schemes a chain has deployed, tested or proposed for its own fund-protecting signatures, so a scheme in an identity layer no longer scores. And a chain that shares another chain's history inherits the published measurements of that history until it has its own.

    28 of 31 chains move, 27 down and one up. The largest move is IOTA, whose post-quantum schemes sit in its identity layer and no longer count on either dimension. Bitcoin Cash moves from 66.0 to 62.0 on inherited exposure. Zcash's ZIP 2005 is counted as preparation for a post-quantum recovery protocol that is not yet specified, not as a post-quantum component. Nervos CKB moves up, its post-quantum component being independently audited and checkable on mainnet. Every chain's score and rank before and after, with the reason, is on the v1.8 page.

    Mochimo Abelian NEAR Protocol Algorand Nervos CKB Bitcoin Cash XRP Ledger Sui Hedera Stellar Zcash Aptos Polkadot Ethereum Cardano BNB Chain Monero IOTA Bitcoin Internet Computer TON Litecoin Bittensor Dogecoin Avalanche Cronos MemeCore Hyperliquid source ↗

  23. Score change

    Methodology v1.8 rescores 28 chains, no tier changes

    The scores below are the ones methodology v1.8 produces, recorded either side for every chain that moved. 27 of the 28 go down and none changes tier.

    The changes: verification now credits only the post-quantum component that protects funds, not the openness of the classical code; NIST alignment scores only schemes a chain has deployed, tested or proposed for its own fund-protecting signatures; and a chain that shares another chain's history inherits the published measurements of that history until it has its own. Every chain's before and after, with the reason, is on the v1.8 page.

    Mochimo Abelian NEAR Protocol Algorand Nervos CKB Bitcoin Cash Sui XRP Ledger Hedera Stellar Zcash Aptos Polkadot Ethereum Cardano BNB Chain Monero IOTA Bitcoin Internet Computer TON Litecoin Bittensor Dogecoin Avalanche Cronos MemeCore Hyperliquid source ↗

  24. Methodology

    Clarification to v1.8: what "usable by ordinary holders" means

    Methodology v1.8's Shipping rung asks for a post-quantum signature live on mainnet and usable by ordinary holders. That phrase has a published meaning: any holder can put their own coins behind the post-quantum signature on mainnet today, with publicly available tools and without anyone's permission. A command-line tool or an SDK counts, and support in a mainstream wallet is not required. Where a placement rests on tools that demanding, the profile says so as a judgement call.

    This is a clarification, not a change: it moves no score and no tier. Solana's profile carries the judgement call it describes.

    source ↗

  25. Correction

    Solana re-cited to Winterwallet, QRL's audits recorded, XRP's partner is not a reviewer, and two dates corrected

    Research for methodology v1.8 found five statements in current profiles that the primary sources contradict. Corrections of fact take effect immediately, in either direction.

    Solana. The profile cited the Blueshift Winternitz Vault as the post-quantum program live on mainnet. That program is not deployed on mainnet: we queried it on 21 October and the account does not exist. Its successor, Blueshift's Winterwallet, is live, an executable program with 23 transactions since its first on 27 April 2026, and any holder can use it through an open-source command-line tool and SDKs. So Solana's Shipping placement and its signature score stand, now cited to Winterwallet, and the unsourced figure of fewer than 300 users is replaced by the on-chain count. Its verification score falls from 8 to 5: Winterwallet's own README says it has not been audited, its code has been reviewed only by its authors, and Google's 2026 citation was of the earlier design rather than of the code now holding funds.

    QRL. The profile said QRL 2.0's external audits had not concluded. Trail of Bits completed its audit of the Go library carrying XMSS and ML-DSA-87 in 2026, with every finding resolved, and the XMSS code mainnet runs was audited by X41 D-Sec in 2018. Verification rises from 8 to 9.

    XRP Ledger. The profile treated Project Eleven's involvement as close to a third-party audit. Ripple's own description is of a partner building the proof of concept, and the code changes in Project Eleven's fork are approved inside its own organisation. Nobody outside the authors has reviewed the post-quantum code. Verification falls from 8 to 5.

    Nervos CKB. The SPHINCS+ lock script was deployed on mainnet on 13 January 2026, not in 2025, and ScaleBit's audit was completed before deployment, not after. No score moves.

    Ethereum. The post-quantum validator signatures have run in four versioned interoperability devnets, from October 2025 to March 2026, with weekly coordination calls. The profile called them weekly devnets. No score moves.

    Solana Quantum Resistant Ledger XRP Ledger Nervos CKB Ethereum source ↗

  26. Correction

    Corrections to Bitcoin Cash, Bitcoin, Algorand, IOTA and the XRP Ledger, and what "reviewed" means

    An outside review of the index found errors that needed no change to the rubric. None of them moves a score.

    Bitcoin Cash. The profile, its coverage entry and its news story said the gap between Bitcoin Cash and Bitcoin was fifteen points. It is 7.5. The arithmetic was done on raw criterion scores before weighting.

    Bitcoin. The say-do record has been withdrawn. Two of its entries did not meet the rules it is published under: one recorded a statement by BTQ, a third party, as if it were a commitment by Bitcoin, and one marked the merge of BIP-360 as a draft as "Shipped", when shipped means the named thing is live on mainnet. Without them the record has two entries, and the rubric publishes a record only when it has at least three, so none is shown. The summary now says that between a quarter and a third of supply sits in addresses with exposed public keys, which is the range its sources support. The cryptography registry cited BIP-360 as evidence for Bitcoin's current schemes; it now cites the libsecp256k1 source for ECDSA and BIP-340 for Schnorr.

    Algorand. Native Falcon-1024 accounts shipped on 22 August. On 18 June, before that, Algorand's post-quantum roadmap said native post-quantum accounts would arrive in the Q3 2026 protocol release. The roadmap entry now cites that post, as archived the day it was published, so the say-do record shows the target delivered on time. The same post sets two more targets the tracker was missing, native Falcon-512 support and native multisig across signature schemes, both by the end of 2026, and both are now open targets. The 19 October correction said multisig had no published date, which was wrong, and removed a claim that stakers would be able to stake from post-quantum accounts on the ground that the source did not mention it. The claim was supportable: the Foundation's press release of 18 June makes it. It had been cited to the wrong page, and it is restored with the press release as its source. Two Algorand blog posts cited in a news story were labelled secondary; they are Algorand's own announcements and are now labelled primary.

    IOTA. The profile described the network IOTA ran before May 2025. On 5 May 2025 the Rebased upgrade replaced IOTA's layer 1 with a Move-based object ledger built on Sui's protocol, and shut the old Stardust mainnet down as it began. The profile now describes the current network and cites its current documentation in place of the Chrysalis-era specification. Rebased signs with Ed25519 by default and also accepts ECDSA over secp256k1 and secp256r1, which the cryptography registry now records as account options; none is post-quantum, and because Ed25519 stays the default the shared-exposure counts do not change. The migration reasoning now rests on Rebased, a network-wide protocol replacement in 2025, rather than on Chrysalis. The tier stays Exposed, and the two IOTA news posts carry correction notes.

    XRP Ledger. The past-due H1 2026 target now says what it promised, an impact assessment, experiments and the Project Eleven proof of concept, and what we could not find: as of 21 October no published assessment or benchmark results.

    The word "reviewed" on profiles was doing two jobs. The daily check confirms that every citation still resolves; it does not re-read the profile. Profiles now show "Sources checked" for that and "Last editorial review" for the date the profile was last read and changed, and the status page says the same. The homepage no longer counts a chain twice when it uses both of the two most common curves. The footer and the About page now give the publisher's registered name, number, place of registration and registered office.

    Bitcoin Cash Bitcoin Algorand IOTA XRP Ledger

  27. Methodology

    Methodology v1.7: evidence grades, coins that never migrate, and how disputes and rule changes work

    Three additions, none of which changes a score or a weight.

    Every entry in the cryptography registry now says what kind of source stands behind it, strongest first: read on-chain, source code or a release, a specification or proposal, or a statement or write-up. How far a scheme is deployed and how well that is evidenced are separate facts. Of the 72 entries on the first pass, one is read on-chain, 15 rest on source code or a release, 23 on a specification or proposal and 33 on a statement or write-up, which shows plainly where the record needs stronger evidence.

    Each profile now records the chain's stated policy on coins whose holders never move them to post-quantum keys. Zcash is the only chain with an adopted mechanism. Six have a formal proposal: Bitcoin, Stellar and Tron would sunset legacy signatures, and Cardano, Polkadot and the XRP Ledger propose a way to recover coins with a post-quantum proof. Twenty-one have no stated policy, and QRL, Mochimo and Abelian are not applicable because they have used post-quantum signatures from the start. No approach is marked better than another.

    The methodology now states how a rating is disputed and how the rules change. Anyone, including a chain, can send a primary source that contradicts a rating; while it is checked the profile carries an Under review label and the rating stands, and the check closes with a changelog entry whatever it finds. A change to the rubric that would lower any chain's score is published at least 30 days before it takes effect. Every revision of the rubric is listed on the methodology page, separately from score changes.

    source ↗

  28. Methodology

    Methodology v1.6: a cryptography registry, published beside the score

    Every profile now records the cryptography a chain uses as entries in a shared registry, not only as prose: the scheme, what it is used for, and how far it is deployed, from mandatory on mainnet down to proposed. Each scheme is recorded once, with its standard and whether Shor's algorithm breaks it. No score changes and no weight changes. The signature dimension is still scored by hand against its anchors, and every entry restates what the chain's profile already says and cites, so the registry adds no new claim about any chain.

    What it adds is the view across chains that thirty-one profiles of prose could not give. The first pass records seventeen schemes and seventy-two usages. Read across, ECDSA on secp256k1 is the default account scheme on fourteen rated chains and Ed25519 on thirteen, with two chains, Hedera and the XRP Ledger, letting accounts choose either. A single advance against either curve would reach every one of them at once.

    Two rules keep the registry honest. Where a role exists and its scheme cannot be confirmed from a primary source, the entry says unknown, and unknown is never shown as safe or as exposed: Hyperliquid's validator consensus is the first such entry, because the node source is not public. And a build check compares each chain's recorded usages with its tier, failing if they contradict each other, for example a Tier 5 chain recorded with a post-quantum account scheme live on mainnet.

    source ↗

  29. Correction

    Algorand: native Falcon-1024 accounts confirmed live since 22 August, migration 8 to 9

    The Algorand profile went eight weeks behind the chain. The go-algorand 5.0.0 consensus upgrade, which makes Falcon-1024 a native account type, activated on mainnet at round 64,318,659 on 22 August 2026, the first block produced under consensus version V42. We confirmed the round and the version from block headers on a public mainnet node. The profile still listed native Falcon-1024 accounts as in progress for Q3 2026, and the migration score was held at 8 on the stated ground that holders could not yet migrate.

    They can. An existing account can be rekeyed to a Falcon-1024 key and keep its address, assets and history, after which the protocol ignores signatures from the old Ed25519 key, and Pera Wallet supports both creating quantum accounts and rekeying to them. That meets the top migration band, under which holders can migrate today. It sits at 9 rather than 10 because the route is opt-in account by account, some dApps do not yet support quantum accounts, and post-quantum multisig, which institutional and treasury holders need, is not yet available. The Hardy Score moves from 77.5 to 79.0. The tier stays Shipping and the rank does not change.

    The record also needs a second correction. On 13 August the signature score moved from 8 to 9 on the publication of the 5.0.0 release, nine days before the upgrade activated. Under the mainnet rule that move was early. The score it reached was right from 22 August and stands, but the change should have waited for activation, and this entry records that it did not.

    The roadmap now shows native Falcon-1024 accounts as shipped on 22 August, inside the Q3 2026 window Algorand published. The end-2026 entry is narrowed to what its source states: Falcon-512 by the end of 2026, with scheme-agnostic multisig planned but undated. The earlier wording also listed staking support, which the source does not mention.

    Algorand source ↗

  30. Methodology

    Methodology v1.5: published delivery dates, tracked beside the score

    Where a chain has published a date for a post-quantum deliverable, the roadmap entry now carries that date as a target, and a new commitments page lists every target across the index with whether it has passed. No score changes, no weight changes, and no chain is ranked by it, for the reasons v1.4 gave for the say-do record: a weight on deadlines missed would reward the chain that never publishes a date over the one that publishes an honest roadmap and slips it.

    The field exists because a roadmap entry's date could not answer the question on its own. On some entries it is when something happened, on others when a statement was made, and on others when delivery is due. A target is only ever the last of these, and is recorded only where the chain's foundation, its core development team or a formally adopted improvement proposal published the date for that specific deliverable.

    The first pass checked every dated, unshipped roadmap entry against its cited source and recorded ten targets across six chains: Algorand, Ethereum, Hedera, Stellar, Sui and the XRP Ledger. Others were left untracked where the source dates a programme as a whole rather than each deliverable in it, or does not carry the date at all. Of the ten, one has passed: the XRP Ledger's second phase, formal experimentation with NIST-standardised algorithms, targeted for the first half of 2026, for which no completion has been published.

    A target stated as a quarter, half or year is due on the last day of that period. A passed target is shown as under review for fourteen days, so a delivery the dataset has not yet recorded can be checked, and as past target after that. When a chain moves a date, the earlier target stays on the record.

    source ↗

  31. Development

    Stellar Development Foundation released stellar-core v30.0.0 with ML-DSA verification host functions

    On 16 October 2026 the Stellar Development Foundation published stellar-core v30.0.0, which bumps the ledger protocol to version 30 and ungates CAP-0087, adding native Soroban host functions for ML-DSA signature verification, alongside CAP-0084 and CAP-0088. This is validator software rather than a network state change: protocol 30 only applies once validators vote it in, and even then ML-DSA would be verification available to Soroban contract accounts, not a signature scheme protecting classic XLM accounts, which continue to use Ed25519. For the rating to move, the public network would have to be confirmed running protocol 30, and then a route for existing classic account holders to hold funds under quantum-safe authentication would have to be live.

    Stellar source ↗

  32. Development

    Sui added an ML-DSA-65 signature scheme to its devnet release, ahead of its testnet target

    The devnet-v1.82.0 release, published by MystenLabs on 12 October 2026, registers ML-DSA-65 as signature scheme 7, accepts ML-DSA-65 signatures and multisig members through ExecuteTransaction, verifies them in VerifySignature, and adds matching GraphQL and Rust SDK types. This is devnet code only: Sui mainnet accounts are still signed with Ed25519, devnet state is reset on a regular cadence, and no holder can protect funds with a post-quantum key today. For the signature rating to move, ML-DSA-65 accounts would need to be usable by the public on a persistent test network, and then available on mainnet as a first-class account type, which Sui has scheduled for the first quarter of 2027.

    Sui source ↗

  33. Development

    Sui merged ML-DSA-65 account signatures into the node, enabled on devnet only

    On 7 October 2026 Mysten Labs merged a pull request adding ML-DSA-65 (FIPS 204) as Sui account signature scheme flag 0x07, with keystore, address derivation, CLI keytool support and hybrid multisig members, gated behind a new mldsa65_auth protocol flag turned on in protocol version 139 for devnet. Testnet and mainnet validators continue to reject these signatures as unsupported, mnemonic derivation is not implemented, and the gRPC and GraphQL surfaces are deferred to a later change. Sui accounts on mainnet remain protected by Ed25519 alone. The rating would move when ML-DSA-65 is enabled on the persistent public testnet, and again when it is accepted by mainnet validators as a first-class account type.

    Sui source ↗

  34. Correction

    Correction: a post published this morning announced coverage to 25 chains while the index held 31, and no guard read news posts at all

    The post announcing Monero and Mochimo said, in its headline and its answer block, that they took coverage to 25 chains. That was true on 13 August. The post published on the 19th, by which time the index held 31. It had been drafted from a six-day-old changelog entry, in the present tense, and it merged.

    Two things had to be missing at once for that to reach a reader, and both were.

    The claims guard added yesterday reads src/content/chains and nothing else. No sentence in any published post had ever been checked against the dataset. That is now fixed: the scanner reads the news collection too, and a claim in a post is registered exactly as a claim in a profile is.

    The second gap was subtler and is the more useful lesson. "Taking coverage to 25 chains" is index-scoped and quantitative, but it is not comparative. It ranks nothing and names no other chain, so both halves of the pattern that catches "the only chain in this index" slide straight off it. A whole class of claim, the size of the index, was invisible to a guard built to protect claims about the index. Counts are now matched separately and held to a stricter rule than comparisons: write the live figure as the {{chains}} token, which reads the dataset at build time and cannot go stale, or register the number as historical with the date it was true and say that date in the sentence. A number registered as historical whose sentence does not carry its year fails the build, because the date is the only thing that stops a reader taking it as current.

    Turning the guard on the news collection immediately found something worse than a stale number. The QRL post, live since 12 August, opened by saying every other chain in this index is having a conversation about migration. Mochimo and Abelian launched post-quantum too and never needed one. It is the same error corrected on the profiles yesterday, of the same shape, on the same chain, surviving in a post because posts were not being read. The sentence now names all three chains that launched post-quantum, and it is checked against the tier data rather than trusted, so the claim re-verifies itself whenever a chain enters or leaves Tier 1. Three other comparative sentences in older posts were found at the same time and are now registered with predicates: Algorand's placement, IOTA's statement about elliptic-curve reliance, and Monero's about the gap it filled.

    The Monero and Mochimo post itself has been rewritten as what it always was, a record of a change made on 13 August rather than news of one made today. The event is in the past tense, the post opens by saying when it was published and what it records, the historical count carries its date, and the current figure comes from the live token beside it. Its ratings were never wrong: those are read from the index on every build. Only the narrative around them had aged.

    All four rules were tested by breaking them. The sentence exactly as it published, a historical count with its date removed, a new unregistered comparison in a post, and a falsified predicate each produce a red build.

    Monero Mochimo Quantum Resistant Ledger source ↗

  35. Correction

    Correction: the Zcash roadmap was sourced to a page that stopped being readable, and the recovery path it described has been live since July

    A CoinDesk article from 8 May 2026 was carrying four load-bearing citations on the Zcash profile: the deployment and migration dimensions, and two of the three roadmap entries. Some time on 18 August that URL began returning a 429 to automated clients, which failed the source check on every build. The fix is not an allowlist entry. It is the one the source file already recommends: repoint at sources that can be read.

    Going to the primaries corrected the record in a direction the profile did not anticipate. ZIP 2005, whose title is Ironwood Quantum Recoverability rather than Orchard quantum recoverability, is not pending. ZIP 258 specifies that it activates with the NU6.3 network upgrade at block 3,428,143, and the chain passed that block on 28 July 2026. The deployment note said a ZIP "is deploying" a recovery path and the verification band said the construction was "not yet deployed". Both were three weeks out of date. The profile understated Zcash rather than overstating it, which is the less common direction and no more acceptable.

    Two claims are withdrawn rather than repointed, because no primary source carries them. The May 2026 roadmap entry said Zcash had set out a plan for quantum-recoverable wallets within a month and full post-quantum protection on a twelve to eighteen month horizon. The 2027 entry said a full post-quantum protocol migration was targeted for that year. Both came from the CoinDesk headline. Neither the ZIPs, the Zcash Foundation's NU7 polling results nor anything else we could read states a date for the full migration, so the profile now says we could not confirm one.

    The roadmap that replaces them carries two dated, sourced facts: the February 2026 NU7 polling result, where quantum recoverability drew 90.5 per cent support among ZCAP participants and 94.6 per cent among coinholders, and the July 2026 activation of ZIP 2005 at NU6.3.

    One substantive fact was missing altogether and has been added. The recovery path covers only funds moved into the Ironwood pool. ZIP 2005 states that anything left in the Sprout, Sapling or Orchard pools would be inaccessible once those protocols were disabled. A holder reading the old profile would have taken the protection as automatic.

    No score changed. Zcash remains Tier 3 with deployment at 5, migration at 8 and verification at 8. That placement now deserves a re-read in both directions, and the reasons are recorded here rather than settled quietly. Tier 3 is defined as a funded roadmap with public dates, and the only public date Zcash had has just been withdrawn as unverifiable, which points down. Against that, the chain has shipped a working mitigation on mainnet, which most of the tier has not, and which points up. The spine measures dated promises and post-quantum signatures, and Zcash has delivered something that is neither.

    Zcash source ↗

  36. Correction

    Correction: four claims comparing a chain to the rest of the index were false, and nothing was checking them

    A full audit of the platform found four live statements that compare one chain to the whole index and had stopped being true. Two of them had profiles contradicting each other in public.

    QRL's summary said it was "the only chain in the index where a post-quantum signature is mandatory for every account on mainnet", and its first question answered that it was "the only chain in this index with no quantum-vulnerable signature scheme available on mainnet at all". Mochimo is the same case and has been since the same month: both launched in June 2018, both score 10 on the signature dimension, and Mochimo's own row states that its node source contains no elliptic-curve signature implementation. The claims were wrong on the index's two highest-ranked rows at once. QRL's summary now describes QRL without the comparison, and the question names both chains.

    Mochimo made the mirror-image error. Its migration note said having no classical legacy "removes the hardest problem every other chain in this index faces", which is not true of QRL or Abelian, the other two chains that launched post-quantum. It now refers to every chain that did not launch post-quantum.

    Nervos CKB said that using a finalised NIST standard live on mainnet was something "no other chain in this index does". That was true when written and stopped being true when NEAR was added on 16 August with ML-DSA-65 under FIPS 204. The sentence now names NEAR.

    Solana's placement was described as "the most generous placement in the index" and "the most contestable call in this index". Bitcoin Cash was placed in Tier 2 on the same contract-level reasoning two days earlier, so both are now hedged. Nervos CKB's "the cleanest migration in the index" is hedged for the same reason, against Sui, XRP Ledger and NEAR, which all score the same 9.

    No score changed in any of this. Every correction is to prose that compared chains, not to a rating.

    The reason all four survived is that nothing checked them. From today every sentence in the dataset that is both scoped to the index and comparative has to be registered, and the build fails on any that is not. Thirty are registered. Eleven carry a predicate evaluated against the live data on every build, so they re-verify themselves: QRL and Mochimo being the only two chains scoring 10 on signature is now arithmetic rather than memory. Seventeen are judgements no predicate can express, and each is pinned to the number of chains in the index when a person last read it, so changing the size of the index fails them and forces the re-read that did not happen last week. Two trip the pattern while asserting no ranking, and say so.

    The register is at src/lib/claims.ts and the guard at scripts/check-claims.mjs. Both were tested by breaking them: an unregistered claim, an edited sentence, a falsified predicate and a change in the number of chains each produce a red build.

    Quantum Resistant Ledger Mochimo Nervos CKB Solana source ↗

  37. Correction

    Correction: the MemeCore consensus detail was sourced to a page we could not read

    MemeCore was published hours earlier today citing a press release for its consensus design. That URL refuses automated clients with a 403, which the source checker reports as a bot policy rather than link rot, and the distinction hid a real problem: we had never actually read the page. The claims taken from it came from a search-engine summary.

    Most of what that summary said held up against a syndication of the same release that can be read: the 9 September 2025 launch date, the EVM-compatible layer 1 description, the Proof of Meme combination of Proof of Authority and delegated Proof of Stake, the ten-block validator rotation and the seven million token self-stake. Two details did not appear in the readable version at all. The profile said the top seven validators are elected in real time and that the set refreshes roughly every seventy seconds. Both are now withdrawn, and the citation points at the version we can read.

    No score changed. The migration dimension still scores 1 and the reasoning still turns on a small and identifiable set of parties being able to agree a scheme change, which the ten-block rotation and the self-stake floor support on their own. But the argument was previously resting partly on a number we could not verify, and a rating that names a figure should be able to show where the figure came from.

    The general lesson is being recorded rather than quietly fixed. A 403 in the source checker is reported as a bot policy, which is accurate and which made it easy to treat an unreadable page as an acceptable citation. It is acceptable for a source whose content was verified when it was written down. It is not acceptable for one that never was.

    MemeCore source ↗

  38. Coverage

    The coverage rule run properly: four chains added, one held back, and several candidates correctly absent

    The inclusion rule published on 13 August was applied against live market capitalisations rather than against a list of chains that came to mind. That is a different exercise and it produced a different answer.

    Filtering out stablecoins, tokens, oracles and layer 2s per the scope boundary, five of the twenty-five largest layer 1s were unrated. Four are now in: Internet Computer at 14.5, Bittensor at 11.0, Cronos at 8.5 and MemeCore at 8.5. All four are Exposed. None has published a post-quantum roadmap, improvement proposal or research programme addressing its own signatures, and in each case the absence is the finding rather than a gap in our reading.

    Internet Computer is the one worth reading. Its distinguishing feature is the cryptography at risk: chain-key signatures rest on BLS for consensus and certification and on threshold ECDSA and Schnorr for canister keys, and the subnet public key that lets any client verify a certified response is published by design and cannot be withheld. DFINITY's chief scientist has said in public that the network was built with crypto agility and that replacement algorithms would go to the NNS at the appropriate time. That is a real statement from a real cryptographer and it is not a proposal, a programme or a date, which is what the Debating rung asks for. The same reading placed Cosmos Hub and Kaspa outside the index entirely.

    Canton Network is held back rather than rated, and it is the only chain inside the twenty-five largest we do not cover. Secondary sources report Ed25519 by default with ECDSA over P-256 and P-384 supported, which would be an unremarkable quantum-vulnerable position, but every version of the security documentation stating those schemes served a navigation shell rather than the text. Publishing a signature assessment from a search-engine summary of a page we could not read would break the rule that every data point carries a primary source, and the rule is worth more than the row.

    Several chains considered for this pass are absent because the rule says they should be, not because they were overlooked: Cosmos Hub, Kaspa, Ethereum Classic, Mina, Filecoin, Sei, Injective and Celestia all sit outside the top twenty-five layer 1s by size and none has a published post-quantum position we could find. The about page already says that a chain meeting none of the three tests is absent because nothing about its quantum position is yet in question, and that is the case here. Anyone who thinks otherwise should send the source.

    Internet Computer Bittensor Cronos MemeCore source ↗

  39. Methodology

    Methodology v1.4: two things published beside the score, neither of them in it

    Two artefacts join the profile in v1.4. Neither changes a single score, and that is the design rather than a limitation of the first pass.

    The first is the say-do record. A chain can announce post-quantum work indefinitely without shipping any, and announcing is cheaper than shipping. Where we can compile one, a profile now carries the chain's dated public commitments over a stated window, each with a source and a status, and a counted line: how many shipped, how many shipped in part, how many did not. The obvious move was to turn that into a shipped-to-announced ratio and deduct from the score, which is what at least one competing index does. We declined for three reasons. The score's claim is that a reader can reproduce it from six published dimension scores and six published weights, and an input derived from a corpus only we hold cannot be reproduced by anyone without our corpus. A weight on how much a chain has said is a weight on press-release volume, which would mark down a chain that publishes an honest roadmap and slips it against a chain that published nothing. And the ratio divides by zero on exactly the chains the measure is aimed at.

    So it is counted, not scored, and the entries are printed rather than compressed into a coefficient. A count can be checked against the list underneath it. Three commitments is the floor: below that the record is an anecdote that this layout would lend the authority of a register.

    The second is exposure as a quantity. The exposure dimension is a 0 to 10 score and, as the published limits already said, it is scored on address structure as much as on measurement, which left a reader without the figure they actually want. Where a credible measurement exists the profile now prints it, with the amount, the share where the source states one, who measured it and when. Where sources disagree we print all of them. Bitcoin is the case the rule was written for: published estimates run from about 4 million BTC to about 7 million, and that spread is where each analyst draws the line between exposed and unexposed. A measurement is evidence behind the exposure score rather than an input alongside it, so the dimension is still scored against the published anchors.

    Both fields are optional in the dataset and both render nothing when absent, because inventing a measurement from a block explorer or padding a ledger to reach the floor would be a worse failure than an absent section.

    source ↗

  40. Coverage

    NEAR Protocol enters at Tier 2 and 81.5, the highest score in the index for a chain not built post-quantum from genesis

    NEAR joins the index in fourth place, behind only the three chains that were post-quantum from their first block.

    The nearcore 2.13.0 release notes state that it "stabilized the FIPS 204 ML-DSA-65 post-quantum signature scheme as a third transaction-signature and access-key scheme alongside ed25519 and secp256k1". Protocol version 86 carrying it was voted in on mainnet from 20 July 2026. That is a NIST-standardised post-quantum signature working as a first-class account credential on a live mainnet, which no other retrofitting chain in this index has.

    NEAR's account model is what makes this possible. Accounts are human-readable identifiers controlled by rotatable access keys rather than addresses derived from a keypair, so rotating to ML-DSA-65 is a single on-chain transaction that changes neither the account name nor the balance. The migration dimension scores 9 on that basis, which is the highest in the index outside the native chains.

    One detail deserves more attention than it has had. NEAR stores an ML-DSA-65 key as a 32-byte SHA3-256 hash rather than as the 1952-byte key, so a rotated account publishes a hash and not a public key. On a chain where every account's access keys are readable on-chain from creation, that turns rotation into a fix for exposure as well as for signature strength.

    What keeps NEAR out of Tier 1 is that all of this is optional. Ed25519 and secp256k1 remain valid, no sunset for them has been proposed or dated, and no target has been published for how much of the account set should hold a post-quantum key by when. Effectively every account on the network still has a quantum-vulnerable public key in plain sight until its owner acts, which is why the exposure dimension scores 2 despite the rotation path being open.

    NEAR Protocol source ↗

  41. Coverage

    Bitcoin Cash enters at Tier 2 and 66.0, forty-nine points above Bitcoin

    Bitcoin Cash joins the index above Bitcoin, and the gap is large enough that it needs explaining rather than just reporting.

    Neither chain has changed its own signature scheme. Both still sign with ECDSA and Schnorr on secp256k1. The difference is entirely in the scripting layer. The Layla upgrade activated on Bitcoin Cash mainnet at 12:00 UTC on 15 May 2026, bundling the Loops, Functions, Pay to Script and Bitwise improvement proposals. Those features made Quantumroot practical: a vault design that verifies Leighton-Micali One-Time Signatures inside Bitcoin Script, resting only on SHA-256. LM-OTS is specified in RFC 8554 and is the one-time signature underlying the LMS scheme NIST approves in SP 800-208. Wallets including OPTN Labs and Paytaca shipped support.

    So a Bitcoin Cash holder can put coins behind a post-quantum signature on mainnet today. A Bitcoin holder cannot. This index ranks preparation, and on that measure the two chains are no longer in the same position.

    Bitcoin Cash is placed in Tier 2 on the same reasoning already applied to the other contract-level case in this index, where an application-level quantum-resistant vault protecting real funds on mainnet counts as shipping. That is the most generous reading available and the profile says so: a reader who thinks only protocol features should count would put this chain in Tier 3 and take 7.5 points off.

    The exposure dimension is the weak point and we would rather flag it than bury it. Bitcoin Cash inherits Bitcoin's chain history to August 2017, which means it inherits every pre-fork pay-to-public-key output with its key already published. Nobody has measured exposed supply on Bitcoin Cash, so the dimension is scored on the address model at the floor of its band, which is the limitation this rubric already publishes. Bitcoin scores 1 there on the strength of measurements running from 4 million to 7 million coins. If somebody produces the equivalent count for Bitcoin Cash at similar levels, that dimension falls sharply and this gap narrows. It is the number we would most like to see published.

    Bitcoin Cash source ↗

  42. Methodology

    Methodology v1.3: placement inside a band has to be stated

    This page claimed the Hardy Score is arithmetic rather than opinion. That was true of the total given six dimension scores, and it was never true one level down. An anchor reading "7 to 9" leaves a three-point choice, worth nine points of the total on the signature dimension, and until now nothing in the data had to say why it landed where it did. The strongest objection any chain could raise was that we had given it the bottom of our own band without justifying it.

    From v1.3 every score sitting inside an anchor that covers more than one value carries a stated reason naming the value we did not choose and the fact that decided between them, printed on the profile under "placement in the band" and in the Markdown mirror. That covers 105 of the 150 dimension cells in the index; the other 45 are the 25 deployment scores, whose anchors are generated from the tier list and cover one value each, and 20 signature scores sitting at a flat 0 or 10.

    The rule is enforced twice, by the collection schema and by a standalone check that runs before the site is built, and both call the same function, so neither can drift from the other.

    The check is deliberately mechanical: it verifies that a comparison was made, not that it was a good one. It requires the text to name another score in the band, as a digit or a word, or to use one of a short list of placement phrases, and that list is now published on the methodology page rather than kept as an in-house style note. A lint rule that shapes what a reader sees should not be invisible to them.

    No score changed in this work. Where writing a justification would have changed our mind about a value, that is a separate entry with its own reasoning.

    source ↗

  43. Methodology

    Methodology v1.2: the Debating floor gets a substance test

    Tier 4 read "the threat is acknowledged and proposals exist", which set no bar for who was proposing or where. A single forum post cleared it, which made the fourth rung the one genuinely gameable seam in the spine.

    Debating now asks for post-quantum work on the chain's own signatures, documented by people with authority over it, in a formal improvement proposal or a public research programme. Tier 5 is scoped to match, so its "no plan, proposal or research programme" test is explicitly about the signatures securing mainnet funds rather than about post-quantum work anywhere in a project.

    One chain moves: IOTA, whose post-quantum engineering lives in its identity layer rather than at layer 1. Separately, the signature dimension's 1 to 3 anchor promised credit for "a post-quantum implementation running on a public testnet or devnet", while the dataset consistently scored short-lived devnets and one-off benchmarks at 0. The anchor now says what the scoring actually does: the band needs an implementation live and usable by the public on a persistent test network, and devnet experiments sit at 0. No score changed as a result of that correction, because the data already followed the stricter reading.

    The published formula, the tier-to-score mapping and the share of weight carried by the signature and deployment dimensions are now generated from the weights themselves rather than typed out, so a future change to a weight cannot leave the methodology page describing arithmetic the site no longer performs.

    source ↗

  44. Score change

    IOTA moves from Debating to Exposed

    IOTA held Tier 4 on a stated intention to adopt future quantum-resistant standards. The v1.2 Debating floor asks for more than intent: a proposal in the chain's own improvement process, or a public research programme, aimed at the signatures that protect mainnet funds.

    A search of the iotaledger improvement-proposal and node repositories returns no quantum-related issue at all, and IOTA's layer 1 has signed with Ed25519 since Chrysalis replaced Winternitz one-time signatures in 2021. The post-quantum work IOTA has shipped is real but sits in IOTA Identity, where ML-DSA, SLH-DSA and Falcon secure verifiable credentials rather than tokens.

    Only the deployment dimension moves, from 2 to 1, because the tier is the only thing that changed. The profile carries the reasoning as a declared judgement call: this is a close placement, and a reader who counts the Foundation's demonstrated post-quantum capability as evidence of intent toward layer 1 would reasonably leave IOTA in Debating.

    IOTA source ↗

  45. Score change

    Tron: Falcon-512 is live on Nile, and the profile was two months behind it

    Tron's entry recorded an announced intention to adopt NIST post-quantum signatures and deliberately declined to credit it, stating that the score would move if Tron published a specification, a named parameter set or a testnet implementation. All three exist and predate that entry.

    TIP-899, Post-Quantum Signature Support, was opened in Tron's own improvement-proposal repository on 30 June 2026 with status Draft, specifying Falcon-512 and ML-DSA-44 across transactions, block production, node relay handshakes and the TVM, down to canonical wire encodings and address derivation. Falcon-512 was then activated on the public Nile testnet by governance proposal, which any reader can verify against the chain parameters: getAllowFnDsa512 reads 1 on Nile and the parameter is absent from mainnet entirely.

    Four dimensions move. Signature goes from 0 to 2, into the band for a post-quantum implementation live on a persistent public test network, held at 2 rather than 3 because ML-DSA-44 is staged on Nile at 0 and has not been activated. NIST alignment goes from 4 to 7, since named standardised parameter sets specified to the byte are a committed selection rather than a candidate reference. Migration goes from 2 to 5, because TIP-899's permission-weight coexistence is a real route off a vulnerable key, though a mechanism is not a plan and no sunset or date is proposed. Verification goes from 5 to 7 on the open specification, open source client and on-chain checkability.

    The tier does not move: Tier 3 asks for a funded roadmap with public dates, and TIP-899 carries none.

    This correction is the index working as intended on one axis and failing on another. The score rose sharply on evidence while the tier held, which is what separate axes are for. It should not have taken until now to notice.

    Tron source ↗

  46. Coverage

    Monero and Mochimo added, taking the index to 25 chains

    Both rows follow directly from the coverage rule published the same day.

    Monero enters on the scale test as the tenth largest layer 1 and was the most conspicuous gap in the index. It is placed in Tier 4: Debating, because it funded and completed dedicated post-quantum research in 2020 and has named candidate schemes since, but has selected nothing and scheduled nothing. Its exposure score is the lowest given to any chain here, because a one-time output public key is published on-chain for every output and a quantum break would also unmask senders in historical ring signatures retroactively.

    Mochimo enters on the deployment test at Tier 1: Native. Its WOTS+ signing was verified in the node source rather than accepted from project material, and the repository contains no elliptic-curve signature implementation of any kind, which is what makes post-quantum signing mandatory rather than optional. Its NIST alignment is held at 7 because NIST SP 800-208 approves XMSS and LMS rather than the standalone WOTS+ construction Mochimo uses.

    Monero Mochimo source ↗

  47. Coverage

    The coverage inclusion rule is published

    Until now the about page said only that the index covers the largest chains, the most advanced post-quantum deployments and the chains most often named as quantum-safe. That described our practice without being testable, so 'why is this chain not rated?' had no principled answer.

    Coverage is now a published rule: a layer 1 is in scope if it is one of the twenty-five largest by market capitalisation, or it has published a post-quantum position of any kind at any size, or it runs a post-quantum signature scheme on mainnet at any size. A live public mainnet and a primary-source-verifiable scheme are required in all three cases.

    Market value decides who gets assessed and never how they score, which is the distinction the methodology page draws.

    source ↗

  48. Correction

    Bitcoin and Cardano exposure citations repointed to primary sources

    No score changed. Bitcoin's exposure dimension cited a Forbes article for a figure Deloitte produced, and now cites Deloitte's own analysis directly.

    Cardano's exposure dimension cited Input Output's Cardano Vision 2026 announcement for claims about the address model, stake key visibility and the share of ADA that has moved, none of which that article makes. It now cites CIP-19, which defines a Shelley address as a payment credential plus a delegation credential, each a blake2b-224 hash of an Ed25519 verification key.

    The unmeasured claim about how much ADA has moved has been removed rather than resourced, and the profile now states plainly that no published measurement of Cardano's exposed share could be found.

    Bitcoin Cardano source ↗

  49. Correction

    Cardano's D3.1 deliverable named as its source names it

    Cardano's profile described deliverable D3.1 as publishing a migration strategy as a Cardano Improvement Proposal. Input Output's own wording is a SIP. The profile and roadmap now use the term the source uses. No score changed.

    Cardano source ↗

  50. Score change

    Algorand: signature 8 to 9

    Native Falcon-1024 accounts shipped as a first-class protocol-level account type in the go-algorand 5.0.0 stable consensus release, moving signature to the top of the 7-9 band while Ed25519 remains the default. Detected from release v5.0.0-stable and verified against the linked source before merge.

    Algorand source ↗

  51. Methodology

    Methodology v1.1: the bottom of the spine becomes Exposed

    The fifth rung of the readiness spine was Unverified, which described a chain marketing itself as quantum-safe without a confirmed deployment. That left no rung for a chain with quantum-vulnerable signatures and no published position at all, so five such chains sat in Debating carrying a label more generous than their evidence.

    The fifth rung is now Exposed: quantum-vulnerable signatures on mainnet today, and no public post-quantum plan, proposal or research programme. Unverified becomes a flag rather than a rung, applied to a chain whose marketing claim cannot be confirmed but whose evidence still supports a published row.

    The deployment-score mapping is unchanged, so this re-labels the floor rather than re-weighting the rubric.

  52. Score change

    Five chains re-tiered from Debating to Exposed

    Avalanche, Dogecoin, Hyperliquid, Litecoin and TON were placed in Tier 4: Debating only because the spine had nowhere lower, and each carried a caveat saying so. Under the v1.1 spine they move to Tier 5: Exposed, which is what the evidence supports: quantum-vulnerable signatures securing funds on mainnet today, and no post-quantum plan, proposal or research programme that we could find.

    Their deployment dimension falls from 2 to 1, which lowers each Hardy Score by 2.5 points. No other dimension changed and no other chain moved.

    Bitcoin, BNB Chain, IOTA and Tron remain in Debating, because each has acknowledged the threat and has proposals, research or a stated intention on the public record.

    Avalanche Dogecoin Hyperliquid Litecoin TON

  53. Coverage

    QANplatform held back pending a public mainnet

    QANplatform was rated at the foot of the index while the bottom rung was Unverified. The v1.1 rung is Exposed, which describes the signatures securing funds on a live mainnet, and QANplatform has no public mainnet: there is no deployed scheme to inspect and no balances to assess.

    Placing it on that rung would assert something we cannot check, and placing it higher would credit marketing, so the row is held back under the same rule that withholds Cellframe and Quranium.

    Nothing here disputes QANplatform’s algorithm choice, which is NIST-standardised, or its component audits, which are real. The row returns when a mainnet is live and its signature scheme can be confirmed against a primary source.

  54. Coverage

    Coverage expanded to 24 layer-1 chains

    Fourteen chains were added after verification against primary sources: Hedera, Sui, Polkadot, Zcash, Stellar and Aptos join Tier 3 on the strength of published roadmaps, while BNB Chain, Tron, Avalanche, Dogecoin, Litecoin, TON and Hyperliquid enter Tier 4. Abelian enters Tier 1, having run lattice-based post-quantum signatures on mainnet since 2022. Every added row carries a note and a primary source on all six dimensions.

    Hedera Sui Polkadot Zcash Stellar Aptos Abelian

  55. Coverage

    Cellframe and Quranium held back pending verification

    Both projects market native post-quantum protection and both may well deserve a high placement, but neither could be confirmed. Cellframe documentation lists post-quantum algorithms as available without confirming which scheme secures ordinary transactions by default. Quranium developer documentation was not reachable at the time of writing, leaving its claim resting on announcements rather than an inspectable specification. Publishing an unverified high score would damage this index as much as publishing an unfair low one, so both rows are withheld until the deployed scheme can be checked.

  56. Methodology

    Scope boundary published, and Quant and Starknet ruled out

    The index rates layer-1 blockchains only, meaning networks whose own signature scheme secures the balances people hold. Layer 2s, oracles, middleware, stablecoins and tokens are excluded, each for a stated reason, on the About page.

    Two named exclusions follow: Quant, because Overledger is interoperability middleware and QNT is an ERC-20 token that carries Ethereum exposure rather than its own, and Starknet, because it is an Ethereum layer 2 whose settlement security is partly inherited.

    Starknet is excluded despite substantive post-quantum work, since its hash-based STARK proofs are not vulnerable to Shor while its Stark-curve account keys are, and that distinction is not comparable on a layer-1 scale.

  57. Correction

    IOTA reclassified from Native to Debating

    IOTA is widely described as quantum-resistant on the strength of its original Winternitz one-time signature scheme. That scheme was removed in the Chrysalis upgrade in 2021 and replaced with Ed25519, which is quantum-vulnerable. IOTA’s current post-quantum support (ML-DSA, SLH-DSA and Falcon) sits in IOTA Identity and covers verifiable credentials, not layer-1 transaction signatures. We found no dated plan to restore post-quantum signatures at layer 1, so IOTA enters the index at Tier 4: Debating, not Tier 1: Native.

    IOTA source ↗

  58. Correction

    Nervos CKB classified as Shipping rather than Committed

    Nervos CKB’s SPHINCS+ lock script was audited by ScaleBit and began mainnet deployment in 2025, and a wallet using it has shipped. That is a post-quantum signature protecting real funds on mainnet, which places Nervos in Tier 2: Shipping rather than Tier 3: Committed.

    Nervos CKB source ↗

  59. Coverage

    Index launched with ten chains

    The Hardy Index published its first ranked dataset: Bitcoin, Ethereum, Solana, XRP Ledger, Cardano, Algorand, Nervos CKB, IOTA, QRL and QANplatform. Every dimension score carries a note and a primary source.

  60. Methodology

    Hardy Score methodology v1.0 published

    The six weighted dimensions, their 0 to 10 anchors and the five-tier readiness spine were published in full. The deployment dimension is derived from the tier rather than scored separately, so a tier and a score can never contradict each other.

Spotted something wrong? Send the primary source that contradicts it to index@hardyindex.com. Corrections are logged here, including ours.

This is a security-readiness assessment, not investment advice.