-
Notifications
You must be signed in to change notification settings - Fork 146
Newsletters: add 389 (2026-01-23) #2617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
bitschmidty
wants to merge
6
commits into
bitcoinops:master
Choose a base branch
from
bitschmidty:2026-01-23-newsletter
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8a99dea
Newsletters: add 389 (2026-01-23)
bitschmidty 5f9b57a
Added Pickhardt item.
TumaBitcoiner 1a34734
Update _posts/en/newsletters/2026-01-23-newsletter.md to fix the build
bitschmidty ae57e9b
News389: fixup payment channel news item spacing, formatting
bitschmidty 9324989
News389: add client services segment
bitschmidty 25586c8
News389: add lede
bitschmidty File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,100 @@ | ||
| --- | ||
| title: 'Bitcoin Optech Newsletter #389' | ||
| permalink: /en/newsletters/2026/01/23/ | ||
| name: 2026-01-23-newsletter | ||
| slug: 2026-01-23-newsletter | ||
| type: newsletter | ||
| layout: newsletter | ||
| lang: en | ||
| --- | ||
| This week's newsletter links to a paper on the study of payment channel networks. | ||
| Also included are our regular sections describing recent updates to services and | ||
| client software, announcing new releases and release candidates, and summarizing | ||
| notable changes to popular Bitcoin infrastructure software. | ||
|
|
||
| ## News | ||
|
|
||
| - **A mathematical theory of payment channel networks**: René Pickhardt [posted][channels post] | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Only a quick review here, but not sure if https://bitcoinops.org/en/podcast/2024/12/12/ is applicable. Or perhaps a better resource is https://bitcoinops.org/en/newsletters/2024/12/13/#insights-into-channel-depletion that covers other items and references the deep dive |
||
| about the publication of his new [paper][channels paper] called "A Mathematical Theory of | ||
| Payment Channel Network". In the paper, Pickhardt groups several observations, gathered | ||
| during years of research, under a single geometric framework. In particular, the paper aims to | ||
| analyze common phenomena, such as channel depletion and capital innefficiencies of two-party | ||
| channels, assessing how they are inter-connected and why they are true. | ||
|
|
||
| The main paper contributions are the following: | ||
|
|
||
| - A model for feasible wealth distributions of users on the lightning network | ||
| given a channel graph; | ||
|
|
||
| - A formular for estimating the upper bound of payment bandwidth for payments; | ||
|
|
||
| - A method to estimate the likelihood that a payment is feasible (see | ||
| [Newsletter #309][news309 feasibility]); | ||
|
|
||
| - An analysis on different | ||
| [mitigation strategies][mitigation post] for channel depletion. | ||
|
|
||
| - The conclusion that two-party channels put strong constraints to the ability of liquidity to | ||
| flow between peers of the network. | ||
|
|
||
| According to Pickhardt, the insights coming from his research were the motivation behind his | ||
| recent post about using Ark as a channel factory (see [Newsletter #387][new387 ark]). | ||
| Pickhardt also provided his [collection][pickhardt gh] of code, notebooks, and papers that | ||
| were used as groundwork for his research. | ||
|
|
||
| Finally, Pickhardt opened the discussion on his work to questions and feedback from the LN | ||
| developer community on how the protocol design could be influenced by his research and on | ||
| the best use for multi-party channels. | ||
|
|
||
| ## Changes to services and client software | ||
|
|
||
| *In this monthly feature, we highlight interesting updates to Bitcoin | ||
| wallets and services.* | ||
|
|
||
| - **Experimental Electrum server for testing silent payments:** | ||
| [Frigate Electrum Server][frigate gh] implements the [remote scanner][bip352 | ||
| remote scanner] service from [BIP352][] to provide [silent payment][topic | ||
| silent payments] scanning for client applications. The proof of concept also | ||
| uses modern GPU computation to decrease scanning time which is useful for | ||
| providing multi-user instances that handle many simultaneous scanning requests. | ||
|
|
||
| - **BDK WASM library:** | ||
| The [bdk-wasm][bdk-wasm gh] library, originally developed and [used][metamask | ||
| blog] by the MetaMask organization, provides access to BDK features in | ||
| environments that support WebAssembly (WASM). | ||
|
|
||
| ## 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._ | ||
|
|
||
| FIXME:Gustavojfe | ||
|
|
||
| ## Notable code and documentation changes | ||
|
|
||
| _Notable recent changes in [Bitcoin Core][bitcoin core repo], [Core | ||
| Lightning][core lightning repo], [Eclair][eclair repo], [LDK][ldk repo], | ||
| [LND][lnd repo], [libsecp256k1][libsecp256k1 repo], [Hardware Wallet | ||
| Interface (HWI)][hwi repo], [Rust Bitcoin][rust bitcoin repo], [BTCPay | ||
| Server][btcpay server repo], [BDK][bdk repo], [Bitcoin Improvement | ||
| Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], | ||
| [Lightning BLIPs][blips repo], [Bitcoin Inquisition][bitcoin inquisition | ||
| repo], and [BINANAs][binana repo]._ | ||
|
|
||
| FIXME:Gustavojfe | ||
|
|
||
| {% include snippets/recap-ad.md when="2026-01-27 17:30" %} | ||
| {% include references.md %} | ||
| {% include linkers/issues.md v=2 issues="" %} | ||
|
|
||
| [channels post]: https://delvingbitcoin.org/t/a-mathematical-theory-of-payment-channel-networks/2204 | ||
| [channels paper]: https://arxiv.org/pdf/2601.04835 | ||
| [news309 feasibility]: /en/newsletters/2024/06/28/#estimating-the-likelihood-that-an-ln-payment-is-feasible | ||
| [mitigation post]: https://delvingbitcoin.org/t/mitigating-channel-depletion-in-the-lightning-network-a-survey-of-potential-solutions/1640/1 | ||
| [new387 ark]: /en/newsletters/2026/01/09/#using-ark-as-a-channel-factory | ||
| [pickhardt gh]: https://github.com/renepickhardt/Lightning-Network-Limitations | ||
| [frigate gh]: https://github.com/sparrowwallet/frigate | ||
| [bip352 remote scanner]: https://github.com/silent-payments/BIP0352-index-server-specification/blob/main/README.md#remote-scanner-ephemeral | ||
| [bdk-wasm gh]: https://github.com/bitcoindevkit/bdk-wasm | ||
| [metamask blog]: https://metamask.io/news/bitcoin-on-metamask-btc-wallet | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.