Who Pays for Chain Analysis? We Read the Contracts
USAspending shows 154 Chainalysis and 66 TRM Labs federal awards — $154.8M and $135.5M. Then a breach leaked the client list itself. Follow the money, with numbers.
The surveillance industry publishes its own income statement — in public, for free. Much of the debate about chain analysis is about capability: what heuristics can see, what Monero hides, where the limits are. We walked that technical ground in October. What almost nobody does is read the other half of the file: who pays, how much, and for what. That file is open. USAspending.gov lists every prime federal contract, searchable by keyword, down to the individual award ID. This week the industry handed us a second document nobody asked for: a breach disclosure in which the flagship vendor's own client credential graph leaked. Between the procurement ledger and the incident report, the business model of chain analysis can be read the way we read order books — line by line, with numbers.
The government floor, measured. At USAspending.gov on 22 November 2026, keyword search with recipient filtering and subawards excluded gives: 154 prime awards naming Chainalysis entities since FY2016, totaling $154,824,712. The agency split: Department of the Treasury $73.6M, Department of Justice $50.8M, Department of Homeland Security $23.3M — 95% of the ledger sits in those three. The largest single item is a $26.8M Treasury award (2023–2026) for the 'Chainalysis all assets suite of tools, training and support' supporting criminal investigations 'of a financial nature involving cyber or cryptocurrency components'; another $11.8M funds IRS Criminal Investigation's cyber crimes unit 'case support and training'. The average award is about $1.0M. This is not marketing collateral. It is the customer list, with invoice amounts attached, published by the customer's own government.
The 2026 inflection, measured. TRM Labs' ledger is smaller in count — 66 awards, $135,499,570 — and more concentrated: DHS holds $108.4M, an 80.0% share. One item explains the concentration: award 70CMSD26C00000005, $94,655,840, from Homeland Security Investigations for the 'Homeland Security Task Force National Coordination Center Cyber Disruption Center'. That single 2026 contract is larger than TRM's entire 2021–2025 federal book ($29.2M) combined — 3.6 times it. The timing is not subtle: the award landed months after North Korea-linked actors drained roughly $6.3 billion from Binance in the largest crypto theft on record, and the same week US reporting announced a dedicated anti-fraud center. Government demand for tracing is not a steady subscription. It is elastic, and it spikes with each catastrophe — which is exactly when the privacy arguments of ordinary users get dragged into the same legislation.
The second customer, and our own place downstream. Government is the floor; the commercial layer sits on top. The breach disclosure conveniently enumerated the product families exchanges buy: Reactor (investigation graphs), Data Solutions, the KYT interface and API (real-time transaction monitoring), and address-screening products. This is how the compliance budget becomes a spread: a venue pays per-transaction monitoring, then prices the risk it detects into its spreads, fees and withdrawal friction. We want to be precise about ourselves here: as an aggregator we hold no client graph and subscribe to none of this — but the liquidity pools on the other side of our quotes do run address-risk screening on deposits, which is why some orders get held and why we wrote an entire guide on the mechanics. A no-KYC front end does not delete the industry; it only removes you, personally, from its datasets. (how Monero fees work)
Then the industry leaked its own org chart. On 31 October 2026, Chainalysis disclosed that an external actor using what it called 'offensive agentic techniques' — AI-driven tooling, turned against an AI-driven surveillance vendor — had reached internal tools and exposed names, emails, user IDs and role labels for platform users. Its follow-ups made it worse, not better: by its own Wednesday statement, names, usernames, password hashes and live tokens for all Chainalysis users had been exposed in an on-path (man-in-the-middle) attack. The company pulled its login portal offline, along with Reactor, Data Solutions, the KYT interface/API and address-screening products, and began re-admitting customers one allowlist entry at a time: submit your trusted IPs, reset your password, rotate your API keys. Read that sentence again slowly, because it contains the whole thesis of this piece: the crown jewel of the chain analysis industry turned out to be its own client credential graph. The map of who watches what, leaked through a login path.
A natural experiment nobody scheduled. For most of a week, the industry's flagship vendor could not clear addresses in real time. Consider what that means for everyone downstream: an exchange whose KYT subscription is down cannot screen deposits; a compliance desk cannot price risk it cannot compute; somewhere in every stack that depends on one vendor, the queue grows. We did not have to imagine this failure mode — it happened, publicly, with the vendor's name on it. This is the strongest argument we know against stacking your entire financial privacy strategy on any single intermediary, including the analysis industry's customers: concentration converts one vendor's Tuesday into your withdrawal's Friday. Our own answer is structural rather than moral: we hold no client graph to leak, print both transaction hashes so settlement is verifiable without trusting us, and route across pools so that no single upstream is a lifeline. The dependency we cannot remove — pool-side screening — we at least name, loudly, in our own docs.
The honest counterpoint: the product works. We are not going to pretend the tracing industry is useless, because the record says otherwise. The attribution of the $6.3 billion Binance theft moved within days, not years, and the takedowns we have documented — ChipMixer, Sinbad, the Samourai prosecutions — all rest on exactly this capability. Stolen funds getting traced is good for everyone whose coins were not stolen. Our quarrel with the industry is therefore narrow and specific: its revenue floor is elastic public money that spikes with catastrophe and then gets spent on rules that bind people who were never suspects; its commercial layer prices a risk score into spreads without showing the score; and its concentration means the whole compliance stack shares single points of failure — as this month proved empirically. And the bill lands on users: compliance budgets are paid out of the spreads KYC venues charge, a cost curve we measured to be invisible next to a printed premium.
Where the ledger converges with our quotes. Today, 22 November 2026 around 12:03 UTC, with Monero spot at $485.08 and Bitcoin at $61,019 (CoinGecko): 1,000 USDT-TRC20 bought 2.031403 XMR across two routes — an implied $492.27 per XMR, +1.48% over spot; selling 1 XMR fetched 481.794 USDT-TRC20, −0.68%; a 0.05 BTC leg quoted 6.205832 XMR across two routes, −1.34% against the spot cross. Those premiums are our entire visible bill, and they are the same kind of number you can now read in the procurement ledger — printed, public, checkable. The rest of this industry's pricing is not. Watch two things with us: the quarterly award ledger, where elastic government demand keeps inflecting; and the breach follow-ups, where the answers to 'which client records, whose tokens, what persistence' will tell you more about the surveillance network's real shape than any marketing deck ever will. (XMR to USDT exit)
Closing ledger. Three numbers pin the business model: $154.8M of Chainalysis prime federal awards since FY2016 across 154 contracts; $135.5M for TRM Labs across 66, with 80% from one department; and one $94.7M contract in 2026 that outbids five prior years combined — all published by the customer's own government, all checked by us this morning. Then one incident: the industry's flagship vendor, whose product is knowing things about strangers, spent a week unable to know things about its own users, because their password hashes and live tokens walked out through a login path. Follow the money and you find the floor is government; follow the breach and you find the ceiling is concentration. We take the same position we always take: no client graph at our layer, both hashes printed, premiums published to two decimal places — and a standing disagreement, stated honestly, with an industry whose useful product is funded by bills its users never see.