Bitcoin Optech newsletter #299 is here:
- newsletter describes a proposal to relay weak blocks to improve compact block performance in a network with multiple divergent mempool policies
- announces the addition of five BIP editors
- summarizes popular Q&A from Stack Exchange
- Optech Newsletter #299 Recap on Twitter Spaces
https://bitcoinops.org/en/newsletters/2024/04/24/
Greg Sanders posted to Delving Bitcoin about using weak blocks to improve compact block relay, particularly in the presence of divergent policies for transaction relay and mining. A weak block is a block with insufficient proof-of-work (PoW) to become the next block on the blockchain but which otherwise has a valid structure and set of valid transactions...
https://bitcoinops.org/en/newsletters/2024/04/24/#weak-blocks-proof-of-concept-implementation
After public discussion, the following contributors have been made BIP editors: Bryan “Kanzure” Bishop, Jon Atack, Mark “Murch” Erhardt, Olaoluwa “Roasbeef” Osuntokun, and Ruben Somsen.
https://bitcoinops.org/en/newsletters/2024/04/24/#bip-editors-update
Selected Q&A from Bitcoin Stack Exchange:
- Where exactly is the “off-by-one” difficulty bug?
- How is P2TR different than P2PKH using opcodes from a developer perspective?
- Are replacement transactions larger in size than their predecessors and than non-RBF transactions?
- Are Bitcoin signatures still vulnerable to nonce reuse?
- How do miners manually add transactions to a block template?
https://bitcoinops.org/en/newsletters/2024/04/24/#selected-qa-from-bitcoin-stack-exchange
Bitcoin Optech will host an audio recap discussion of this newsletter with special guest Gregory Sanders on Twitter Spaces Thursday at 14:30 UTC. Join us to discuss or ask questions!
https://twitter.com/i/spaces/1nAKEaQWybkKL
Bitcoin Optech /
npub1hk…a432p
2024-04-24 11:25:47
Author Public Key
npub1hkuk45c6c6h3y0rks0z4wa0wyyud5ru0qy0rn9x4dgnjwrnfy46s5a432pPublished at
2024-04-24 11:25:47Event JSON
{
"id": "11388d80ae4f1a4ec14b213dc59e8c950071e221d305aabefbaa7adb8121e549",
"pubkey": "bdb96ad31ac6af123c7683c55775ee2138da0f8f011e3994d56a27270e692575",
"created_at": 1713957947,
"kind": 1,
"tags": [
[
"t",
"299"
],
[
"t",
"299"
],
[
"t",
"weak-blocks-proof-of-concept-implementation"
],
[
"t",
"bip-editors-update"
],
[
"t",
"selected-qa-from-bitcoin-stack-exchange"
]
],
"content": "Bitcoin Optech newsletter #299 is here:\n\n- newsletter describes a proposal to relay weak blocks to improve compact block performance in a network with multiple divergent mempool policies\n- announces the addition of five BIP editors\n- summarizes popular Q\u0026A from Stack Exchange\n- Optech Newsletter #299 Recap on Twitter Spaces\nhttps://bitcoinops.org/en/newsletters/2024/04/24/\n\nGreg Sanders posted to Delving Bitcoin about using weak blocks to improve compact block relay, particularly in the presence of divergent policies for transaction relay and mining. A weak block is a block with insufficient proof-of-work (PoW) to become the next block on the blockchain but which otherwise has a valid structure and set of valid transactions...\nhttps://bitcoinops.org/en/newsletters/2024/04/24/#weak-blocks-proof-of-concept-implementation\n\nAfter public discussion, the following contributors have been made BIP editors: Bryan “Kanzure” Bishop, Jon Atack, Mark “Murch” Erhardt, Olaoluwa “Roasbeef” Osuntokun, and Ruben Somsen.\nhttps://bitcoinops.org/en/newsletters/2024/04/24/#bip-editors-update\n\nSelected Q\u0026A from Bitcoin Stack Exchange:\n\n- Where exactly is the “off-by-one” difficulty bug?\n- How is P2TR different than P2PKH using opcodes from a developer perspective?\n- Are replacement transactions larger in size than their predecessors and than non-RBF transactions?\n- Are Bitcoin signatures still vulnerable to nonce reuse?\n- How do miners manually add transactions to a block template?\nhttps://bitcoinops.org/en/newsletters/2024/04/24/#selected-qa-from-bitcoin-stack-exchange\n\nBitcoin Optech will host an audio recap discussion of this newsletter with special guest Gregory Sanders on Twitter Spaces Thursday at 14:30 UTC. Join us to discuss or ask questions!\nhttps://twitter.com/i/spaces/1nAKEaQWybkKL",
"sig": "442ac88384be0cc5cd289cf3a7d63db178f394b5af740cd593cabe76fe879e2d84fb994071ab54c062630868790e54186dcc1cd95ea3df4e599a530e85d6780a"
}