-
Core V30 expands op_return data up to 100,000 bytes.
-
Other referents of the ecosystem, such as Adam Back, will run the next version of Core.
Jimmy Song, author of five books and self -conside by an «expert» in Bitcoin, said he will not adopt version 30 of the Bitcoin Core client.
The launch of this Core update is scheduled for October and has generated debate for its most visible change: the expansion of the data limit in the op_return transactions up to 100,000 bytes, which enables to register in the blocks non -monetary information that Many describe as «spam.»
In a publication on September 16, Song explained the reasons why he will not migrate to the new version.
The first one is linked to the «Obsolescence of the option data carriersize»a parameter that until now allowed to limit the amount of non -monetary data in transactions.
Song added:
«The argument in favor of obsolescence is based on the idea that this particular filter has no effect. Although it is formulated in technical terms, the argument is ultimately an economic statement: that the non -visible effects do not exist.»
Jimmy Song, writer and specialist in Bitcoin.
In that sense, as Cryptonoticias explained, when announcing Core V30, the software collaborators team stressed that users’ freedom to decide how to interact with Bitcoin remains essential “against coercion”, stressing that That autonomy protects the network.
Song’s second reason suggests that, with V30, the option data carriersize It is set by default at 100,000 bytes.
Song questions that this decision was made by administrative and non -technical reasons And as explained:
«The decision is based on political reasons, such as avoiding multiple change requests for each size adjustment. I think this opens the gates too soon and, again, of an unfounded economic claim.»
Jimmy Song, writer and specialist in Bitcoin.
The third point of its rejection is related to the reduction of the minimum transaction rate, which goes from 1 satoshi per Vbyte to 0.1 satoshis per Vbyte. This new practice, carried out by mining pools, has been growing in recent months.
Song argued that this filter had prevented some mining pools, such as Mara Pool, to include transactions considered as spamgiven that They ran a risk of being orphaned (Not included in the blocks). «I think it is unnecessary for both miners and users,» he said.
Finally, Song stressed that he will not adopt Core V30 because, in his opinion, the new transactions broadcast policy Delegates too much in the great mining poolswhich reinforces its centralization.
A different vision: Adam Back
The Song position contrasts with that of other Bitcoiners referents.
As Cryptonoticias, Adam Back, founder of Blockstream, notified it, said that «Probably» will run core v30 And that could use a patch of «preferential peering» (Preferential pairing) If it were available.
The term «preferential peering» It is a technique that allows nodes to connect priority with others that Similar policies apply of acceptance of transactions, for example, limiting extensive data in Op_return.
This practice provides greater control to nodes, but can also fragment the network if isolated groups are formed according to their policies.
For back, the risk of mining centralization is more relevant than Proliferation of transactions with non -monetary data I am not bitcoin.
According to your vision, trying to block such records in the blocks will not really stop its inclusion, while imposing strict filters could concentrate the validation power in less actors.