Bitcoin wallet Medusa has announced that its node’s infrastructure has been migrated to customer Bitcoin Knot, according to a June 15th statement. “We decided to abandon Core’s lack of consensus, his arrogance, and lack of respect for Bitcoiner and Node,” the team behind the wallet said.
Medusa Movement, a Lightning Network (LN) wallet that does not require ID verification (KYC), is Knot node runners experience a sustained increasechallenges the domination of the Bitcoin core.
According to Cindance data at the time of this article, Knots operates almost 2,700 nodes. Represents more than 12% of total nodes (almost 22,000), unpublished percentage. When the transition to knot was tightened last April, there were 840 operators, so the current volume amounted to an increase of around 221% since then.
What’s related is that, by chance, Core Falls grows while the number of knot operators has become famous since April. The latter customer version is totaling over 19,000 nodes, down from 21,000.
They also looked into different versions of Core individually, according to the Clark Moody Dashboard platform. The knots are placed third and third among the nodes.
In the following image extracted from that source, we observe how the knots of versions 28.1 and 29 of Bitcoin Core were left.
Transaction policy differences
As reported by Cryptoics, users migration, It supports transaction policies for both clientsdefines the operations that a node accepts, its members (a temporary space where pending confirmation transactions are pending) and the broadcast is saved.
Knots give you stronger control over these policies and allow users reject unnecessary transactions of Non-financial data (text, images, etc.) by many bitcoiners spam.
Meanwhile, the core maintains the 80-byte limit for the op_return transaction in the latest version (v.29). This is an operational code that allows you to embed non-financial data (such as metadata or images) into a Bitcoin file. However, the following version v.30, This limit will rise to 100,000 bytes.
Core adjustments towards the higher limits of OP_Return, perceived as a generous overload by some bitcoiner developers, could continue to promote diverse use, from inscriptions of data to applications that divert the original Bitcoin approach as a financial system.
On the other hand, knots are consistent with those who prefer to limit their abilities; Provides tools for filtering transactions.
Therefore, Medusa’s decision to adopt a knot reflects his commitment to a more selective approach to transactions, but the competition between the core and knot continues to form the Bitcoin infrastructure.