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.

Coldcard RNG Vulnerability Analysis by Device & Firmware

stackernews-rng-analysis-by-device

https://stacker.news/items/1536654

Organisation
Stacker News
Evidence role
Community discussion
Published
2026-07-31
Source changes
0
Detected differences
1
Unreviewed
0
Copies held
2

itsrealfake's device-and-firmware breakdown of which COLDCARD models and firmware ranges carried the RNG defect. The post body is a single image, which this text-only capture does not hold; the comment discussion is captured. The analysis is the author's, not verified here. Captured through the site's public GraphQL API: the rendered pages crash the capture tab, and the API answers POST from this host. The query fixes the captured surface to the item's title, text and two levels of comments, each with author and absolute timestamp.

Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked .

  1. Earliest copy held
    seen · Captured here 1,077 chars
    Extracted text as captured 
    {
  "data": {
    "item": {
      "comments": {
        "comments": [
          {
            "createdAt": "2026-07-31T05:14:33.372Z",
            "text": "@Lobotomite [shared](https://stacker.news/items/1536440/r/k00b?commentId=1536598) block's very thorough analysis: [https://engineering.block.xyz/blog/predictable-rng-fallback-and-32-bit-reseed-in-coldcard-firmware](https://engineering.block.xyz/blog/predictable-rng-fallback-and-32-bit-reseed-in-coldcard-firmware)",
            "user": {
              "name": "k00b"
            }
          },
          {
            "createdAt": "2026-07-31T06:16:47.574Z",
            "text": "The way I understand it, strong passphrase and/or human made mmnemonic are still safe, right? 馃",
            "user": {
              "name": "kilianbuhn"
            }
          }
        ]
      },
      "createdAt": "2026-07-31T05:06:10.322Z",
      "text": "![](https://m.stacker.news/150269)",
      "title": "Coldcard RNG Vulnerability Analysis by Device & Firmware",
      "user": {
        "name": "itsrealfake"
      }
    }
  }
}
1 presentation-noise difference. Sidebar, ticker and other page chrome churn that our review classified as not being a change to what the source says.
  • +7 -7 Only the JSON ordering of existing comments changed; their text and timestamps were unchanged.
How to check this yourself

The excerpts and plain unified diffs above show the text this project held and how it changed. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.

Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.