I have a feeling that the node "c=" is experiencing some issues. The thing is, I've noticed that its capacity has decreased over the past few days. You can verify this yourself using the viewer at amboss.space. Another indirect sign of problems is that when I tried to cooperatively close channels with it a few minutes ago—channels that haven't been used for payments in 14 days—several channels were unable to be closed cooperatively, even though the node is online. This usually happens when a node has lost data about the channels. The node itself is online, but when a remote peer connects to it and requests, for example, to cooperatively close a channel that was with it, the node doesn't respond because it no longer has data about the channel. With this node, I have the feeling that this exact problem is occurring. It would be interesting to know from the owners of this node whether they are indeed experiencing any problems currently, whether they've had a failure or not. I think they have. #LightningNetwork

Hello everyone! I decided to try out a new optimization algorithm that came to my mind recently. It works as follows: channels that haven't been used to send payments in the last 14 days are considered suboptimal for maintaining liquidity, and I close such channels. Also, to avoid closing channels that were opened less than 30 days ago, because I take on the commitment to keep a channel open for at least 30 days, I exclude those channels from this closing condition. Previously, I thought a channel was well utilized when the amount sent and received exceeded the channel's capacity, meaning that payments at least once fully utilized the entire channel. But now I realized that's not entirely correct, because there could be channels that were used well and actively several months ago, but for example, no payments have been made in the last two weeks. Does it make sense to keep such channels? I think not. Today's closing algorithm, it seems to me, won't lead to a decrease in the number of passing payments because it will close channels that haven't used a single payment through the #LNBiG network in the last two weeks. What's most interesting is that there are actually a lot of such channels. It's approximately one sixth of the total capacity I'm using on my side in open channels at the moment. Yes, and I almost forgot, I decided to execute the channel closures right now because the Bitcoin transaction fee is currently at its minimal level, and channels can be closed with a fee of 1 vbyte/sat #LightningNetwork #Lightning #LN

Hi everyone! The node called Hub-1 has changed the server and IP address accordingly. A scheduled migration to another server, to different hardware, was carried out. Current information about IP addresses can be found in the Lightning Network Explorer amboss.space at this link:

Amboss Space

LNBiG [Hub-1] - 034ea8...76c0d5 - Amboss Space

LNBiG [Hub-1] - 034ea80f8b148c750463546bd999bf7321a0e6dfc60aaf84bd0400a2e8d376c0d5 - 363 channels - capacity 38,538,708,313 sats - Bitcoin Mainnet ...

#LNBiG #LightningNetwork

Hello everyone! I wanted to let you know that from around mid-November to about today, which is two and a half months, I kept all my channels with zero outgoing commission (completely zero), meaning the base fee was zero and the fee rate was zero. I did this out of curiosity to see the maximum number of payments and the maximum amount of bitcoins that would pass through. After this period, I can roughly say that under these conditions I had a maximum of 30 bitcoins per day, averaging around 20 bitcoins per day, with the number of transactions at about 20,000 per day. Today I've decided to end this experiment because I don't see much point in continuing it, as it probably negatively affects other participants in the #Lightning network due to it being sheer dumping. Therefore, from today, I raised the fees, but not by much; I set the fee rate to 10 ppm and the base fee to 10 millisatoshis. It will be interesting for me to see how many payments will now go through and what the daily transaction volume will be... #LNBiG #LightningNetwork #Stats