Multiple large vendors that support lightning network vendors are seeing practically no usage by anyone: https://x.com/CoinCards/status/1809702144288882870
For the diehard technologists, it's interesting to note that Satoshi's original whitepaper called for a much larger blocksize (32MB, verse 1MB pre-SegWit/Lightning); myself, I ran BitcoinUnlimited with 16MB block acceptance well into 2018 (I'm anti anti anti SegWit/Lightning).
For some reason, years of BIPs have claimed that "1MB is necessary due to bandwidth limitations..." which even in 2017 was horseshit... but now it's 2024 and I can get 300mbps fiber for $57.99/month (with a ping <3ms).
HODL.
Miners are (and always have been) allowed to mine blocks containing zero transactions (i.e. ~0kB, not including necessities). It's us nodes that choose to reject/accept (of course there is Venn overlap).
This was common until block congestion actually started encouraging senders to include transaction fees; these [still!-]voluntarily fees represent a healthy addition to the blockreward, so most miners incur the minimal overhead for much-greater profit.
Yet zero-transaction blocks continue to be mined (albeit less-frequently).
Aint' nobody else got time for that.
Bitcoin Cash (BCH) functions as Bitcoin, digital cash, still, Bitcoin (BTC) is a digital Ponzi scheme for morons run by the US government.
Layer 2 is helpful but does not entirely remove the need for space on chain. In LN for example, every channel opening and closing uses block space.
Hint hint hint
I say illusion of scalability because it's still hamstrung by Bitcoin in a major way. You still need to use Bitcoin to enter the system, which is a big bottleneck. For security you also need to be able to settle to the Bitcoin blockchain in a cheap and reliable way, which just won't scale with a congested blockchain.
Lightning is honestly pretty shit and it's not at all a solution to Bitcoin's problems.
You set aside some funds on the global ledger and then you can use those funds to transact in a much more efficient, truly p2p manner, without touching the global ledger. Eventually, you net out everything and settle it all at once on-chain, utilizing its features to resolve any conflicts.
.. between the two parties that started the link, up to the initial value. It's so limited as to be useless. It's like a bar tab where you have to put down a deposit of the maximum amount you might spend first.
https://docs.lightning.engineering/the-lightning-network/pay...
But to make that work, you have to be online in real time to receive funds. It's not like on-chain transactions that complete without needing your direct involvement. If you're not online, then somebody has to do that on your behalf and now you're back to having someone else custody your funds. Here's a good article explaining it:
https://github.com/moneybutton/yours-channels/blob/master/do...
(You also need someone online monitoring for fraud, even without intermediates, but at least that part can be outsourced without trusting someone with custody.)
Assuming of course that there's a path between the sender and receiver, and that there's enough liquidity at each step of the way.
Otherwise, you need to setup a new channel, paying dearly for it once more.
If Bitcoin scalability is the problem Lightning Solves, then it almost tautologically fails when you realize that entering into a Lightning Channel requires a base Bitcoin transaction. If every person on Earth tried to take on-chain Bitcoin into a LN Channel, it would skyrocket the fee-rate.
The only other option then would be for all Bitcoin purchased to exist on Lightning, so people simply buy LN Bitcoin. This is not impractical to get started; exchanges simply send and receive LN BTC. But Lightning security relies on the ability to get a transaction posted to the base layer Bitcoin.
If everyone is using lightning, and thousands of users are attacked on Lightning at once, the chain would not be able to handle the influx and would leave many victims. Not only that, but the LN node network would naturally centralize, especially with liquidity requirements.
It would be much better to properly scale some base layer.
So practically: not a good solution.