-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: LND-CLN err=update_fee XXXXXX unaffordable #8675
Comments
cc @ziggie1984 in case he has any ideas |
The only way for this to recover is to wait until fees go down, or ask your CLN node to run a setting which discards the fee check. CLN Setting:
|
I'm been told in the Telegram group that modifying this setting doesn't help. Is that right? |
My CLN peer says he tried running with that setting. Fees at 100 are not that high. I use feeurl to feed more realistic estimates, not bitcoin core. Maybe CLN gets too high estimates (my bitcoin core thinks the fees are 1150 still), because they don't have such a setting. |
CLN related bug: ElementsProject/lightning#7254 |
From CLN Docs:
see: https://github.com/ElementsProject/lightning/blob/master/doc/lightningd-config.5.md |
Made no difference, same error (( |
Can you report detailed logs of both nodes while this setting is active. |
Asked for some node details here: ElementsProject/lightning#7254 (comment) |
My CLN peer did not send me his logs. My LND logs did not show anything different. The HTLC just expired and the channel FCd ((( |
I answered you there: ElementsProject/lightning#7254 (comment) BTW I think we may have found another related bug in LND: when feeurl cannot be retrived, it seems it defaults to 253sat/kw, which is ridiculous. This might be the problem, plus unable to renegotiate with CLN once the new low fee is stablished. I will open another issue. |
Background
Running an LND node, have a non-anchor channel with a CLN peer. After the chain fees jumped, the two nodes can no longer maintain connection: state update from LND causes CLN to reply with warning "err=update_fee XXXXXX unaffordable" and hang up. A pending HTLC is at risk to cause an FC.
Log from my side:
On CLN side:
The error persists since the halving and the update fee stays at 448000.
Your environment
lnd
LND 0.17.4-betauname -a
on *Nix) Umbrelbtcd
,bitcoind
, or other backend Bitcoin Core 26.0.0Steps to reproduce
Chain fees go to 1000+ then back to 100+
Expected behaviour
The channel between nodes continue to work
Actual behaviour
The channel between nodes keeps disconnecting
I reported to both CLN and LND devs, but no one wants to take responsibility for this bug...
The text was updated successfully, but these errors were encountered: