|
37 | 37 | `Event::PersistStaticInvoice`s and `Event::StaticInvoiceRequested`s. |
38 | 38 | * Zero-Fee-Commitment channels are now supported in LDK. These channels remove |
39 | 39 | 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`. |
45 | 48 | * `Event::BumpTransaction` is now always generated even if the transaction has |
46 | 49 | sufficient fee. This allows you to manage transaction broadcasting more |
47 | 50 | granularly for anchor channels (#4001). |
|
92 | 95 | * `Persist` now takes a `MonitorName` rather than a `funding_txo` `OutPoint` to |
93 | 96 | ensure the storage key is consistent across splices (#3569). |
94 | 97 | * `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). |
95 | 103 | * Various instances of channel closure which provided a |
96 | 104 | `ClosureReason::HolderForceClosed` now provide more accurate |
97 | 105 | `ClosureReason`s, especially `ClosureReason::ProcessingError` (#3881). |
|
132 | 140 | force-closed (#3989). |
133 | 141 | * `lightning-liquidity`'s service support now properly responds to the |
134 | 142 | `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). |
135 | 146 | * The fields in `SocketAddress::OnionV3` are now corectly parsed, and the |
136 | 147 | `Display` for such addresses is now lowercase (#4090). |
137 | 148 | * `PeerManager` is now more conservative about disconnecting peers which aren't |
|
0 commit comments