COLDCARD, CLN disclosures, zk proof of reserves - Bitcoin Optech Newsletter #416
stackernews-optech-416-thread
- Organisation
- Stacker News
- Evidence role
- Community discussion
- Published
- 2026-07-31
- Source changes
- 0
- Detected differences
- 0
- Unreviewed
- 0
- Copies held
- 1
schmidty linking Bitcoin Optech newsletter #416, which warned about the COLDCARD vulnerability. The newsletter itself is registered as optech-416; this source holds the Stacker News discussion of it. 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-01T08:45:23.024Z", "text": "Cold cock that coin", "user": { "name": "LAXITIVA" } }, { "createdAt": "2026-08-01T07:04:13.728Z", "text": "Cold cock a cold one", "user": { "name": "LAXITIVA" } } ] }, "createdAt": "2026-07-31T13:18:41.879Z", "text": "Bitcoin Optech newsletter #416 is here:\n\n- warns about a severe vulnerability affecting wallets generated by COLDCARD signing devices\n- summarizes the disclosure of two denial-of-service vulnerabilities in Core Lightning\n- describes a proof of concept for a zero-knowledge proof of reserves\n- summarizes popular Q&A from Stack Exchange\n- Optech Newsletter #416 Podcast\nhttps://bitcoinops.org/en/newsletters/2026/07/31/\n\nIf you used a COLDCARD to generate a wallet, any funds received by that wallet are at risk of theft and should be carefully moved to an unaffected wallet as soon as possible...\nhttps://bitcoinops.org/en/newsletters/2026/07/31/#move-funds-secured-by-coldcard-generated-keys\n\nOn 30 July 2026, some Bitcoin users discovered that funds from their COLDCARD wallets had been stolen in a series of unexpected transactions on 29 July. Over the course of the day, a bug was identified in the firmware of the COLDCARD that causes wallets to be generated with insufficient entropy. As of this writing, estimated losses exceed 1,000 BTC, a figure that may continue to rise as the situation develops...\nhttps://bitcoinops.org/en/newsletters/2026/07/31/#wallets-generated-by-coldcard-at-risk-of-theft\n\nChandra Pratap posted to Delving Bitcoin about two denial-of-service (DoS) vulnerabilities he found in Core Lightning...\nhttps://bitcoinops.org/en/newsletters/2026/07/31/#disclosure-of-two-dos-vulnerabilities-in-core-lightning\n\nfabohax posted about zkPoH (“zero-knowledge proof-of-hodl”), a proof of concept for a non-custodial proof of reserves system for Bitcoin...\nhttps://bitcoinops.org/en/newsletters/2026/07/31/#proof-of-concept-for-a-zero-knowledge-proof-of-reserves\n\nSelected Q&A from Bitcoin Stack Exchange\n- What is Bitcoin’s objective definition of transaction neutrality?\n- Why does BIP110’s decentralization benefit not outweigh its impact on transaction neutrality?\n- Why does BIP110 require a 55% signaling threshold if its nodes reject non-signaling blocks?\n- Why use ElligatorSwift encoding in BIP324?\n- Was the OP_SUCCESSx reservation in BIP342 designed with specific opcode families in mind?\n- What is the difference between the long-term feerate and the discard feerate?\n- What is the quickest method for migrating a legacy wallet to a descriptor wallet on a pruned node?\n- Is there historical data on orphan/stale block rates during high-fee periods?\nhttps://bitcoinops.org/en/newsletters/2026/07/31/#selected-qa-from-bitcoin-stack-exchange\n\nBitcoin Optech will host an audio recap discussion of this newsletter streaming live on X/Twitter Tuesday at 16:30 UTC.", "title": "COLDCARD, CLN disclosures, zk proof of reserves - Bitcoin Optech Newsletter #416", "user": { "name": "schmidty" } } } }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.