It also does not mention that technically bitcoin cannot accomodate 1 billion users to use it every day for their transactions without causing the network to increase fees and price out many users.
That's on L1. But 1 billion users on the Lightning network is doable. But that's not going to happen as long as there are
multiple competing LN implementations competing against each other. There must be just one standards maker, and making another LN reference client won't help you with that because you will just end up with the N+1 problem (look it up on XKCD).
I propose the community will do a decentralized election process by means of running the LN client they prefer to be the reference body (this process will be significantly easier as Lightning Labs/lnd is already enveloped in scandals around its own implementation, and there are no other major competitors to c-lightning & lnd).
doesnt matter if LN is run but different dev teams on different protocols(separate sub-nets)
or there is a single LN... the problem is all the versions lf LN have major flaws..
the main being lack of consensus protocol (fails to solve byzantine generals problem)
the next being the actual paying of more people on a network
by which the three directions for LN are..
a. master hubs everyone has a channel with.. (avoiding routing)
b. users playing pass the parcel down a stream of users (using routing) where the more users on the network means more hops to go through to reach everyone
c. users require more channels for more potential destinations to have a more direct contact without as many hops.
each of these directions fall flat into the problem of value liquidity.
a. this scenario needs a master hub to have alot of value locked up to have liquidity in each of its channels to palm off to its customers
b. for every hop along a lengthy route they have to rely on each person along the route to have available balance and be online to service that payment. the more people in the network. the more distance between source and destinations, the more hops means the more chance of running into a roadblock
c. the more channels a user needs to open the more funds it needs to lock up (like the (a) hub problem, but where funds are locked on the user side) where the user becomes a hub. meaning if all they have invested/acquired of crypto is like $800 worth. 2 channels is $400 per channel 16 channels is $50 a channel. which then limits how much they can spend at at given time to a destination available only on one channel
LN has many other flaws too. not just routing bottlenecks of liquidity issues of channels or the requirement of all parties involved in a payment needing to be online. or the requirement of middlemen to sign whereby they can just be assy and refuse, holding payments up/delaying 'success'/fail messages. or the fact that the more hops needed=more fee due to having to pay each hop. or the issue around having to map larger routing tables becomes a bloat of gossip the bigger the network gets and the more data required just to update. or the issues around centralisation of hubs or the dilution of spendable value if users had to have more channels.
.
but also that the settlement and punishment parts and the initial funding locks are not firmly ruled systems which are audited by the network to ensure compliance.. yep LN is not a consensus network and does not fulfil the byzantine generals problem