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.

Whether firmware could ignore dice entropy

notgrubles-2085481084888760400

https://x.com/notgrubles/status/2085481084888760400

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

grubles says he is all for rolling dice for entropy but asks what prevents a firmware flaw from also ignoring the dice-roll entropy and falling back to the flawed RNG. It states the verifiability problem at the centre of the dice mitigation: the advice can be sound while the owner has no way to confirm the device followed it. The post drew BTC Sessions' verification procedure, held at btcsessions-2085612074806251668, and sits against PortlandHODL's report of checking the dice path across firmware versions at portlandhodl-dice-roll-verification. An attached video is not captured here, only its poster frame. The post asks a question and does not report such behaviour; nothing in it is a finding.

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.