Unable to cooperative close with LOOP because of fees disagreement

[zx9r]

trafficstars

As title says, LOOP node best offer to close channel is 566 sats which I guess it is about 3-4 sats/b which is too much given the mempool is totally empty and a lot of non full blocks in a row are being mined.

I tried disconnecting from LOOP several times. It automatically reconnects and initiates a renegotiation but they get to the same result.

2022-11-05 17:21:35.740 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 183 sat to close chan 2022-11-05 17:21:35.914 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=183, remote_offer=2353 2022-11-05 17:21:35.915 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 201 sat to close chan 2022-11-05 17:21:36.092 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=201, remote_offer=2118 2022-11-05 17:21:36.093 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 221 sat to close chan 2022-11-05 17:21:36.266 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=221, remote_offer=1907 2022-11-05 17:21:36.266 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 243 sat to close chan 2022-11-05 17:21:36.440 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=243, remote_offer=1717 2022-11-05 17:21:36.441 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 267 sat to close chan 2022-11-05 17:21:36.614 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=267, remote_offer=1546 2022-11-05 17:21:36.615 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 293 sat to close chan 2022-11-05 17:21:36.790 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=293, remote_offer=1392 2022-11-05 17:21:36.791 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 322 sat to close chan 2022-11-05 17:21:36.966 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=322, remote_offer=1253 2022-11-05 17:21:36.966 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 354 sat to close chan 2022-11-05 17:21:37.140 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=354, remote_offer=1128 2022-11-05 17:21:37.141 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 389 sat to close chan 2022-11-05 17:21:37.318 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=389, remote_offer=1016 2022-11-05 17:21:37.319 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 427 sat to close chan 2022-11-05 17:21:37.492 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=427, remote_offer=915 2022-11-05 17:21:37.493 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 469 sat to close chan 2022-11-05 17:21:37.666 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=469, remote_offer=824 2022-11-05 17:21:37.666 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): proposing fee of 515 sat to close chan 2022-11-05 17:21:37.840 [INF] CHCL: ChannelPoint(4ec7c5300e4c90ceed8c9ed89d0bed0ccc2de6a52e43a42fd9703d64059bf1ba:2): computing fee compromise, ideal=183, last_sent=515, remote_offer=742 2022-11-05 17:21:37.841 [ERR] PEER: Peer(021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d): unable to process close msg: latest fee proposal exceeds max fee: 0.00000566 BTC > 0.00000549 BTC

[alexbosworth]

what bitcoin estimate mode in lnd.conf?

[zx9r]

bitcoind.estimatemode=ECONOMICAL

and

coop-close-target-confs=1000

[alexbosworth]

try using estimate mode conservative

[zx9r]

Yeah of course I could do that, but why paying 3x or 4x more than necessary ? Wouldn't it be better for everyone that LOOP uses mode economical ?

[alexbosworth]

if 566 in chain fees are consuming a large part of your costs, i'd consider a larger channel to try and aggregate more payment volume in a single transaction

[zx9r]

Aggregating more payment volume doesnt change the fact that 566 is 3-4x more than necessary.

Even worse, since bitcoin estimate mode is a global parameter and you cannot change it specically for LOOP channels, it would affect all other channels as well.

[alexbosworth]

Thanks for the feedback, we are definitely looking at options for reducing the costs associated with being a peer with Loop and I would stay tuned for updates there

[zx9r]

I am having same problem with another LOOP channel, this time with bitcoind.estimatemode=CONSERVATIVE

2022-11-28 14:05:40.578 [ERR] PEER: Peer(021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d): unable to process close msg: latest fee proposal exceeds max fee: 0.00000602 BTC > 0.00000585 BTC

[alexbosworth]

Did you try disconnecting and then reconnecting?

What is your coop-close-target-confs setting?

[zx9r]

Yes, I tried rebooting LND and also disconnecting with LOOP. When connecting again it tries to negotiate but with the same result

coop-close-target-confs=1000

[alexbosworth]

OK another option is to wait until the fee estimations come into alignment

[zx9r]

Yeah, been trying that several times since yesterday. I hope eventually they get to an agreement

[zx9r]

I just set coop-close-target-confs=100 (down from 1000) and still not agree on fees:

2022-11-29 14:12:31.504 [ERR] PEER: Peer(021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d): unable to process close msg: latest fee proposal exceeds max fee: 0.00000602 BTC > 0.00000585 BTC

[alexbosworth]

What happens if you set it to 10?

[hieblmi]

Closing due to inactivity. lnd might have seen improvements in its fee negotiation during closures in the meantime. Please re-open if needed.