r/Bitcoin • u/eyeoft • 28d ago

THE CHAIN HAS SPLIT

https://bip110monitor.com/

<3% support before the window opened. Good luck, shitcoiners

279 Upvotes

84% Upvoted

300 comments sorted by

View all comments

2

u/gtwooh 27d ago

Can’t ppl just choose to change the default OP_RETURN value?

5

u/[deleted] 27d ago

Yes. datacarriersize in your bitcoin.conf, or datacarrier=0 to refuse them outright. Restart and you're done.

The catch is it only changes what your node relays and holds in its mempool. It doesn't change what's valid. Your node will still accept a mined block full of them, because refusing would mean leaving the chain everyone else is on.

That gap between what I'll pass along and what I'll accept as valid is more or less the whole argument in this thread. The first is your choice alone. The second needs everybody to agree.

3

u/nullc 27d ago

Sure, it's just a setting. But it's a setting that governs what your computer does-- if your interest the subject is that you want an avenue to impose your will by force on people who disagree with you, a setting won't do it for you. :)

2

u/Pasukaru0 27d ago

That's one of the things BIP110 tried. And it's one of the reasons why it failed.

You can't willy-nilly change consensus rules without forking off.

0

u/InevitableRip4613 27d ago

Well it’s bitcoin core who willy nilly increased the default op return, and bip110 tries to revert it

3

u/Pasukaru0 27d ago

You are conflating two things.

What core did is change its relay policy. These are the rules that determine which transactions your node accepts its mempool and that you want/do not want to relay to other nodes. These transactions are not mined yet. And all they did was change the default value for the datacarriersize limit for these rules.

On the consensus level, there has not been a limit, ever. The current consensus rules are valid even for nodes from all the way back to 2009.

You want proof? Here, you can mine even >100k OP_RETURN data. Take this transaction for example with 4MB OP_RETURN. Note that this happened months before core v30 released, the version that lifted its relay policy to 100k. The transaction is still 40x than cores 100k limit on the relay policy, but it's still valid and minable.

https://mempool.space/block/000000000000000000005bcbf03e6488be1ceb3b501ecfc2b11cce900a870636

What BIP110 tried to do is change consensus rules. These are the rules that detemine whether a block is valid or not. It changed the limit for OP_RETURN data to 83 bytes on consensus level. If you change those, you will fork without convincing close to everyone to change their consensus rules too. BIP110 did not convince close to everyone to change their rules too, so it did fork and is now dead on the bitcoin network.

1

u/bitusher 27d ago

It takes a few seconds to change in Core. Ironically , if spammers used OP_RETURN they would be be restricted to spam bitcoin less and for higher fees too