COLDCARD vulnerability what happened, and what to do
Informational only, and this site never asks for your recovery words. details

Informational only. This is independent analysis and an evidence-backed explainer, not financial, security or legal advice, and not a substitute for professional advice about your own situation. It is not affiliated with, endorsed by, or speaking for Coinkite, Block, or any other party named here. Published estimates are attributed, and differing scenarios are kept separate with their assumptions. Act on your own judgement. Editorial standards and corrections.

Do not disclose recovery material to a website, form, message or support account. This site never asks for it. Deliberate recovery on independently verified offline equipment is a separate operation. Seed-word safety.

COLDCARD funds flow monitor

coldcard-watch

https://coldcard-watch.vercel.app/

Organisation
community tracker
Evidence role
Chain monitor
Published
continuously updated
Source changes
4
Detected differences
5
Unreviewed
1
Copies held
6

The tracker expanded on 1 Aug from the first 1,195-address episode to two episodes totalling 2,321 addresses and 1,128.4717 BTC. It includes a browser-local address checker and follows spends from the consolidation addresses hop by hop. It labels the first episode 29 July without stating a timezone; the corresponding on-chain window begins 30 July at 01:10 UTC. Operator anonymous; figures cross-check against Galaxy's published map for the first episode.

Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked 2 Aug 2026, 00:59 UTC.

Public privacy boundary

Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain victim addresses. Integrity hashes, capture times and reviewed change summaries remain available below.

  1. unreviewed difference between 1 Aug 2026, 17:43 UTC and 2 Aug 2026, 00:59 UTC Current unreviewed

    This detected difference has not yet been reviewed for capture noise.

    seen 2 Aug 2026, 00:59 UTC · Captured here text sha256 12d56347621a0f35500d58e8 3,483 chars
  2. source content difference between 1 Aug 2026, 14:03 UTC and 1 Aug 2026, 17:43 UTC source content

    The tracker's headline moved from 1,128.6633 BTC across 2,334 verified addresses to 1,158.8480 BTC across 2,686, and its address-check copy changed with it. The cluster description of three windows on 30 and 31 July was unchanged.

    seen 1 Aug 2026, 17:43 UTC · Captured here text sha256 bbc0fb62e38a8b78aa7453ed 3,483 chars
  3. source content difference between 1 Aug 2026, 13:01 UTC and 1 Aug 2026, 14:03 UTC source content

    The tracker moved from two episodes to three clusters by adding 13 addresses in block 960455, changed the destination set from four addresses to six, revised the same-block count for the last drained address from 250 to 237, and added an explanatory note about the two-scale timeline.

    seen 1 Aug 2026, 14:03 UTC · Captured here text sha256 8fc213bdceca00b258640db0 3,483 chars
  4. source content difference between 1 Aug 2026, 05:28 UTC and 1 Aug 2026, 13:01 UTC source content

    The tracker added dashboard, address-list and methodology navigation, described its figures as verified minimums and a floor rather than totals, and changed its checkable address set from 2,321 to 2,334.

    seen 1 Aug 2026, 13:01 UTC · Captured here text sha256 3d782a34299af47360984f7a 3,268 chars
  5. source content difference between 1 Aug 2026, 02:34 UTC and 1 Aug 2026, 05:28 UTC source content

    The tracker expanded from the first 1,195-address episode to two episodes totalling 2,321 addresses and changed its headline from 1,082.5696 BTC to 1,128.4717 BTC.

    seen 1 Aug 2026, 05:28 UTC · Captured here text sha256 7b782d15f055bbb267fd7147 2,926 chars
  6. Earliest copy held
    seen 1 Aug 2026, 02:34 UTC · Captured here text sha256 585b2fc9457be2325806c01e 2,984 chars
How to check this yourself

Each copy above is identified by the SHA-256 of its extracted text, shown beside it, and the diffs are plain unified diffs. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.

Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.