This week’s newsletter summarizes a discussion about lowering the default minimum transaction relay feerate in Bitcoin Core and other nodes. Also included are our regular sections with the summary of a Bitcoin Core PR Review Club, announcements of new releases and release candidates, and descriptions of notable changes to popular Bitcoin infrastructure projects.
● Lowering the default minimum transaction relay feerate: 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. Other node software implements similar policies.
● Alternative relay criteria: it was suggested that transactions violating certain default criteria (such as the default minimum feerate) could instead fulfill some separate criteria that make DoS attacks costly—for example, if a modest amount of hashcash-style proof of work committed to the transaction to relay.
The discussion did not reach a clear conclusion as of this writing.
Bitcoin Core PR Review Club
In this monthly section, we summarize a recent Bitcoin Core PR Review Club meeting, highlighting some of the important questions and answers. Click on a question below to see a summary of the answer from the meeting.
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.
What does the
ArgsManagerdo? Why or why not should it belong in
ArgsManager is a global data structure for handling configuration options (
bitcoin.confand command line arguments). While the consensus engine may contain parameterizable values (namely, the sizes of caches), a node does not need this data structure to stay in consensus. Rather, as Bitcoin Core-specific functionality, code handling these configuration options belongs in
What are the validation caches? Why would they belong in
When a new block arrives, the most computationally expensive part of validation is script (i.e. signature) validation for its transactions. Since nodes keeping a mempool will have usually seen and validated these transactions already, block validation performance is significantly increased by caching (successful) script and signature verifications. These caches are logically part of the consensus engine because consensus-critical block validation code needs them. As such, these caches belong in
What does it mean for something to be consensus-critical if it isn’t a consensus rule? Does
src/consensuscontain all the consensus-critical code?
Participants agreed that signature verification enforces consensus rules, while caching doesn’t. However, if the caching code contains a bug that results in storing invalid signatures, the node would no longer be enforcing consensus rules. As such, signature caching is considered consensus-critical. Consensus code doesn’t actually live in
src/consensusyet; much of the consensus rules and consensus-critical code lives in
What tools do you use for “code archeology” to understand the background of why a value exists?
Participants listed several commands and tools including
git log, entering the commit hash into the pull requests page, using the Github
Blamebutton when viewing a file, and using the Github search bar. ➚
This PR changes the type of
size_t. What is the difference between
size_t, and why should a
size_thold these values?
uint64_ttypes are 64-bits (signed and unsigned, respectively) across all platforms and compilers. The
size_ttype is an unsigned integer guaranteed to be able to hold the length (in bytes) of any object in memory; its size depends on the system. As such,
size_tis exactly suited for these variables holding the cache sizes as a number of bytes. ➚
Releases and release candidates
New releases and release candidates for popular Bitcoin infrastructure projects. Please consider upgrading to new releases or helping to test release candidates.
- ● Core Lightning 0.12.0rc1 is a release candidate for the next major version of this popular LN node implementation.
Notable code and documentation changes
Notable changes this week in Bitcoin Core, Core Lightning, Eclair, LDK, LND, libsecp256k1, Hardware Wallet Interface (HWI), Rust Bitcoin, BTCPay Server, BDK, Bitcoin Improvement Proposals (BIPs), and Lightning BOLTs.
● Bitcoin Core #25610 sets by default the startup option
-walletrbfand uses by default the
replaceableoption for the RPCs
createpsbt. Transactions created via the GUI were already opt-in RBF by default. This follows the update mentioned in Newsletter #208, enabling node operators to switch their node’s transaction replacement behavior from the default opt-in RBF (BIP125) to full RBF. RPC opt-in by default was proposed in 2017 in Bitcoin Core #9527 when the primary objections were the novelty at the time, the inability to bump transactions and the GUI not having functionality to disable RBF—all of which have since been addressed.
● Bitcoin Core #24584 amends coin selection to prefer input sets composed of a single output type. This addresses scenarios in which mixed-type input sets reveal the change output of preceding transactions. This follows a related privacy improvement to always match the change type to a recipient output (see Newsletter #181).
● Core Lightning #5071 adds a bookkeeper plugin that provides an accounting record of movements of bitcoins by the node running the plugin, including the ability to track the amount spent on fees. The merged PR includes several new RPC commands.