Bitcoin Optech newsletter #288 is here:
- announces the disclosure of a block stalling bug in Bitcoin Core affecting LN
- relays a concern about how to securely open new zero-conf channels with version 3 relay
- describes a contract protocol rule when allowing an external party to contribute an input to a tx
- summarizes discussions about a proposal for new tx replacement rules to avoid pinning
- provides a brief update on the mailing list
- #288 Recap on Twitter Spaces
https://bitcoinops.org/en/newsletters/2024/02/07/
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...
https://bitcoinops.org/en/newsletters/2024/02/07/#public-disclosure-of-a-block-stalling-bug-in-bitcoin-core-affecting-ln
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...
https://bitcoinops.org/en/newsletters/2024/02/07/#securely-opening-zero-conf-channels-with-v3-transactions
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...
https://bitcoinops.org/en/newsletters/2024/02/07/#requirement-to-verify-inputs-use-segwit-in-protocols-vulnerable-to-txid-malleability
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...
https://bitcoinops.org/en/newsletters/2024/02/07/#proposal-for-replace-by-feerate-to-escape-pinning
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.
https://bitcoinops.org/en/newsletters/2024/02/07/#bitcoin-dev-mailing-list-migration-update
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!
https://twitter.com/i/spaces/1OyKAWlAaewJb
Bitcoin Optech /
npub1hk…a432p
2024-02-07 14:21:38
Author Public Key
npub1hkuk45c6c6h3y0rks0z4wa0wyyud5ru0qy0rn9x4dgnjwrnfy46s5a432pPublished at
2024-02-07 14:21:38Event JSON
{
"id": "ec24204dbb46710ca9259be69e891badaaed7f6150b89effa3c7d55fcb08410c",
"pubkey": "bdb96ad31ac6af123c7683c55775ee2138da0f8f011e3994d56a27270e692575",
"created_at": 1707315698,
"kind": 1,
"tags": [
[
"t",
"288"
],
[
"t",
"288"
],
[
"t",
"public-disclosure-of-a-block-stalling-bug-in-bitcoin-core-affecting-ln"
],
[
"t",
"securely-opening-zero-conf-channels-with-v3-transactions"
],
[
"t",
"requirement-to-verify-inputs-use-segwit-in-protocols-vulnerable-to-txid-malleability"
],
[
"t",
"proposal-for-replace-by-feerate-to-escape-pinning"
],
[
"t",
"bitcoin-dev-mailing-list-migration-update"
]
],
"content": "Bitcoin Optech newsletter #288 is here:\n\n- announces the disclosure of a block stalling bug in Bitcoin Core affecting LN\n- relays a concern about how to securely open new zero-conf channels with version 3 relay\n- describes a contract protocol rule when allowing an external party to contribute an input to a tx\n- summarizes discussions about a proposal for new tx replacement rules to avoid pinning\n- provides a brief update on the mailing list\n- #288 Recap on Twitter Spaces\nhttps://bitcoinops.org/en/newsletters/2024/02/07/\n\nEugene 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...\nhttps://bitcoinops.org/en/newsletters/2024/02/07/#public-disclosure-of-a-block-stalling-bug-in-bitcoin-core-affecting-ln\n\nMatt 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...\nhttps://bitcoinops.org/en/newsletters/2024/02/07/#securely-opening-zero-conf-channels-with-v3-transactions\n\nBastien 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...\nhttps://bitcoinops.org/en/newsletters/2024/02/07/#requirement-to-verify-inputs-use-segwit-in-protocols-vulnerable-to-txid-malleability\n\nPeter 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...\nhttps://bitcoinops.org/en/newsletters/2024/02/07/#proposal-for-replace-by-feerate-to-escape-pinning\n\nAs 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.\nhttps://bitcoinops.org/en/newsletters/2024/02/07/#bitcoin-dev-mailing-list-migration-update\n\nBitcoin 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!\nhttps://twitter.com/i/spaces/1OyKAWlAaewJb",
"sig": "b100660b2cdf6fb154d478caa554cdd0b9e1890cc7bccbb9d34547a3eb46ecab190cb7cc0db17700a7ec75a4056a6dabd8454461e49f4121711b28c03eb58716"
}