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.

Bitkey entropy long-form answer

benowhere-bitkey-entropy-answer

https://x.com/BEN0WHERE/status/2084027233656860920

Captured screenshot of the post by @BEN0WHERE, posted 2 Aug 2026, 21:23 UTC
@BEN0WHERE posted captured full-size capture → original post →
Author
@BEN0WHERE
Organisation
independent
Evidence role
downstream-wallet-scope
Posted
Capture status
capture held

Long-form answer to whether Bitkey has enough entropy, written from the Bitkey team's perspective: three keys generated in separate environments, with the stated OS RNG, EFR32MG24 Secure Vault TRNG and server-module sources named per key.

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.