Bink developer and co-founder Mike Schmidt commented on the social network on September 22nd. Pull the request (PR or application for change) 33453 Delete GitHub depreciation DataCarriersize With Bitcoin Core. September 30th, this application was accepted and is included in client version 30 (V30). Some of the community interpreted this as an attempt to control the damages of the latest version of Bitcoin Core prior to its arrival in October.
This was commented on Mike Schmidt on September 22, when he presented the proposal.
Today I opened a request for a change to Bitcoin Core to eliminate the obsolescence of options «DataCarrier»y«DataCarriersize». We understand that this is a sensitive issue for Bitcoin Core users, so we will also publish it to (X) to increase visibility and receive comments that are otherwise not appropriate in PR.
Mike Schmidt, Brink Developer and Co Founder
In the context of Bitcoin, the field DataCarriersize Refers to software configuration parameters. This defines the maximum size of bytes in OP_return output that the node accepts to send and weaken in the transaction. Therefore, this field serves as a filter for inscriptions (any data other than expenditure) This allows users to limit the amount of “spam” sent to Bitcoin nodes and blocks.
According to Bitcoin mechanics, this option was completely eliminated until September 30th. However, users can still use it on the Bitcoin Core V30.
Those who support maintaining and using these options are some of Bitcoin’s most enthusiastic supporters, and depriving them of the right to disapprove options is not good for Bitcoin Core or Bitcoin. I know people are still against the value of a given op_return, but this change will allow us to continue to establish value, at least for the core users of Bitcoin, as they seem better. Bitcoin certainly has more battles and greater progress, so I would like to move forward together to fight them.
Mike Schmidt, Brink Developer and Co Founder.
As reported by Cryptootics, Bitcoin Core raises the OP_Return limit by 100,000 bytes. This raises concern for Bitcoiner, who views Bitcoin as an exclusive currency network, and spam is a threat.
This size of the OP_Return field allows more arbitrary data to be embedded in the block. Absence of DataCarrier y DataCarrieresize It implies that Core prevents filtering of OP_Return transactions.
However, the PR 33453 brings you a return option. The community seems safe, but I’m not sure.
For some bitcoiners, DataCarriersize It’s a “broken” option anyway, but Adambak disagrees. On V30, the default number for this option Allow 9 times more data storage than allowed in v29 and previous versions. Therefore, Luke Dashjr is expressed on the subject.
Don’t allow bad actors to deceive you by believing that Bitcoin Core 30 will enable the limits of again Carrier size. (…). In addition to not limiting the default value, they even broke it even further. DataCarrierSize = 83 Now (from Core 30) allows 83 exits that add up to 830 bytes of spam, rather than 92 bytes of spam (not arbitrary at 9 bytes), as in Core 29 and before.
Luke Dashjr, keeps Bitcoin Knots customers.
That said, the default options for these fields You can use or modify them thanks to the changes introduced in Bitcoin Core by Mike Schmidt.
Although counterparts, by researchers at Bitmex, they have not mentioned anything about returns. DataCarriersize The Bitcoin Core V30 concludes that updates are desirable at the individual node level, as it can use the compact block proposals imagined by Matt Corrallo. This proposal benefits high OP_RETURN limits.
However, Bitmex suggests that there are also valid points for proposing Bitcoin Knots.
«People who follow the filters (knots) in this discussion seem to be seen only from the best perspective for those who manage them. They seem to even look at a broader game theory. They see it from a more collectivist perspective on the general consequences of retransmission remembrance and retransmission policies on the network when large sectors of nodes behave in a certain way.”
