The Counterparty is a record of crypto-market counterparty exposure: who is connected to whom, what has already failed, and what the wire is reporting today. It is a computed publication. Every count, table and ranking on the site is derived from a dataset held in this repository, and where the dataset holds nothing the page says so rather than filling the gap.
Four things are published here, and nothing else is claimed.
The Wire is the desk's index of published crypto and macro headlines — 1,800 items in the current window, 2026-07-24 to 2026-07-27. The headline and summary on each item belong to the publisher that wrote them and link straight back to the original; what this masthead adds is the entity tagging.
The Record is the entity file: 3,667 counterparties with a published page, drawn from 11,787 mapped entities across 44 kinds — companies, protocols, tokens, chains, exchanges, regulators, funds, bridges and the rest. Each published record is described in this masthead's own words.
The Ledger is the incident history: 44 incidents on record. 24 of them carry a loss figure recorded against the incident, totalling $75,399M; the other 20 read undisclosed, because no figure is on record and estimating one would be inventing it.
The Docket is the regulation beat as the wire reports it — 155 items tagged across the same window, newest first.
Behind those four sit 25,338 typed relations, 3,262 dated events, and licence and regulator references covering 327 licences and 174 regulators.
Every figure above is counted at build time from the dataset the pages render. None is entered by hand.
The record is not written page by page. A generator reads the dataset, computes everything the page shows, and writes the HTML. What follows is what that code actually does.
A relation is a typed, directed edge between two entities. Connectedness is measured as degree: the number of distinct entities a given entity is tied to, counted in both directions, with self-edges dropped and each pair counted once however many times it appears. That is why an entity named in ten relations to the same counterparty does not outrank one tied to ten different counterparties.
Every wire item carries a list of entity ids. An entity's mention count is simply how many indexed items name it, and the “most-referenced counterparty” ranking on the front page is that count sorted — computed, not measured. This site has no analytics property, so it cannot report what is most read and does not pretend to.
An entity is rendered as a link only when its record has actually been written to disk; otherwise its name appears as plain text. The graph knows about far more entities than are published, and the generator refuses to link into a page that would 404.
Citations are attached to entities, not to sentences bolted on afterwards. 1,072 entities carry at least one citation and 503 of those stand on three or more. Records without citations state what the graph holds and no more; they do not borrow authority they have not earned.
The three prices in the utility bar are fetched at page load from /api/prices, an edge-cached proxy. No price is ever baked into the HTML — if the proxy is unavailable the em-dashes simply stay. See the privacy note for what that request does and does not carry.
Where the incident record has no loss figure, the cell reads undisclosed. Where a column would hold one repeated value for all 44 rows, the column is dropped rather than dressed up. Where the desk has no longform, the slot carries a computed ranking instead of an essay nobody wrote.
Stated plainly, because it would otherwise be guessed at: The Counterparty and DeFi Intel are two public brands run by the same desk, from one repository, over one data pipeline.
The mockups this design came from asked for several things the data and the infrastructure cannot honestly support. They are absent rather than faked, and it is worth saying which.
The commitments that are real are set out in full on the editorial standards page, together with how errors in the record are corrected.