Bitcoin Optech newsletter #210 is here:
- describes a proposed BIP for creating signed messages for non-legacy addresses
- summarizes a discussion about provably burning small amounts of bitcoin for denial of service protection
- summarizes popular questions and answers from Bitcoin Stack Exchange
- Optech Newsletter #210 Recap on Twitter Spaces
Bitcoin Core and many other wallets have long included support for signing and verifying arbitrary messages when the key used to sign them corresponds to a P2PKH address. Bitcoin Core doesn’t support signing or verifying arbitrary messages for any other address type, including addresses covering single-sig P2SH-P2WPKH, native P2WPKH, and P2TR outputs...
Several developers discussed use cases and designs of onchain transactions that destroy bitcoins (“burn” bitcoins) in small increments as a proof of resource consumption...
Selected Q&A from Bitcoin Stack Exchange:
- Why do invalid signatures in OP_CHECKSIGADD not push to the stack?
- What are packages in Bitcoin Core and what is their use case?
- How much blockspace would it take to spend the complete UTXO set?
- Does an uneconomical output need to be kept in the UTXO set?
- Is there code in libsecp256k1 that should be moved to the Bitcoin Core codebase?
- Mining stale low-difficulty blocks as a DoS attack
Bitcoin Optech will be hosting an audio recap discussion of this newsletter on Twitter Spaces at 15:00 UTC. Join us to discuss or ask questions!
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!