Skip to content

Excessive fees for automatically forced closed channel #8329

Discussion options

You must be logged in to vote

Looking at the logs, it seems that there was some connectivity issues between my node and the remote node

Since this is the root cause, do you know why it happened?

Then ONLY 30 seconds later, it creates a sweep transaction that uses CPFP to bump the fee to 206,967 sats:

It had to because the outgoing htlc had expired. However it's bad that it doesn't take economical actions, which should be fixed once #1226 is properly handled.

It also tries to waste 163,542 more sats on another transaction that seems to fail:

This is an anchor sweeping transaction created using the remote commitment. This is required in case your peer is also force closing.

The transaction was accepted on the blo…

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@ericpp
Comment options

@yyforyongyu
Comment options

@ericpp
Comment options

@yyforyongyu
Comment options

Answer selected by ericpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants