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.

VULN-109 description and code reference

laurentmt-vuln109-sources

https://x.com/LaurentMT/status/2084434979912663547

Captured screenshot of the post by @LaurentMT, posted 4 Aug 2026, 00:23 UTC
@LaurentMT posted captured full-size capture → original post →
Author
@LaurentMT
Organisation
independent
Evidence role
prior-warning-claim
Posted
Capture status
capture held

Posts the VULN-109 description from the karma-x.io article behind the prior-discovery claim together with the referenced ae.c code line, in reply to Fully Noded's developer; presented as the sources for the claim that this bug class was flagged before the incident.

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.