Bitcoin Optech newsletter #305 is here:
- describes a proposed light client protocol for silent payments
- summarizes two new proposed descriptors for taproot
- links to a discussion about whether opcodes with overlapping features should be added in a soft fork
- summarizes popular Q&A from Stack Exchange
- Optech Newsletter #305 Recap on Twitter Spaces
https://bitcoinops.org/en/newsletters/2024/05/31/
Setor Blagogee posted to Delving Bitcoin to describe a draft specification for a protocol to help lightweight clients receive silent payments (SPs)...
https://bitcoinops.org/en/newsletters/2024/05/31/#light-client-protocol-for-silent-payments
Oghenovo Usiwoma posted to Delving Bitcoin about two new proposed descriptors for constructing taproot spend conditions...
https://bitcoinops.org/en/newsletters/2024/05/31/#raw-taproot-descriptors
Pierre Rochard asks if proposed soft forks that can provide much of the same features at a similar cost should be considered mutually exclusive, or whether it would make sense to activate multiple proposals and let developers use whichever alternative they prefer...
https://bitcoinops.org/en/newsletters/2024/05/31/#should-overlapping-soft-fork-proposals-be-considered-mutually-exclusive
Selected Q&A from Bitcoin Stack Exchange:
- What’s the smallest possible coinbase tx / block size?
- Understanding Script’s number encoding, CScriptNum
- Is there a way to make an address public but hide how many BTC it contains?
- Testing increased feerates in regtest
- Why is my P2P_V2 peer connected over a v1 connection?
- Does a P2PKH tx send to the hash of the uncompressed or compressed key?
- What are different ways to broadcast a block to the Bitcoin network?
https://bitcoinops.org/en/newsletters/2024/05/31/#selected-qa-from-bitcoin-stack-exchange
Bitcoin Optech will host an audio recap discussion of this newsletter with special guests Oghenovo Usiwoma and Pierre Rochard on Twitter Spaces Tuesday at 14:30 UTC. Join us to discuss or ask questions!
https://twitter.com/i/spaces/1eaKbgnYgOBGX
Bitcoin Optech /
npub1hk…a432p
2024-05-31 11:30:37
Author Public Key
npub1hkuk45c6c6h3y0rks0z4wa0wyyud5ru0qy0rn9x4dgnjwrnfy46s5a432pPublished at
2024-05-31 11:30:37Event JSON
{
"id": "cd507ad78cc3228b0be9dcc6cba9a3c10f5e1ed9174739d15b9cd3a37c046e34",
"pubkey": "bdb96ad31ac6af123c7683c55775ee2138da0f8f011e3994d56a27270e692575",
"created_at": 1717155037,
"kind": 1,
"tags": [
[
"t",
"305"
],
[
"t",
"light-client-protocol-for-silent-payments"
],
[
"t",
"raw-taproot-descriptors"
],
[
"t",
"should-overlapping-soft-fork-proposals-be-considered-mutually-exclusive"
],
[
"t",
"selected-qa-from-bitcoin-stack-exchange"
]
],
"content": "Bitcoin Optech newsletter #305 is here:\n\n- describes a proposed light client protocol for silent payments\n- summarizes two new proposed descriptors for taproot\n- links to a discussion about whether opcodes with overlapping features should be added in a soft fork\n- summarizes popular Q\u0026A from Stack Exchange\n- Optech Newsletter #305 Recap on Twitter Spaces\nhttps://bitcoinops.org/en/newsletters/2024/05/31/\n\nSetor Blagogee posted to Delving Bitcoin to describe a draft specification for a protocol to help lightweight clients receive silent payments (SPs)...\nhttps://bitcoinops.org/en/newsletters/2024/05/31/#light-client-protocol-for-silent-payments\n\nOghenovo Usiwoma posted to Delving Bitcoin about two new proposed descriptors for constructing taproot spend conditions...\nhttps://bitcoinops.org/en/newsletters/2024/05/31/#raw-taproot-descriptors\n\nPierre Rochard asks if proposed soft forks that can provide much of the same features at a similar cost should be considered mutually exclusive, or whether it would make sense to activate multiple proposals and let developers use whichever alternative they prefer...\nhttps://bitcoinops.org/en/newsletters/2024/05/31/#should-overlapping-soft-fork-proposals-be-considered-mutually-exclusive\n\nSelected Q\u0026A from Bitcoin Stack Exchange:\n\n- What’s the smallest possible coinbase tx / block size?\n- Understanding Script’s number encoding, CScriptNum \n- Is there a way to make an address public but hide how many BTC it contains?\n- Testing increased feerates in regtest\n- Why is my P2P_V2 peer connected over a v1 connection?\n- Does a P2PKH tx send to the hash of the uncompressed or compressed key?\n- What are different ways to broadcast a block to the Bitcoin network?\nhttps://bitcoinops.org/en/newsletters/2024/05/31/#selected-qa-from-bitcoin-stack-exchange\n\nBitcoin Optech will host an audio recap discussion of this newsletter with special guests Oghenovo Usiwoma and Pierre Rochard on Twitter Spaces Tuesday at 14:30 UTC. Join us to discuss or ask questions!\nhttps://twitter.com/i/spaces/1eaKbgnYgOBGX\n",
"sig": "01cb194f22350ab50dab377b9719812bf0e26ab509f7f6f0c76ecb4db30017b2de5148dbbf7959d0c00351ee29e0dd466f76f0d287b6100e8604a605c058cc38"
}