The other restrictions prevent the same issue. OP_RETURN is not the only contiguous region that can be abused. There is no "different issue" addressed by RDTS.
There's also no evidence an OP_RETURN-o...
This is not true: OP_RETURN has been uncapped at the consensus level since its introduction in 2014, the attack vector was open all along and everyone technical knew about it, including the press.
You are actually contradicting yourself by affirming both "OP_RETURN is not the only vector" and "v30 opened this attack vector"... in the same message 🤦.
You also reject that capping OP_RETURN would be a sufficient change, but pretends that RDTS is doing nothing more than reversing Core v30... 🤔
Since you can't ignore that your arguments are loaded with technical and logical fallacies, and since you are essentially taking your peers for manipulable morons, I can only conclude that the good of Bitcoin isn't the point here. Sad to see a long-term contributor go down such a path, but at this point this is clearly malicious behavior.
Thank you for your past contributions. May you someday come back to your senses. 🫡
You are actually contradicting yourself by affirming both "OP_RETURN is not the only vector" and "v30 opened this attack vector"... in the same message 🤦.
You also reject that capping OP_RETURN would be a sufficient change, but pretends that RDTS is doing nothing more than reversing Core v30... 🤔
Since you can't ignore that your arguments are loaded with technical and logical fallacies, and since you are essentially taking your peers for manipulable morons, I can only conclude that the good of Bitcoin isn't the point here. Sad to see a long-term contributor go down such a path, but at this point this is clearly malicious behavior.
Thank you for your past contributions. May you someday come back to your senses. 🫡
21❤️1
