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.

Resurfaced 2021 entropy joke with chatbot commentary

bramk-2084618965226074604

https://x.com/bramk/status/2084618965226074604

Captured screenshot of the post by @bramk, posted 4 Aug 2026, 12:34 UTC
@bramk posted captured full-size capture → original post →
Author
@bramk
Organisation
independent
Evidence role
social statement
Posted
Capture status
capture held

One word, "Insane", over a stacked screenshot: a COLDCARD post dated 10 October 2021 joking that "the project makers could have a 'bug' in the entropy generation for later retrieval", a user asking Grok what the mathematical odds of that are, and Grok's reply. The reply names the retirement-attack pattern, in which makers intentionally weaken entropy so they can recover funds later, says the odds of pure coincidence are "effectively zero", and then describes the 2026 event as an accidental firmware bug that reduced seed entropy to roughly 40 bits on affected devices. Held because this is the vehicle by which the 2021 vendor post recirculated during the incident as an insinuation about the vendor's intent, and because that insinuation is carried entirely by machine-generated text quoted inside an image rather than by anything the post itself establishes. Nothing in the attached screenshot is verified here, and registration is not endorsement.

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.