HEI

Historical Exchange Index

A quiet registry of crypto exchanges, active and gone.

Data quality

Quality and coverage

Inspect where the registry is strong, where evidence or archives are thin, and which reviewed records need further strengthening.

Entities869
Events1004
Evidence3497
Generated2026-07-18
Entity archive coverage94%

entities with an archived URL

High-confidence entities54%

share of all reviewed entities

Average evidence per entity4

total evidence records divided by entities

High-reliability evidence48%

1687 of 3497 evidence records

Archived evidence share90%

3155 / 3497 evidence items

Entities with 0 evidence0

0% of entities

Entity confidence

Reviewed confidence classification on exchange entity records.

High470 · 54%
Medium388 · 45%
Low11 · 1%

Evidence reliability

Reviewed reliability classification on public evidence records.

High1687 · 48%
Medium1761 · 50%
Low49 · 1%

Evidence depth by entity

Number of evidence records associated with each reviewed exchange entity.

zero0 · 0%
1 source1 · 0%
2–4 sources590 · 68%
5+ sources278 · 32%

Record freshness

Time since the entity record was last reviewed, using last_verified_at.

0–30 days640 · 74%
31–90 days172 · 20%
91–180 days57 · 7%

Coverage

Archive, date, origin, domain, and confidence coverage with explicit denominators.

MetricValueDenominator / note
Archive coverage94813 / 869 entities
Dead-side archive coverage100215 / 215 dead-side
Active-side archive coverage91598 / 654 active-side
High-confidence share54470 / 869 entities
Launch date known49430 / 869 entities
Death date known100214 / 215 dead-side
Origin known100869 / 869 entities
Original domain known94813 / 869 entities

Evidence source types

Composition of the public evidence layer by source category.

Official statement1311 · 37%
Official blog218 · 6%
Official social32 · 1%
Archive capture178 · 5%
News article637 · 18%
Court document9 · 0%
Regulatory notice89 · 3%
Database reference970 · 28%
Community reference50 · 1%
Other3 · 0%

Evidence claim scope

What kind of registry claim each evidence record is intended to support.

Entity1039 · 30%
Event760 · 22%
Status972 · 28%
Death reason52 · 1%
Launch date378 · 11%
Death date64 · 2%
URL history194 · 6%
Ownership38 · 1%

Selected missing-field counts

Visible selected field gaps. A retained unknown value is not automatically an error.

MetricValueDenominator / note
Missing launch date43951% of entities
Dead-side missing death date10% of dead-side
Missing origin00% of entities
Missing original domain566% of entities

Completeness indicators

Selected public coverage indicators. These do not form a hidden quality score.

MetricValueDenominator / note
Aliases present74639 / 869 entities
Notes present100867 / 869 entities
Summary present100869 / 869 entities
Archived URL present94813 / 869 entities
Dead-side with 2+ evidence100214 / 215 dead-side
Entities with 0 evidence00% of entities
Entities with 1 evidence10% of entities

Metric definitions

Definitions and denominators used to interpret this public summary.

Entity confidence
The reviewed confidence classification stored on each exchange entity record.
All reviewed public entities.
Evidence reliability
The reviewed reliability classification stored on each evidence record.
All reviewed public evidence records.
Evidence depth
How many evidence records are associated with each exchange entity.
All reviewed public entities.
Archive coverage
Whether an entity record includes an archived URL reference. It does not measure the completeness of every historical page.
The entity population named in each metric note.
Record freshness
Elapsed time since the entity last_verified_at date, grouped into review-recency bands.
All reviewed public entities.
Unknown-field rates
Visible missing values in selected public entity fields. Unknown values are not automatically treated as errors.
All entities or dead-side entities, as stated in each metric note.
This summary is generated from reviewed public HEI records. Internal monitoring findings, private research notes, unresolved candidate queues, and operator-only repair priorities are not published here.