Every coin sitting on an address our own map ties to an exchange, day by day. The level is pinned to a public snapshot of every funded bitcoin address on Sep-12 2026 and carried forward by our own daily flows; to the left of the anchor the line is rolled BACK from it by the same flows. Pick a venue above.
1,596,285 BTC all mapped exchanges · BTC on our map on Oct-22 2026, the last day in this build, measured and published by askthetape.com.
Exchanges hold customer coins on addresses of their own. We map those addresses ourselves — 2,560,727 addresses, 49,876 of them funded on the day of the anchor — so «how much does Binance hold» becomes a number we can count instead of a number we have to buy. We draw the 49 venues with both a readable anchor and flows, and name the other mapped entities in the passport. THE LEVEL comes from a public snapshot of every funded bitcoin address (one public snapshot of every address balance, taken on Sep-12 2026): intersect it with our map and you get the coins on each venue on that day — 1,660,024 BTC on the whole map, 8.27 % of every bitcoin in that snapshot. BETWEEN snapshots the level is carried by our own daily net flow, the same tape the netflow page draws as bars; to the LEFT of the anchor the line is rolled back from it the same way, so the further left you read, the more the line leans on the tape and the less on the snapshot. 🩸 THIS IS ONE MAP'S NUMBER: another address map finds other cold storage and other clusters, so it prints another level for the same venue — and at least one of our own clusters we have already traced to the wrong house: 81,000 BTC filed under «okx» in an earlier read turned out to be Gemini's cold storage. We do not calibrate to anybody's map.
| leg | two files, both already in the build and neither of them a new capture: `data/reserve_anchor.json` (the anchor — our map v2.1b, md5 `7e3b8ae875b1b99519207df46f94e38c`, 2,560,727 addresses, 49,876 of them funded in the snapshot; per-entity levels under `by_entity`) and `data/v21_entity_daily.csv` (the daily tape — columns `d · entity · inflow · outflow · n`, Jan-01 2022 → Oct-22 2026). The level of a venue on a day = its anchor level + the sum of its own daily net since the anchor day. |
|---|---|
| anchor | public address→balance snapshot: a public monthly dump of every funded address, file of September 12 2026 (59,559,457 addresses; 20,083,046 BTC total = chain-supply check) — a public snapshot of every funded bitcoin address, taken at 00:00 UTC, intersected with our map. It is the only INDEPENDENT reading of the level in this project: it knows nothing about our map. It was taken once, on Sep-12 2026, and the series is that level carried forward by our own netflow — it has not been re-anchored since (re-anchoring is manual), so a number here moves when coins move; a re-anchoring, when it lands, will be named here. The anchor sits on the close of Sep-11 2026, not of Sep-12 2026: a snapshot taken at 00:00 UTC is the chain as the PREVIOUS day ended, and that reading was measured, not assumed — lining the window up on 00:00Z leaves a residual of 898 BTC against our own tape, lining it up on the file's Last-Modified stamp leaves 1,483. 🩸 This matters next door too: the single reserve line on the netflow page reads the SAME anchor, and until this build it pinned it one day later — one day's net below this page, 597.85 BTC on these numbers. Both pages now sit on the close of Sep-11 2026 and print the same level there; the only distance left between them is the held-back Kraken hub. |
| 🩸 how far the anchor and the tape drift apart — measured, not promised | 2026-09-01 → 2026-10-01, 14 exchanges: the snapshot moved -9,414 BTC in total, our tape says +9,684, and the median exchange is 84.0 % apart. Σ|residual| 35,288 BTC against Σ|Δ| 29,150 (121.1 %); the worst single name is Binance (-1,940 from the dump against +7,283 from the tape). That is the judge that found twelve leaky days in the July–August tape (since re-extracted from our own node); it runs on every re-anchoring. |
| 🩸 what the number is NOT | it is not «the reserve» — it is the reserve OF OUR MAP. A venue holds coins on addresses we have not found yet, and every address we have not found is missing from its line. The honest size of that gap is the PoR addendum: 63,501 BTC of exchange addresses published by the venues themselves (391 funded) are not in map v2.1b yet and are NOT added here — they enter in the next map version, and until then the anchor and the flows both run on the same map, which is what keeps the two halves of the number consistent. |
| 🩸 which venues are drawn, and which are named instead | the pick list is not a list we typed: it is every entity that has a number in the anchor AND a line in the tape, ordered by its level on the last closed day, and the chart draws the 13 largest of the 49. The rest are in «all mapped exchanges» and not on their own pill. 9 entities carry a line in the tape but no number in the anchor and are drawn NOWHERE: biconomy, binance_pool, bitb_bitcoin_etf_holdings_address, fastex, fire, hibt, indodax, localbitcoins_com, swisborg_reserve_wallets. 15 entities have an anchor but no flows on this tape at all (they are exchanges that died before it starts): 796, bit x, bitbay net, bter, btradeaustralia, bx in th, cex io, coincafe and 7 more. 5 entities sit in the anchor with no level we can read (biconomy, fastex, fire, hibt, localbitcoins_com) — named here rather than drawn as a zero. |
| 🩸 which coins are counted as an exchange's | the same rule as the flows page: the three non-trading wallets in the map (a mining pool's payout wallet, an ETF's holdings address and a custody service) are NOT exchanges and are out of every number here, which leaves 49 venues. Kraken is the one venue with a second line: seven addresses whose level matches the venue statistically but whose ownership is not proven on-chain sit in a held-back layer — in the reserve they are shown, in the flow tape they are not, and the page says so rather than quietly picking one. |
| cadence | daily, one point per closed UTC day. The running day is never drawn: the calendar of this page is the calendar of the flows page, and a day the tape has not finished reading is left out on both. A day the tape is missing entirely leaves a GAP in the line — not a zero and not a straight bridge — and its move is not carried into the level either, so the line holds its last known value across the hole. On this build 1756 of 1756 days are drawn. |
| policy | no new capture and no backfill: both files are already pulled by the build for other pages, the snapshot is public and re-taken monthly by hand, and nothing on this page calls out to the network. · export: whole history |
| this build | data to Oct-22 2026 |
| policy | no backfill · read it here · export: whole history |
The chart itself is drawn in the browser: turn JavaScript on to hover a day, pick a window and draw your line. The numbers above come from the last build, Oct-23 2026 21:24Z.
What the tape says today · what's new · all 111 metrics