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.

Bitcoinnewscom 2083715303087673392

bitcoinnewscom-2083715303087673392

https://x.com/BitcoinNewsCom/status/2083715303087673392

Captured screenshot of the post by @BitcoinNewsCom, posted 2 Aug 2026, 00:43 UTC
@BitcoinNewsCom posted captured full-size capture → original post →
Author
@BitcoinNewsCom
Organisation
independent
Evidence role
social statement
Posted
Capture status
capture held

Bitcoin News reports ddustin's analysis that a compiler conflict led a developer to disable the hardware RNG by setting MICROPY_HW_ENABLE_RNG to 0, silently falling back to the Yasmarang software RNG.

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.