Since April, the number of Knots nodes operators are significantly raised and Core’s falls.
The transaction policy of both clients is the foundation behind migration.
Medusa, a Bitcoin Wallet, announced that the infrastructure of its nodes was migrated to the customer Bitcoin Knots, according to a June 15 statement. “We decided to abandon Core’s lack of consensus, his arrogance and lack of respect for Bitcoiners and nodes,” said the team behind this Wallet.
He motion of Medusa, a Lightning Network (LN) purse that does not require identity verification (KYC), arrives when the Nodes runners with Knots experience a sustained increasechallenging the dominance, still in force, by Bitcoin Core.
According to data From Cindance at the time of this article, Knots operates almost 2,700 nodes, representing more than 12% of the total nodes (almost 22,000), an unpublished percentage. Last April, when migration to Knots was enhanced, there were 840 operators, so the current amount is equivalent to a rise of around 221% since then.
The relevant thing is that, since April the number of Knots operators grows notoriously while, in coincidence, Core falls. The versions of the latter customer total more than 19,000 nodes, a number that comes in decrease from the 21,000.
Also, separately contemplating the different versions of Core and according to the platform Clark Moody Dashboard, Knots is positioned third in preference among the nodes.
In the following image extracted from that source it is observed how Knots was left behind versions 28.1 and 29 of Bitcoin Core:
Differences in transactions policies
User migration, as cryptoics reported, responds to the transactions policies of both clientsthat define which operations a node accepts, stores in its Mempool (a temporary space where pending confirmation transactions) and broadcasts are stored.
Knots offers greater control over these policies, allowing users reject unwanted transactions of Non -financial data (such as text or images), considered by many bitcoiners as spam
Core, on the other hand, in its latest version (v.29) maintains a limit of 80 bytes for op_return transactions, the operation code that allows to embed non -financial data (such as metadata or images) in the Bitcoin file. However, its next version, v.30, will raise this limit to 100,000 bytes.
The Core adjustment towards a higher limit in Op_return, perceived by some bitcoiners developers as permissive excess, could continue to facilitate diverse uses, from data inscriptions to applications that divert the original Bitcoin approach as a monetary system.
Knots, on the other hand, aligns with those who prefer to restrict those capacities, offering tools to filter transactions.
Thus, Medusa’s decision to adopt Knots would reflect a commitment to a more selective approach to transactions, while competition between Core and Knots continues to mold the Bitcoin infrastructure.
