Oddbean new post about | logout
 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