The way I see it, the only thing that needs to happen is to add nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk's anti inscriptions filter. This is essentially a bug that was introduced as a result of changes that were needed for lightning to work and it makes sense the fix the bug.
Once that is done I think bitcoin should ossify as much as possible and the innovation should happen higher in the protocol stack.
I can see that argument but I'm not sold. Filter seems anti for me. I like lightning but if it/taproot has damaged the base layer... As I have said, my head hurts
I get it, it's a huge topic. I've watched a lot of what nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr has had to say about it on his YouTube channel and I think he lays it all out very honestly and makes an iron clad case.
Ultimately, spam filters have always been a part of bitcoin, but in changing bitcoin for lightning a bug was introduced that allowed a new way to spam. We should just add a filter to cover that too.
https://x.com/boomer_btc/status/1918320027192664349
This is quite good.
Yeah Bob is a legend
Has anyone noticed that Bitvmv2 has been putting abritary data into the UTXO set rather than OP Return like Casey and his ordinals. Not a fan of Lukes 83 byte cap limit filters as this introduces "permission" into a permissionless network. But can't help but wonder why everyone are so focused on arbitary data on the OP Return when recent activity has mainly been Bitvmv2. These arguments are best had at bitdevs 🧡
The real concern IMHO as stated by LaurentMT:
"Concerns about jpeg and ordinals spamming the Bitcoin blockchain are a distraction.
You should be concerned about a state-backed usd coin using the Bitcoin blockchain as its data availability layer and outpricing the monetary use of bitcoin."
🤗
If people look at blocks. Most ordinals activity are like 0.00000400 BTC at the moment. Not really a concern? 🤷
