Methodology · revision · v1.8
Methodology v1.8: what changed on 21 October 2026
In force since 21 October 2026. Every score on this site is calculated under it, and the table below records every chain either side of the change.
In short
- Four changes: two tiers reworded, verification and NIST alignment re-anchored to the signatures that protect funds, and one new rule for exposure.
- 28 of 31 chains change score, 27 of them down. The largest move is IOTA, 18.5 to 10.5. No chain changes tier, and no weight changes.
1. Shipping and Committed say what they test, and no chain moves
The objection it answers. Solana's tier broke the tier's own definition, and the Committed tier was not applied as written: it required public dates that four of its chains do not have.
Before, v1.7
- Tier 2: Shipping
- Post-quantum signature features are live on mainnet and a migration for existing holders is underway.
- Tier 3: Committed
- A funded roadmap with public dates and active research exists, but no post-quantum signature is live on mainnet.
After, v1.8
- Tier 2: Shipping
- A post-quantum signature is live on mainnet and usable by ordinary holders.
- Usable by ordinary holders
- Usable by ordinary holders means any holder can put their own coins behind the post-quantum signature on mainnet today, with publicly available tools and without anyone’s permission. Publicly available means released software a holder can install: a published release or package, not code that is unmerged or unreleased. A command-line tool or an SDK counts. Support in a mainstream wallet is not required, and where a placement rests on tools that demanding, the profile says so as a judgement call.
- Tier 3: Committed
- The chain’s own authority, meaning its foundation, its core team or an adopted improvement proposal, has published a plan to replace its fund-protecting signatures with post-quantum ones, naming the scheme or a funded programme to select one, but no post-quantum signature is live on mainnet. A draft proposal is not a plan.
Shipping asked for a migration to be underway as well as a post-quantum signature on mainnet. The migration dimension already scores whether holders can move, so a chain was being judged on it twice, and Solana sat in Shipping against the letter of its own rung. Its profile said so in a caveat. The rung now tests the one thing it is named for, so that caveat goes. A narrower judgement call stays on Solana's profile: its post-quantum wallet is reached through a command-line tool and has seen little use, and a reader who requires wallet support would place it a rung lower.
Committed asked for a roadmap "with public dates". Dates are what the commitments tracker records, beside the score, and four chains placed in Committed have no dated target there. Enforcing the clause would have demoted them for a missing tracker entry rather than a missing plan. The rung now asks for a plan published by the chain's own authority, naming a post-quantum scheme or a funded programme to select one, and says outright that a draft proposal is not a plan. That keeps Tron in Debating: its TIP-899 is a draft.
This change moves no score.
2. Verification judges the post-quantum component, not the classical code
The objection it answers. Verification was effectively inverted: chains with no post-quantum component outscored chains that deploy one.
Before, v1.7
- Measures
- Whether the chain’s post-quantum claims are backed by open source, third-party audits and independent review, or rest on marketing.
- 9 to 10
- Open source, independently audited, with the claim checkable on-chain or in public research.
- 6 to 8
- Open source with public review or a named third-party audit of the relevant component.
- 3 to 5
- Some independent verification exists, but the headline quantum-safety claim itself is not verified.
- 0 to 2
- Claims rest on marketing material with no independent verification.
After, v1.8
- Measures
- Whether the post-quantum component protecting the chain’s funds is open source, independently reviewed and audited, and checkable on-chain. The openness of the classical codebase earns nothing here. Public review means review by people outside the team that wrote the component, done in the open: an outside reviewer on a public pull request, an improvement-proposal process with outside participation, or published research on the implementation. Review inside the authoring team does not count, and neither does review of an upstream library the component calls. Fund-protecting signatures are the ones that authorise spends and the validator signatures that finalise them. A scheme used elsewhere in the stack, such as an identity or credential layer, does not count.
- 9 to 10
- The post-quantum component is open source, independently audited, and its use is checkable on-chain.
- 6 to 8
- The post-quantum component is open source with public review or a named audit.
- 3 to 5
- A post-quantum component exists, on mainnet, on a persistent testnet or as a merged implementation, but is unreviewed.
- 0 to 2
- No post-quantum component exists, or the claims rest on marketing.
The dimension was meant to ask whether a chain's post-quantum claims are backed by open code, audits and review. In practice it scored open-source pedigree: a chain with no post-quantum component at all could score 9 for the openness of the classical code a quantum computer would break, while a chain that actually deploys one scored 5. The anchors now read the post-quantum component that protects funds, and a chain with none sits in the bottom band whatever its codebase is like.
Chains with nothing post-quantum protecting funds fall to 2 or below. At a 5% weight the largest single move is 3.5 points.
3. NIST alignment counts only schemes for the chain's own fund-protecting signatures
The objection it answers. NIST alignment credited schemes that protect no funds. IOTA scored 4 for its identity layer, which was the main reason an Exposed chain ranked above Bitcoin.
Before, v1.7
- Measures
- Whether the chosen post-quantum scheme is standardised by NIST (ML-DSA, SLH-DSA, XMSS, LMS), on the NIST standardisation track (Falcon/FN-DSA), or bespoke and unreviewed.
- 0 to 2
- No named post-quantum scheme, or a proprietary scheme with no public cryptanalysis.
After, v1.8
- Measures
- Whether the post-quantum scheme the chain has deployed, tested or proposed for its own fund-protecting signatures is standardised by NIST (ML-DSA, SLH-DSA, XMSS, LMS), on the NIST standardisation track (Falcon/FN-DSA), or bespoke and unreviewed. Fund-protecting signatures are the ones that authorise spends and the validator signatures that finalise them. A scheme used elsewhere in the stack, such as an identity or credential layer, does not count.
- 0 to 2
- No post-quantum scheme named for the chain’s fund-protecting signatures, or a proprietary scheme with no public cryptanalysis.
The dimension scores how well a chain's chosen post-quantum scheme is standardised. It now scores only schemes the chain has deployed, tested or proposed for its own fund-protecting signatures, which includes the validator signatures that finalise them. A scheme elsewhere in the stack, such as an identity or credential layer, protects something, but not the coins this index rates.
We considered the narrower version, crediting only schemes on a dated plan, and did not adopt it. It would also have moved Bitcoin and Monero, whose research references NIST schemes as candidates, and the existing 3 to 5 band is written for exactly that case. As worded, this change moves one chain, IOTA, and puts an Exposed chain back below one that is debating the problem in the open.
4. A chain that shares another chain's history shares its measured exposure
The objection it answers. Bitcoin Cash scored 6 on exposure against Bitcoin's 1, although it inherited every pre-2017 pay-to-public-key output.
Before, v1.7
- Exposure
- No rule. A fork was scored on its own address model, as though its history began at the split.
After, v1.8
- New rule
- Where a chain shares another chain’s transaction history, as a fork does, the published measurements of that shared history apply to it until a measurement specific to the chain exists. Coins that sat in exposed outputs before the split are still exposed after it, on both chains.
Bitcoin Cash carries every output that existed on Bitcoin before August 2017, including the early pay-to-public-key outputs whose keys have always been on-chain. The measurements of that exposure were applied to Bitcoin and not to Bitcoin Cash, so the chain with the measurements scored 1 and the chain sharing the same history scored 6. Being measured was punished and being unmeasured was rewarded.
The rule is written for any chain that shares history, not for Bitcoin Cash, and it lapses for a chain the moment a measurement of its own exists. Today it applies to Bitcoin Cash, whose tier is unaffected.
Every chain, before and after
All 31 chains, in their rank order before the change, including the 3 whose score did not move, so nobody has to infer from a gap that a chain was not modelled. Scores are Hardy Scores out of 100. The reason is given wherever a score moved.
| Chain | v1.7 | v1.8 | Change | Rank v1.7 | Rank v1.8 | What moves |
|---|---|---|---|---|---|---|
| Quantum Resistant Ledger | 92.5 | 92.5 | 0.0 | 1 | 1 | No change. |
| Mochimo | 90.0 | 89.0 | −1.0 | 2 | 2 | Verification 7 to 5. Verification re-anchored to the post-quantum component, which has had no outside review or audit. |
| Abelian | 84.5 | 84.0 | −0.5 | 3 | 3 | Verification 5 to 4. Verification re-anchored to the post-quantum component, which has had no outside review or audit. |
| NEAR Protocol | 81.5 | 80.0 | −1.5 | 4 | 4 | Verification 8 to 5. Verification re-anchored to the post-quantum component, which has had no outside review or audit. |
| Algorand | 79.0 | 77.0 | −2.0 | 5 | 5 | Verification 9 to 5. Verification re-anchored to the post-quantum component, which has had no outside review or audit. |
| Nervos CKB | 75.5 | 76.0 | +0.5 | 6 | 6 | Verification 8 to 9. Verification re-anchored to the post-quantum component, which is audited and checkable on-chain. |
| Bitcoin Cash | 66.0 | 62.0 | −4.0 | 7 | 7 | Exposure 6 to 2. Exposure: the measured pre-fork pay-to-public-key outputs it shares with Bitcoin now apply to it. Verification re-anchored; the score holds at 5. |
| Solana | 53.0 | 53.0 | 0.0 | 8 | 8 | No change. |
| Sui | 45.5 | 43.5 | −2.0 | 9 | 10 | Verification 8 to 4. Verification re-anchored to the post-quantum component, which has had no outside review or audit. Corrected on 22 October 2026: NIST alignment 9 to 8, because ML-DSA-65 is not yet in use on mainnet. Now 42.0. |
| XRP Ledger | 45.0 | 44.5 | −0.5 | 10 | 9 | Verification 5 to 4. Verification re-anchored to the post-quantum component, which has had no outside review or audit. Corrected on 22 October 2026: NIST alignment 9 to 8, because ML-DSA is on AlphaNet, not mainnet. Now 43.0. |
| Hedera | 42.0 | 39.5 | −2.5 | 11 | 11 | Verification 7 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Stellar | 41.0 | 39.0 | −2.0 | 12 | 13 | Verification 8 to 4. Verification re-anchored to the post-quantum component, which has had no outside review or audit. |
| Zcash | 41.0 | 38.0 | −3.0 | 13 | 15 | Verification 8 to 2. Verification re-anchored: ZIP 2005 keeps notes recoverable for a post-quantum protocol not yet specified, which is preparation rather than a component. Proposal amended on 21 October 2026. |
| Aptos | 40.5 | 39.0 | −1.5 | 14 | 12 | Verification 7 to 4. Verification re-anchored to the post-quantum component, which has had no outside review or audit. Corrected on 22 October 2026: NIST alignment 9 to 8, because SLH-DSA is enabled on devnet only; migration 6 to 7, because AIP-137 is accepted and accounts rotate in place. Now 39.0. |
| Polkadot | 40.5 | 37.5 | −3.0 | 15 | 16 | Verification 8 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Ethereum | 40.0 | 38.5 | −1.5 | 16 | 14 | Verification 9 to 6. Verification re-anchored to the post-quantum component, which has had no outside review or audit. |
| Cardano | 37.5 | 34.0 | −3.5 | 17 | 18 | Verification 9 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Tron | 34.5 | 34.5 | 0.0 | 18 | 17 | No change. |
| BNB Chain | 22.5 | 20.0 | −2.5 | 19 | 19 | Verification 7 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Monero | 21.0 | 17.5 | −3.5 | 20 | 20 | Verification 9 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| IOTA | 18.5 | 10.5 | −8.0 | 21 | 24 | Verification 6 to 2; NIST alignment 4 to 0. NIST alignment and verification now count only fund-protecting signatures; IOTA's post-quantum schemes are in its identity layer. |
| Bitcoin | 17.0 | 14.5 | −2.5 | 22 | 21 | Verification 7 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Internet Computer | 14.5 | 13.0 | −1.5 | 23 | 22 | Verification 5 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| TON | 13.0 | 11.0 | −2.0 | 24 | 23 | Verification 6 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Litecoin | 12.5 | 10.5 | −2.0 | 25 | 25 | Verification 6 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Bittensor | 11.0 | 9.5 | −1.5 | 26 | 26 | Verification 5 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Dogecoin | 11.0 | 9.0 | −2.0 | 27 | 27 | Verification 6 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Avalanche | 10.5 | 8.5 | −2.0 | 28 | 28 | Verification 6 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Cronos | 8.5 | 7.0 | −1.5 | 29 | 29 | Verification 5 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| MemeCore | 8.5 | 7.0 | −1.5 | 30 | 30 | Verification 5 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
| Hyperliquid | 7.0 | 5.5 | −1.5 | 31 | 31 | Verification 5 to 2. Verification re-anchored: no post-quantum component protects funds, so the classical codebase no longer earns this dimension. |
Recorded on 21 October 2026, the day v1.8 took effect. A score corrected since then keeps its row as recorded, with the correction and the score now noted beside it.
If you think a score is wrong
Send the primary source that shows it, through the contact form as a correction, or to index@hardyindex.com. A chain's own submission is treated exactly like anyone else's. A correction of fact takes effect as soon as it is confirmed, and the changelog records it with the score either side.
The full rubric in force today is on the methodology page.