Crypto, and many of the main candidates, are Nakamoto at, Nick Sabo, so I recently returned to social networks and intervened in discussions about the role of rates and data restrictions on the Bitcoin network.
A conversation launched by developer CalleBTC explains how rates acted as a filter for spam in nearly 17 years, but Szabo warns of legal and technical risks when considering changes to the protocol, such as an increase in the OP_RETURN limit.
The exchange began on September 27th, when CalleBTC announced that it has been working effectively as a Bitcoin protection mechanism since its creation. The logic after Callebtc’s argument is an attack of “spam” (data considered a relationship) They are alienated by the cost of making them, This is because sending transactions with Bitcoin requires payment of fees to the miner.
Szabo responded on September 28th, noting that these rates protect miners but do not provide sufficient incentives for the full node.
This allows the creator of BitGold to mention the fact that there is no weight in the reason why Bitcoin nodes stop broadcasting transactions using any data on the network. They do not receive financial incentives of all kinds.
The rate protects the miners, but does not provide enough disappointment to protect the full node. Of course, this has always been a problem. However, increasing the Op_return allocation will probably exacerbate this issue. It also increases legal risk.
Nick Szabo, Creador de Bitgold.
Cryptographic authors believe they will extend the OP_RETURN limit, which allows transactions to contain arbitrary data. It can exacerbate the issue of Bitcoin spam and increase legal exposure on your network. He argued that legal risk could increase if data became more accessible, suggesting that standardized forms could facilitate authorities’ identification of illegal content.
However, CalleBtc added an important comment on September 29th. «Welcome again, Nick. Did you know that changes to the Op_return policy are discussed only about broadcast policies, not blockchain consensus? I just want to make sure I agree with the context here. “
CalleBTC is a key Bitcoin application developer. He is currently working on projects such as Bitchat and Cashu. It is the declared detractor of Bitcoin Knot. Its customer development is overly personalized with numbers: Luke Dashjr.
For developers, Bitcoin Knot and his proposal are not a critical replacement for Bitcoin Core, the protocol’s major customer.
The contradictions point out in Callebtc’s Szabo argument suggest that the former believes that, although in some way undesirable, illegal material was recorded directly in the chain. It will have less regulatory impact than something that can be easily visualized with external software to the protocol. This is because data in the OP_Return field is punished, meaning that they can be filtered (objectively pursued in Bitcoin Knot), and because lawmakers and regulators have limited technical knowledge to reveal what is within the Bitcoin block.
Counteralig is that illegal content in standard standard format that appears easily in standard software is likely to impress lawyers, judges, and ju-seekers, and therefore is more legally risky than fragmented or hidden data that requires specialized software for reconfiguration. These demonstrations are part of the process of convincing the legal director of the defendant node operator that he has knowledge of the content.
Nick Szabo, Creador de Bitgold.
Still, Szabo believes that increasing the OP_Return limit to 100,000 bytes will encourage the distribution of illegal content that is approaching conscious or unconsciously, to producers of Bitcoin Knot, where filtering these spam transactions is a priority.
This ongoing discussion, which also joined by Adam Back, is part of a broader discussion within the Bitcoin community regarding the OP_Return limit, a function that allows data to be stored on the blockchain.
Currently, this limit is established at 83 bytes per transaction. This is a limitation designed to prevent the network from saturating with information that is not related to value transfer. but, Bitcoin Core raises the limit to 100,000 bytes.
The decision on Bitcoin Core produced a split. Some consider the potential for innovation, while others, including Sabo, fear that they will promote the use of Bitcoin to store unwanted or illegal data, affect decentralization and attract regulatory scrutiny.
As reported by Cryptoics, Nick Szabo is known for his work at Bit Gold, Bitcoin concept precursor developed in 1998. Developers have a trajectory that closely links with the foundations of cryptocurrency and intelligent contracts.
His proposal for a decentralized digital currency that did not rely on central authorities anticipated several elements of the Bitcoin design launched by Nakamoto At.
Though he has never been confirmed to be the creator of Bitcoin, Szabo’s reenactment in this discussion strengthens his influence on the evolution of the protocol and provides a technical and philosophical perspective that continues to resonate with the community.
(tagstotranslate) bitcoin (btc)
