I get it, it's a huge topic. I've watched a lot of what nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshscy566r 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.

Reply to this note

Please Login to reply.

Discussion

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? 🤷