@@ -7,7 +7,13 @@ type: newsletter
77layout : newsletter
88lang : en
99---
10- This week's newsletter FIXME: harding
10+ This week's newsletter describes a proposal to limit public
11+ participation in Bitcoin Core repositories, announces a significant
12+ improvements to BitVM-style contracts, and summarizes research into
13+ LN channel rebalancing. Also included are our regular sections
14+ summarizing recent changes to clients and services, announcing new
15+ releases and release candidates, and describing recent changes to popular
16+ Bitcoin infrastructure software.
1117
1218## News
1319
@@ -23,13 +29,13 @@ This week's newsletter FIXME:harding
2329
2430 Bishop's post suggests a method for online privatization, but
2531 Antoine Poinsot [ questioned] [ poinsot priv ] whether that method would
26- actually achieve the goal. Poinsot also suggested that many private
32+ achieve the goal. Poinsot also suggested that many private
2733 office discussions might occur not out of fear of public reproach but
28- because of "the natural advantages of in-persion discussions".
34+ because of "the natural advantages of in-person discussions".
2935
30- Several replies suggested, in essence, that making major changes is
36+ Several replies suggested that making major changes is
3137 probably not warranted at this time but that stronger moderation of
32- comments on the repository would probably alleviate the most
38+ comments on the repository might alleviate the most
3339 significant type of disruption. However, other replies noted several
3440 challenges with stronger moderation.
3541
@@ -45,7 +51,7 @@ This week's newsletter FIXME:harding
4551 contracts. Based on an [ idea] [ rubin garbled ] by Jeremy Rubin that
4652 builds on new cryptographic primitives, the new approach "reduces the
4753 onchain cost of a dispute by over 1,000 times compared to the previous
48- design", with disprovable transactions being "just 200 bytes".
54+ design", with disprove transactions being "just 200 bytes".
4955
5056 However, Linus's paper notes the tradeoff for this approach: it
5157 "requires a multi-terabyte offchain data setup". The paper gives an
@@ -65,7 +71,7 @@ This week's newsletter FIXME:harding
6571
6672 Pickhardt notes that there are several challenges to a global approach and
6773 asks interested parties to answer a few questions, such as whether
68- this is an approach worth pursuing and how to address certain
74+ this approach is worth pursuing and how to address certain
6975 implementation details.
7076
7177## Changes to services and client software
@@ -98,11 +104,14 @@ _New releases and release candidates for popular Bitcoin infrastructure
98104projects. Please consider upgrading to new releases or helping to test
99105release candidates._
100106
101- - [ Core Lightning 25.05] [ ] is a release for the next major
102- version of this popular LN node implementation.
103- FIXME: harding_add_details
104-
105- <!-- FIXME:harding to update on Thursday -->
107+ - [ Core Lightning 25.05] [ ] is a release of the next major
108+ version of this popular LN node implementation. It reduces the
109+ latency of relaying and resolving payments, improves fee
110+ management, provides [ splicing] [ topic splicing ] support compatible
111+ with Eclair, and enables [ peer storage] [ topic peer storage ] by
112+ default. Note: its [ release documentation] [ core lightning 25.05 ]
113+ contains a warning for users of the ` --experimental-splicing `
114+ configuration option.
106115
107116## Notable code and documentation changes
108117
0 commit comments