This week’s newsletter describes a paper and a short discussion about probabilistic path selection for LN and includes our regular sections with summaries of popular questions and answers from the Bitcoin StackExchange, release and release candidates, and notable changes to Bitcoin infrastructure software.
- ● Upgrade BTCPay Server to 126.96.36.199: this release fixes “one critical and several low-impact vulnerabilities that affected BTCPay Server versions 188.8.131.52 and older”, according to the project’s release notes.
● Paper on probabilistic path selection: René Pickhardt posted to the Lightning-Dev mailing list a paper he co-authored with Sergei Tikhomirov, Alex Biryukov, and Mariusz Nowostawski. The paper models a network of channels having a uniform distribution of balances within their respective channel capacity. E.g., for a channel with the capacity of 100 million satoshis between Alice and Bob, the paper assumes all of the following states are equally as likely for that channel, and that the same holds true for every other channel on the network:
Alice Bob 0 sat 100,000,000 sat 1 sat 99,999,999 sat … … 100,000,000 sat 0 sat
Making this assumption allows the authors to draw conclusions about the probability that a payment will succeed based on its amount and how many hops (channels) it needs to traverse. This allows the authors to prove the benefit of several known heuristics—such as keeping paths short and using multipath payments to break larger payments into smaller payments (under certain other assumptions). They also use the model to evaluate new proposals, such as allowing Just-In-Time (JIT) rebalancing via bolts #780.
The paper uses its conclusions to provide a routing algorithm that it claims can reduce payment retry attempts by 20% compared to their simplification of existing routing algorithms. The new algorithm prefers routes with a higher computed probability of success, whereas existing algorithms use a heuristic approach. Combined with JIT rebalancing, they estimate a 48% improvement. Given that each retry usually requires several seconds, and could take much longer in some cases, this could provide an improved user experience. The algorithm was tested against several example networks, including one drawn from a snapshot of almost 1,000 live channels.
The paper deliberately does not take routing fees into consideration, and most responses on the mailing list focused on how to use the results while still ensuring users don’t pay an excessive amount of fees.
● Updated article about payment batching: Optech has published an article about payment batching, updated from our original announcement of it in Newsletter #37. Payment batching is a technique that can help spenders save up to 80% on transaction fees.
Selected Q&A from Bitcoin StackExchange
Bitcoin StackExchange is one of the first places Optech contributors look for answers to their questions—or when we have a few spare moments to help curious or confused users. In this monthly feature, we highlight some of the top-voted questions and answers posted since our last update.
● How hard is it for an exchange to adopt native segwit? Bitcoin developer instagibbs lists a few considerations for exchanges implementing native segwit including address generation, ensuring spendability, support and business considerations, and compatibility of signing infrastructure like Hardware Security Modules (HSMs).
● How do you calculate when 98% of Bitcoin will be mined? While Murch provides an estimate of 2030-2031 for when 98% of all bitcoins will be mined, he also links to a reward schedule Google Sheet with additional metrics.
● How can I use Bitcoin Core with the anonymous network protocol I2P? With the merge of Bitcoin Core #20685, Bitcoin supports the I2P network. Michael Folkson summarizes Jon Atack’s original thread on how to configure Bitcoin Core to use I2P.
● Will nodes with a larger-than-default mempool retransmit transactions that have been dropped from smaller mempools? Pieter Wuille notes that transaction rebroadcasting is currently a wallet responsibility, that perhaps nodes should also rebroadcast unconfirmed transactions, and points to Bitcoin Core #21061 as working toward that goal.
● Should block height or MTP or a mixture of both be used in a soft fork activation mechanism? David A. Harding outlines the advantages and disadvantages of both Median Time Past (MTP) and block heights as timing mechanisms within Bitcoin. MTP roughly corresponds to clock time but can be manipulated by miners to skip a signaling period. Block heights are not consistent but are also not miner-gameable in the same way as MTP.
● Why is it recommended to “not send round number amounts when making payments” for increased privacy? User chytrik provides different examples to illustrate the round number heuristic and why avoiding round payment amounts can be better for privacy.
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.
Notable code and documentation changes
Notable changes this week in Bitcoin Core, C-Lightning, Eclair, LND, Rust-Lightning, libsecp256k1, Hardware Wallet Interface (HWI), Rust Bitcoin, BTCPay Server, Bitcoin Improvement Proposals (BIPs), and Lightning BOLTs.
● Bitcoin Core #17227 adds a new
make apktarget to the build system which packages bitcoin-qt for the Android operating system. This continues previous work which added support for packaging the Android NDK. Also included are documentation for building Bitcoin Core for Android and a continuous integration job to test the Android build system.
● Rust-Lightning #849 makes a channel’s
cltv_expiry_deltaconfigurable and reduces the default value from 72 blocks to 36 blocks. This parameter sets the deadline by which a node must settle a payment attempt with its upstream peer after learning from its downstream peer whether that payment succeeded; it must be long enough to confirm a transaction onchain if necessary but should be short enough that it’s competitive with other nodes that are trying to minimize possible delays. See also Newsletter #40 where LND reduced its value to 40 blocks.
● C-Lightning #4427 makes it possible to experiment with dual funded payment channels by using the configuration option
--experimental-dual-fund. Dual funding allows funds for the initial channel balance to be contributed by both the node initiating the channel and the node accepting the channel, which can be useful for merchants and other users who want to begin receiving payments as soon as the channel finishes opening.
● Eclair #1738 updates the penalty enforcement mechanism for revoked HTLCs when anchor outputs are being used. A change unrelated to anchor outputs, but introduced at the same time they were added to the protocol, created the possibility to combine multiple
SIGHASH_SINGLE|SIGHASH_ANYONECANPAYHTLC outputs into a single transaction (see Newsletter #128. This PR ensures that all outputs that are spendable with the revocation key are claimed in the same transaction instead of claiming only one per transaction.
● BIPs #1080 updates BIP8 with a
minimum_activation_heightparameter that delays the time nodes begin enforcing a locked-in soft fork until after the specified height. This makes BIP8 compatible with the Speedy Trial proposal (see Newsletter #139) that would allow miners to activate taproot but would not begin enforcing taproot’s rules until roughly six months after the release of software implementing Speedy Trial.