FWITW here’s my take on the Core vs. Knots storm-in-a-teacup. It feels like yet another manufactured crisis aimed at seizing control of the codebase — starting around two years ago with hundreds of millions of dollars burned on transaction fees to spam the network with superfluous data. Tellingly, that activity came to an abrupt halt right around Trump’s election, and now 1 sat/vB transactions prevail as if nothing happened. Despite this, panic is being stirred, with calls to abandon Bitcoin Core for a client maintained by a single developer, who wants to decide which transactions are “good” and get through, and which are “bad” and get memory-holed. It will be telling if the drama continues now that Core has backtracked a bit. If it does, it’s a clear sign this fight isn’t about halting ‘spam’ at all, it’s about control of the codebase. And on that subject: this episode only reinforces the urgency of ossifying the codebase against anything beyond essential maintenance and security fixes, ideally before the original cypherpunks retire. In my mind the deepest confidence and respect must go to those who not only bootstrapped Bitcoin, but also stood firm in defending it during the Blocksize Wars.

Replies (4)

Why does it matter how many devs a project has if it's open source and therefore verifiable by anyone who would consider running it? Knots is basically all the core devs' work with a few differences. I am on the Knots side, simply because Core's actions are unacceptable to me and it is the only alternative. But I do not resort to emotion and ad hominem, which *many* in both sides of this argument are guilty of. That part feels very manufactured indeed. It is exactly what the fiat overlords would like to see as well.
I respect your choice of implementation and for engaging in open, civilised debate. Thank you! It is ultimately what makes the network stronger. Attackers will try to divide us, which is why we must stay focused and grounded in the technical and game-theoretical realities whenever division arises. On the technical side, I think we can agree that control of Bitcoin’s codebase is critical. One developer holding the commit keys is a single point of failure. Even a short-lived failure could cause reputational damage to the network.
The more eyes on the code the better :) I’m with you: I don’t want my node chewing through superfluous data. Filters promise efficiency, but in practice they introduce complexity, edge-case failures, and new attack surfaces… The fee market is ultimately the best arbiter of spam. @calle ‘s explainer nails it.