Rust Bitcoin 0.29 is a major new release series. Its release notes note that it includes breaking API changes but also numerous new features and bug fixes, including support for compact block relay data structures (BIP152) and improvements to taproot and PSBT support...
Discreet Log Contracts (DLCs) allow a trusted third party known as an oracle to attest to a piece of data. Individuals who trust that oracle can use that attestation in contracts without revealing to the oracle that a contract exists or what its terms are, among other benefits of DLCs.
This week, Lloyd Fournier posted to the DLC-Dev mailing list about the benefits of having an oracle make their attestation using Boneh-Lynn-Shacham (BLS) signatures...
Bitcoin Optech newsletter #213 is here:
- describes how BLS signatures could be used to improve DLCs without consensus changes to Bitcoin
- Rust Bitcoin 0.29 and Core Lightning 0.12.0rc2 releases
- Optech Newsletter #213 Recap on Twitter Spaces
Default minimum transaction relay feerates are the policy implemented by nodes for ignoring individual unconfirmed transactions whose feerate is below a certain amount...
'Decouple validation cache initialization from ArgsManager is a PR' by Carl Dong that separates node configuration logic from the initialization of signature and script caches. It is part of the libbitcoinkernel project...
Bitcoin Core only relays individual unconfirmed transactions that pay a feerate of at least one satoshi per vbyte (1 sat/vbyte). If a node’s mempool fills with transactions paying at least 1 sat/vbyte, then a higher feerate will need to be paid. Transactions paying a lower feerate can still be included in blocks by miners and those blocks will be relayed...
Bitcoin Optech newsletter #212 is here:
- summarizes a discussion about lowering the default minimum transaction relay feerate in Bitcoin Core and other nodes
- recaps the "Decouple validation cache initialization from ArgsManager" Bitcoin Core PR Review Club Meeting
- adds a 'Default minimum transaction relay feerates' topic
- Optech Newsletter #212 Recap on Twitter Spaces
Bitcoin Optech will be hosting an audio recap discussion of this newsletter with Andrew Chow on Twitter Spaces at 15:00 UTC. Join us to discuss or ask questions!
Andrew Chow posted a proposed BIP to the Bitcoin-Dev mailing list for allowing a single descriptor to specify two related BIP32 paths for HD key generation. The first path would be for generating addresses to which incoming payments could be received. The second address would be for internal payments within the wallet, namely returning change back to the wallet after spending a UTXO.
Bitcoin Optech newsletter #211 is here:
- describes a proposal to allow multiple derivation paths in a single output script descriptor
- Optech Newsletter #211 Recap on Twitter Spaces
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!
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
Several developers discussed use cases and designs of onchain transactions that destroy bitcoins (“burn” bitcoins) in small increments as a proof of resource consumption...
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...
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
Changes to services and client software:
- LNP/BP release Storm beta software
- Robinhood supports bech32
- Sphinx announces VLS signing device
Bram Cohen posted about the problem of fee sniping and suggests keeping transaction fees at about 10% of total block rewards (the remainder being subsidy) as a possible solution.
Tail emission is not inflationary starts with an argument by Peter Todd that perpetually paying miners with newly created bitcoins will not lead to the number of bitcoins in circulation increasing forever
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!