You want to stop changing Bitcoin? Start by rolling back Core v30. Core v30 changed Bitcoin by removing your ability to set datacarrier limits (PR #32406). They took away a config option that existed since 2014. That's a protocol policy change disguised as "no change." BIP-110 doesn't change Bitcoin - it restores your ability to choose what your node relays, just like you could in v0.9 through v29. Running 29.2? Enjoy missing security patches and CVE fixes. The "don't change" crowd always ends up running ancient, vulnerable software because they can't distinguish between breaking changes (Core v30) and enabling changes (BIP-110). Bitcoin isn't a statue. It's a consensus system. The question isn't "change vs no change" - it's who controls the change: you or Citrea-funded Core devs? Stay on 29.2 if you want. But don't pretend you're preserving Bitcoin while Core turns it into a file-sharing network for monkey JPEGs. References: View quoted note → View quoted note →