Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Bitcoin The basic developer Antoine Point is a merged request to remove the long-term 80-Bajt OP_return Relay Cap, launched one of the most dividing Mempool policies from the block size wars.
In a quick escalation, a separate contributor published and public script bash For automatic banknotes, any known node running bitcoin nodes, an implementation designated as a policy now representing approximately 13 percent of the achievable bitcoin peers.
The scenario published in Github 24 May, accepts year -round setban on all of them /Satoshi:Knots/ User agents.
If they were widely accepted, it would effectively isolate Almost 3,000 publicly reachable nodes, according to the latest number of 2,938 Coin dance k 24.
Unlike past disputes Excessive consensus rules focus on the current relay policy. With the planned V30 Core client for the release of October 3, the operational distribution could materialize without a hard fork.
The Implementation of nodes He has gained dynamics since the main team served on 6 May a change of OP_RETURN POINTOT policy.
His share in the achievable nodes doubled in May in May and continued to climb in June and coincided with the voice criticism of the change from its main administrator Luke Dashjra, who described the removal of the cap as “complete madness”.
While OP_RETURN is not critical consensus, the node policy decision form the transactions and Mempool filtering, which in turn affects what miners include in blocks and which transactions carrying data at all reach the network.
Bitcoin Operational War
The original dispute dates back to the original recovery of Bitcoin Core to enforce the 80byte OP_RETURN limit in 2014. Initially, a tool that allows data inscriptions such as notarial hash or token metadata.
More recently, innovation as Ordinary And the BRC-20 tokens used a similar mechanics to insert high-volume fees into the chain. The planned edition in October Core V30 will completely remove the ceiling, allowing creators of transactions to include greater payload OP_RETURN, provided they pay the necessary fees.
Opponents consider this shift that undermines the role of bitcoins as a slim, monetary settlement. Samson Mow, CEO of Jan3 and frequent critic of data usage patterns, urged Users “refuse to upgrade and stay on 29.0 or run nodes”, which is to produce a problem as a network integrity protection.
Others as Peter Todd, who created an earlier version of the same design in 2023, sees removal as a necessarily Simplification, which gives up the market conditions and incentives of fees.
Since CAP op_return is enforced at the policy level, nodes operators can accept or refuse to change individually. This dynamics increased the role of miners and relay infrastructure operators who eventually decide which transactions make it candidate blocks.
If the critical number of pages of the best pools with nodes, blocks full of larger data OP_RETURN can spread effectively and create a de facto veto. Conversely, if the default values of Core dominate, alternative policies could become silent and economically irrelevant.
Key participants started trading in personal accusations because the dispute migrated from Github to public channels like X. POINSOT defendant Critics of “intentionally misleading” the public and “produce *** up”, in the middle of growing hostility in technical matters, administration of public and communication standards.
Wider consequences can spread to the ability of bitcoins to adapt divergent political views without shattering its operational cohesion.
Differences from consensus from the wars of the block size
Unlike the 2017 block size debates, OP_return does not require incompatible consensus rules. Nevertheless, the threat of divided network weaving, especially if coordinated peer prohibitions are expanded. While the spread of blocks in two camps can remain functional, the transaction relay paths could break, which affected the markets of fees, data services and blockchain analysis.
The Bitcoin Core’s V30 client is now scheduled To freeze on August 20, with a planned branch for approximately 6 September and the final edition of the final edition focused on October 3 according to the updated schedule of Github. No main mining pools, including foundry, Antpool, F2Pool, ViabTC or Binance Pool, have not issued a statement on relay policy settings, which should be open, whether the V30 changes spread or face silent resistance.
Since May 24th, the number of bitcoin nodes nodes continued to rise and reached 2,938, which is the highest record and represents more than 13 percent of reaching peers. The original BAN script remains alive and at least one new tool has appeared, BTC-Magic-Guard, offering filtering based on Iptables for isolation of nodes operating clients of policy.
Meanwhile, the subsequent proposal to allow multiple OP_RETURN outputs on the transaction recently taken after back -backing, indicating that it is unlikely that the core keeps re -evaluate or narrow the merged policy in front of the V30 ships.
Meanwhile, the network remains unified according to the shared rules of consensus, but unresolved divergence in relay behavior, connection and nodal policy caused the soft division before the October release to make a soft division of a tangible scenario.
