It‘s not a vulnerability nor a security issue! It’s just a use case you don’t like. That’s all, don’t pretend otherwise!
Don’t get me wrong, I also think that inscriptions are useless, but the difference is that I don’t tell people how to use bitcoin.
Login to reply
Replies (5)
It’s been years since Bitcoin Core filters prevented the appearance of abuse similar to inscription, and yet I haven’t seen a single person complain about it.
https://x.com/giacomozucco/status/1735150513203593576?s=20
Learn to read. Or code. Or whatever it is impacting your ability to understand that this IS a vulnerability.
Can I ask for clarification for what Core is vulnerable to? What are the ramifications for never fixing this 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
$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..😐