Skip to content

Commit 37f6ad1

Browse files
committed
f forgot manual-broadcast, one backported fix, and add added note about relay
1 parent a5acf3c commit 37f6ad1

File tree

1 file changed

+16
-5
lines changed

1 file changed

+16
-5
lines changed

CHANGELOG.md

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -37,11 +37,14 @@
3737
`Event::PersistStaticInvoice`s and `Event::StaticInvoiceRequested`s.
3838
* Zero-Fee-Commitment channels are now supported in LDK. These channels remove
3939
force-closure risk for feerate disagreements by using a fixed, zero fee on
40-
presigned transactions, relying on anchor bumps instead. This only works with
41-
LDK peers, and feature signaling may change in a future version of LDK,
42-
breaking compatibility. This is negotiated automatically for
43-
manually-accepted inbound channels and negotiated for outbound channels based
44-
on `ChannelHandshakeConfig::negotiate_anchor_zero_fee_commitments`.
40+
presigned transactions, relying on anchor bumps instead. They also utilize
41+
the new TRUC policy in Bitcoin Core 29 to substantially improve the lightning
42+
security model. This requires having a path of Bitcoin Core 29+ nodes between
43+
you and a miner for transactions to be mined. This only works with LDK peers,
44+
and feature signaling may change in a future version of LDK, breaking
45+
compatibility. This is negotiated automatically for manually-accepted inbound
46+
channels and negotiated for outbound channels based on
47+
`ChannelHandshakeConfig::negotiate_anchor_zero_fee_commitments`.
4548
* `Event::BumpTransaction` is now always generated even if the transaction has
4649
sufficient fee. This allows you to manage transaction broadcasting more
4750
granularly for anchor channels (#4001).
@@ -92,6 +95,11 @@
9295
* `Persist` now takes a `MonitorName` rather than a `funding_txo` `OutPoint` to
9396
ensure the storage key is consistent across splices (#3569).
9497
* `lightning-liquidity` now supports persisting relevant state (#4059, #4118).
98+
* `ChannelManager::funding_transaction_generated_manual_broadcast` was added to
99+
open a channel without automatically broadcasting the funding transaction
100+
(#3838). In it and `unsafe_manual_funding_transaction_generated`
101+
force-closure logic has been updated to no longer automatically broadcast the
102+
commitment tx unless the funding transaction has been seen on-chain (#4109).
95103
* Various instances of channel closure which provided a
96104
`ClosureReason::HolderForceClosed` now provide more accurate
97105
`ClosureReason`s, especially `ClosureReason::ProcessingError` (#3881).
@@ -132,6 +140,9 @@
132140
force-closed (#3989).
133141
* `lightning-liquidity`'s service support now properly responds to the
134142
`ListProtocols` message (#3785).
143+
* A rare race which might lead `PeerManager` (and `lightning-net-tokio`) to
144+
stop reading from a peer until a new message is sent to that peer has been
145+
fixed (#4168).
135146
* The fields in `SocketAddress::OnionV3` are now corectly parsed, and the
136147
`Display` for such addresses is now lowercase (#4090).
137148
* `PeerManager` is now more conservative about disconnecting peers which aren't

0 commit comments

Comments
 (0)