Bitcoin dev proposes excommunication for OP_RETURN ‘garbageman’
The post Bitcoin dev proposes excommunication for OP_RETURN ‘garbageman’ appeared on BitcoinEthereumNews.com. In an escalation of the Bitcoin OP_RETURN war, the leader of an initiative to change the world’s most popular software for Bitcoin nodes is proposing an unusual punishment for anybody attempting to slow his upcoming change to the network. Insisting that Bitcoin Core’s default mempool should accommodate large amounts of corporate data storage and information unrelated to the on-chain movement of bitcoin (BTC), Peter Todd is coding up a severe punishment for node operators filtering large transactions from operators of Libre Relay, Todd’s accommodative creation. Currently, default mempool settings of Bitcoin Core node software will not relay large OP_RETURN outputs. On the other hand, direct-to-miner mempools like MARA Slipstream will accept these non-standard transactions, as will Todd’s Libre Relay. However, people who don’t like Todd’s Libre Relay accommodation of corporate data storage have created so-called “garbageman” software that penalizes Libre Relay node operators who propagate such large transactions. Viewing Libre Relay’s queue of massive transactions unrelated to the on-chain movement of BTC as a sneaky workaround, garbageman nodes attempt to filter out certain transactions by pretending to be Libre Relay nodes and Sybil-attacking their broadcasts. This drowns out their attempts to broadcast large transactions around the Bitcoin network. Todd, in response, is working on a counterattack to defend his software. He wants Bitcoin node operators to be able to drop (disconnect from) garbageman nodes and through complicated mathematics and code stemming from Greg Maxwell’s earlier work, he’s working on reliable ways to estimate that a node is running this garbageman attack. Bitcoin’s garbageman For context, the Bitcoin community has been fighting a minor civil war this year over on-chain data storage. Protos has been covering their battles for months. Specifically, two camps have feuded over the default data storage allowance of Bitcoin Core’s queue of pending transactions or “mempool.” With…
The post Bitcoin dev proposes excommunication for OP_RETURN ‘garbageman’ appeared on BitcoinEthereumNews.com.
In an escalation of the Bitcoin OP_RETURN war, the leader of an initiative to change the world’s most popular software for Bitcoin nodes is proposing an unusual punishment for anybody attempting to slow his upcoming change to the network. Insisting that Bitcoin Core’s default mempool should accommodate large amounts of corporate data storage and information unrelated to the on-chain movement of bitcoin (BTC), Peter Todd is coding up a severe punishment for node operators filtering large transactions from operators of Libre Relay, Todd’s accommodative creation. Currently, default mempool settings of Bitcoin Core node software will not relay large OP_RETURN outputs. On the other hand, direct-to-miner mempools like MARA Slipstream will accept these non-standard transactions, as will Todd’s Libre Relay. However, people who don’t like Todd’s Libre Relay accommodation of corporate data storage have created so-called “garbageman” software that penalizes Libre Relay node operators who propagate such large transactions. Viewing Libre Relay’s queue of massive transactions unrelated to the on-chain movement of BTC as a sneaky workaround, garbageman nodes attempt to filter out certain transactions by pretending to be Libre Relay nodes and Sybil-attacking their broadcasts. This drowns out their attempts to broadcast large transactions around the Bitcoin network. Todd, in response, is working on a counterattack to defend his software. He wants Bitcoin node operators to be able to drop (disconnect from) garbageman nodes and through complicated mathematics and code stemming from Greg Maxwell’s earlier work, he’s working on reliable ways to estimate that a node is running this garbageman attack. Bitcoin’s garbageman For context, the Bitcoin community has been fighting a minor civil war this year over on-chain data storage. Protos has been covering their battles for months. Specifically, two camps have feuded over the default data storage allowance of Bitcoin Core’s queue of pending transactions or “mempool.” With…
What's Your Reaction?
