Bitcoin Optech #432 covers DCPPs, Eclair DoS fix, and Stratum V2 testing
Summary
The newsletter discusses decentralized mining pool payout protocols and the 'rich list attack' where large miners dominate outputs. It details a memory exhaustion DoS vulnerability in Eclair v0.14.0 fixed in v0.14.1. The episode covers stale tip relay debates and software updates including Lightning v16.0.8 and Coldcard firmware. It highlights industry adoption of Stratum V2 by Foundry and Mara Foundation. Finally, it lists privacy and stability fixes in Bitcoin Core and Lightning implementations.
Key takeaways
- 1 Single Coinbase output payouts for join pools are obstructed because miners vary the coinbase transaction for extra nonce space, making the transaction size unknown until a block is found, preventing pre-signing of exit transactions.
Unidentified speaker (speaker_0) · 1:19
- 2 COM, who ran a public P2 pool node, examined two five hundred forty, five P two pool Coinbase transactions, and argued that growth alone, without any attacker, squeezed out small miners because P two pool raised the share difficulty of miners expected to earn under zero. Zero zero one BTC per block.
Unidentified speaker (speaker_0) · 2:27
Episode sections
- 0:00 – 3:07
Newsletter Overview and Mining Pool Payouts
The newsletter covers decentralized mining pool payouts, a DoS vulnerability in Eclair, and stale tip relay discussions. It highlights an analysis by Developer 7D5X9 on decentralized Coinbase payout protocols (DCPPs) and the challenges of scaling outputs without covenants.
- 3:07 – 4:27
Eclair DoS Vulnerability Disclosure
A memory exhaustion DoS vulnerability in Eclair v0.14.0 was disclosed, fixed in v0.14.1. The bug allowed peers to crash nodes by exploiting a missing lower-bound check on batch sizes in BOLT2 messages.
- 4:27 – 6:11
Stale Tip Relay Discussion
Antoine Poinsot suggested relaying only headers for stale blocks to prevent incentivizing selfish mining, while Anthony Towns argued that relaying full block data is necessary to settle disputes and that the revenue gain for selfish miners is small but calculable.
- 6:11 – 10:14
Software Updates and Service Changes
Updates include Lightning v16.0.8 making Taproot default, Coldcard firmware adding Codel 30/2 support, Wavelength on Mainnet, BullBitcoin making PayJoin default, and Stratum V2 testing by Foundry and Mara Foundation.
- 10:14 – 19:45
Bitcoin Core and Lightning Fixes
Bitcoin Core 30.6750.7 fixed a Tor/I2P privacy leak. Core Lightning 9730 added HTLC recovery tools. LDK fixed channel ID collisions and fee budget overruns. LND fixed invoice expiry validation and HDLC recovery issues.
Assets discussed
| Asset | Kind | Stance | Context |
|---|---|---|---|
| BitcoinBTC | crypto | neutral | describing notable. changes to popular Bitcoin, Infrastructure Software |
“Stance” is how the speakers talked about the asset, not a recommendation.
Claims worth verifying
Developer 7D5X9 posted an analysis to Delving Bitcoin arguing that decentralized Coinbase payout protocols (DCPPs) do not scale because mining firmware limits Coinbase transaction size and each output displaces fee-paying transactions.
Unidentified speaker (speaker_0) ·0:39
How to verify: Check Delving Bitcoin archives for posts by 7D5X9 regarding DCPPs and mining firmware limits. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
A rich list attack allows a large miner splitting hash rate across identities to outrank small miners in Coinbase transaction outputs if the pool has more miners than outputs.
Unidentified speaker (speaker_0) ·0:59
How to verify: Review the Delving Bitcoin post by 7D5X9 cited in the newsletter for the technical explanation of the rich list attack vector. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
The Eclair DoS vulnerability affected version 0.14.0 and was fixed in version 0.14.1, released in July 2020.
Unidentified speaker (speaker_0) ·3:27
How to verify: Check Eclair GitHub releases for v0.14.0 and v0.14.1 release dates and changelogs. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
The Eclair vulnerability exploited a missing lower-bound check on the batch size field in BOLT2 start batch messages, allowing a batch size of zero.
Unidentified speaker (speaker_0) ·3:47
How to verify: Review BOLT2 specification for batch size constraints and Eclair source code commits fixing the lower bound check. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Anthony Towns estimated that a pool with 20% network hashrate gains approximately 16.1 BTC per year by mining on its own block instead of a competing block.
Unidentified speaker (speaker_0) ·5:31
How to verify: Check the Bitcoin Dev mailing list thread on BIP332 stale tip relay for Anthony Towns' calculations and arguments. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Lightning v16.0.8 makes Taproot the default for new wallets.
Unidentified speaker (speaker_0) ·6:21
How to verify: Check Lightning Labs release notes for v16.0.8. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Coldcard firmware versions 5.6.3 and 1.5.3Q add support for generating and importing Codel 30/2 secrets.
Unidentified speaker (speaker_0) ·6:41
How to verify: Check Coinkite website or GitHub for Coldcard firmware release notes. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Mara Foundation mined its first block using Stratum V2.
Unidentified speaker (speaker_0) ·8:20
How to verify: Check Mara Foundation blog or Twitter for announcements regarding Stratum V2 block mining. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Bitcoin Core 30.6750.7 fixes a privacy leak in address discovery over Tor and I2P where malicious peers could claim to see the node at an arbitrary routable IP.
Unidentified speaker (speaker_0) ·10:34
How to verify: Check Bitcoin Core GitHub commit 30.6750.7 or release notes for the Tor/I2P privacy fix. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Core Lightning 9730 adds the lightning_sontool recover command to manually recover HTLC outputs after local channel state loss.
Unidentified speaker (speaker_0) ·11:33
How to verify: Check Core Lightning documentation or GitHub for the 9730 release notes and lightning_sontool details. For recent events, verify 2026-08-20 through 2026-11-20. Use another period only when the speaker explicitly names it.
Do your own research
- Verify Eclair v0.14.1 release notes and BOLT2 specification for batch size enforcement.
- Check P2Pool share difficulty metrics and historical earnings data for small miners.
- Review Bitcoin Core 30.6750.7 changelog for Tor/I2P privacy leak details.
- Examine Coldcard firmware release notes for Codel 30/2 and Shamir share implementation.
- Monitor Foundry and Mara Foundation Stratum V2 adoption status.
- Analyze Anthony Towns' calculation of selfish mining revenue gains.
- Assess DCPP scalability challenges without covenants.
- Review Lightning v16.0.8 Taproot default implications.
Full transcriptexpand
0:00Unidentified speaker (UNKNOWN): This
0:00Unidentified speaker (speaker_0): week's newsletter Summarize is an analysis of decentralized mining pool payouts, describes the disclosure of a fixed denial of service vulnerability in ECLIR, and links to continued discussion about whether stale tip relay should include block data. Also included are our regular sections describing recent changes to services and client software, announcing new releases and release candidates, and describing notable. changes to popular Bitcoin, Infrastructure Software, News, Framework for Decentralized Mining Pool Payouts, Developer 7D5X9, posted to Delving Bitcoin an analysis of how decentralized mining pools can pay miners directly from Coinbase transactions, which the Postcalls to Decentralized Centralized Coinbase, Payout Protocols, DCPPs, giving every miner its own. output does not scale because mining firmware limits Coinbase transaction size, and each output displaces fee-paying transactions. The Post argues that when a pool has more miners than outputs, any rule ranking miners by work allows a rich list attack, where a large miner splits its hash rate across identities that each still outrank the smallest miners, pushing them out of the Coinbase transaction. According to seven D five X9, earlier designs only move this problem.
1:19Braidpool shifts it from who receives an output to who controls the pool's threshold key newsletter three hundred forty. For a single coinbase output paying a join pool with unilateral exits, the obstacle is that miners vary the coinbase transaction for extra noncy space, so its T's, it is unknown and exit. transactions, cannot be signed until a block is found. 7D5X9 believes this leaves the output controlled by a single key or threshold of keys until a soft fork enables rebindable signatures, such as those proposed in BIP 440 8. 7. In sketches based on spark style state chains and on arc, an attacker keeping one small claim. per subtree can block cheap cooperative settlement, raising miners' costs, though the POST considers this. Less severe for ARC, the POST concludes that a join pool does not decide which out, puts enter the Coinbase transaction. It sees two options for that evaluated random draw, an idea credited to Matt Corrallo, or Out, puts reserved for designated operators. Learn Bitcoin.
2:27COM, who ran a public P2 pool node, examined two five hundred forty, five P two pool Coinbase transactions, and argued that growth alone, without any attacker, squeezed out small miners because P two pool raised the share difficulty of miners expected to earn under zero. Zero zero one BTC per block. For its successor P two pool two, Jungly Jungley suggested a limit of sixteen out. outputs given current firmware. Stephen Roos replied that he could not think of a scheme worth exploring without covenants, which would let a Coinbase output deterministically commit to an ARC transaction tree that pays every miner who uses the same ARC server. Disclosure of a do S vulnerability in Eclair, ROAP Raupe posted to Delving Bitcoin the responsible disclosure of a memory exhaustion denial. of service due S vulnerability affecting Eclair version 0, 14, 0 and fixed in july 2020, six in release zero, fourteen, one, any peer able to connect to a vulnerable node could crash it, even without having a channel with it. The bug gave an attacker no direct access to funds, but repeatedly crashing a node could put its channel funds at risk. Users still running zero. 14, 0 should upgrade, the attack vector leveraged a missing size check in Eclair. According
3:47to Bold II, messages can be sent in batches to be treated as a single logical update through the start batch message, which among other fields carries the batch size. According to the specifications, the size must be at most twenty and strictly greater than one, while Eclair checked for the upper bound, it did not enforce the lower one. An attacker would have been able to use this vulnerability by sending a start batch message with batch size equals zero, followed by commitment signed messages, which are sent in batches during splicing. Since the code stopped adding messages to its internal batch, only once the number of received messages reached the batch size, which was zero, thus always lower than the number of messages received. The list never stopped growing, leading to memory exhaustion. The vulnerability was fixed by having the code check the lower bound two, as specified in bold two. Continued discussion of stale tip relay. Antoine Poinsot replied to the Bitcoin Dev mailing list thread about BIB three hundred thirty, two stale tip relay, C see newsletters four, hundred seventeen and four hundred twenty.
4:51three, to suggest that nodes initially relay only the headers of stale blocks, Pointsot argued that headers are enough to make stale blocks observable. Relaying the block data as well lets nodes reorganise faster to a chain built on a stale block, which increases the expected revenue of a miner that briefly keeps mining on its own block after. Losing a block race, Pointsart Poinsart considered the that effect most likely small, but not worth working out rigorously. Anthony Towns replied that any miner who would benefit can cheaply implement stale block relay itself. Townes estimated that a pool with twenty per cent of network hashrate already gains about sixteen. One B to C per year by mining on its own block instead of a competing block, it saw first at the same height, and that, cutting the relay delay of the resulting one block reorg from five seconds to one would raise that to sixteen. Thirty six BTC. Towns also argued that stale headers can raise concerns, such as possible selfish mining,
5:51but only the block data can settle them. Poinsot agreed that the estimate appears to cover the effect on honest mining incentives, and, while still seeing most of the value in headers, did not want to block. relaying full blocks. Changes to services and client software. In this monthly feature, we highlight interesting updates to Bitcoin wallets and services. Liner V16, Zero released, Liner V16. 8 form at C Newsletter 424 and makes Taperoot the default for new wallets. Cold card firmware adds Codex 30, 2 backups, Coinkite announced Cold Card Firmware versions 5, 6, 3 and 1, 5, 3Q, which adds support for generating and importing Codex 30, 2 secrets, and for splitting the devices. Wallet into 2 to 9 Shamia shares for later recovery. The releases also add support for Perin. Perrin, Put height and time lock times in PSPT. PSBTV 2 transactions. Wavelength released on Maynet. Lightning Labs announced that Wavelength, its arc-like payments toolkit C Newsletter 415, is available on
7:00Maynet as an alpha with accounts limited to 3, 100, 0, €0 SATs. Bull Bitcoin makes PayJoin the default for exchange orders. BullBitcoin announced that on-chain purchases and sales made on its exchange through the BullBit. BullBitcoin mobile wallet now use Pageoin by. Default C Newsletter three hundred thirty eight version six fourteen. Zero of the wallet also adds experimental support for sending and receiving silent payments. Breeze SDK adds silent payment sending version zero twenty eight. Zero of the Spark Spark-based based Breeze SDK adds support for sending to silent payment addresses. Silent Payments Scanner for Electrum Plugin. Oli Shiriyev announced us be scanned, a watch-only silent payments scanner that works with the electrum sending plugin covered in newsletter 419. It can scan for payments using the user's own Bitcoin core node, a blind bit server, or a For blind bit server combined with compact block filters from P2P peers. Stratum V2 releases and pool adoption, the Stratum V2 reference implementation released as V2 apps v0, 9, 0, which adds support for Bitcoin Core 30, 2, X, including submitting found blocks over its IPC, interface and hardens its job declarator Client C
8:20Newsletter 3, 180, 4 for previous coverage. Separately, Mara Foundation and announced that Mara mined its first block using Strotum V2, and Foundry announced that it has begun testing Strotum V2 on its pool. Coinswap renamed to OpenSwap, OpenSwap V0, 2. 3 is the first release under the new name of the Coinswap Protocol implementation, formerly called Coinswap, C see Newsletter 4, 415. 115. It adds an Electrum Server backend option. swaps that pay a third-party address, and when built with lightning support, swaps between on-chain funds and LN through LDK server see Newsletter 406. Releases and release candidates. Please consider upgrading to new releases or helping to test release candidates. Core Lightning 26. 12RC1 is a release candidate for the next major version of this popular LN node implementation. It will be the first major release since 2060
9:27and covers two release cycles. It adds a tool for recovering HDLC out, puts after channel state loss, C see Core Lightning 9730 below, improves payment pathfinding. see Newsletters 418 and 430, and adds experimental support for a new Cooperative Close Protocol, see Newsletter 413. The release notes also announce that X Pay will replace Pay in 27. Notable code and documentation changes. Notable recent changes in Bitcoin Core, Core Lightning, Eclair, LDK, LN. LD, Libsect 2, 150, 6K1, Hardware Wallet Interface, HWI, Rust Bitcoin, B2C Pay Server, BDK, Bitcoin Improvement Proposals, BIPS. Lightning Bolts, Lightning Blips, Bitcoin Inquisition, and Binonas. Bitcoin Core 30, 6750. 7 fixes a privacy leak in address discovery over Tor and I2P. Previously, when a node connected outbound to a malicious Tor or I2P peer, that peer could claim to see the node at an arbitrary routable IP
10:34address in its version message. Bitcoin Core could then advertise that address back to the peer, along with its own Clonet listening port. A distinctive port could then help correlate the connection with the Clonet node that was observed using the same port, see newsletter 50. 2. for an earlier Tor listening port fix. Bitcoin Core now ignores the address that Tor and I2P Pierce report, seeing the node at. BIP 2003, 150. 6 replaces the placeholder Genesis parameters in BIP 90, 5 with those of the mind testnet 5 Genesis block, and marks the BIP as deployed. The Genesis Coinbase includes the date 2, 100 2005. 2006, 111 14, and the hash of Mainnit block 9, 175, 7, 144. Committing to that hash ensures that the testnet 5 Genesis block could only be mined after Maine. It reached that height. See Newsletter 4, 130. Core For Lightning 9730 adds the lightning. Sontool Suntool recover took command to manually recover. HTLC out, puts after local channel, state loss. Once the peer publishes its latest commitment transaction, the recovering node can already reclaim its main output using a static channel backup.
11:54Given the local HSM secret, channel and HTLC HDLC details, and the peers per commitment point, the new command identifies matching HDLC. outputs. The tool constructs signed transactions to reclaim outgoing HDLCs after a timeout or to claim incoming HDLCs with known primages. However, the operator must manually review and broadcast the transactions. A cooperative CLN peer Here, can export the public point using the dump commitments point, only command without revealing secret. secrets. LDK 5005, 160. One fixes a potential loss of forwarded funds when a peer sends revoke and ACK before LDK sends the corresponding commitment signed message. Previously, LDK could accept this premature acknowledgement and advance its internal commitment number. Consequently, it could sign a commitment that differed from the one recorded by its on-chain monitor. If the peer published that commitment,
12:54LDK might fail to claim the incoming HDLC, even after paying the outgoing HDLC, despite knowing its primage. LDK now rejects the premature acknowledgement and force closes the channel. The fix was released in ADK 02 8C Newsletter 430 431. 1. Newsletter 420 4206 6 described an earlier bug. that left a signed commitment. Unmonitored during reconnection. LDK 5005, 160, 2 and 5005, 140, 5 fixed channel ID collisions that a malicious peer could create between its channels and an LDK node. In the first, the peer could reuse a force closed channels known ID as a new channel's temporary ID. This could prevent LDK from recording a force. forwarded payments primage in the closed channels monitor, leaving the incoming HDLC unclaimed after the outgoing HDLC had been paid. In the second, the peer could calculate a channel's future final ID from its funding transaction, and submit another opening request with that temporary ID. If the original channel adopted its final ID before the application accepted the new request, acceptance could overwrite its funded state. LDK now rejects conflicting ID and rechecks them at acceptance. Both fixes were also released in LDK zero, two, eight.
14:13See newsletter four hundred twenty seven for related channel ID collisions that could cause a do S in Eclair. LDK five thousand five hundred fifty seven fixes a vulnerability that allowed malicious requests. peers to disrupt transaction monitoring on nodes using an electrum back end. The peer could propose a channel whose claimed funding output reused an already watched out point, but with a different locking script. Registering that proposal could overwrite the legitimate watch's stored script, even if LDK K subsequently rejected the channel. LDK would then query Electrum for transactions associated with the bogus script, and might miss a transaction spending the real output, preventing a timely response to a channel closure. LDK now retains every distinct script registered for an outpoint, so a bogus registration cannot suppress the legitimate watch. This fix was also released in LDK 0, two, eight, LDK five thousand five hundred and fifty, eight and five thousand four hundred and eighty. two fixed two ways payments could exceed their fee budget. The first PR addresses the handling of an omitted fee limit setting for a sink payments using static bolt, twelve invoices, see newsletter three hundred twenty one. LDK now applies its default cap of one percent of the payment amount plus fifty
15:33sat when the application omits the setting. Previously omitting it removed the limit entirely. allowing a malicious receiver to supply a blinded path with excessive fees. This fix was also released in LDK 0, 2, 8, the second PR addresses retries when a route adds value to meet an HTLC minimum. LDK treated the extra value as part of the requested payment, and restored the failed path's fee budget on retry, allowing the total spend to exceed its limit. LDK now retries only the remaining amount owed and counts any excess against the remaining fee budget. LD 110050 5 changes how LD reports non AMP invoices as settled. Although applications could already monitor when the settlement of individual HDLCs HTLCs was locked in off chain chain's C Newsletter. 224 L LD D could mark an invoice as settled. as soon as the primage was released. The invoice now enters the pending settle state on primage release. Once every HTLC in the payment has a final off-chain or on chain outcome, L and D marks the invoice as settled if all parts were collected or cancelled if any failed. A cancelled invoice can still have collected some parts, which are not refunded, so applications should credit only the amounts from the finalized, successful
16:52HDLCs. An invoice's primage released flag records whether LD has committed to releasing the primage. MP payment sets still settle at Primage Release. LD 110050. One fixes expiry validation when completing multipath payments and AMP payments. Previously, L and D checked each HDLC when it arrived. If more blocks were mined while the receiver waited for the remaining parts, L and D could release primages even though an earlier HDLC no longer had the required expiry margin for on-chain collection. Now LND rechecks every part against the current block height when the final part arrives. If a previously accepted part is now too close to expiry, L LND and D fails that set and leaves the invoice open for another attempt. See Newsletter 4, 120, 4 for earlier work on cancelling individual AMP sets. LND 11004, 170, 2 and 1008, 140, 2 fixed cases where temporary bekend errors or one problematic input could block otherwise valid sweeps. The first keeps inputs available for retry after temporary or unclassified errors during Memphol. Mempool acceptance. Checks. C Newsletter 370, 3. It was released in LD 0, 20, 1, 8 beta and 0,
18:1120, 8 beta C Newsletter 4301. The second uses diagnostic transactions that are never. Broadcast to test subsets assets of a rejected batch. If an invalid or conflicting input can be identified, LD LND excludes. it from the next attempt and retries the remaining inputs. Asterisk L D eleven thousand five hundred forty two fixes recovery of forwarded HDLCs after channel reconnections. When replaying stored forwarding batches, L and D could filter out acknowledged HDLCs and then use the remaining ENT, NT, his is new positions to look up metadata indexed by their original positions. This could cause unresolved HDLCs to be skipped or misassociated. Additionally, if a channel's HDLC handler stopped after LD recorded the batch, but before handing off an HDLC, an incomplete record could be left behind, causing retries to be discarded as duplicates, L and D now preserves the original batch indexes and removes incomplete records after a failed handle. handoff, allowing unresolved HDLCs to be retried. The fix was released in L and D 0 20 1 8 Beta and 0 20 8 Beta C Newsletter four hundred thirty one want more. For more discussion about the topics mentioned in this newsletter,
19:31join us for the weekly Bitcoin Optech Optec recap on Riverside. FM at seventeen thirty UTC on november twenty fourth. four. The discussion is also recorded and will be available from our podcasts page.