I hope everyone here agrees with me that writing Ordinals/BRC20 in the blockchain using JSON is a massive
space monster. (You might also believe that Ordinals are negative in their entirety and should be removed. Well there's another thread on this board for saying that.)
Lightning would be a nice way to solve this BRC-20 bug problem. I am in favor of moving these transactions off chain. I saw this article a few days ago.
Unfortunately, wishing it onto the Lightning network won't make it happen.
1. The Lightning network has less than 5% of transactions, by volume. It's not being used. Moving this to Lightning would at best only solve 5% of the problem.
2.
OP, but the problem, Ordinals/NFT users want to store their dick pics and fart sounds in a bank vault, not in a museum. They believe it's part of the attraction, and part of what makes them "more valuable".
Wind FURY nailed it. This spam only has value because it is being immortalized in something valuable - the Bitcoin blockchain.
Unfortunately, this is coming at the cost of Bitcoin's original purpose as a peer-to-peer method of exchange. It is destroying it's value.
This bug is acting more like a parasite that is killing it's host.
Lightning is not a real solution and this BRC-20 bug needs to be patched.
I know I commented in some places that all this live money on these tokens is preventing us from pulling the plug, but come to think of it, if we can get even a slice of these users to dump their spam on some off-chain protocol instead, using one of the new technologies, then that would be a good time to push a "deprecation" of unlimited Taproot data size and eventually shut it down on the rest of those BRC20 holdouts.
Because the general sentiment of the dev mailing list, is that currently nothing is going to happen. Perhaps they are thinking that because they might still see a use case in unlimited Taproot witness size.
Now with these alternate technologies springing up like Taproot Assets, Ark, and others, when people eventually script those things creatively on those protocols, it will hopefully be agreed on by core devs that nobody has actually used Taproot witness size for anything useful and go along with its deprecation.