they have latched on to the "lifting op_return limits in relay policy enables csam" which is factually incorrect. this can happen today without any changes to core, and it doesn't make it any easier either due to preferential peering of libre relay nodes.
basically they are just using this factually incorrect statement to attack core devs and to attract state level attacks.
It’s pathetic and gross. Honestly I was going to stay out of this debate but the Knotzis have forced me to wade in.
this is exactly the kind of info ive been looking for.
this is exactly the kind of info i look for during flame wars. actually code understanding, from actual code contributors, addressing the actual core claims.
Can you explain this better? How can this happen today?
Im not trying to make a point, im really trying to understand
because uncapped op_return is the actual rules of the network. capped op_return is an unenforceable policy that is easy to route around.
now if we think this is bad, we should softfork an actual limit so its impossible to get around.
When you mean easy? How easy, easy for very technical people, or like direct submission to miners? Because if its not feasible to reliably route around the op_return limit I don't see why you should be basically removing it
easy as in you can go to https://opreturnbot.com/ and put in whatever you want. this uses libre relay as their backend.
if you want something custom you can just download librerelay and send it that way.
people creating large op_returns with image data need to be somewhat technical anyways. if they can do that then they can download librerelay and broadcast it to a miner
there is no "upload jpg" on the bitcoin client, you will be using custom software regardless. and it can be as easy as a website. knots doesn't do shit all to stop it.
All non-monetary data transactions can be fixed.
Its because filters works. Thats why runes and ordinals shitcoiners are scared from tight nodes policies.
