The last 24 hours of #LNBiG (fee rate 700ppm + 1 sat base fee): Amount transactions: 3481 The sum of transfered BTC: 14.46587534 Percentile 0%: 1 sats Percentile 25%: 10575 sats Percentile 50%: 41896 sats Percentile 75%: 223953 sats Percentile 95%: 1361523 sats Last 24 hours fee earning: 799958 sat (0.00799958 BTC) #LightningNetwork

The last 24 hours of #LNBiG (2025-03-16): Amount transactions: 25811 The sum of transfered BTC: 35.06102923 Percentile 0%: 1 sats Percentile 25%: 592 sats Percentile 50%: 10000 sats Percentile 75%: 86062 sats Percentile 95%: 564560 sats Last 24 hours fee earning: 20886 sat (0.00020886 BTC) #LightningNetwork #Stats

The last 24 hours of #LNBiG (2025-03-14): Amount transactions: 25390 The sum of transfered BTC: 25.54321901 Percentile 0%: 1 sats Percentile 25%: 245 sats Percentile 50%: 3175 sats Percentile 75%: 52924 sats Percentile 95%: 510422 sats Last 24 hours fee earning: 17241 sat (0.00017241 #BTC) #LightningNetwork #LN

The last 24 hours of #LNBiG #Stats: Amount transactions: 31291 The sum of transfered BTC: 16.04263519 Percentile 0%: 1 sats Percentile 25%: 56 sats Percentile 50%: 848 sats Percentile 75%: 12320 sats Percentile 95%: 173687 sats Last 24 hours fee earning: 9582 sat (0.00009582 BTC) #LightningNetwork

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 - 365 channels - capacity 45,373,742,699 sats - Bitcoin Mainnet ...

#LNBiG #LightningNetwork