But he's never once responded to my criticisms or concerns: It's all innuendo with the "CSAM and shitcoin friendly Core cabal" or some shit like that. I won't deny that there are bad people trying to infiltrate bitcoin development, but don't think for a second that they wouldn't also be trying to infiltrate the Knots side as well, or use the same arguments to hinder adoption.

Replies (1)

I do not see the situation as an acute emergency, even if it is sometimes framed that way by the Knots side. And i agree, it would be naive to assume that any side is immune to compromised actors. Based on what I have observed over the past months, I still lean toward the Knots position. The increase of the OP_RETURN limit was controversial from the outset. For months, the Knots side made it clear that their objective was to reverse the change. Despite that, there has been no visible willingness to seriously reconsider it. More nodes are now running Knots than Core v30. That cannot reasonably be described as a clear and uncontested mandate. Yet even in light of these signals, there has been no meaningful reflection or attempt at compromise. The obvious question remains: why? The main argument in favor of the change is mining centralization. Without the adjustment, fee markets could develop outside node policy, allowing larger OP_RETURN data to be compensated directly to miners. The concern is that this would create long-term centralization pressure. If the real issue is the potential for bypassing node policy, an equally effective approach would be to tighten consensus rules rather than relax OP_RETURN limits. A stricter consensus limit would make large OP_RETURN data fundamentally impossible, eliminate the bypass vector entirely, and at the same time address the broader data concern. This is precisely the direction the proposed fork takes. It may be stricter than necessary, but it attempts to solve the same underlying problem Core claims to address, without introducing new incentive shifts or expanding Bitcoin’s attack surface. I believe the legal dimension is relevant too, even if, in theory, node operators are not doing anything illegal themselves. The fact that they are not responsible for the content does not eliminate the practical risk. If illegal material is embedded in the blockchain, running a node could still expose someone to legal scrutiny or prosecution on the grounds that they are distributing, or storing that data. This risk may be especially significant in developing, or more authoritarian countries, where legal systems are less predictable and due process is weaker. The recent events surrounding Samurai Wallet show that even when individuals are acting within the law, authorities may still pursue aggressive enforcement actions. That reality should be taken seriously when changing fundemental things in bitcoin.
↑