If you run a routing node, things you could do if you haven't done already to reduce the possibility of force closures because the current mempool situation is crazy.

1. Stop automated rebalances

2. Raise fees

3. Raise cltv delta (mine's 120)

4. Raise minhtlc to only forward large payments.

5. Pray to the mempool gods.

6 Ask for forgiveness when bitching about overpaying FCs at 10 s/vb 2 months ago

Reply to this note

Please Login to reply.

Discussion

This will kill your channel and inactive channels will more likely be force closed. Follow these instructions at your own peril ๐Ÿคท๐Ÿปโ€โ™‚๏ธ

What? Kill your channel?

I agree with 5 and 6, but the other ones makes no sense to me. Would you mind explain why you are suggesting them?

everything is targeted towards less htlcs flying around.

No automated rebalances means less HTLCS flying around by your own node.

Raising cltv delta means you raise the timeout you give for the htlc, so your peer has more time to come back online to prevent a force closure.

Setting higher fee rates again means you forward less payments and probably you'll forward real payments and not just somebody else's rebalances.

Raising min htlc means you'll forward only larger size payments and not small ones like zaps. Imagine getting force closed in this mempool for a 10 sat zap payment.

thanks for the long answer! I understand cltv delta, but still don't get why you'd want less htlc through your node. How they 'll increase the chance of force close?

More htlcs and more is the probability of force closures because you never know which one would get stuck. Generally nodes with less activity experience much less force closures.

You also should probably assess your peers, if you know a peer is going offline frequently you should probably cut them.

so, force close are for htlc getting stuck?

The number one reason, yes.

thanks! ๐Ÿ™