You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My pending self-payment rebalancing attempt with a peer going offline due to emergency didn't immediately FC when the self-payment maturity hit < 0. Then LND determined a day later to FC the channel, but causing an overpayment of 12x. Assumption is, that the sweep bumper continued to increase the commit-fee, while payments-expiration-grace-period=10000h in lnd.conf kept the channel from force-closing.
Your environment
version of lnd: lnd version 0.18.2-beta commit=v0.18.2-beta
which operating system (uname -a on *Nix): Linux debian-nuc 6.1.0-18-amd64 Fix name typo in README #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
version of btcd, bitcoind, or other backend: Bitcoin Core RPC client version v26.0.0
any other relevant environment details: payments-expiration-grace-period=10000h
Steps to reproduce
Logs attached where we can reproduce it.
I would assume to reproduce, we would need a peer, send a self-payment, peer goes offline, and observe LND logs behaviour handling the sweeper fees
Expected behaviour
When within the self-payment grace period, the sweeper should not bump the fee but steady state until leaving the period window.
Background
My pending self-payment rebalancing attempt with a peer going offline due to emergency didn't immediately FC when the self-payment maturity hit < 0. Then LND determined a day later to FC the channel, but causing an overpayment of 12x. Assumption is, that the sweep bumper continued to increase the commit-fee, while
payments-expiration-grace-period=10000hin lnd.conf kept the channel from force-closing.Your environment
lnd: lnd version 0.18.2-beta commit=v0.18.2-betauname -aon *Nix): Linux debian-nuc 6.1.0-18-amd64 Fix name typo in README #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linuxbtcd,bitcoind, or other backend: Bitcoin Core RPC client version v26.0.0Steps to reproduce
Logs attached where we can reproduce it.
I would assume to reproduce, we would need a peer, send a self-payment, peer goes offline, and observe LND logs behaviour handling the sweeper fees
Expected behaviour
When within the self-payment grace period, the sweeper should not bump the fee but steady state until leaving the period window.
Actual behaviour
https://mempool.space/tx/abc65c90a8b00ab6418a0ddb304269fa694cc2b4bf62c95aa1e286abc52a9e65
Fee rate 59.5 sat/vB where a Fee rate of 4 sat/vB would have been sufficient.
PinsLNN_01_fc-2024-10-15.log