Repository: lightningnetwork/lnd (language: go)

Issue:
[bug]: provide more details on the new RBF cooperative close feature in release notes
In the latest release notes, we have

https://github.com/lightningnetwork/lnd/blob/b34afa33f6993e4f24e481f83757751f0f8983de/docs/release-notes/release-notes-0.19.0.md?plain=1#L133-L147

which links to a PR that has no description and a bunch of commits.

This is a big and powerful change that I think we should more clearly explain to users in english what is going on and what it is compatible with.

Some key points that I think we should mention:

- This uses the new protocol defined at https://github.com/lightning/bolts/pull/1205/files which is called `option_simple_close`. Channel peers must support `option_simple_close` for this new protocol to work.
- It is not compatible with older LND versions, closing channels with channel peers that use older LND versions must use CPFP still to increase the effective fee.
- It _should_ work with peers running [eclair version 0.12.0 and greater](https://github.com/ACINQ/eclair/blob/master/docs/release-notes/eclair-v0.12.0.md#simplified-mutual-close).
- LDK does not seem to have implemented `option_simple_close` (https://github.com/lightningdevkit/rust-lightning/issues/2433), so it will not work with channel peers running any current version of LDK.
- CLN does not seem to have any documentation regarding `option_simple_close`, so it likely does not work with channel peers running CLN.


Discussion / hints:
> which links to a PR

https://bitcoinops.org/en/newsletters/2025/03/28/#lnd-8453 also mentions a number of additional PR related to this feature. Are these PR also relevant and worth mentioning or is Bitcoin Optech wrong?
We also need to make it clear that it does not work in the following situations:

1. taproot channels (https://github.com/lightningnetwork/lnd/issues/9662)
2. custom channels (https://github.com/lightningnetwork/lnd/issues/9663)

Fix patch:
diff --git a/docs/release-notes/release-notes-0.19.0.md b/docs/release-notes/release-notes-0.19.0.md
index 831888a678..e2b1f0b6a3 100644
--- a/docs/release-notes/release-notes-0.19.0.md
+++ b/docs/release-notes/release-notes-0.19.0.md
@@ -132,19 +132,35 @@ when running LND with an aux component injected (custom channels).
 ## Protocol Updates
 
 * `lnd` now [supports the new RBF cooperative close
-  flow](https://github.com/lightningnetwork/lnd/pull/9610). Unlike the old
-  flow, this version now uses RBF to enable either side to increase their fee
-  rate using their _own_ channel funds. This removes the old "negotiation"
-  logic that could fail, with a version where either side can increase the fee
-  on their coop close transaction using their channel balance. 
-
-  This new feature can be activated with a new config flag:
+  flow](https://github.com/lightningnetwork/lnd/pull/9610). This flow is based
+  on a new protocol `option_simple_close` defined with the bolt proposal
+  [1205](https://github.com/lightning/bolts/pull/1205)
+  Unlike the old flow, this version now uses RBF to enable either side to
+  increase their fee rate using their _own_ channel funds.
+  This replaces the old "negotiation" logic that could fail, with a version
+  where either side can increase the fee on their coop close transaction using
+  their channel balance.
+
+  Channel peers must support the `option_simple_close` for this new protocol to
+  work. This new feature can be activated with a new config flag:
   `--protocol.rbf-coop-close`.
 
   With this new co-op close type, users can issue multiple `lncli closechannnel`
   commands with increasing fee rates to use RBF to bump an existing signed co-op
   close transaction.
 
+  Please note this feature is not compatible with older LND versions.
+  When closing channels with peers running older versions, fee bumping the
+  closing transaction would be done via CPFP.
+
+  Regarding interoperation cross implementations, it currently only works
+  with Eclair v0.12.0 or up. Interop with other implementations should work 
+  as they roll out support for this protocol.
+
+  This protocol currently does not support the channel types:
+  - Taproot channels
+  - Taproot asset channels
+
 * [Support](https://github.com/lightningnetwork/lnd/pull/8390) for 
   [experimental endorsement](https://github.com/lightning/blips/pull/27) 
   signal relay was added. This signal has *no impact* on routing, and


Test patch: