LN node: balances mismatch

[simpic]

I'm running lnd and I manage it using Thunderhub.
I have opened 2 channels (1,3M and 1,0M as capacity) and I had to pay some fees for onchain txs, including extra fees for a CPFP tx for the first channel (using bumpfee command). Since the fees have been charged on BTC balance, shouldn't the total LN balance be 2,3M?

Why instead I have this balance?



Missing 6689 sats...

[1714507699]

1714507699

[1714507699]

1714507699

[LoyceV]

Missing 6689 sats...

Is that the reserved amount, meant as on-chain fee to close the channel later on? Or is the amount labeled as "Not Available" already the reserved amount?

[nc50lc]

It could be but the amount labeled as "Not Available" is not corrisponding to the missing amount.
-snip-
What am I missing?

In the "Channels" tab, do you have any other channel beside those two?
If so and if it's offline or similar, it may be the listed "Not Available" balance.

[simpic]

It could be but the amount labeled as "Not Available" is not corrisponding to the missing amount.
-snip-
What am I missing?

In the "Channels" tab, do you have any other channel beside those two?
If so and if it's offline or similar, it may be the listed "Not Available" balance.

No, I have just the 2 channels I have opened.

[simpic]

Please make me to figure out what is wrong with the amount of my Lightning balance!
Now the channels I have opened are 3 (1M + 1,3M + 2M) and 9169 sats are currently locked for channel closures (it should be corrisponding to "Not Available" in the image below)... So why the total is not 4,3M but 4,289,841 instead??!?



What am I missing?

[WZBcoin]

I am having problem with my LN wallet (RAspiblitz) and while searching for solutions and help. I come across this option which I think  can help you know about output balance differences.

OP_CHECKSEQUENCEVERIFY in one of the discussion at bitcoin stackexchange forum. where the term was clarified.

It basically checks, if an input's sequence number is smaller than the sequence threshold (1 << 31 = 2147483648), and if so, it will compare the nLockTime against the sequence number of the input.

This may give you some insight into the wallet balance output... Hope I am not misleading you, but give alook at that.