Skip to content

Update CHANGELOG for 0.2 #4256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 3, 2025
Merged

Update CHANGELOG for 0.2 #4256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,13 @@
pre-signed transactions, relying on anchor bumps instead. They also utilize
the new TRUC + ephemeral dust policy in Bitcoin Core 29 to substantially
improve the lightning security model. This requires having a path of Bitcoin
Core 29+ nodes between you and a miner for transactions to be mined. This
only works with LDK peers, and feature signaling may change in a future
version of LDK, breaking compatibility. This is negotiated automatically for
manually-accepted inbound channels and negotiated for outbound channels based
on `ChannelHandshakeConfig::negotiate_anchor_zero_fee_commitments`.
Core 29+ nodes between you and a miner for transactions to be mined. Bitcoin
Knots blocks these transactions by default, and is not recommended for use
with a lightning node. 0FC channels currently only work with LDK peers, and
feature signaling may change in a future version of LDK, breaking
compatibility. This is negotiated automatically for manually-accepted inbound
channels and negotiated for outbound channels based on
`ChannelHandshakeConfig::negotiate_anchor_zero_fee_commitments`.
* `Event::BumpTransaction` is now always generated even if the transaction has
sufficient fee. This allows you to manage transaction broadcasting more
granularly for anchor channels (#4001).
Expand Down