Bitcoin Optech #288: Block Stalling Bug in Core, Zero-conf Channels with v3 Transactions & More
This issue discusses Bitcoin Core bug impacting LN, concern about how to securely open new specific zero-conf channels, contract protocol rules, proposal to prevent transaction pinning, and provides a Bitcoin-Dev mailing list update.
- "Eugene Siegel announced to Delving Bitcoin a bug in Bitcoin Core he had responsibly disclosed almost three years ago. Bitcoin Core 22 and higher contain fixes for the bug, but many people are still running affected versions..."
- "Matt Corallo posted to Delving Bitcoin to discuss how to securely allow zero-conf channel opening when the proposed v3 transaction relay policy is being used..."
- "Bastien Teinturier posted to Delving Bitcoin to describe an easy-to-overlook requirement for protocols where a third party contributes an input to a transaction whose txid must not change after a different user contributes a signature to the transaction..."
- "Peter Todd posted to the Bitcoin-Dev mailing list a proposal for a set of transaction replacement policies that can be used even when existing replace-by-fee (RBF) policies won’t allow a transaction to be replaced..."
- "As of this writing, the Bitcoin-Dev mailing list is no longer accepting new emails as part of the process of migrating it to a different list server. Optech will provide an update when the migration is complete."
- "Bitcoin Optech will host an audio recap discussion of this newsletter with special guest Bastien Teinturier on Twitter Spaces Thursday at 15:00 UTC. Join us to discuss or ask questions!"
