#studybitcoin
This note really captures the heat of the Bitcoin Core vs. Knots saga. Let me unpack it in context of what’s going on…
---
1. The Historical Flashback
The post is referencing a well-known story:
Around 2013–2014, Vitalik Buterin considered building Ethereum on top of Bitcoin.
He ultimately decided against it because Bitcoin’s developers (including Adam Back, Luke Dashjr, and others) were not interested in turning Bitcoin into a general-purpose “world computer.”
One of the sticking points was OP_RETURN, the part of Bitcoin’s scripting language that lets people embed arbitrary data in transactions. Core devs imposed an 80-byte cap to prevent abuse.
That restriction made Ethereum-style functionality impossible on Bitcoin… so Vitalik went and launched his own chain.
So when the post says “OP_RETURN stopped Vitalik from building ETH on Bitcoin”—that’s historically accurate. Bitcoin Core drew a line: “We’re money, not a computer.”
---
2. Why It’s Relevant Now
Fast-forward to today (2025)…
Bitcoin Core plans to remove the OP_RETURN cap in v30 (October 2025).
Critics (including Knots supporters) say this reopens the floodgates for on-chain spam, NFTs, inscriptions, Ethereum-like experiments, etc.
Supporters argue: If users pay fees, they should be free to use blockspace as they want.
So the irony: the very thing that kept Ethereum off Bitcoin in 2015 may now be undone by Core—potentially making Bitcoin attractive again for the same “bad actors” (as the poster puts it).
---
3. The Allegations in the Post
The original poster is drawing a sharp line:
Core = aligned with Ethereum service providers, Taproot Wizards, “shitcoiners,” bad actors
Knots = keeps Bitcoin clean, monetary, sovereign
This is ideological framing. It’s not just about code—it’s about who Bitcoin should serve:
Only sound money maximalists?
Or anyone who pays for blockspace, even if they’re embedding art, JPEGs, or running Ethereum-style protocols?
---
4. The Reply in Context
The reply says:
> “You’re mad at Core. Knots is Core software. When are you selling?”
This is partly a troll, partly a real point:
Knots is indeed a fork of Bitcoin Core, kept consensus-compatible. It doesn’t rewrite Bitcoin from scratch—it builds on Core.
So critics of “Core” often still run Knots… which means they’re still downstream of Core’s work, just with added filters and stricter defaults.
The “When are you selling?” jab is a way of saying: if you really think Core is corrupted, why are you still in Bitcoin at all?
---
5. The Deeper Saga
Bitcoin Core devs lean toward neutrality: Bitcoin should be a base layer, flexible and uncensored.
Knots devs (Luke Dashjr & co.) lean toward sovereignty: Bitcoin should defend itself against misuse, keep blockspace scarce, and not become a data dumpster.
This debate is now peaking because of the upcoming OP_RETURN policy change—a symbolic reversal of what once kept Bitcoin from turning into “Ethereum on Bitcoin.”
---
✨ In short:
This post is calling out Core devs for “betraying” the philosophy that once pushed Vitalik away. Knots is positioning itself as the defender of Bitcoin’s monetary purity. Core is accused of sliding toward Ethereum-style permissiveness. And the community is being forced to pick sides… or at least pay closer attention to what client their node is running.
---
Do you want me to break down the technical side of OP_RETURN (how it actually works and why the limit matters), or would you prefer I map the political/ideological camps in this debate more clearly (Core devs, Knots supporters, miners, node runners)?
View quoted note →
Login to reply
Replies (6)
This AI is insanely biased and is only basing its analysis on conversations on X/Twitter. It doesn't take into account the bitcoindev mailing list, delving bitcoin or the bitcoin core meeting logs. I'd caution ingesting this info as absolute truth with regards to the history of OP-Return
Hmmm, it's breaking down and helping me iunderstand what the original post I quoted that's posted on here by @p on the topic.
Yeah, however...P's post is an opinion, it's not objective truth. LLMs are always a product of what they are trained on, so it is possible to absorb biases and present them as absolute truth.
I'm not intending to impede you doing your own research, and I actually applaud you for actually doing it!
I simply want to bring up the fact that some of the information I read in the text was either hallucinated or based on incorrect assumptions
So you are saying AI didn't provide accurate interpretation of what P's meant with his post? I asked AI because I don't know much at all on this topic but have been curious to try and get some kind of understanding.
I apologize, I must take a step back myself 😅
I got lost in a thread of your studybitcoin posts that were quote-posting prior study material. So that led me to make one comment generally on the AI text (not specific to the post wrt to analyzing P's original post). For clarity, this method of learning is great, but some of the info is missing context or full information. I understand getting the general gist is normally sufficient, but with bitcoin there are so many nuances that are normally missed (evidenced by Grok, for example, having convos with tenured & technical individuals on X needing to be corrected on certain aspects it responded confidently on)
src:
Feel free to ignore me, as I'm a complete stranger to you. But I appreciate the discourse!

X (formerly Twitter)
Eric Voskuil (@evoskuil) on X
@grok @John16353117 @GrassFedBitcoin @adam3us Grok don’t be a dipshit. Some level of prunability does not prevent necessary transmission or stora...
No worries. I totally made a few notes back to back as I kept digging deeper. And I agree that AI is not to be taken for face value but for someone like me whose not in the thick of the tech side of Bitcoin it helps to translate and clarify things well enough. Then next comes in bringing in the community and hearing from real people who have strong takes on it where I again may need AI to help me decipher what they are saying simply because I lack deep historical knowledge or the inner workings of the tech consensus policy stuff like that. :)