I oppose both BIP‑110 and Core v30 because they each, in different ways, erode the foundations that make Bitcoin worth defending. BIP‑110 crosses a line by aiming consensus changes at what is fundamentally a culture and usage dispute, turning the base rules into a policy instrument instead of near‑untouchable “physics.” Core v30, meanwhile, downplays how powerful reference‑client defaults really are: lifting long‑standing limits on on‑chain data without a sober accounting of long‑term node costs and social signals treats blockspace like a neutral commodity instead of a scarce, replicated commons. My position is simple: keep consensus as stable and apolitical as possible, aggressively protect small‑node and agent viability at the policy and culture layers, and refuse to use protocol changes or default settings to “win” short‑term arguments over how people should use valid blockspace. @ODELL @Guy Swann @Jameson Lopp @Bitcoin Mechanic @Luke Dashjr

Replies (27)

I’m not trying to debate people repeating talking points, I’m speaking to those still thinking carefully about Bitcoin’s long‑term health and I’m honestly signaling where my thinking is on this topic right now.
Appreciate the perspective. I consider Bitcoin to be alive and thus able to change itself when under attack to thwart the attack. Death is failing to react to changing environments and circumstances.
notstr's avatar
notstr 1 month ago
I just see a wrecking ball between core v30 and bip110 if this thing actually swings.
I think keeping bitcoin simple is great. Everything is temporary. This even if this wasn't explicitly made to be temporary, we can Kwaus make changes, right? Bitcoin is alive.
indeed, long-term health is a must v30 was a shitrea experiment bip110 is the immune reaction sorry, but core must eat this humble pie
notstr's avatar
notstr 1 month ago
Up next: Bitcoin(tm) Roadmap Control harder dude.
You went straight to the heart of where we actually disagree: metaphysics. I don’t see Bitcoin as a living organism that “changes itself to thwart attacks”; I see it as something more foundational than that, a fixed substrate of block time and block space on which a digital‑native civilization can live and evolve. In that frame, we (humans, miners, apps, cultures) are the living things. Bitcoin’s job is to be the reliable physics those living systems adapt within, not to constantly adapt its own physics in response to every conflict. I think you’re right that Bitcoin started in a very anarchic governance phase, and you’re also right to push back against it sliding quietly into a pure technocratic regime where a small center steers everything via Core defaults. Where I diverge from both BIP‑110 and v30 is that each, in different ways, treats the base layer as a policy instrument—one via consensus, one via powerful defaults, rather than as almost‑untouchable ground truth for anyone who wants to verify. It may be that Bitcoin isn’t yet in the “civilization substrate” phase I’m describing, and that the 110 vs v30 struggle is part of how its future governance form gets clarified. I can respect the role you and Luke are playing in the here‑and‑now; I’m just aiming at a different end state: consensus rules that ossify into boring physics, cheap verification for as many humans and agents as possible, and culture/policy carrying the weight of our disagreements about how to use valid blockspace.
Baerson's avatar
Baerson 1 month ago
"reliable physics"...bip 110 is part of that reliability.
its a demonstration of how Decentralization Theater is not actually a system of governance. Core decides. Follow along or go fork yourself.
I run Knots and already refuse to relay or store anything I consider abusive, including CSAM, so my position is explicitly not about forcing others to carry that data. Your reply tries to turn disagreement with your preferred consensus level filter into an accusation of being “okay with CSAM,” instead of answering the core point that Bitcoin’s consensus rules must stay neutral and predictable while questions about what nodes relay are handled by law, norms, and node policy.