Bitcoin Optech Newsletter #426

AI editorial brief — source checked

This week's Bitcoin Optech Newsletter #426 covers a draft BIP for dynamic one-byte message type IDs in BIP324, a discussion on including BIP numbers in tagged hash tags, and a proposal for Shielded Bitcoin—a metaprotocol enabling private onchain transfers without consensus changes. It also lists new releases and security updates for Bitcoin Core, Core Lightning, LDK, and BTCPay Server, along with notable fixes in various infrastructure projects.

1. A draft BIP lets each peer choose its own one-byte message type IDs for messages sent over the v2 P2P transport.
   Source evidence

   ● Dynamic one-byte message type IDs for BIP324: Anthony Towns posted to the Bitcoin-Dev mailing list a draft BIP that lets each peer choose its own one-byte message type IDs…
2. The goal of the proposed metaprotocol is to transfer bitcoin privately, revealing neither the amount transferred nor the counterparties involved in the transaction.
   Source evidence

   The goal of the proposed metaprotocol is to transfer bitcoin privately, revealing neither the amount transferred nor the counterparties involved in the transaction. It aims…
3. Bitcoin Core #36277 fixes a potential transaction origin privacy leak in the experimental, opt-in private broadcasting feature.
   Source evidence

   ● Bitcoin Core #36277 fixes a potential transaction origin privacy leak in the experimental, opt-in private broadcasting feature (see Newsletters #388 and #425). Previously,…
4. Core Lightning 26.06.9 is a security release that fixes vulnerabilities in channel reestablishment, splicing, HTLC handling, and access controls.
   Source evidence

   ● Core Lightning 26.06.9 is a security release of this popular LN node implementation. It fixes vulnerabilities in channel reestablishment, splicing, HTLC handling, and…
5. LDK #5057 fixes a vulnerability that could allow a malicious channel peer to steal the value of a forwarded HTLC.
   Source evidence

   ● LDK #5057 fixes a vulnerability that could allow a malicious channel peer to steal the value of a forwarded HTLC. During reconnection, a peer could falsely claim in a…

What remains uncertain: The text does not establish whether the Shielded Bitcoin metaprotocol has been implemented beyond the paper proposal, nor does it confirm adoption timelines for the dynamic message type IDs BIP.