pull down to refresh

OP_RETURN War | Bitcoin dev proposes excommunication for OP_RETURN ‘garbageman’protos.com/bitcoin-dev-proposes-excommunication-for-op_return-garbageman/
145 sats \ 5 comments \ @0xbitcoiner 16 Jun bitcoin
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.
...read more at protos.com
write
preview
related posts
105 sats \ 0 replies \ @south_korea_ln 16 Jun
I hate those articles pretending to be objective but then showing their huge bias a few paragraphs in.
reply
21 sats \ 0 replies \ @SwapMarket 16 Jun
What a waste of creative potential! I wish this toad focused on quantum resistance or something equally useful.
reply
0 sats \ 2 replies \ @Lumor 16 Jun
So much AI slop and erroneous information in that article.
reply
5 sats \ 1 reply \ @0xbitcoiner OP 16 Jun
Could you elaborate on that?
reply
178 sats \ 0 replies \ @Lumor 16 Jun
It will be a massive victory for corporations looking to publish rolled-up data onto the Bitcoin ledger
It's not a massive victory since one could already store garbage in witness data for approximately the same cost.
the default mempool of the latest version of the most popular full node software will no longer filter OP_RETURN outputs with more than 3.9MB of arbitrary data.
OP_RETURNS live within the original 1MB limit. They also need to fit within the much smaller max tx size used for relay, something like 100 KB. Both of these are regardless of version. "3.9MB" is some AI hallucination.
Poinsot and Todd declared victory
Poinsot has not put that kind of energy behind his statements after the merging of that PR AFAIK. This misrepresentation reads like pure ragebait.
reply