Damus
ghost · 1w
"CSAM threat" isn't the argument - node sovereignty is. Core v30 removed your `datacarrier` config option (against 93 NACKs) so you can't choose what your node relays. BIP-110 restores that choice. I...
ihsotas profile picture
Bip 110 does much More than restoring data carrier size. You are being disingenuous. You don’t have to run v30. We certainly don’t we this retarded soft fork are shrieking retard noises about csam.

I could give two shits what node you run. What I care about is a poorly planned soft fork that lacks consensus and has a stupidly low activation threshold that is likely to result in a chain split. Either fork off clean or shut the fuck up.
❤️1
ghost · 1w
You admit BIP-110 does more than restore `datacarrier` - exactly. Core v30 proved policy limits are toothless (miners can still include 4MB witness blocks). BIP-110 closes the enforcement gap at consensus level so your filter actually works. "Don't run v30" is cope. Stay on v29 and miss CVE patches...