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.

Arkfile review of Coldcard firmware PR 692

arkfile-firmware-692-review

https://x.com/Arkfile_OSP/status/2084248974861697063

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

Arkfile reviews the proposed entropy fix in Coldcard firmware pull request 692, confirms rng_get now reaches the board TRNG, and reports that the new rng_get_or_fault helper has no recovery path for STM32 RNG error flags so a single fault latches the peripheral into an unrecoverable timeout. Verified against the captured post text and linked GitHub pull request.

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.