News294: add services and client software section

Author: bitschmidty

_data/compatibility/bitgo.yaml

@@ -16,9 +16,9 @@ rbf:
       shows_replaced_version: "false"
       shows_original_version: "false"
     send:
-      signals_bip125: "false"
-      list: "untested"
-      details: "untested"
+      signals_bip125: "true"
+      list: "true"
+      details: "true"
       shows_replaced_version: "untested"
       shows_original_version: "untested"
   examples:

_posts/en/newsletters/2024-03-20-newsletter.md

@@ -7,7 +7,12 @@ type: newsletter
 layout: newsletter
 lang: en
 ---
-This week's newsletter FIXME
+This week's newsletter announces a project to create a BIP324 proxy for
+light clients and summarizes discussion about a proposed BTC Lisp
+language.  Also included are our regular sections describing recent
+changes to clients and services, announcing new releases and release
+candidates, and summarizing notable changes to popular Bitcoin
+infrastructure software.
 
 ## News
 
@@ -38,7 +43,7 @@ This week's newsletter FIXME
   software that wants to natively support the v2 Bitcoin P2P protocol.
 
 - **Overview of BTC Lisp:** Anthony Towns [posted][towns lisp] to
-  Delving Bitcoin about his experiments over the past couple years
+  Delving Bitcoin about his experiments over the past couple of years
   creating a variant of the [Lisp][] language for Bitcoin, called BTC
   Lisp.  See Newsletters [#293][news293 lisp] and [#191][news191 lisp]
   for previous discussions.  The post goes into significant detail; we
@@ -50,18 +55,18 @@ This week's newsletter FIXME
   Lisp interpreter or the bucket of opcodes that would need to accompany
   it is too hard [but] it is pretty annoying to write Lisp code without
   a compiler translating from a higher level representation down to the
-  consensus-level opcodes, [though] that seems solvable.  [T]this could
+  consensus-level opcodes, [though] that seems solvable.  [T]his could
   be taken further [by] implementing a language like this and deploying
   it on signet/inquisition."
 
   Russell O'Connor, developer of the [Simplicity][topic simplicity]
   language that may also one day be considered as an alternative
   consensus scripting language, [replied][oconnor lisp] with some
   comparisons between Bitcoin's current Script language, Simplicity, and
-  Chia/BTC Lisp.  He concludes, "Simplicity and the [Chia Lisp Virtual
-  Machine] clvm are both low level languages that are meant to be easy
+  Chia/BTC Lisp.  He concludes, "Simplicity and the clvm [Chia Lisp Virtual
+  Machine] are both low level languages that are meant to be easy
   for machines to evaluate, which causes tradeoffs that make them hard
-  for humans to read. They are intended to be the compiled from some
+  for humans to read. They are intended to be compiled from some
   different, human-readable, non-consensus-critical language.
   Simplicity and the clvm are different ways of expressing the same old
   things: fetching data from an environment, tupling up bits of data,
@@ -70,10 +75,10 @@ This week's newsletter FIXME
   efficient low-level consensus language and high-level non-consensus
   comprehensible language] regardless, the details of the low-level
   language become somewhat less important. I.e., with some effort, your
-  high level BTC lisp language could probably be translated/complied to
+  high level BTC lisp language could probably be translated/compiled to
   Simplicity [...] Similarly, wherever the design of [Simplicity-based]
   Simphony [high-level non-consensus language] ends up, it can probably
-  be translated/complied your low level BTC lisp language, with each
+  be translated/compiled [to] your low level BTC lisp language, with each
   translator/compiler language pair offering different potential
   complexity/optimization opportunities."
 
@@ -82,22 +87,53 @@ This week's newsletter FIXME
 *In this monthly feature, we highlight interesting updates to Bitcoin
 wallets and services.*
 
-FIXME:bitschmidty
+- **BitGo adds RBF support:**
+  In a [recent blog][bitgo blog], BitGo announced support for fee bumping using
+  [replace-by-fee (RBF)][topic rbf] in their wallet and API.
+
+- **Phoenix Wallet v2.2.0 released:**
+  With this release, Phoenix can now support [splices][topic splicing] while
+  making LN payments using the quiescence protocol (see [Newsletter
+  #262][news262 eclair2680]). Additionally, Phoenix improved the swap-in feature
+  privacy and fees by using their [swaproot][swaproot blog] protocol.
+
+- **Bitkey hardware signing device released:**
+  The [Bitkey][bitkey website] device is designed to be used in a 2-of-3
+  multisig setup with a mobile device and a Bitkey server key. Source code for
+  the firmware and various components are [available][bitkey github] under a
+  Commons Clause modified MIT License.
+
+- **Envoy v1.6.0 released:**
+  The [release][envoy blog] adds features for fee bumping transactions as well as canceling
+  transactions, both enabled using replace-by-fee (RBF).
+
+- **VLS v0.11.0 released:**
+  The [beta release][vls beta 3] allows multiple signing devices for the same
+  Lightning node, a feature they call [tag team signing][vls blog].
+
+- **Portal hardware signing device announced:**
+  The [recently announced][portal tweet] Portal device works with smartphones
+  using NFC with hardware and software source [available][portal github].
+
+- **Braiins mining pool adds Lightning support:**
+  The Braiins mining pool [announced][braiins tweet] a beta for mining payouts through Lightning.
+
+- **Ledger Bitcoin App 2.2.0 released:**
+  The [2.2.0 release][ledger 2.2.0] adds [miniscript][topic miniscript] support
+  for [taproot][topic taproot].
 
 ## 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.*
 
-- [Bitcoin Core 26.1rc1][] is a release candidate for a maintenance release
+- [Bitcoin Core 26.1rc2][] is a release candidate for a maintenance release
   of the network's predominant full node implementation.
 
 - [Bitcoin Core 27.0rc1][] is a release candidate for the next major
   version of the network's predominant full node implementation.
 
-<!-- FIXME:harding to update on Tuesday -->
-
 ## Notable code and documentation changes
 
 _Notable recent changes in [Bitcoin Core][bitcoin core repo], [Core
@@ -114,7 +150,7 @@ development branch and so those changes will likely not be released
 until about six months after the release of the upcoming version 27.*
 
 - [Bitcoin Core #27375][] adds support to the `-proxy` and `-onion`
-  feature for using Unix domain sockets rather than local TCP ports.
+  features for using Unix domain sockets rather than local TCP ports.
   Sockets can be faster than TCP ports and offer different security
   tradeoffs.
 
@@ -127,34 +163,44 @@ until about six months after the release of the upcoming version 27.*
   access if the local node connects to it, such as by the user calling
   the `addnode` RPC.
 
-- [Bitcoin Core #29306][] adds [sibling eviction][topic sibling
-  eviction] for transactions descended from an unconfirmed [v3
+- [Bitcoin Core #29306][] adds [sibling eviction][topic kindred
+  rbf] for transactions descended from an unconfirmed [v3
   parent][topic v3 transaction relay].  This can provide a satisfactory
   alternative to [CPFP carve-out][topic cpfp carve out], which is
   currently used by [LN anchor outputs][topic anchor outputs].  V3
-  transaction relay is not currently enabled for mainnet and (as noted
-  above) this PR is merged into the development branch that is not
-  expected to be released for about six months.
+  transaction relay, including sibling eviction, is not currently
+  enabled for mainnet.
 
 - [LND #8310][] allows the `rpcuser` and `rpcpass` (password)
-  configuration parameters to be retrieved from the Unix environment.
+  configuration parameters to be retrieved from the system environment.
   This can allow, for example, a `lnd.conf` file to be managed using a
   non-private revision control system without storing the private
   username and password.
 
 - [Rust Bitcoin #2458][] adds support for signing [PSBTs][topic psbt]
-  for transactions that include taproot inputs.
+  that include taproot inputs.
 
-{% assign day_after_posting = page.date | date: "%s" | plus: 86400 | date: "%Y-%m-%d 14:00" %}
+{% assign day_after_posting = page.date | date: "%s" | plus: 86400 | date: "%Y-%m-%d 14:30" %}
 {% include snippets/recap-ad.md when=day_after_posting %}
 {% include references.md %}
 {% include linkers/issues.md v=2 issues="27375,27114,29306,8310,2458" %}
-[bitcoin core 26.1rc1]: https://bitcoincore.org/bin/bitcoin-core-26.1/
+[bitcoin core 26.1rc2]: https://bitcoincore.org/bin/bitcoin-core-26.1/
 [Bitcoin Core 27.0rc1]: https://bitcoincore.org/bin/bitcoin-core-27.0/test.rc1/
-[topic sibling eviction]: https://example.com/#FIXME-harding-to-write-topic-page
 [lisp]: https://en.wikipedia.org/wiki/Lisp_(programming_language)
 [news293 lisp]: /en/newsletters/2024/03/13/#overview-of-chia-lisp-for-bitcoiners
 [news191 lisp]: /en/newsletters/2022/03/16/#using-chia-lisp
 [falbesoner bip324]: https://delvingbitcoin.org/t/bip324-proxy-easy-integration-of-v2-transport-protocol-for-light-clients-poc/678
 [towns lisp]: https://delvingbitcoin.org/t/btc-lisp-as-an-alternative-to-script/682
 [oconnor lisp]: https://delvingbitcoin.org/t/btc-lisp-as-an-alternative-to-script/682/7
+[bitgo blog]: https://blog.bitgo.com/available-now-for-clients-bitgo-introduces-replace-by-fee-f74e2593b245
+[news262 eclair2680]: /en/newsletters/2023/08/02/#eclair-2680
+[swaproot blog]: https://acinq.co/blog/phoenix-swaproot
+[bitkey website]: https://bitkey.world/
+[bitkey github]: https://github.com/proto-at-block/bitkey
+[envoy blog]: https://foundation.xyz/2024/03/envoy-version-1-6-0-is-now-live/
+[vls beta 3]: https://gitlab.com/lightning-signer/validating-lightning-signer/-/releases/v0.11.0
+[vls blog]: https://vls.tech/posts/tag-team/
+[portal tweet]: https://twitter.com/afilini/status/1766085500106920268
+[portal github]: https://github.com/TwentyTwoHW
+[braiins tweet]: https://twitter.com/BraiinsMining/status/1760319741560856983
+[ledger 2.2.0]: https://github.com/LedgerHQ/app-bitcoin-new/releases/tag/2.2.0

_topics/en/miniscript.md

@@ -86,6 +86,9 @@ optech_mentions:
     url: /en/wizardsardine-miniscript/
     date: 2023-11-15
 
+  - title: "Ledger Bitcoin App 2.2.0 adds miniscript support for taproot"
+    url: /en/newsletters/2024/03/20/#ledger-bitcoin-app-2-2-0-released
+
 ## Optional.  Same format as "primary_sources" above
 see_also:
   - title: "Miniscript: streamlined Bitcoin scripting"

_topics/en/psbt.md

@@ -210,6 +210,9 @@ optech_mentions:
   - title: Proposed BIP specifying how to include descriptors in PSBTs
     url: /en/newsletters/2024/01/03/#descriptors-in-psbt-draft-bip
 
+  - title: "Rust Bitcoin #2458 adds support for signing PSBTs that include taproot inputs"
+    url: /en/newsletters/2024/03/20/#rust-bitcoin-2458
+
 ## Optional.  Same format as "primary_sources" above
 see_also:
   - title: Output Script Descriptors

_topics/en/replace-by-fee.md

@@ -174,6 +174,9 @@ optech_mentions:
   - title: "Pure replace by feerate is not guaranteed to be incentive compatible"
     url: /en/newsletters/2024/02/21/#pure-replace-by-feerate-doesn-t-guarantee-incentive-compatibility
 
+  - title: "BitGo adds RBF support"
+    url: /en/newsletters/2024/03/20/#bitgo-adds-rbf-support
+
 ## Optional.  Same format as "primary_sources" above
 see_also:
   - title: Transaction pinning

_topics/en/simplicity.md

@@ -45,6 +45,9 @@ optech_mentions:
   - title: "BTC-Script (based on Chia Lisp) as an alternative to Simplicity"
     url: /en/newsletters/2022/03/16/#using-chia-lisp
 
+  - title: "Comparisons betwen Simplicity and BTC Lisp"
+    url: /en/newsletters/2024/03/20/#overview-of-btc-lisp
+
 ## Optional.  Same format as "primary_sources" above
 see_also:
   - title: "Simplicity: A New Language for Blockchains"

_topics/en/splicing.md

@@ -74,6 +74,9 @@ optech_mentions:
   - title: "Challenges with splicing and zero-conf channels when using v3 transaction topology"
     url: /en/newsletters/2024/02/07/#securely-opening-zero-conf-channels-with-v3-transactions
 
+  - title: "Phoenix Wallet v2.2.0 adds support for splicing using the quiescence protocol"
+    url: /en/newsletters/2024/03/20/#phoenix-wallet-v2-2-0-released
+
 ## Optional.  Same format as "primary_sources" above
 see_also:
   - title: Interactive transaction construction protocol

_topics/en/v2-p2p-transport.md

@@ -74,6 +74,9 @@ optech_mentions:
   - title: "Bitcoin Core #29347 enables v2 P2P transport by default"
     url: /en/newsletters/2024/02/07/#bitcoin-core-29347
 
+  - title: "New project to create a BIP324 proxy for light clients"
+    url: /en/newsletters/2024/03/20/#bip324-proxy-for-light-clients
+
 ## Optional.  Same format as "primary_sources" above
 see_also:
   - title: BIP151