Bitcoin Thursday — October 8, 2026

by @chaosmagic23 · 2026-10-11

*Lightning updates, security disclosures, and progress toward more private Bitcoin payments.* ![Bitcoin Thursday](https://ipfs.3speak.tv/ipfs/QmUKj1jtqVHaLA8FiLqgHwQmZAmDxeX5JBQMbroBArnRJz) Welcome back to **Bitcoin Thursday**! (A bit late on a Sunday) This edition covers developments published or newly highlighted since October 1. Some underlying fixes and research are older; their original dates are included so that a new report does not become a misleading “new discovery.” ## 1. LND 0.21.4 is now released **LND v0.21.4-beta was released on October 1**, after the previous edition of this series. Despite “beta” being part of LND’s version naming, this release is listed as a regular release rather than a release candidate. The update fixes problems that could leave Lightning payments pending during channel transitions, potentially triggering unnecessary force closes and on-chain fees. It also improves invoice handling and rejects invoices containing multiple payment-hash fields. Another change concerns **new legacy channels**: LND no longer opens or accepts channels using the old commitment format. Existing legacy channels continue to work. For operators, this is worth reviewing before an upgrade, particularly if other software interacts with the channel-opening API. New channel negotiations now require explicit channel types. The release credits contributors including **Andras Banki-Horvath, elsirion, Gijs van Dam, Nishant Bansal, Olaoluwa Osuntokun, Yong Yu, and Ziggie**. **Sources:** [Official LND 0.21.4 release](https://github.com/lightningnetwork/lnd/releases/tag/v0.21.4-beta) · [Detailed release notes](https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.21.4.md) ## 2. Eclair security disclosure: old versions can be overwhelmed Bitcoin Optech’s **October 2** newsletter highlighted two denial-of-service vulnerabilities disclosed by **Matt Morehouse on September 24**. Both affected **Eclair 0.13.1 and earlier** and were fixed in **Eclair 0.14.0**, released in May. One flaw involved expensive parsing of feature information. The other involved decompression of incoming gossip queries without a suitable output limit. In testing, malicious messages could exhaust resources and take a node offline. These are documented availability attacks, not evidence that Bitcoin’s consensus rules were broken or that funds were stolen. Morehouse found the first issue with his **smite** Lightning fuzzer. He investigated the second through LLM-assisted analysis followed by experiments. **What it means:** Eclair operators still using affected versions should review the disclosure and upgrade. The version numbers matter: an Eclair advisory does not automatically apply to LND or Core Lightning. **Sources:** [Matt Morehouse’s original disclosure](https://delvingbitcoin.org/t/disclosure-dos-vulnerabilities-fixed-in-eclair-v0-14-0/2914) · [Bitcoin Optech Newsletter #425](https://bitcoinops.org/en/newsletters/2026/10/02/) ### Bitcoin meme of the week ![Bitcoin Meme](https://ipfs.3speak.tv/ipfs/QmUewkVwsKr12xqDRKCM7gxq3vQnv4zkh9SkcZj31fMcjA) *Watching the candles is optional. Maintaining your node deserves a place on the calendar.* ## 3. Silent Payments make progress in Bitcoin Core Bitcoin Optech’s October 2 issue also highlighted **Bitcoin Core PR #35301**, authored by **Eunovo** and merged on **September 23**. The change adds foundational work for **BIP352 Silent Payments**, including address handling, payment-output derivation, and scanning for payments. Silent Payments aim to improve privacy when receiving Bitcoin without repeatedly publishing ordinary reusable addresses. However, this merge **does not yet enable sending or receiving Silent Payments through Bitcoin Core’s wallet GUI or RPCs**. For everyday users, it is an implementation milestone to follow. For developers, it provides building blocks for further wallet integration. **Sources:** [Original Bitcoin Core pull request](https://github.com/bitcoin/bitcoin/pull/35301) · [BIP352 specification](https://github.com/bitcoin/bips/blob/master/bip-0352.mediawiki) ## 4. Could wallet labels follow you between devices? Another proposal highlighted on October 2 tackles a familiar wallet problem: transaction labels and notes can become stranded on one device. **Jakub** proposed synchronizing BIP329 wallet-label records through a shared, untrusted storage service, with the records protected by authenticated encryption. The discussion includes using Nostr as a transport. **Craig Raw**, the developer behind Sparrow Wallet, argued for considering broader communication between wallets and raised privacy concerns about the transport choice. A key unresolved question is whether encryption should depend on wallet descriptors or a separate secret. Descriptor-based recovery could be convenient, but anyone who has obtained the relevant extended public keys may also gain access to the labels. **What it means:** This is a design discussion, not a standard that all wallets already support. It shows that Bitcoin privacy also depends on protecting the information we attach to our transactions. **Sources:** [Bitcoin Optech’s summary and links to the original discussion](https://bitcoinops.org/en/newsletters/2026/10/02/) · [BIP329 wallet-label format](https://github.com/bitcoin/bips/blob/master/bip-0329.mediawiki) ## This week’s perspective Lightning reliability remains the most practical theme: review the release notes for the implementation you actually use and distinguish security disclosures from confirmed thefts. Meanwhile, Silent Payments and encrypted label synchronization show progress toward better wallet privacy. **Which matters most to you: reliable Lightning routing, private payments, or easier wallet management?** --- *Bitcoin Thursday follows the technology behind the headlines.* *There is no order without chaos!* <center> ![chaosmagic23](https://i.imgur.com/k0RmE7l.gif) [![learn Bitcoin - Earn Sats](https://ipfs.3speak.tv/ipfs/QmYYYqzPPHnv4GmRV8fCNA3Ts94KnVyTHTFMqFRThbzoVB)](https://satsman.com?ref=chaosmagic23&c=grow-your-army) [![Vote for the BBH Witness](https://images.ecency.com/p/62PdCouTvNPDFdqJorCLnfauvZdwTKWtZntNNFmwMaciHfYFayjqRqLJecV1xudQgyrfGq5ooM3F9CsDGvoXPVteHCYXXR359MgyWAE4mNXf7AN.png?format=match&mode=fit)](https://witness.the-hive-mobile.app/#/witnesses/@thebbhproject) <sup>[Vote for the BBH Witness](https://witness.the-hive-mobile.app/#/witnesses/@thebbhproject)</sup> <br> ![v4v.app](https://images.ecency.com/DQmV6sp6A93pm4PP62g4cuFcUSvSRac1aa6iZvpLh14WL7D/image.png) <sup>chaosmagic23@sats.v4v.app</sup><br> </center> *Images and screenshots are from me or AI generated* <sub>Posted via [HiveSuite](https://hivesuite.app/@chaosmagic23/bitcoin-thursday-october-8-2026-d3wirxnz)</sub>

View this post on HiveSuite