LNBϟG

Official LNBϟG account in Nostr ;-) I like zaptoshis! :)
SimpleX: https://simplex.chat/contact#/?v=2-6&smp=smp%3A%2F%2Fhejn2gVIqNU6xjtGM3OwQeuk8ZEbDXVJXAlnSBJBWUA%3D%40smp16.simplex.im%2FNnGdg9PBPg0uaTinG_11zZ7j5jX2QwXL%23%2F%3Fv%3D1-3%26dh%3DMCowBQYDK2VuAyEA0F3-LRe490bk_FV00E6Y2rySPuW_jE0R6FgyPK1dDUo%253D%26srv%3Dp3ktngodzi6qrf7w64mmde3syuzrv57y55hxabqcq3l5p6oi7yzze6qd.onion

Public Key

npub1ngumlqmus6xkrmvvee4yc7swh9h4uk7vpq4ddt7a2jtvkc22y0asrse3pv

NIP-05 Address

boss@lnbig.com

NIP-57 Address

lnbig@getalby.com

Profile Code

nprofile1qqsf5wdlsd7gdrtpakxvu6jv0g8tjm67t0xqs2kk4lw4f9ktv99z87cpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsysy4pk

Publishing to

relay.damus.io

nos.lol

nostr-pub.wellorder.net

Author Public Key

npub1ngumlqmus6xkrmvvee4yc7swh9h4uk7vpq4ddt7a2jtvkc22y0asrse3pv

Show more details

Last Notes

2023-11-09 14:38:31

Some nodes did not work for about 8-9 hours (from 2023-11-09 03:38 UTC time). I apologize for the downtime. The reason is that one of the running bitcoin core servers did not respond, which is why the lnd servers shut down themselves. #LNBiG #Downtime #Status #LightningNetwork

2023-09-23 21:33:20

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

2023-09-23 20:34:53

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
#nevent1q…7fdw

2023-09-23 20:25:24

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
#nevent1q…ar26

2023-09-23 20:16:09

- reply

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.

2023-09-23 20:11:49

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

2023-05-11 17:41:18

- reply

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 ;-)

2023-05-11 17:37:04

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

2023-04-01 22:35:24

- reply

🫂

2023-03-10 14:44:13

- reply

Sometimes the network graph of LN has old IPs for some nodes. It's problem of v0.15.5 of LND. I hope that v0.16 will resolve this problem (I often moved nodes to other hardware because I am doing now an upgrade of servers hardware)

2023-03-10 11:21:34

- reply

Everything was ok yesterday. Please more info if you have a problems now

2023-03-03 19:27:01

The last 24 hours of LNBIG (2023-03-03):
Amount transactions: 10181
The sum of transfered BTC: 19.80413689
Percentile 0%: 1 sats
Percentile 25%: 10000 sats
Percentile 50%: 47978 sats
Percentile 75%: 160001 sats
Percentile 95%: 930932 sats
Last 24 hours fee earning: 36196 sat (0.00036196 BTC)

2023-03-01 15:43:58

- reply

The Lightning protocol operates in millizatoshis. Including the LNURL (and NIP-57). But for some reasons unknown to me, the developers of LNURL solutions often ignore this and round it up to a thousand (1 sat). I patched the snort a little with my hands so that I could specify fractional parts. More than 90% of NIP-57 providers do not work, but the jp55 lightning address works with msats. And I sent to him 1/1000 of satoshi 😃

2023-02-28 18:54:03

GE 😄

2023-02-28 18:37:16

https://nostr.build/i/nostr.build_41942ff5b5ee6e78504e392cdfb28905bf8441b56eb4598ed503328bd52c43ea.png

2023-02-28 14:52:33

- reply

It seems to me that the best thing so far is for the client programs of Nostr to offer simple settings to go only through Tor, and in no other way. #[5] ?

2023-02-28 14:49:42

- reply

And what about mobile devices? For example, if the Nostr client periodically loads feeds (for a certain npub through a "subscription")? Have a VPN enabled all the time? And if you need to turn it off sometimes? However, in Android, you can specify that certain applications go only through a VPN. But it's all complicated for the average user.

2023-02-28 13:56:21

- reply

Just imagine that any oppositionist of the government has a Nostr account. In this case, it is enough for the authorities to put in Login his well-known key, go in and see all the keys (nostr accounts) of those who wrote to him personally in correspondence. Next, it is a matter of technique to calculate the IP addresses of those who wrote to him. Especially if you deploy a network of fake relays in order to collect data.

2023-02-28 13:52:57

- reply

If anyone wants to personally check - go to https://snort.social/, click "Login" and specify any npub* key - you will see everything as the owner of the public key would see, except that you will not be able to read the text of personal correspondence with anyone. It's not very nice to find out about it ;-/

2023-02-28 13:46:12

- reply

Given the specifics of Nostra, that it is impossible to delete data is even more dangerous. For example, you wrote to someone in private correspondence and anyone can then see with whom and when you corresponded. This is, in fact, public metadata in plain sight... I think in the future we will learn about more than one case when they were arrested for it (China, Russia, etc..)

2023-02-28 13:43:58

To be honest, I am concerned about the anonymity in Nostr. If you suddenly don't know, then when you view your account through the web version, then:
1) Every relay knows your referrer (site name)
2) Relay knows your IP address, and probably your npub (when there is a request to subscribe to a feed about a certain user - about you yourself)
Also, if you correspond with someone in a personal chat, everyone can find out with whom and how many messages (only they do not know the text of the correspondence). All this is quite dangerous for those who want to remain anonymous. For example, in totalitarian regimes it is very dangerous.

2023-02-28 13:33:21

The snort web interface (i deployed it at localhost from github sources) works very smooth! It's best web interface by my opinion

2023-02-28 13:27:58

Today LNBIG stats (2023-02-28):
The last 24 hours of LNBIG:
Amount transactions: 8291
The sum of transfered BTC: 10.53969468
Percentile 0%: 1 sats
Percentile 25%: 10000 sats
Percentile 50%: 37001 sats
Percentile 75%: 70000 sats
Percentile 95%: 341022 sats
Last 24 hours fee earning: 15609 sat (0.00015609 BTC)

2023-02-27 14:51:40

Thank you #[0] for NIP-05! Now it looks very cool!
https://i.imgur.com/WvsPO5A.jpg

2023-02-16 13:41:29

- reply

PV 🌞