Recently, I have found that Bitcoin developers are stuck in a passionate dispute over the proposal to eliminate the long-standing 80-byte constraints imposed on the Op_return function. As this technical standoff intensifies, an alternative Bitcoin client known as Bitcoin Knot has witnessed a notable climb with the adoption of nodes.
Op_return controversy drives a surge in Bitcoin Knot adoption
The proposal, introduced by Peter Todd, aims to eliminate the 80-byte limit on OP_Return output. This sparked a considerable pushback from developers who viewed this change as opposed to the spirit of Bitcoin’s design.
Supporters argue that existing caps are whimsical, outdated and prone to wobbling. Certainly, Bitcoin’s order inscriptions and runes are already moving along the limits. Developer Luke Dashjr has described as a major critic of abolishing the 80-byte ceiling of Op_return. He labeled the plan as “total madness” and framed it as a direct attack on the network.
Dashjr warns you that it may loosen the data guard rail. The dispute burned a prominent jump in the intense Github debate, censorship claims and Bitcoin Knot’s development in April. Knots is an alternative full-node build engraved from Bitcoin core and tuned for granular control.
Compared to Bitcoin Core, it expands Knot Ship extensions, additional patches, and Member Politics dials that control transactions in node relays or archives. On April 1st, 674 knot nodes were visible, and today the tally reached 1,006. However, with this increase, Bitcoin Core remains a common client.
As of 4pm on Saturday, 20,213 public Bitcoin core nodes are now reachable. Of the 21,326 aggregated public nodes, the core accounts for 94.78%, while the knot claims about 4.72%. If a knot node refuses to consider something that is considered spam, i.e. oversized Op_return data, etc., the Core node can propagate those transactions as long as it meets Bitcoin consensus rules and Core’s Mempool parameters.
Even if knots emerge as the most dominant clients and refuse to relay consensus valid transactions such as core nodes supported by remaining minority peers and miners, they can ultimately shake up their transfers. A tolerant mining policy that runs the core nodes ultimately guides the transaction to the block, but propagation can be slower if knots dominate and most relays are controlled.
Furthermore, even under this theoretical scenario, the knot will not become “Bitcoin” due to pure node counting. As long as both the knots and cores adhere to the same consensus rules, each represents Bitcoin. Clients will stop matching with Bitcoin when hard forks rewrite those rules, and in addition to nodes, communities, Bitcoin miners determine the longest and best breeding chain as a real ledger. Therefore, although the aggregation of the knot nodes is interesting, it remains insufficient to block data storage if the OP_Return cap is lifted.