That’s how some describe the fierce conflict between Bitcoin Core and Bitcoin Knots — a battle that could redefine the very nature of the protocol.
At stake: Bitcoin’s neutrality and the future of the blockchain.
Bitcoin Core — the most widely used software to run a node — was originally coded by Satoshi.
But Core ≠ Bitcoin.
Any Bitcoiner can choose another implementation. That’s decentralization.
Now, a storm is brewing inside Core…
A new proposal suggests removing the 80-byte limit in the OP_RETURN field.
It might sound technical — but it’s huge.
Why? Because it shifts Bitcoin from being a monetary network…
…toward a general-purpose blockchain like Ethereum or Solana.
Removing this limit enables:
- On-chain data storage (images, NFTs, tokens…)
- Ethereum-style use cases
- More congestion, higher fees, and heavier nodes
And most controversially:
the new limit would be non-configurable.
Translation: Core devs decide for everyone. A clear break from the principle of individual sovereignty.
Tensions escalate.
Some critical voices — like bitcoinmechanic — are banned from the Core GitHub.
Words like censorship, conflicts of interest, and centralization drift are flying around.
Here’s what it looks like:
✔️ ACK = Accept the change
❌ NACK = Push back
Enter: Bitcoin Knots.
A fork of Core, maintained by OG dev Luke Dashjr, which keeps user freedom intact. In 2025, Knots is gaining serious traction.
The war isn’t just in code — it’s ideological: “Don’t trust. Verify.”
Every node operator has the power to say NO.
The community is mobilizing:
- Cut donations to compromised devs
- Launch educational campaigns
- Expose bad actors
- Boycott biased podcasts & events
Because in Bitcoin, vigilance is the last line of defense.
