Excessive fees for automatically forced closed channel #8329
-
While I was busy celebrating New Years Weekend, my node decided to waste 206,967 sats to force close a 500k sat channel. Looking at the logs, it seems that there was some connectivity issues between my node and the remote node:
Eventually an htlc hit a timeout and attempted to force close the channel with a 29,615 sat fee:
Then ONLY 30 seconds later, it creates a sweep transaction that uses CPFP to bump the fee to 206,967 sats:
It also tries to waste 163,542 more sats on another transaction that seems to fail:
The transaction was accepted on the blockchain, but my node still refuses to acknowledge it. It also refuses to acknowledge the force close that it did during Thanksgiving that I had to manually bump (2351706de72637b19f80c6c5eefe764e84c39f560fbace7d08a96c7f53cf26a5).
During the Thanksgiving auto force close, it tried to create a transaction with a small fee that wasn't being accepted and I had to manually bump it to 100 sats/vB. After that happened, I adjusted How do I make it use a reasonable fee when force closing a channel? How do I get it to acknowledge these force closed channels? I tried to use |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Since this is the root cause, do you know why it happened?
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.
This is an anchor sweeping transaction created using the remote commitment. This is required in case your peer is also force closing.
After the FC transaction being confirmed, you still need to wait a few more blocks to unlock your
This config is used to set the FC fee rate. After that, based on the timelocks in HTLCs, there will be a CPFP attempt if the timelock has expired.
Aside from #1226, there's |
Beta Was this translation helpful? Give feedback.
Since this is the root cause, do you know why it happened?
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.
This is an anchor sweeping transaction created using the remote commitment. This is required in case your peer is also force closing.