Skip to content

Note the mempool policy requirements of zero-fee commitment channels #4187

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
Oct 29, 2025
+5 −0
Merged

Note the mempool policy requirements of zero-fee commitment channels #4187

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
5 changes: 5 additions & 0 deletions lightning/src/util/config.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,11 @@ pub struct ChannelHandshakeConfig {
/// back to a `anchors_zero_fee_htlc` (if [`Self::negotiate_anchors_zero_fee_htlc_tx`]
/// is set) or `static_remote_key` channel.
///
/// For a force-close transaction to reach miners and get confirmed,
/// zero-fee commitment channels require a path from your Bitcoin node to miners that
/// relays TRUC transactions (BIP 431), P2A outputs, and Ephemeral Dust. Currently, only
/// nodes running Bitcoin Core v29 and above relay transactions with these features.
///
/// Default value: `false` (This value is likely to change to `true` in the future.)
///
/// [TRUC]: (https://bitcoinops.org/en/topics/version-3-transaction-relay/)
Expand Down
Loading