pull down to refresh
0 sats \ 1 reply \ @aliceandthewonderland OP 9 Jan \ parent \ on: LN channel reserve question bitcoin_beginners
It seems you’re correct—I tested it myself. With a 500k inbound channel using Voltage, it appears to set a 1% reserve of the total capacity, which amounts to 5,000 sats. I was able to successfully send sats until the outbound liquidity was reduced to 5,001 sats. However, it seems the system doesn’t allow the balance to drop below 5,000 sats, as I kept encountering insufficient balance errors.
Don’t know why Bitcoin Design explained it like reserve value will dynamically changed on local liquidity end.
The commit fee is changing based on mempool fees. That is affecting directly your channels "can send" and is very visible on smaller channels.
But the channel reserve is mostly 1%. I think is possible to set thet % in your node settings, but I never use it.
Read here more about commit fee:
- https://lightningwiki.net/index.php/Fees
- https://bitcoin.stackexchange.com/questions/89232/why-is-my-spendable-msat-much-lower-than-msatoshi-to-us/89235#89235
Then you have also the channel buffers:
https://github.com/lightningnetwork/lnd/blob/6dea86428d031171af30119e3f6599820dc5454a/lnwallet/channel.go#L3803-L3815
Then you have also the anchor reserves. I suggest to always have a UTXO of max 100k sats in your node onchain wallet, that can be used for these anchor reserves and bumping fees for opening/closing channels.
That's why not all wallet and node interface, will show up the correct "can send" or can receive" because are many other hidden aspects and sometimes in their inteface is quite hard to be reflected. But as a user you always have to take them in consideration. when is about to send or receive into a channel.
reply