Bitcoin Knots Surges During the Core v30 OP_RETURN Dispute
Bitcoin Knots' share of publicly reachable nodes surged during the controversy over Bitcoin Core v30's default OP_RETURN relay policy, with one widely cited tracker putting Knots above one quarter of reachable nodes by September 14. The migration turned a developer-policy argument into observable node-operator behavior.
By mid-September 2025, the dispute over Bitcoin Core v30's planned relay-policy changes had moved beyond mailing lists and social media into visible node-operator behavior. Bitcoin Knots, an alternative full-node implementation maintained by Luke Dashjr, was gaining users rapidly because it retained stricter default filtering policies. On September 14, Bitcoin.com reported Coin Dance data showing Knots above 25% of publicly reachable nodes, up sharply from the preceding week.
The argument centered especially on Bitcoin Core v30's treatment of OP_RETURN data. Core developers planned to raise the default data-carrier limit and allow multiple OP_RETURN outputs, while critics argued that the change would encourage non-monetary data storage and weaken node operators' ability to discourage it. Supporters of the Core change argued that restrictive relay policy could not prevent miners from including such data and could push users toward less transparent or less efficient encoding methods. Knots became the main software vehicle for operators who wanted stricter defaults.
Node-share estimates were contested and should not be confused with a vote on Bitcoin's consensus rules. Reachable-node trackers observe only nodes that advertise themselves publicly, methodologies can differ, and contemporary critics questioned whether some Knots counts were inflated. Even with those limitations, the migration was historically significant because it demonstrated real operator response to a policy dispute before Core v30's final October release. The controversy then continued into a broader Core-versus-Knots governance fight later in the year.