Resonance Cascade The II's avatar
Resonance Cascade The II
npub18hvy...q4vy
Watching the consumption of things we currently value, cascading into an energy network
#nostr feels like what social networking would’ve been if it evolved directly from IRC and Usenet rather than being captured by big platforms like Facebook and Twitter. Just an unencumbered vibe
Poinsot just confirmed, if you are concerned about CSAM being on your Bitcoin node, simply, do not run a Bitcoin node. V30 is a direct attack on decentralization
Tornado cash Devs - "we didn't intend for bad actors to use our service, it's for anyone" Samurai wallet devs - "we didn't conspire to commit money laundering" Bitcoin core devs - "we didn't envision our changes, to become a CSAM transmission service"
Bitcoin Core "maintainers" need only to look at tornado cash and samurai wallet developers to work out where they may end up!
If you owned an aircraft, and you had a group of people that maintained it, and over time these "maintainers" started making radical changes, from the original designers specification. Would you be concerned about unintended consequences?
My #Bitcoin node runs on a Debian based i7 3770S with a 2TB drive. This CPU is almost 15 years old and performs other tasks and services. At idle along with POE switch running a few other devices and modem router it pulls 79 watts from the wall. I want Bitcoin to always be able to run on old hardware.
If #Bitcoin Core v30 supporters truly want to sign and publish arbitrary data, they already have #NOSTR, which uses the same private key cryptography, without spamming Bitcoin with junk. The push to expand OP_RETURN isn’t about necessity, it’s about ego. They want to piggyback on Bitcoin’s proof-of-work just to stamp their digital trinkets onto the chain, while offloading the costs of their vanity project onto every node runners who has to carry that bloat forever.