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.

Rob1ham 2085087812534116402

rob1ham-2085087812534116402

https://x.com/Rob1Ham/status/2085087812534116402

Captured screenshot of the post by @Rob1Ham, posted 5 Aug 2026, 19:37 UTC
@Rob1Ham posted captured full-size capture → original post →
Author
@Rob1Ham
Organisation
independent
Evidence role
ai-security-response
Posted
Capture status
capture held

Rob Hamilton naming libsecp256k1 the cleanest repository found in the Red Team sweep and crediting its maintainers. A negative result from the scan, which is rarely published, and useful context for the finding counts in callebtc-2085024458012586286. The assessment is his and the underlying scan output is not public.

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.