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.

nvk.wtf articles index

nvkwtf-articles

https://nvk.wtf/articles

Latest reviewed change

source content difference between and

The articles index added a seventh entry, a Wizardsardine technical autopsy by Loic Morel dated August 11, 2026.

seen +12 -1 full history below
 2026
 2024
 
-6 articles
+7 articles
+
+Coldcard: the technical autopsy of an entropy failure
+(opens in a new tab)

First lines only. The complete diff is in the timeline below.

Organisation
nvk.wtf
Evidence role
Aggregator
Published
not established
Source changes
1
Detected differences
3
Unreviewed
0
Copies held
4

Index of third-party reporting and research on the incident, each entry linked out to its source. The site is an aggregator run alongside promotion of competing open-source hardware (SeedSigner, BTClock, Passport) and takes an openly critical stance toward NVK and Coinkite, so its selection and summaries are editorial and interested; the operator is not named on the site. Tracked for what it chooses to include and when, and as a discovery feed: anything it surfaces is followed to the primary and registered there, never cited from this copy. SPA with no feed or API; every path serves the app shell, so capture goes through the browser.

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. source content difference between and Current source content +12 -1

    The articles index added a seventh entry, a Wizardsardine technical autopsy by Loic Morel dated August 11, 2026.

    seen · Captured here 3,566 chars
    What changed from the previous capture 13 lines
     2026
     2024
     
    -6 articles
    +7 articles
    +
    +Coldcard: the technical autopsy of an entropy failure
    +(opens in a new tab)
    +
    +Wizardsardine
    +Loïc Morel
    +11 Aug 2026
    +
    +The technical companion to the same publication's 1 August writeup, which was written for users. It reconstructs the code path down to the missing symbol export that left seed generation bound to MicroPython's software generator, and recounts the entropy figures that had circulated the week before, arguing the real candidate space is closer to 2^22 on the Mk3 and 2^52 on the Mk4, Mk5 and Q. Also puts numbers on the chance of two Coldcards starting from the same state, prices an exhaustive sweep in rented GPU time, separates what broke (cloning, paper wallets, Key Teleport) from what held (the RFC 6979 nonces, backup encryption, the dice-only path), and reads the 31 July patch closely enough to note the faulty guard is still there.
     
     Coldcard and the limits of “don't trust, verify”
     (opens in a new tab)
    
    Extracted text as captured
    Articles
    
    Reporting and research on the Coldcard vulnerability, linked at the source.
    
    Newest first
    Oldest first
    All years
    2026
    2024
    
    7 articles
    
    Coldcard: the technical autopsy of an entropy failure
    (opens in a new tab)
    
    Wizardsardine
    ·
    Loïc Morel
    ·
    11 Aug 2026
    
    The technical companion to the same publication's 1 August writeup, which was written for users. It reconstructs the code path down to the missing symbol export that left seed generation bound to MicroPython's software generator, and recounts the entropy figures that had circulated the week before, arguing the real candidate space is closer to 2^22 on the Mk3 and 2^52 on the Mk4, Mk5 and Q. Also puts numbers on the chance of two Coldcards starting from the same state, prices an exhaustive sweep in rented GPU time, separates what broke (cloning, paper wallets, Key Teleport) from what held (the RFC 6979 nonces, backup encryption, the dice-only path), and reads the 31 July patch closely enough to note the faulty guard is still there.
    
    Coldcard and the limits of “don't trust, verify”
    (opens in a new tab)
    
    Bennet.org
    ·
    Bennet
    ·
    3 Aug 2026
    
    Starts with how a disabled flag routed seed generation to a predictable fallback, then turns to the harder questions: whether a flaw that cannot be patched retroactively could have been disclosed responsibly at all, where the responsibility sits, and why the author rejects laying it at the door of AI. Also defends the people who recommended the device in good faith, and argues the episode is a vendor failure rather than a case against self-custody.
    
    Don't trust NVK, verify.
    (opens in a new tab)
    
    X
    ·
    Zach Herbert

    Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.

  2. Earliest copy held
    seen · Captured here 2,673 chars
    Extracted text as captured
    Articles
    
    Reporting and research on the Coldcard vulnerability, linked at the source.
    
    Newest first
    Oldest first
    Coldcard and the limits of “don't trust, verify”
    (opens in a new tab)
    
    Bennet.org
    ·
    Bennet
    ·
    3 Aug 2026
    
    Starts with how a disabled flag routed seed generation to a predictable fallback, then turns to the harder questions: whether a flaw that cannot be patched retroactively could have been disclosed responsibly at all, where the responsibility sits, and why the author rejects laying it at the door of AI. Also defends the people who recommended the device in good faith, and argues the episode is a vendor failure rather than a case against self-custody.
    
    Don't trust NVK, verify.
    (opens in a new tab)
    
    X
    ·
    Zach Herbert
    ·
    3 Aug 2026
    
    A long, densely linked rebuttal by the cofounder and CEO of Foundation Devices, one of the companies it says NVK attacked. It gathers years of quotes — each linked to the podcast, post or commit it came from — on the treatment of Passport and SeedSigner, the handling of security disclosures, and the GPL and trademark disputes. An interested party, and it says so, closing: "Do not trust NVK. Do not trust me either. Verify."
    
    This Isn't the End of Bitcoin Self-Custody
    (opens in a new tab)
    
    Frank Corva's Newsletter
    ·
    Frank Corva
    ·
    2 Aug 2026
    
    Written for owners of an affected device: where to move funds, covering hardware and software wallets, custodians and multisig services, then an explanation of the firmware bug and a primer on entropy. Openly opinionated — it also argues a case against Coldcard and dice rolls, and for multi-vendor multisig.
    
    Critical Coldcard flaw: what happened, who is affected, and what to do

    Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.

2 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
  • +5 -2 The article-index controls reordered and displayed its article count; the listed articles were unchanged.
  • +3 -0 The article-index filter controls rendered in this capture; the listed articles 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.