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.

Red Team origin dates, scanning costs and disclosure advice

rob1ham-2085494034026598854

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

Captured screenshot of the post by @Rob1Ham, posted 6 Aug 2026, 22:31 UTC
@Rob1Ham posted captured full-size capture → original post →
Author
@Rob1Ham
Organisation
independent
Evidence role
social statement
Posted
Capture status
capture held

Rob Hamilton dates the start of the Red Team initiative by pointing at a reply of his to @callebtc one day earlier, notes that Kimi K3 went open weights on 27 July, and says his group was already red-teaming its own infrastructure as it launched. He argues that after the Coldcard hack it became evident most software maintainers were not using frontier AI tools for defensive security, puts the cost of scanning most small or medium codebases at $10 to $30 in credits, credits @opencode for multi-model access, urges projects to add a security.md file so responsible disclosure has a clean path, and asks readers to donate to the @OpenSats red team fund. Two interests: Hamilton works at AnchorWatch, a commercial custody provider, and the post solicits funding for the effort he leads. Held for the dates and cost figures, which are among the most specific published about the post-incident scanning campaign; they are his own and are not verified here.

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.