Data

The index as data

Name: The Hardy Index: Cryptography registry
Creator: Hardy
License: https://creativecommons.org/licenses/by/4.0/

The ratings, the post-quantum commitments and the cryptography registry, as JSON files rebuilt every day from the same records the site is built from.

Licence and attribution

Every file here is licensed under Creative Commons Attribution 4.0. Use it for anything, including commercially, provided you attribute it like this: The Hardy Index, hardyindex.com, as of the date in the file's as_of field. The date matters, because scores change and a stale figure attributed to us misrepresents us. The full reuse terms are in the terms of use.

The files

Current ratings

index.json index.csv

One record per rated chain: rank, tier, Hardy Score, and the six dimension scores with their weights and sources.

slug, name, ticker: The chain, as the site names it.
rank: Position in the index, by Hardy Score, ties broken alphabetically.
tier, tier_name: Readiness tier, 1 (Native) to 5 (Exposed).
hardy_score: 0 to 100, one decimal place: the weighted sum of the six dimension scores.
claims_unverified: True where the chain markets a post-quantum claim no primary source confirms.
under_review: Set while a fact behind the profile is being checked: since when, and what. The rating stands meanwhile.
unmigrated_policy: The chain's stated policy on coins that never move to post-quantum keys: stance (adopted, proposed, none-stated or not-applicable), approach (sunset, freeze, recover or leave), source and the date it was checked.
dimensions: For each of the six dimensions: score (0 to 10), weight (percent) and the primary source behind the score.
last_updated, last_reviewed: When the profile last changed, and when every source it cites last resolved.
profile: The page carrying the reasoning behind every number.

Post-quantum commitments

commitments.json commitments.csv

Every delivery date a rated chain has published for its post-quantum work, and whether it has passed.

chain, chain_name, milestone: Whose commitment, and what was committed to.
target: The date as the chain published it (YYYY, YYYY-MM, YYYY-MM-DD, YYYY-Qn or YYYY-Hn), its wording, its source, and when it was set.
due: The last day of the target period.
state, state_label: open, past-target, delivered-on-time, delivered-late or delivered.
under_review, days_past: Whether a passed target is still inside the 14-day review window, and how far past it is.
delivered: The delivery date, once shipped.
earlier_targets: Every date the chain published before the current one, with the day it was replaced.

Cryptography registry

algorithms.json algorithms.csv

Every scheme the rated chains use, each chain's usage of it, and which chains share a scheme Shor's algorithm breaks.

records: One row per chain, scheme and role: parameter set, role, deployment (mainnet-mandatory down to proposed, or unknown), evidence (on-chain, source-code, specification or statement: the kind of source behind the row) and source. An unknown usage names no algorithm.
algorithms: id, name, aliases, family, quantum (broken-by-shor or believed-resistant), standard (body, document, final or draft) and sources.
shared_exposure: For each scheme Shor breaks, the chains whose accounts sign with it by default or by mandate.

Cite this dataset

Use the date of the file you used. As of 13 November 2026:

Hardy (2026). The Hardy Index: blockchain quantum readiness datasets, as of 2026-11-13. https://hardyindex.com/data. Licensed CC BY 4.0.

@misc{hardyindex_20261113,
  author       = {{Hardy}},
  title        = {The Hardy Index: blockchain quantum readiness datasets},
  year         = {2026},
  howpublished = {\url{https://hardyindex.com/data}},
  note         = {As of 2026-11-13. Licensed CC BY 4.0},
}

Each JSON file repeats the exact attribution line in its attribution field, and each CSV row carries its as_of date. To follow changes as they happen, subscribe to the changes feed (Atom). A CITATION.cff file is published for reference managers.

What every file carries

Each file wraps its records in the same envelope: dataset, as_of, methodology_version, licence, the attribution line to use, and schema_version, currently 1. A change that would break a reader's code raises the schema version; adding a field does not.

What is not here, and why

Our writing. The reasoning behind each score, the profile answers and the guides are on the pages each record links to. The files carry the facts and the sources; the prose stays where it can be read in context.
Score history as a file. Every past change is published, dated and sourced, in the changelog.
Copies of the pages we cite. We keep them to notice when a source changes, and they are other publishers' work, so they are not ours to publish.

The same data is in the Markdown copy of every page, and llms.txt lists it all. Questions about the data go through the contact form.