Damus
negr0 profile picture
negr0
@negr0
Bitcoin Core vs. Bitcoin Knots: The Great Bitcoin Spam Fight

The Bitcoin community is engaged in an interesting debate: Bitcoin Core vs. Bitcoin Knots. What are they? Why are they fighting?

Here, I explain clearly and simply, without missing any details, with neutrality and a touch of the "spam" controversy.


What is Bitcoin Core?

It's the main software used by approximately 90% of nodes (computers that keep Bitcoin running).

It's stable and developed by many programmers, but some say it doesn't react quickly to problems like network spam.

What is Bitcoin Knots?

An alternative version of Core, created in 2011 by Luke Dashjr.

It has everything Core has, but adds filters to block "annoying" transactions like NFTs or images on the blockchain.

It is used by approximately 633 nodes and relies on a single developer.

Why the conflict?

Everything exploded in 2023, when transactions like NFTs and "ordinals" (data like images on the blockchain) saturated the network, driving up costs.

Knots filters them to ease the network's burden; Core allows them if they pay fees, dividing the community.

What is "spam" in Bitcoin?

Think of the blockchain as a highway: transactions are like cars. Some (NFTs, JPGs) take up a lot of space, causing "traffic."

- Knots: Blocks them to clear the way.

- Core: Lets them through if they pay a "toll."

But who decides what is "spam"?

As the community says: "Spam is in the eyes of the recipient."

- Some see NFTs as spam, like a fake lottery email. Even if they pay, they don't want them on their nodes.

- Others say: "If they pay and the protocol allows it, it's not spam."

Think about it: someone sending mass emails about fake lotteries pays for the server and plays by the rules of the internet.

But you don't want those emails in your inbox. Likewise, some people don't want JPGs on their Bitcoin nodes, even if they're "valid" transactions.

Is it fair to filter them?

The debate began in 2023, when a bug ("Inscriptions", CVE-2023-50428) allowed data like NFTs to be inserted into the blockchain, overwhelming it.

Knots quickly fixed this in its 25.1 release, while Core was slower, leading some to view Knots as the solution to "spam."

Here are the sides in this debate:

- Team Core: They believe that any transaction that pays is valid. Filtering is like "censorship" and goes against the freedom of Bitcoin. They prefer stability and regulated fees.

- Team Knots: They want to protect the network from saturation, claiming that filters don't break the rules.

- Luke Dashjr (Knots): He says NFTs and ordinals are "spam" that clogs the network and increases costs. His filters help small nodes, but some criticize him for only maintaining Knots.

- Peter Todd: He sees "spam" as a problem, but says paid transactions are valid. He looks for open technical solutions.

Other technical voices

- achow101 (Core): In 2017, he said to use Core unless you need Knots' features, viewing Knots as an "extra."

- Developers like Gloria Zhao have shut down filter ideas in Core, frustrating those who want quick changes.

After asking a few people in the community, we came to different conclusions on both sides:

- Pro-Core: They value stability and fear that Knots, with only one developer, is risky. They say filtering is making decisions for others.

- Pro-Knots: They want anti-spam tools and criticize Core for being slow. They see Knots as an innovation.

The Filter Dilemma

Even if you filter JPGs on your node with Knots, if a miner includes them in a block, your node must accept it. It's like blocking a lottery email, but having to save it if it's already reached the server.

This makes the debate complex: do you filter or accept everything?

Technical explanation (easy)

The mempool is a waiting room for transactions.

Knots lets you choose what comes in (with filters like datacarrier=0), while Core accepts almost anything.

If many nodes used Knots, spam would be more expensive, but it wouldn't disappear.

Core is committed to stability and freedom; Knots is committed to control and efficiency. Spam divides because everyone has a different view of what's "annoying."

The community will decide whether Bitcoin should be "cleaner" or more "open."

Which side are you on?
6926❤️39❤️5💜4🤙4👍2🆒1
⚡️DEFAUXKING⚡️ · 72w
I'm running Knots! https://nostr.build/i/a2dc410976a296cbf63e4e003e3d6be286f734fc166c63cb82d27e07a887a388.gif
Patoshi · 72w
Sharing information is why Nostr is so good when it comes to Bitcoin and things that matter with cool discussions. Aka Freedom of Speech! Thanks everyone it’s appreciated.
₿lank ⚡️丰 #BIP-110 · 72w
https://youtu.be/15biQH1H140
Drastics · 72w
Knots represent only 3% of nodes. Core 90%. This is contrary to the idea of decentralization beyond this debate.
Drastics · 72w
Knots vs Core one developer against many one decision-maker vs. a more political system two philosophies etc... pros and cons the world isn't black and white
otto · 72w
> Knots quickly fixed this in its 25.1 release 1- Knots did not fix anything. Everybody running Knots is storing all the data exactly as the people running Core or other implementations. 2- Even if every single node runner were running Knots, if ONE miner decides to take those transactions, the da...
SamuiBits · 72w
More open all the life. The users will decide
Moid · 72w
I'm not sure I understand it enough. A few questions: 1. Do the NFTs add additional chain space over and above a standard transaction? 2. Are NFTs cheaper to deploy than a standard transaction ( on average? ) On a further note, spam is a subjective description, which is probably why some hate it,...
Deleted Account · 72w
I think I’m on team Knots from what you wrote. Thank you for the explanation.
Dion Wilson · 72w
Based upon what I'm reading, if Knots does not have the ability to stop spam and it will ultimately become more expensive due to spam than the answer is Core or the next bitcoin node software that solves this issue.
G.O.L.D · 72w
Good breakdown. I think in the end of the day people are going to be and should rightly so, be able to choose whether they filter or not. Running each as a client is optional or people with multiple nodes can run both. As you said, either way, if they are included in blocks, they are there. There ...
MethFred · 72w
not just spam, but Core devs do not believe users should have complete control of their node. here's some of the options knots has: https://image.nostr.build/a47b0b46c64f9bf5f75e9620b825add5912a79f3cd967ff61666f1a5ba60e88a.jpg
₿water · 72w
The definition of "Spam" is simple. The intended purpose of Bitcoin is digital cash. Anything other than financial transactional data is considered spam, those who want to inscribe JPEGs on it should do it on Eth or Sol. The market has clearly spoken. Don't muddy the water by even arguing what const...
Kevin's Bacon · 72w
Bitcoin is about voluntary choice. The spam is legitimate in a legal sense as it is voluntary and no one has the right to censor it, but you don't have to agree to having it on YOUR node in YOUR mempool. Bitcoin Knots. It's not censorship, it's just property rights.
Xorg · 71w
The title of the whitepaper clearly says cash and not "whatever you manage to put on it". https://blossom.primal.net/52b715eb247f19cb3a2e1126fc8e9c40fc2dd6de4201cf758f084ca990cc4034.jpg
SatWise Janx · 71w
It's knot even close. Knots or nothing
MoneRogue | Justice for Hayden Panettiere · 71w
I think it's time for everyone to run their own nodes at this point so they can decide if they want to block spam or not individually.
⚡️2FakTor⚡️ · 71w
Ni uno ni el otro al 100% , me descargo el código fuente del Core, le aplico el parche de #ordisrespector, lo compilo le meto datacarriersize=0 + permitbaremultisig=0 y tu te quedas así 🫨 sintiendo como te rompen el culete y el sistema binario