Introduction
Bitcoin was designed to be decentralized — a financial system without kings, gatekeepers, or political middlemen. Yet, beneath the surface of its immaculate blockchain lies a subtle power struggle — not over coins, but over code.
This silent tension between Bitcoin Core and Bitcoin Knots developers raises a critical question: Who really controls Bitcoin’s direction?
What Is Bitcoin Core?
Bitcoin Core is the original and most widely used implementation of the Bitcoin protocol. It’s what most nodes run, and it’s maintained by a group of trusted developers led by long-time contributors.
These developers are responsible for:
- Reviewing and merging code changes
- Releasing new Bitcoin versions
- Ensuring network stability and backward compatibility
In many ways, Bitcoin Core acts as the de facto authority in Bitcoin’s development — not by law, but by reputation and trust.
Enter Bitcoin Knots: The Fork That Watches the Watchers
Bitcoin Knots, created by developer Luke Dashjr, is a fork of Bitcoin Core — essentially a version that adds extra features and stricter rules. It’s fully compatible with the Bitcoin network, but it serves as a check-and-balance to Core’s dominance.
Knots differs by:
- Including policy and monitoring tools that Bitcoin Core excludes
- Enforcing more conservative security and privacy standards
- Rejecting certain patches or policy changes deemed too risky or centralizing
In essence, Knots represents a philosophy: that no single group of developers should have unchecked influence over Bitcoin’s evolution.
The Politics Behind the Code
While Bitcoin’s protocol is decentralized, its development isn’t immune to politics.
Here’s where the friction begins:
- Centralization of trust: Bitcoin Core’s maintainers control the main repository. That means they decide what gets merged — and what doesn’t.
- Ideological divides: Some developers favor cautious, minimal changes; others push for innovation and scalability.
- Power perception: Running “Core” often equals legitimacy in the Bitcoin ecosystem. Knots challenges that narrative, saying decentralization should include development, not just mining or nodes.
Szabo vs. Adam Back: The Clash That Shapes Bitcoin NFTs
The quiet tension between Nick Szabo and Adam Back goes beyond personal disagreement.
It’s a battle over Bitcoin’s identity — whether it should stay a lean monetary protocol or evolve into a broader digital canvas for data, art, and NFTs.
Their conflicting ideas directly influence how Ordinals and Bitcoin NFTs are perceived today.
Szabo’s Warning: Legal and Economic Risks
Nick Szabo, known for his early work on smart contracts, views Bitcoin’s blockchain as sacred ground — a space meant for financial data, not arbitrary storage.
He argues that inscriptions and Ordinals bring legal and economic complications.
Each NFT written onto Bitcoin stays there forever, increasing the chain’s size and potential liability for those running nodes.
In his view, this could make Bitcoin more expensive to maintain and possibly expose operators to unwanted legal scrutiny.
Szabo’s philosophy is simple: keep Bitcoin pure, simple, and defensible.
Adam Back’s Perspective: Preserve Bitcoin’s Core Purpose
Adam Back, CEO of Blockstream and one of Bitcoin’s earliest supporters, also raises concerns about Ordinals — but for technical and practical reasons.
He believes the blockchain should prioritize sound money, not storage for digital art.
Large on-chain files, he argues, waste block space and crowd out real financial transactions.
Still, Back tends to be more pragmatic than Szabo.
He doesn’t oppose innovation outright but favors policy restrictions that discourage what he calls “JPEG spam.”
His goal is to keep Bitcoin efficient and aligned with its original purpose as digital gold.
The Technical Divide: Node Policies and On-Chain Data
Ordinals depend on embedding data in witness or script sections of transactions.
This design means full nodes must store the data permanently.
For developers like Szabo, that’s a problem — it increases storage costs and weakens decentralization.
Meanwhile, Back and the Bitcoin Core team explore ways to limit data-heavy transactions through mempool and relay policies.
In contrast, alternative clients like Bitcoin Knots may remain more open to inscriptions.
This diversity keeps the debate alive and reflects the community’s ongoing balance between innovation and discipline.
Impact on Ordinals and NFTs
The Szabo–Back disagreement ripples through the NFT ecosystem.
If Bitcoin Core implements stricter limits, it could slow the growth of Ordinals.
Wallet developers and marketplaces might also reduce support, making it harder for users to mint or trade Bitcoin-based NFTs.
However, if miners continue to accept and prioritize high-fee inscription transactions, the Ordinals market could still thrive.
Higher fees mean greater miner revenue, giving them an incentive to support NFT activity.
This creates a tug-of-war between economic interest and ideological purity.
What It Means for Bitcoin’s Future
This debate matters because it shapes how decentralized Bitcoin development really is.
Should a small group of maintainers decide what’s “allowed” on the chain, or should free-market incentives rule?
There’s no clear answer, but one thing is certain — the conversation around Szabo and Back highlights how culture and code collide inside Bitcoin.
As the community experiments with Ordinals and new layer-based NFTs, this tension will guide future updates.
Whether Bitcoin becomes a platform for creativity or remains a minimalist monetary network may depend on how this philosophical divide evolves.
Why It Matters
Most Bitcoin users never think about which node software they’re running. Yet this quiet divide could shape Bitcoin’s future in several ways:
- Consensus & Upgrades: If different implementations disagree on rules, it can lead to chain splits or hard forks.
- Governance Transparency: A diverse developer ecosystem prevents concentration of power — vital for Bitcoin’s ethos.
- Network Resilience: Competing clients like Knots ensure that bugs, exploits, or centralization risks in Core don’t endanger the entire network.
Simply put: multiple implementations keep Bitcoin honest.
A Decentralized Network Needs Decentralized Code
Bitcoin’s strength lies in its ability to resist control — whether from governments, corporations, or individuals.
But decentralization isn’t automatic. It requires constant vigilance, diversity of thought, and alternatives like Knots that challenge the status quo.
As the community debates the next steps in scalability, privacy, and regulatory resistance, the real battleground might not be on exchanges or hash rates — but in the GitHub repositories where Bitcoin’s future is written.
Conclusion
The question “Who really controls Bitcoin?” doesn’t have a simple answer.
Power in Bitcoin isn’t owned — it’s earned, distributed, and constantly contested.
In that sense, the quiet tension between Bitcoin Core and Bitcoin Knots isn’t a flaw. It’s a feature — proof that Bitcoin’s spirit of decentralization still lives, line by line, commit by commit.
Trade on MEXC with Zero fees.


