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.

Vendor statement on the disclosure route

coldcardwallet-2085551118164132316

https://x.com/COLDCARDwallet/status/2085551118164132316

Captured screenshot of the post by @COLDCARDwallet, posted 7 Aug 2026, 02:18 UTC
@COLDCARDwallet posted captured full-size capture → original post →
Author
@COLDCARDwallet
Organisation
independent
Evidence role
social statement
Posted
Capture status
capture held

Coinkite's own account, replying to a poster who was arguing that the correction about which generator was at fault, MicroPython's built-in general-purpose RNG rather than a Coinkite fallback, was pointless given the losses. The vendor answers in three sentences: that it is doing all the investigation it can to get to the bottom of it as promised, that it is devastated, and that the hacker could have done the right thing and responsibly disclosed. Primary vendor material and one of the clearest published statements of the vendor's position on how the defect became public. It is also the sentence that was immediately turned back on the vendor, captured here at fractalencrypt-2085576915453157786 and fractalencrypt-2085687538962812943, so the register holds both the statement and its reception. What the investigation has found, and whether disclosure was attempted, are not established by this post or by any captured source.

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.