I respect @LynAlden greatly for all her financial knowledge and everything she is doing to move #bitcoin forward but I do think she is wrong here. We need to actively and unconditionally guard the #bitcoin garden at all costs.

Everything that is created by humans needs maintenance and safeguarding to keep it developing as intended. Bitcoin is money, which is an unavoidable human emergent technology but it is not gravity, it is not a layer 1 natural phenomenon where humans are bound to it instead of the other way around. Let's keep fighting the trolls out of our created garden. The faster the blockchain data size grows, the faster potential node runners are eliminated. Nodes are the decentralization force of bitcoin. Decentralization is what makes bitcoin. Freedom requires vigilance. Do not fall complacent and be ready to fight to protect that which matters. And this issue matters for bitcoin decentralization.

Reply to this note

Please Login to reply.

Discussion

Complacency implies a problem. If I perceived there to be a problem, I'd be happy to vigorously defend it.

I don't view JPEGs or anything else that takes up block space as a problem, given that there is a firm limit on block space.

The only concerning thing I see is UTXO bloat, which was mostly a temporary issue when it was a fad. It's able to be priced out. The OP Return debate doesn't contribute to UTXO bloat, which is why I put it in my "non-issue" category.

No graffiti in my node ssd. Knots helps me choose. Core doesn't.

I run Knots from now on. Simple.

I suggest you find some time to explore this side of Bitcoin and excell just you have done on others.

Remember, getting nice with shitcoiners that want to spill in my node is not a Core devs decision but MY CHOISE!

I choose Knots as long as I'm satisfied and abandoned Core.

Fullstop.

Fair. The threat of this issue can be perceived at different degrees of intensity per individual but the response to it is still a binary. You are either acting against it - meaning you are actively protecting it - or you are facilitating it - even by inaction.

There are two major problems here. Even though UTXO bloat is not a direct consequence of the usage of OP_RETURN, it is an indirect one and it’s not the only issue stemming from it.

First, the UTXO bloat is only an issue because of other spam waves - yes, waves that have been priced out but spam waves nonetheless that bitcoin is becoming more accommodating of - which only increases there reoccurrence in whatever form they may come. The social layer of bitcoin should be the first defense for these attacks. Why let adversarial agents close to your best weapon in this war? Why let them fiddle and test a few bolts? Yes, we might have a tank with a thousand tight bolts - so who cares if only one gets damaged by these non-monetary mercenaries - we still have 999 bolts that are still strong and ready when they are needed, right? Yes, but we are also one bolt weaker because of poor stewardship and lack of vigilance and vision. It’s one thing to get damaged during a legit attack, another is to get weaker by inaction.

These waves have also been funded by short term projects and interest trying to test out the waters of bitcoin. But this vector of attack can be exploited by bigger agents with more sinister motives and larger chests of wars. Why leave an opening that is fairly easy to defend? Why give intel to potential weak points to enemies? Why not actively fix the weak link in the chain?

The second point - even if this is considered just inconsequential graffiti, it is raising the threshold to be able to run a node with accesible hardware - which is an attack vector to decentralization, one of the most important aspect of bitcoin. Spam cannot fill a block more than its intended MB size, but it artificially adds data to the blockchain that now needs to be stored in nodes - forever. Nodes are volunteer - they incur in running nodes without monetary payback or incentives - why make it harder for them?

Bitcoin is man-made, it is a system that needs to be protected - it is not a greater-than-humans, force-of-nature like gravity. We need to give it maintenance and protect its design for it to work as the system was designed to work to be able to achieve its monetary end.

Even though I disagree with you here - I don’t want to appear adversarial towards you. Thanks for all your hard work on the financial side you do for bitcoin. Really appreciate it. Thank you.

OP_RETURN isn't an issue for Bitcoin. You're right about that. It's an issue for me, and anyone else who's using resources to run a node. And when software developers design software that does things I don't want it to do, they'll be treated like the other software developers that write software that does things I don't want it to do.

You're right that it doesn't have to be some big thing. But I'll definitely be glad to see more and more people finally switching over to the software that puts the control in their hands, rather than treating them as a mere user of their own hardware.

Seems like Core's got a lot of contributors though who came up in the age of the cell phone, so perhaps they don't know any better than to treat the owner of the hardware as a simple user who needs someone to protect them from themselves. Some of use find that attitude repugnant and downright disrespectful, and we'll vote with our root access.

I can’t wait to validate CSAM! Thanks pedos!