Altcoin News Official TheBitTimes.com

A Bitcoin fork proposed this weekend would commence an activation period for updating consensus rules to limit data storage unrelated to the on-chain movement of BTC In a dramatic escalation of this year’s OP_RETURN war, pseudonymous dev “Dathon Ohm” revived Bitcoin Improvement Proposal (BIP) 2017, also called “Reduced Data Temporary Softfork,” that might become BIP 444 if someone codes an activation client and formalizes it on GitHub. The new blockchain would refuse many types of common data storage for media, collectibles, roll-ups, and other novelty or business uses at its base, consensus level.  Specifically, the proposal escalates disagreement over Bitcoin Core v30’s relaxed approach to queuing up to 100KB of arbitrary data per transaction in nodes’ memory pools (“mempools”). It would make such contiguous chunks of data incompatible with the blockchain’s rules for valid transactions — not just mempools’ default standar...

The gloves are off in this year’s revival of Bitcoin’s 2010 OP_RETURN war. Weeks into a heated impasse, the leader of the progressive movement seeking to ease data storage limits on Bitcoin Core mempools has dispensed with intellectual arguments, and underhanded rhetoric masquerading as a security warning has gone viral. Antoine Poinsot of Chaincode Labs, the originator of pull request (PR) 32359 to increase OP_RETURN’s datacarrier limit from 83 to hundreds of thousands of bytes, blames his opponent as having “troubles with reality,” “intentionally misleading” with “lies,” and “actively making s*** up.” Chaincode and similarly-minded Brink developers think that Bitcoin’s most popular queue of transactions should relay large OP_RETURN outputs that contain data irrelevant to the movement of BTC. Meanwhile, conservatives find this accommodative policy preposterous, tantamount to a subversion of Bitcoin’s purpose by corporate interests. Luke Dashjr, a leading conservat...