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.

Personal update carrying an aside on seed generation

x_imp0stor-2085542831729279480

https://x.com/x_imp0stor/status/2085542831729279480

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

A long personal update, published by its author, reporting that he has returned home from hospital after a medical emergency described in his own quoted earlier post as a stroke and possibly a heart attack with identified brain damage, and that he does not yet know how the damage will affect him. Most of the post is about his life rather than the incident: finances, a job search, past bitcoin losses through Mt. Gox, Cryptsy, BlockFi, Celsius and a collateralised loan, a backlog of nostr and podcast projects, and hardware he wants to put to use. Two passages touch the record. He expresses sympathy for people who have lost their savings, saying he has been on their side of such events more than once, and he makes a one-line aside imputing intent to the way the affected seed-generation code was released, which no captured source supports and which this archive does not repeat as a finding. Held as first-hand community-response material, with the caveat that its incident content is slight; everything in it is the author's own published account and none of it is 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.