Recent data shows that Bitcoin Knots now powers more than 12% of the 21,908 public Bitcoin nodes. The growing preference for Knots stems largely from debates surrounding Bitcoin Core’s development, particularly proposed adjustments to the OP_RETURN function and its data capacity.
12% and Climbing
Data from Coin Dance shows a steady rise in Bitcoin Knots adoption, with 2,673 public nodes now running the software. The shift follows Bitcoin Core’s decision to eliminate the 80-byte limit on OP_RETURN transactions. The 80-byte limit refers to the maximum amount of non-payment data—like messages or metadata—that could be included in an OP_RETURN transaction output.
Bitcoin Knots takes a more cautious approach, keeping OP_RETURN transactions limited to 42 bytes while giving users tools to block spam or low-value transactions. Its growing adoption pointedly reflects disagreement with Bitcoin Core’s move to eliminate the 80-byte limit—a controversial change now merged in Core’s code repository on Github and expected in its October 2025 release.
By the end of 2024, approximately 410 Bitcoin Knots nodes were operational, translating to roughly 12.5 new nodes coming online each day over 181 days. With Bitcoin Core currently maintaining 19,186 nodes, Knots would need 554 days at its current growth rate to reach half that figure – far exceeding the 107 days remaining until October 2025.
While 12% may sound significant, even if Bitcoin Knots climbs to 50% node adoption, larger OP_RETURN transactions can still be relayed and confirmed—as long as enough Bitcoin Core nodes transmit them and miners include them in blocks. Relay policies vary by implementation, but consensus rules permit these transactions to be mined and deemed valid across the network.
Right now plenty see the uptick as more than technical—to node runners it’s a symbolic protest in code, a signal of pushback against Bitcoin Core’s policy shifts. Node variety doubles as a quiet form of decentralized defiance. Knots nodes can’t stop transactions from getting mined, but they can clog the propagation lanes for heavier data within their own relay circles—especially if their numbers keep climbing.
