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.

Inheritance-key hardware expansion

nunchuk-inheritance-key-options

https://x.com/nunchuk_io/status/2084132206323372215

Captured screenshot of the post by @nunchuk_io, posted 3 Aug 2026, 04:20 UTC
@nunchuk_io posted captured full-size capture → original post →
Author
@nunchuk_io
Organisation
Nunchuk
Evidence role
vendor-update
Posted
Capture status
capture held

Responds to affected users by expanding inheritance-key options for its off-chain timelock protocol beyond Tapsigner and Coldcard: says the Jade and Foundation teams confirmed they are adding on-device encryption support, notes Jade, Ledger and soon BitBox02 already work for the on-chain timelock protocol, and says Ledger and BitBox have been contacted about device encryption.

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.