@@ -15,15 +15,13 @@ This week's newsletter FIXME:harding
1515 Bryan Bishop [ posted] [ bishop priv ] to the Bitcoin-Dev mailing list to
1616 suggest that the Bitcoin Core Project limit the public's ability to
1717 participate in project discussions in order to reduce the amount of
18- disruption caused by non-contributors. He analogized this to
19- "privatizing Bitcoin Core" the way private companies rarely publicly
20- share internal team discussions, shielding their individual employees
21- from public reproach that drains their time and emotional energy. He
18+ disruption caused by non-contributors. He called this
19+ "privatizing Bitcoin Core",
2220 points to examples of this privatization already happening on an ad
2321 hoc basis in private offices with multiple Bitcoin Core contributors,
24- but warns that leaves out many contributors who work remotely .
22+ and warns that in-person privatization leaves out remote contributors.
2523
26- Bishop's post suggests a method for implementing the policy , but
24+ Bishop's post suggests a method for online privatization , but
2725 Antoine Poinsot [ questioned] [ poinsot priv ] whether that method would
2826 actually achieve the goal. Poinsot also suggested that many private
2927 office discussions might occur not out of fear of public reproach but
@@ -35,10 +33,11 @@ This week's newsletter FIXME:harding
3533 significant type of disruption. However, other replies noted several
3634 challenges with stronger moderation.
3735
38- Both Poinsot and Sebastian "The Charlatan" Kung, the only two highly
36+ Poinsot, Sebastian "The Charlatan" Kung, and Russell Yanofsky--- the only highly
3937 active Bitcoin Core contributors to reply to the thread as of the time
40- of writing, [ indicated] [ kung priv ] that they don't think a major
41- change is necessary.
38+ of writing---[ indicated] [ kung priv ] either [ that] [ yanofsky priv ] they don't think a major
39+ change is necessary or that any changes should be made incrementally
40+ over time.
4241
4342- ** Improvements to BitVM-style contracts:** Robin Linus [ posted] [ linus
4443 bitvm3] to Delving Bitcoin to announce a significant reduction in the
@@ -57,14 +56,14 @@ This week's newsletter FIXME:harding
5756 assertion was invalid.
5857
5958- ** Channel rebalancing research:** Rene Pickhardt [ posted] [ pickhardt
60- rebalance] to Delving Bitcoin an idea for rebalancing channels across
61- LN that attempts to maximize the rate of payment feasibility across
62- the whole network. This can be compared to other approaches that look
59+ rebalance] to Delving Bitcoin thoughts about rebalancing channels
60+ to maximize the rate of successful payments across
61+ the whole network. His ideas can be compared to approaches that look
6362 at smaller groups of channels, such as [ friend-of-a-friend
6463 rebalancing] [ topic jit routing ] (see [ Newsletter #54 ] [ news54 foaf
6564 rebalance] ).
6665
67- Pickhardt notes that there are several challenges to this approach and
66+ Pickhardt notes that there are several challenges to a global approach and
6867 asks interested parties to answer a few questions, such as whether
6968 this is an approach worth pursuing and how to address certain
7069 implementation details.
@@ -174,4 +173,5 @@ repo], and [BINANAs][binana repo]._
174173[ starkware sv2 ] : https://github.com/keep-starknet-strange/stratum
175174[ news337 delay ] : /en/newsletters/2025/01/17/#eclair-2936
176175[ news349 attributable ] : /en/newsletters/2025/04/11/#ldk-2256
177- [ news342 peer ] :/en/newsletters/2025/02/21/#ldk-3575
176+ [ news342 peer ] :/en/newsletters/2025/02/21/#ldk-3575
177+ [ yanofsky priv ] : https://github.com/bitcoin-core/meta/issues/19#issuecomment-2961177626
0 commit comments