Thread

“If the developers are shown to be able to censor, then they will become required to censor.” Andreas the GOAT. He’s the reason I got started in the first place, and this is the final word on the debate as far as I’m concerned. Running Bitcoin Core 30. Not sorry, GFY.

Replies (26)

The size limits are censorship argument is retarded. Transaction size limits still exist in v30 mempool policy. Blocksize limits still exist in consensus rules. I'll assume he's talking about censoring non-monetary data via bip444. The argument that if you "censor" (block non-monetary data) now, you will be forced to censor other things (OFAC?) is also retarded. That only works if there's one node implementation and everyone blindly upgrades it. Node runners choose to not upgrade or to switch implementations, as we have recently seen. If Core v31 had OFAC censorship we would fork off. Andreas knows this.
Imo it’s not a matter of censorship. Core 30 changed and increased data limits and sizes that were set in the original code. It’s like trying to alter the US constitution in an attempt to “modernize” it. There’s some things that best left alone. Feel free to correct me if I’m wrong, but I’m pretty firm on that belief.
↩ replying to jgbtc
i can imagine myself in similar shoes to his in a different timeline. sometimes you forget to question yourself when you keep seeing others around as dumb. it puts you in a rabbit hole of bad ideas. and you dont realize until the things you caused touches you back. and then its a long journey getting out of the hole. many has a midwit era. but if you are stuck there as a middle aged man, then that's a problem. not to mention nothing he says in the video makes sense in the context of reality, and what things are. you can stop him multiple times while he talks and correct him. everything he says built on false information that's also built on false information, and some are built on to each recursively.