Running core with MAX_OP_RETURN_RELAY=73 instead of the default 83. Am I censoring?
Running core with MAX_OP_RETURN_RELAY=63 instead of the default 83. Am I censoring?
Running core with MAX_OP_RETURN_RELAY=53 instead of the default 83. Am I censoring?
When do I become a censor?
Login to reply
Replies (8)
The CVE is for the vulnerability enabling Inscriptions to bypass node policy (regardless of what it's set to).
There should be no reason to be angry. It's just the normal procedure for security issues
Learn to read. Or code. Or whatever it is impacting your ability to understand that this IS a vulnerability.
Bypass of datacarriersize limit using OP_FALSE,OP_IF
Ramifications are that datacarriersize, an important node policy parameter, is bypassable. I.e. a bug that makes an option in core not behave as intended.
Common Vulnerabilities and Exposures - Bitcoin Wiki
I can read and I can code. That’s why I can say without doubts that inscriptions is not a vulnerability.
$boost
You just don't know what you're talking about. Allowing anyone to insert that much malicious code is a vulnerability. Whether jpegs or something more malicious.
In his heyday John McAfee would have a ball with this. Exposing privacy and damaging security lol. You don't have a clue what the shadowy "supercoders" can do.
And we absolutely do have a say, and an obligation as to what people do with Bitcoin. Not your keys, not your Bitcoin. Not your protocol, not your Bitcoin..😐
That's not a possible conclusion, so either you can't or haven't or are simply lying
😂😂😂 It's funny that you think you can tell me what I have to think or how I have to use Bitcoin. What a fucking hubris!
🙌