Closed philipp1992 closed 9 months ago
Are you able to reproduce this with lnd v0.15.1?
This sounds expected: each time you add an HTLC, you need to also pay for the fee to add that to the commitment transaction. If you try to add an HTLC, but maybe have the correct balance, it's possible after adding the required fee (at the current fee rate) you don't have enough to still maintain the reserve.
even with the fees added to the calculation, it does not add up to a number that would exceed the channel reserves or am i missing something here?
Base Fees (mSats) 1,000 Fee Rate (milli mSats) 1 Fee Rate (%) 0.0001 Time Lock Delta 18
is it possible to lower the timelock to less than 18 blocks , so we dont have too many pending HTLCs?
So I mean chain fees here. Each HTLC you have increases the size of the commitment transaction. So it's possible that you have enough to send, but once you add the HTLC, those fees are too much.
is it possible to lower the timelock to less than 18 blocks , so we dont have too many pending HTLCs?
These aren't really correlated. However I strongly recommend you increase that CLTV delta to more than 18 blocks (our default is 40, and we're looking at increasing it even further). This is a security parameter, if you can't get a confirmation in that period, then you can risk losing HTLCs.
can you elaborate what you mean with chain fees? does the fee_sat parameter of the payment affect this? shouldnt this also be an [Err] log instead of a debug one?
So it's possible that you have enough to send, but once you add the HTLC, those fees are too much.
can you tell that from the logs ive posted?
In the initial issue you wrote When creating a hodlinvoice on 3
, but from the logs it looks like you attempt a payment from lnd-3
is that correct?
From the logs
"remote_pubkey": "0245d3a17856831ff07e70e1963cb89ec545b5be7cdeccf311a736bb2e2e25ee13",
"channel_point": "606249f2b0cad6976cbb120d242dfc90c327648dfccb5b3e6275e819b5366b89:0",
"chan_id": "2581288264158347264",
"capacity": "15000000",
"local_balance": "14879772",
"remote_balance": "119284",
we can see that the remote balance is already below the channel reserve (150000
).
Background
Im running 3 LND instances
lnd-1--chan--lnd-2--chan--lnd-3
When creating a hodlinvoice on 3, i get the following error:
[DBG] LNWL: ChannelPoint(606249f2b0cad6976cbb120d242dfc90c327648dfccb5b3e6275e819b5366b89:0): May add outgoing htlc rejected: commitment transaction dips peer below chan reserve
The channels have pending / stuck HTLC, but the amount of those is not as high as it would cause the above error.
From lnd-2
LND-2:/# lncli --rpcserver=localhost:10000 --macaroonpath=/data/chain/bitcoin/testnet/admin.macaroon --tlscertpath=/data/tls.cert listchannels --peer $LND1 |grep unsett "unsettled_balance": "79543", "unsettled_balance": "59172",
LND-2:/# lncli --rpcserver=localhost:10000 --macaroonpath=/data/chain/bitcoin/testnet/admin.macaroon --tlscertpath=/data/tls.cert listchannels --peer $LND3 |grep unsett "unsettled_balance": "0", "unsettled_balance": "115114",
Your environment
lnd
0.14.2uname -a
on *Nix) ubuntubtcd
,bitcoind
, or other backend bitcoindlnd-2 listchannels lnd-1
lnd2 listchannels lnd-3
lnd-3 log