COLDCARD RNG incident the public record, collected and explained
Informational only, and this site never asks for your seed words. details

Informational only. This is an open source collection of what others have published about the incident, together with an explanation of it. It is 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. Material is attributed and quoted as published; where sources disagree their scenarios are kept separate with their assumptions rather than reconciled into one answer. Everything is meant to be checked against the linked evidence rather than taken on trust. Act on your own judgement about a particular situation. Editorial standards and corrections.

Do not disclose recovery material to a website, form, message or support account. This site never asks for it, and contributions containing recovery words or private keys are not accepted.

Slipstream multisig migration update: 5,371 BTC

orangesurfbtc-2085513982043963560

https://x.com/OrangeSurfBTC/status/2085513982043963560

Captured screenshot of the post by @OrangeSurfBTC, posted 6 Aug 2026, 23:50 UTC
@OrangeSurfBTC posted captured full-size capture → original post →
Author
@OrangeSurfBTC
Organisation
independent
Evidence role
social statement
Posted
Capture status
capture held

OrangeSurf reports that at least 5,371 BTC, about $345 million at the time, have migrated out of multisig wallets via Slipstream, quoting his own 5 August post that gave 3,890 BTC. Two mempool.space Research charts are attached, both plotting cumulative multisig any-M-of-N BTC output in MARA blocks since height 860,000. The figure counts private-submission multisig migration, not losses, and the poster is associated with mempool.space Research, whose charts the post carries. Held as one dated point in a running series this record keeps in full so the migration curve can be read rather than summarised; the count, the method behind it and the attribution of those flows to incident migration are the monitor's own and are not verified here.

This post is registered as evidence and has a locally held capture. The original remains the canonical publication.

How to check this yourself

Compare the screenshot or a quotation against the original while it is available.