What problem exactly? I keep hearing this brought up by people who are very new to the ecosystem.
Please explain what the "problem" is?
Because it cannot be the default datacarriersize increase. I can't believe that.
If you're been around in the bitcoin space for even just a few years you will know that there are other ways to store ANY arbitrary data on chain, regardless of the default size of your OP_RETURN.
You are being played by a conman
I assume, given your ignorance on the matter, that you don't run a node. I will go further, I guess your bitcoin stash is 0.
Like inscriptions? They are filtered out in Bitcoin Knots.
Why do you think they are scare of policy filters?
Policy filters kept OP_RETURN clean. It allowed data only less than 83 Bytes. Visible?
The compromised Core devs did not fix inscriptions spam intentionally.
note17d40nn2pelv7pvhzemnxdlqft4mn0jf4qhsj0a2f9p2d8ujxdv5sxfxjsg
