This week’s newsletter summarizes several notable changes to popular Bitcoin infrastructure software.
No significant news this week.
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 #25717 adds a “Headers Presync” step during Initial Block Download (IBD) to help prevent Denial of Service (DoS) attacks and step towards removing checkpoints. Nodes use the pre-sync phase to verify that a peer’s headers chain has sufficient work before storing them permanently.
During IBD, adversarial peers may attempt to stall the syncing process, serve blocks that don’t lead to the most-work chain, or simply exhaust the node’s resources. As such, while sync speed and bandwidth usage are important concerns during IBD, a primary design goal is avoiding Denial of Service attacks. Since v0.10.0, Bitcoin Core nodes sync block headers first before downloading block data and reject headers that don’t connect to a set of checkpoints. Instead of using hard-coded values, this new design utilizes the inherent DoS-resistant property of Proof of Work (PoW) puzzles to minimize the amount of memory allocated before finding the main chain.
With these changes, nodes download headers twice during initial headers sync: a first pass to verify the headers’ PoW (without storing them) until the accumulated work meets a predetermined threshold, and then a second pass to store them. To prevent an attacker sending the main chain during presync and then a different, malicious chain during redownload, the node stores commitments to the headers chain during presync.
● Bitcoin Core #25355 adds support for transient, one-time I2P addresses when only outbound I2P connections are allowed. In I2P, the recipient learns the I2P address of the connection initiator. Non-listening I2P nodes will now by default make use of transient I2P addresses when making outbound connections.
● BDK #689 adds an
allow_dustmethod which allows a wallet to create a transaction that violates the dust limit. Bitcoin Core and other nodes which use the same settings won’t relay unconfirmed transactions unless every output (except
OP_RETURN) receives more satoshis than the dust limit. BDK usually prevents users from creating such unrelayable transactions by enforcing the dust limit on the transactions it creates, but this new option allows ignoring that policy. The author of the PR mentions that they’re using it for testing their wallet.