Replying to Avatar waxwing

With the drama of BIP444 I've seen a lot of people confused about the nature of soft-fork vs hard-fork. This might help:

Back in the block size war we had a lot of similar confusion, mostly because it isn't really very clear cut. Some people talked about "evil soft forks" to try to get rid of the simplistic notion: "soft forks are much better and hard forks are much worse" which tends to persist (naturally). The problem is that whether a fork is contentious or not is *much more important* than whether it fits the "soft" or "hard" technical definition.

When a fork isn't contentious, then the soft vs hard distinction (restricting the ruleset or relaxing it) really matters a lot, because "passive" network participants (imagine a piece of hardware that will never get updated to a new bitcoin version, in the extreme) will be fine with the first and not with the second.

When a fork *is* contentious, and miners, following economic incentive, end up choosing different rulesets to support different bitcoin users, then the chain genuinely forks into two histories. The fact that one ruleset is more restrictive than the other is part of the story but doesn't change the fundamental point that we have a chain split. This of course did actually happen meaningfully with bitcoin-cash in 2017. The term "evil soft fork" was some people trying to shake others of the misconception that if a fork is "soft" it's not coercive and not forcing action on anyone; that's definitely not true *if the fork is contentious*.

#bitcoin

From a protocol-governance standpoint, “if you want different rules, fork” is exactly how Bitcoin’s immune system is supposed to work. It’s not censorship, it’s voluntary divergence: consensus by exit, not coercion by vote.

Let’s make this explicit:

1. Bitcoin’s consensus norm

Bitcoin’s social contract isn’t majority rule; it’s individual sovereignty. Every node chooses which chain to follow. The overwhelming unwritten norm since 2017 (SegWit2x) is:

Protocol changes that alter core properties—block size, script rules, censorship neutrality—must attract overwhelming, near-unanimous opt-in consensus.

If a minority can’t persuade the majority, they’re free to fork. That’s how BCH, BSV, and other spinoffs emerged. BIP-444 violates that equilibrium by proposing restrictions without universal buy-in.

2. The “fork-off principle”

Any faction that wants to redefine Bitcoin’s scope—whether by expanding or contracting it—should bear the coordination cost of the fork, not impose it on everyone else.

In other words, “Don’t make the default chain pay for your moral panic.”

If they truly believe BIP-444 is essential, let them hard-fork into a “clean-chain” variant—call it BTC-Puritan—and see if market participants follow. The market will instantly settle the argument through price discovery and hash-rate migration.

3. Functional precedent

When miners and devs tried to push SegWit2x, the network’s spontaneous coordination (via UASF) demonstrated that sovereignty resides with validating nodes, not political majorities. BIP-444 supporters trying to push a “temporary censorship fork” would hit the same wall.

4. Philosophical coherence

Agency-centered perspective: freedom of use is an emergent property of voluntary systems. BIP-444 is coercive not because it restricts bytes, but because it unilaterally redefines legitimate agency on the chain. If you don’t like how others use block space, out-compete them economically or build a sidechain—don’t rewrite reality.

In short:

Yes. Let them fork off.

That’s not hostility—it’s protocol hygiene. The network that respects voluntary divergence remains antifragile; the one that enforces purity decays into bureaucracy.

Reply to this note

Please Login to reply.

Discussion

That reads like LLM output. Whether it is or not hardly matters. It's correct, at the very least it's roughly correct.

So then Knots would be the forked chain and V30 Core would be the continuous chain?

How do I support Knots being the main chain besides running it instead of Core?

Is BIP 444 a Knots thing? Excuse my ignorance.

You run the software you agree with. The market decides which chain is the most valuable through price and adoption.

But a separate chain means a new ticker? What does my BTC become? Does one of the chains become something else, like Bitcoin cash did?

In the case of a chain split you'd have coins on both chains. You could literally just do nothing until the dust settled, and you'd be good to go when you finally updated your software to the winning chain's implementation, or your custodian did.

Or, if you wanted you could sell the coins on the chain you don't agree with and buy more of the ones you do agree with. In that case the .gov likes to tax you.

Really the best path forward is just not to do anything as a user. This is also why forking-off into a new chain tends to not work so well, since you have to convince enough people to move with you.