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.

Pushback on BlockClock concern

llfourn-2085275362607735277

https://x.com/LLFOURN/status/2085275362607735277

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

LLFOURN arguing that the wave of concern about BlockClock, Coinkite's other product, is misplaced: it connects to the internet because that is where bitcoin is, it holds the WiFi password, and it is probably about as insecure as any other device of its kind on a home network. The distinct point is that the device is unremarkable rather than that it is safe, and it is one of the few held sources addressing whether the incident should widen to the vendor's non-signing products. LLFOURN is a repeatedly captured technical voice in this record. The assessment is his and no test of the device is offered.

This post is registered as evidence and has a locally held capture. The original remains the canonical publication. Last checked .

The conversation

Captured . 1 continuation posts, 4 replies held, 1 muted as low signal. Posts are in the archive's own order, oldest first, not the order X ranks them in.

  1. @LLFOURN the registered post 6 Aug 2026, 08:02 UTC
    Captured screenshot of the post by @LLFOURN

    capture taken

  2. @LLFOURN same author, continuing 7 Aug 2026, 00:39 UTC
    Captured screenshot of the post by @LLFOURN

    capture taken

Replies are unmoderated third-party material, reproduced here as part of the record. Inclusion is not endorsement, and nothing in them has been checked by this project.
Replies held in this capture (4)

Low-signal replies are collapsed to one line, never removed. A reply is collapsed only on mechanical grounds: fewer than 40 characters, no text, mentions only, no letters or digits, a bare link, or text identical to another reply in the same capture. What a reply argues is never a reason. Each one says which rule collapsed it, and its screenshot is one click away.

  1. @mutatrum 6 Aug 2026, 08:13 UTC this account is registered elsewhere in the record
    Captured screenshot of the reply by @mutatrum

    capture taken

  2. @4moonsettler 6 Aug 2026, 08:56 UTC no text captured
    show the capture Captured screenshot of the reply by @4moonsettler

    capture taken

  3. Captured screenshot of the reply by @newzealandhodl

    capture taken

  4. @LLFOURN 6 Aug 2026, 22:04 UTC the thread author answering in their own thread
    Captured screenshot of the reply by @LLFOURN

    capture taken

This capture reached the end of the conversation as X served it: it stopped because nothing further loaded, not because a limit was hit. X decides what a reader is shown, so that is not the same as a guarantee of every reply.

  1. Earliest copy held Current
    seen · Captured here 1,611 chars
    Extracted text as captured
    thread: 2085275362607735277
    url: https://x.com/LLFOURN/status/2085275362607735277
    author: LLFOURN
    
    post: 2085275362607735277
    role: focal
    author: LLFOURN
    name: Zero-Knowledge Goof
    created: 2026-08-06T08:02:43Z
    media: 1
    body:
    The blockclock FUD is completely ridiculous. Yes it makes a connection to the internet to find things out about bitcoin (note: bitcoin is on the internet). Yes it has your WiFi password . It's probably as insecure as any other IOT device on your network.
    
    post: 2085526243198546120
    role: self-thread
    author: LLFOURN
    name: Zero-Knowledge Goof
    created: 2026-08-07T00:39:38Z
    media: 0
    body:
    The correct vibe:
    
    post: 2085277980314485189
    role: reply
    author: mutatrum
    name: mutatrum
    created: 2026-08-06T08:13:07Z
    media: 0
    body:
    If there's even a small possibility it was malice, it's not like any other it device.
    
    post: 2085288835764609035
    role: reply
    author: 4moonsettler
    name: moonsettler  CTV / LNHANCE !
    created: 2026-08-06T08:56:15Z
    media: 1
    body:
    
    

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

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.