pull down to refresh
0 sats \ 6 replies \ @r3drun3 OP 19 Dec 2023 \ parent \ on: The Lightning Network is not sufficiently decentralized lightning
I think that article is over simplistic.
More than 30% of all LN nodes on the mainnet running on 5 cloud providers is a problem.
More than 30% of all LN nodes on the mainnet running on 5 cloud providers
How do you know that? Just by reading a chart showing a bunch of IPs?
Do you know how IPs works? From your answer seems that you don't.
If I buy an IP for my home server from amazon cloud, does that mean my server runs on amazon cloud? Is is it literally hosted on amazon cloud?
The answer is simple: NO.
So please DYOR before posting crap.
reply
Private citizens dont usually buy IP on aws or gcp or azure :)
If your node has an "aws IP" which is really a dns name, is it becaus your node instances is running as a service within aws and have a public elastic IP associated to it.
reply
nah, a wireguard vpn setup is more common than you think. I know several node operators who prefer this setup for speed + reliability + privacy.
https://github.com/wtogami/vpn-nat-service-forwarding-howto
reply
thats not entirely true, utilizing aws free tier to get a clearnet ip and then vpn that to your home node is a use case that i've seen at least few noderunners utilizing
of course this is node disproving your original thesis that a lot of capacity is running on major cloud providers but that is a different (non)issue
reply
The page itself states, "(Tor nodes excluded)". So that page is only displaying information about less than 30% of the total number of nodes on the network (source).
So this statement:
More than 30% of all LN nodes on the mainnet running on 5 cloud providers is a problem.
Is incorrect. It would actually be 30% of 30% are on 5 cloud providers, which is 9%, as far any anyone can actually prove.
reply
And private channels
reply