About
Why Historical Exchange Index exists
Historical Exchange Index exists to keep crypto exchange identity, status shifts, major lifecycle events, archived URLs, and supporting evidence in one place. The goal is not to hype current winners, but to preserve a readable historical registry of crypto exchange history.
Existing information is often split across live exchange lists, DEX trackers, news articles, shutdown notices, archived pages, and exchange graveyards. HEI tries to bring those fragments into one structured registry view.
What HEI is
What HEI is not
Current scope
HEI currently provides an entity-level registry, dead-side and active-side views, individual exchange record pages, methodology notes, evidence links, archive-aware URL handling, and a stats page summarizing registry coverage and composition.
The current model is intentionally conservative: entity-level records first, deployment-level splitting later if it becomes necessary. The site is built as a quiet, dense registry rather than a feature-heavy application.
What the current version includes
What the current version does not include
HEI does not currently provide user accounts, public comments, live exchange monitoring, trading functions, automated verification, safety guarantees, liquidity ranking, or full deployment-level views for every DEX chain instance.
Data sources and approach
HEI is built from public records, archived pages, official statements, exchange notices, regulatory or court materials where available, reporting, public databases, and user-submitted corrections.
A source link is not treated as generic decoration. Evidence should support a specific claim such as identity, status, death reason, date, ownership, event history, or URL history. When evidence is weak or conflicting, HEI prefers cautious wording over forced certainty.
Contact and corrections
If you notice a missing record, broken classification, wrong date, unsafe URL treatment, weak evidence, or an important omission, use the contact / correction form below. If you prefer a public report path, GitHub Issues is also available.
Useful corrections include the exchange name, HEI page URL, what appears wrong or incomplete, and supporting source links. Archived links are especially useful for dead-side records.