---
title: "Data: the Hardy Index as open datasets"
url: "https://hardyindex.com/data"
updated: 2026-11-13
---

# The index as data

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 is licensed under Creative Commons Attribution 4.0 (https://creativecommons.org/licenses/by/4.0/). Use it for anything, including commercially, provided you attribute it as: The Hardy Index, hardyindex.com, as of the date in the file's `as_of` field. Full terms: https://hardyindex.com/terms.md.

## Current ratings: https://hardyindex.com/data/index.json

Also as CSV: https://hardyindex.com/data/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: https://hardyindex.com/data/commitments.json

Also as CSV: https://hardyindex.com/data/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: https://hardyindex.com/data/algorithms.json

Also as CSV: https://hardyindex.com/data/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

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

```bibtex
@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},
}
```

Changes feed (Atom): https://hardyindex.com/feed.xml. CITATION.cff: https://hardyindex.com/CITATION.cff.

## 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.
- **Score history as a file.** Every past change is published, dated and sourced, in the changelog: https://hardyindex.com/changelog.md.
- **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.