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.

Rebuttal of the vendor's fallback correction

jamesob-2085555839797166530

https://x.com/jamesob/status/2085555839797166530

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

James O'Beirne replies to Coinkite's "extremely important correction" to Jack Mallers, held at coldcardwallet-2085541034243600805, which argued there was no weak-entropy fallback and that Yasmarang was MicroPython's general-purpose RNG reached through a link-time error. O'Beirne calls that hairsplitting and misdirection, says the device absolutely did fall back to weak entropy, and says the Yasmarang implementation placed in libngu was weaker than MicroPython's because it used hardcoded constants, linking a pinned commit and line range in switck/libngu ngu/random.c. He adds that he warned Coinkite about this issue and that at least one other person did four years before him. This is a direct exchange between the vendor and the auditor whose disclosure history the record already carries; the file he cites is itself held at libngu-random-c, so the comparison can be checked against the source rather than taken on assertion. The warning history and the characterisation of the correction are his own.

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.