Adding to the Public Record on Our Ongoing Investigation - Coldcard
stackernews-coinkite-investigation-record
- Organisation
- Stacker News
- Evidence role
- Community discussion
- Published
- 2026-08-04
- Source changes
- 0
- Detected differences
- 0
- Unreviewed
- 0
- Copies held
- 1
Scoresby linking Coinkite's official 4 August investigation statement, separately held as coldcardwallet-2084731768632991801. The link post's eight-comment discussion records community reception of that statement; the vendor's claims remain attributed to Coinkite and are not independently 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 .
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
-
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 0 lines
Extracted text as captured
{ "data": { "item": { "comments": { "comments": [ { "createdAt": "2026-08-04T20:45:36.733Z", "text": "Self-serving shit. At every opportunity they're trying to ease their own accountability by blaming AI and the magical new security reality, as if no one before Kimi AI could have audited the \"PRNG, not TRNG\" bug.", "user": { "name": "Aeneas" } }, { "createdAt": "2026-08-04T22:01:13.409Z", "text": "An apology would have gone a long way here. .\n\n> Since the incident, we've also tested our code against frontier models, including Kimi K3, Claude Fable, and Codex 5.6. None of them caught it.\n\nWeird, since others have made claims to the contrary. Are they betting on us not believing them?", "user": { "name": "billytheked" } }, { "createdAt": "2026-08-04T21:29:23.988Z", "text": "Conflicts with what Rob Hamilton claims, that he found the bug quickly with Kimi K3. Who ya gonna believe, Coinkite or Rob Hamilton?", "user": { "name": "KiwiBitcoinGuide" } }, { "createdAt": "2026-08-04T20:27:12.756Z", "text": "gonna go out on a limb here and say that this is not the best look for the third or fourth post after a major problem with almost all your products that led to the loss of $100 million.", "user": { "name": "Scoresby" } }, { "createdAt": "2026-08-04T23:52:23.495Z", "text": "for me the whole perfect storm looks like a inside job, until they prove otherwise.\n\nAI just helped thiefs because their firmware was completely flawed", "user": { "name": "Fenix" } },Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
0 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
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.
Compare the screenshot or a quotation against the original while it is available.