I would like to present to your attention my node efficiency #statistics. It is built according to my method, which, perhaps, no one has used yet. Here is his description:
For example, we build statistics for the last N days. Creating for each node an array of length N with the following structure for each element:
[ "sent sats in this day", "received sats in this day", "volume of all channels of this node in this day" ]
We take [all transactions transmitted through our nodes node for this period](https://lightning.engineering/api-docs/api/lnd/lightning/forwarding-history), and taking into account the [chan_id_in and chan_id_out](https://lightning.engineering/api-docs/api/lnd/lightning/forwarding-history#lnrpcforwardingevent) of each transaction, we form arrays for each node - that is, we adjust the values "sent sats in this day" and "received sats in this day".
It is necessary to take into account both open channels and closed ones. For open channels, it is necessary to take into account on what day they were open, and for closed ones - on what day they were open and on what day they were closed. We calculate the days taking into account chan_id of channel and the approximate fact that there are 144 blocks in a day. We take this into account to calculate the total channel volume of each day for each node ("volume of all channels of this node in this day"). We take the time (timestamp_ns) of the transaction from [forwarding event](https://lightning.engineering/api-docs/api/lnd/lightning/forwarding-history#lnrpcforwardingevent).
After all the calculations, we calculate the coefficient (K) for each day of each node: ("sent sats in this day" + "received sats in this day") / "volume of all channels of this node in this day"
This coefficient "K" shows us with what efficiency the channels were used that day. After all, you can transfer a stream of 1M sats through channel(s) with a total volume of 1M sats (K will be 1.0), and you can transfer this 1M sats through a 100K channel, but using it is 10x times more efficient (K will be 10.0)!
After all, I take the median value for each node for all days - this will be the K_target value. Then I sort all the nodes by one such value K_target - nodes with a higher coefficient get higher and are more efficient for us than with a smaller one.
And now there will be results ;-)
#LNBiG #LightningNetwork #Lightning #Stats #Algorithm
I would like to present to your attention my node efficiency #statistics. It is built according to my method, which, perhaps, no one has used yet. Here is his description:
For example, we build statistics for the last N days. Creating for each node an array of length N with the following structure for each element:
[ "sent sats in this day", "received sats in this day", "volume of all channels of this node in this day" ]
We take [all transactions transmitted through our nodes node for this period](https://lightning.engineering/api-docs/api/lnd/lightning/forwarding-history), and taking into account the [chan_id_in and chan_id_out](https://lightning.engineering/api-docs/api/lnd/lightning/forwarding-history#lnrpcforwardingevent) of each transaction, we form arrays for each node - that is, we adjust the values "sent sats in this day" and "received sats in this day".
It is necessary to take into account both open channels and closed ones. For open channels, it is necessary to take into account on what day they were open, and for closed ones - on what day they were open and on what day they were closed. We calculate the days taking into account chan_id of channel and the approximate fact that there are 144 blocks in a day. We take this into account to calculate the total channel volume of each day for each node ("volume of all channels of this node in this day"). We take the time (timestamp_ns) of the transaction from [forwarding event](https://lightning.engineering/api-docs/api/lnd/lightning/forwarding-history#lnrpcforwardingevent).
After all the calculations, we calculate the coefficient (K) for each day of each node: ("sent sats in this day" + "received sats in this day") / "volume of all channels of this node in this day"
This coefficient "K" shows us with what efficiency the channels were used that day. After all, you can transfer a stream of 1M sats through channel(s) with a total volume of 1M sats (K will be 1.0), and you can transfer this 1M sats through a 100K channel, but using it is 10x times more efficient (K will be 10.0)!
After all, I take the median value for each node for all days - this will be the K_target value. Then I sort all the nodes by one such value K_target - nodes with a higher coefficient get higher and are more efficient for us than with a smaller one.
And now there will be results ;-)
#LNBiG #LightningNetwork #Lightning #Stats #Algorithm
The **third change** is that outgoing paid channels are opened with a mandatory requirement to support anchor channels from your side!
For most, this change will go unnoticed, but for the owners of the old lightning nodes software, this means that they will not be able to open a paid channel outgoing to them from the LNBiG network (of course, funds for payment will not be taken thanks to the HODL invoice).
I have to do this for the reason that in the current situation it is very dangerous to have channels without anchor support. Such channels are difficult to close if the bitcoin network fee market is growing and remains with a high fees for a very long time.
#LightningNetwork #LNBiG #News
nostr:nevent1qqsdzh8e5r9vgklhu9t9fhmq4a432cvw8rx6akscgun3w9347m62aegppemhxue69uhkummn9ekx7mp0wj7fdw
The other good #news is that the #Tor v3 network is already configured on [those seven nodes](https://lnbig.com/#/our-nodes) that will continue to work.
Each of the seven nodes has an IPv4 and Tor address. #IPv6 I will add later. This means that you can open channels from the Tor network to these nodes. I also added the ability to open outgoing paid channels to nodes in the Tor v3 network (previously, this required a node from the Tor network to make a connection to the my node specified in the instructions for opening a paid channel). #LNBiG #LightningNetwork
nostr:nevent1qqsdpgn7c0updllwh6w7paxc2jwt59qrrsm442xh3vdu25jwfmpk50cppemhxue69uhkummn9ekx7mp074ar26
I have collected and will collect statistics on all good channels and their nodes, and then I will open channels from those 7 nodes that will work further. To do this, I will finish the scripts that will do this. I will try to make everything go as smoothly as possible.
Hello everyone!
There are some #news from [LNBiG](https://lnbig.com/):
The number of nodes of the #LNBiG network will soon be reduced from 25 nodes to 7 ones. For more than a month, the opening of channels has been working only from/to 7 nodes. The list of active nodes is visible in the ["Our nodes"](https://lnbig.com/#/our-nodes) section. #LightningNetwork
A little more detail about this:
I decided to reduce the number of nodes to optimize my network.
Nodes will be closed gradually, with priority on cooperative closing of channels. All channels on the closing nodes were opened more than 30 days ago. This period is prescribed in the conditions when opening the channel as the minimum period that I tried to observe when opening paid outgoing channels.
Hello everyone!
There are some #news from [LNBiG](https://lnbig.com/):
The number of nodes of the #LNBiG network will soon be reduced from 25 nodes to 7 ones. For more than a month, the opening of channels has been working only from/to 7 nodes. The list of active nodes is visible in the ["Our nodes"](https://lnbig.com/#/our-nodes) section. #LightningNetwork
The last 24 hours of LNBIG (2023-06-16):
Amount transactions: 8064
The sum of transfered BTC: 16.17980531
Percentile 0%: 1 sats
Percentile 25%: 15864 sats
Percentile 50%: 73069 sats
Percentile 75%: 189263 sats
Percentile 95%: 831771 sats
Last 24 hours fee earning: 16720 sat (0.0001672 BTC)
#LNBiG #Stats #Lightning #LightningNetwork
The last 24 hours of LNBIG (2023-06-15):
Amount transactions: 10149
The sum of transfered BTC: 23.89853676
Percentile 0%: 1 sats
Percentile 25%: 11444 sats
Percentile 50%: 78706 sats
Percentile 75%: 191132 sats
Percentile 95%: 1132150 sats
Last 24 hours fee earning: 17891 sat (0.00017891 BTC)
#LNBiG #Stats #Lightning #LightningNetwork
I deployed now the fresh version of Snort web app with own imgproxy (imgproxy.lnbig.com)! Welcome to https://snort.lnbig.com ! #Nostr #Pleb #Plebstr #Snort
Except for the subtleties (translate has not been launched yet) - this site is similar in functionality to the original https://snort.social/. This can be useful for those who want to use not one #Nostr network explorer, but several. For example, if the main https://snort.social/ website does not work, you can use #LNBiG fork snort.lnbig.com with own imgproxy site ;-)
I deployed now the fresh version of Snort web app with own imgproxy (imgproxy.lnbig.com)! Welcome to https://snort.lnbig.com ! #Nostr #Pleb #Plebstr #Snort
The **last 24 hours** of #LNBIG (**2023-05-10**):
Amount **transactions: 6679**
The sum of **transfered BTC: 8.11484953**
Percentile 0%: 1 sats
Percentile 25%: 21 sats
Percentile 50%: 14358 sats
Percentile 75%: 100000 sats
Percentile 95%: 411354 sats
Last 24 hours **fee earning: 4651 sat** (0.00004651 BTC)
#LightningNetwork #Stats
https://twitter.com/stephanlivera/status/1654128466575654913 #LightningNetwork #Lightning
Today #LNBiG stats (2023-05-07):
The last 24 hours of LNBIG:
Amount transactions: 64413
The sum of transfered BTC: 13.71202436
Percentile 0%: 1 sats
Percentile 25%: 2 sats
Percentile 50%: 2 sats
Percentile 75%: 2 sats
Percentile 95%: 43235 sats
Last 24 hours fee earning: 7143 sat (0.00007143 BTC)
Now there are very low fees: 1 msat base fee / 10 ppm (0.001% from payment!). Don't forget open channels with https://lnbig.com/ nodes (when on-chain fees will be sane)! ;-)
#LightningNetwork #Bitcoin #LN #Lightning #Nostr #Plebchain #pleb
Right now all the servers are working. Now there is a new version of LND v0.16.1.
One shitcoin overtakes another shitcoin. What's great about that? I don't care ;)
At the moment, the software is being updated on the servers of #LNBiG network, so all servers are being stopped and updated right now. #LightingNetwork
The LND-39 was moved to LND-38, so if you have a troubles with connect of with channels just connect with new URI:
02c91d6aa51aa940608b497b6beebcb1aec05be3c47704b682b3889424679ca490@213.174.156.82:9735
Or use Amboss explorer for example:
https://amboss.space/node/02c91d6aa51aa940608b497b6beebcb1aec05be3c47704b682b3889424679ca490
#LNBIG
The lnd-10 (https://amboss.space/node/02bb24da3d0fb0793f4918c7599f973cc402f0912ec3fb530470f1fc08bdd6ecb5) was moved to lnd-37 server. If you have troubles with connect please only connect to node by this URI: 02bb24da3d0fb0793f4918c7599f973cc402f0912ec3fb530470f1fc08bdd6ecb5@213.174.156.81:9735
#LNBIG