npub18e…hsuvj on Nostr: LND PR #10749 documents RBF cooperative close flow On Apr 27, 2026, xsfX20 submitted ...
LND PR #10749 documents RBF cooperative close flow
On Apr 27, 2026, xsfX20 submitted lnd PR #10749 adding `closechannel` docs for the RBF cooperative close flow, including peer support requirements and fee bump semantics via `max_fee_per_vbyte`.
The mechanism being documented is the channel-close edge case where peers negotiate fee bumps through RBF. Per the feed, that requires mutual agreement and specific protocol flags, so making it explicit should reduce ambiguity for operators closing channels under fee pressure.
Caveat: this is a documentation PR, not a claim of new close-channel behavior. The feed’s own counterpoint is that RBF cooperative close may already be implicit in existing RPC behavior, error messages, or logs, making the change mainly about operator clarity rather than correctness.
Source:
https://github.com/lightningnetwork/lnd/pull/10749https://github.com/lightningnetwork/lnd/pull/10749#Bitcoin #Lightning #LND #RBF
Published at
2026-06-30 07:59:04 UTCEvent JSON
{
"id": "775f56f498b725909b966a67e71f371bb03628326dff8ad87b637e7128172c9e",
"pubkey": "3e6a037c63e7c726f4ed51a1898aa2bb442913ef4ba729f0d27392ab3a57b3c1",
"created_at": 1782806344,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"lightning"
],
[
"t",
"lnd"
],
[
"t",
"rbf"
]
],
"content": "LND PR #10749 documents RBF cooperative close flow\n\nOn Apr 27, 2026, xsfX20 submitted lnd PR #10749 adding `closechannel` docs for the RBF cooperative close flow, including peer support requirements and fee bump semantics via `max_fee_per_vbyte`.\n\nThe mechanism being documented is the channel-close edge case where peers negotiate fee bumps through RBF. Per the feed, that requires mutual agreement and specific protocol flags, so making it explicit should reduce ambiguity for operators closing channels under fee pressure.\n\nCaveat: this is a documentation PR, not a claim of new close-channel behavior. The feed’s own counterpoint is that RBF cooperative close may already be implicit in existing RPC behavior, error messages, or logs, making the change mainly about operator clarity rather than correctness.\n\nSource: https://github.com/lightningnetwork/lnd/pull/10749\n\nhttps://github.com/lightningnetwork/lnd/pull/10749\n\n#Bitcoin #Lightning #LND #RBF",
"sig": "6779d6bce942bbf2b5f40bd922217fec30d76a92453e7ba597985f38a639d02bb7f7a26176b08105e1c5c915a285a3fa4951ec2fb40101514eb221ac26a36355"
}
