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: the technical autopsy of an entropy failure

stackernews-technical-autopsy-entropy-failure

https://stacker.news/items/1546011

Organisation
Stacker News
Evidence role
Community discussion
Published
2026-08-11
Source changes
0
Detected differences
0
Unreviewed
0
Copies held
1

k00b relaying a detailed postmortem that claims the Mk3 and Mk4 candidate spaces are smaller than previously reported, estimates sweep costs and collision probabilities, and compares device-class vulnerability. The numerical claims are the author's and are reported here without endorsement; the thread is a significant technical counterpoint to earlier published estimates. 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 Current
    seen · Captured here 2,454 chars
    Extracted text as captured
    {
      "data": {
        "item": {
          "comments": {
            "comments": [
              {
                "createdAt": "2026-08-12T00:05:45.584Z",
                "text": "Nice data, but I hate to say it: the writing has that distinctive sloptastic vibe to it, and my aesthetic reaction to it is so bad that I can't bring myself to read the otherwise very interesting analysis.  I was especially interested in the birthday paradox section, but paragraphs like:\n\n> This model does not describe the real firmware, and it is worth saying so straight away. `_start_scan()` is only called at the beginning of a burst, and a burst only closes 250 milliseconds after the last release, at `mempad.py:159`. 2 people entering a PIN of the same length do not, then, consume the same number of draws: the fast typist chains several keys into a single burst, the hesitant one triggers a burst per key. Add to that backtracking, abandoned attempts, mistyped entries, and the `_rand_below()` loop that redraws when a draw is rejected. The generator’s real rank at creation time depends on typing cadence, not on PIN length.\n\ngot me gagging",
                "user": {
                  "name": "SimpleStacker"
                }
              }
            ]
          },
          "createdAt": "2026-08-11T23:52:53.482Z",
          "text": "This is *very* detailed postmortem of the coldcard vulnerability correcting the candidate space sizes (they are smaller than previously reported), estimating the probability of collisions among devices, and estimating the cost of sweeping the candidate spaces for each device class under different assumptions.\n\nFor Mk3s without passphrases or dice rolls, you can test the sweepability of nearly all candidates for $61 of rented RTX 4090 time \\~9 days on a single RTX 4090. In comparison it takes years to do the same for Mk4 class devices even assuming more information is known.\n\n![](https://m.stacker.news/151909)\n\nThe candidate space for the mk3 is hundreds of thousands of times, and a million times for mk4 class devices, smaller than Block and others published.\n\n![](https://m.stacker.news/151910)\n\nAnd, assuming a fleet of 30,000 mk3 devices and a few other things, they put they likelihood of collisions at 1 in 1,000.\n\nThere's lot of bits in here that weren't in the earlier reports for anyone that's a detail devil.",
          "title": "Coldcard: the technical autopsy of an entropy failure",
          "user": {
            "name": "k00b"
          }
        }
      }
    }
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.