Skip to content

Commit 8a814fc

Browse files
Leo Weesegitbook-bot
authored andcommitted
GITBOOK-509: change request with no subject merged in GitBook
1 parent 7f44f1e commit 8a814fc

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

lightning-network-tools/lnd/unconfirmed-bitcoin-transactions.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,12 +79,26 @@ In case the above fails, (e.g. `the passed output does not belong to the wallet`
7979

8080
When closing channels, we differentiate between cooperative closes of active channels, and unilateral closes, or force closes, of inactive channels.
8181

82+
### CPFP
83+
8284
For **cooperative closures**, we can use the `lncli wallet bumpfee` command in a similar way as above. We will need to identify the output of the closing transaction that belongs to our wallet using a block explorer. This means the command can only be run if you had at least some balance in this channel.
8385

8486
In the case of a **force close**, we can use the command `lncli wallet bumpclosefee` to create a CPFP transaction that spends the outputs of our channel closure transaction. You will only be able to make use of this command if it was created as an anchor channel. To run the command successfully, you will need to specify the [channel point](../../community-resources/glossary.md#channel-point) of the channel that is being force closed.
8587

8688
To bump any commitment transaction, LND will apply new logic starting from version 0.18. LND will consider the value of the transaction, eventual deadlines and queue the sweep for the next batch. To bump the transaction right away, the `--immediate` flag can be used. Budget and deadline can be overriden with the `--budget` and `--conf_target` flags.
8789

90+
### RBF
91+
92+
Starting from LND 0.19, it is possible to bump the transaction cooperatively closing a channel using replace-by-fee (RBF). The feature has to be enabled by both peers using the `protocol.rbf-coop-close=true` flag and only applies to channels opened after the flag was applied.
93+
94+
When channels of this type are closed, the closing party always pays for the closing transaction, regardless of which peer initiated the channel open. Each time the fee of the closing transaction is bumped, the party initiating the fee increase pays the full fee.
95+
96+
To bump the close transaction of a channel, simply apply the `lncli closechannel` command again with a higher fee or lower confirmation target.
97+
98+
{% hint style="warning" %}
99+
As of now, this feature is incompatible with simple taproot channels.
100+
{% endhint %}
101+
88102
## Sweeper
89103

90104
Outputs resulting from channel force closures will have to be swept. Please refer to the Sweeper guide for how to manage fees for these transactions.

0 commit comments

Comments
 (0)