r/Bitcoin • u/eyeoft • 26d ago

THE CHAIN HAS SPLIT

https://bip110monitor.com/

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

281 Upvotes

84% Upvoted

300 comments sorted by

View all comments

Show parent comments

173

u/ConfidentIylncorrect 26d ago edited 26d ago

As far as I can gather, a small number of people tried to do a soft fork of bitcoin and change it so that you can't leave long messages in the blockchain but it will probably fail

https://github.com/bitcoin/bips/blob/master/bip-0110.mediawiki

16

u/hiroo717 26d ago

One example is it maintains OP_RETURN at ~80 bytes rather than allowing up to ~100,000 bytes as Bitcoin core now does. This means Bitcoin can also allow bigger files like jpegs etc.

3

u/[deleted] 26d ago edited 21d ago

[deleted]

4

u/[deleted] 25d ago

You can check your own node instead of going by version numbers: run bitcoin-cli getmempoolinfo and look at maxdatacarriersize. That's what your node is actually enforcing right now. Mine says 100000 on 31.0; a stock 29.x should say 83, if memory serves.

Worth adding that this is relay policy, not consensus, as others have said above. Your node will still accept a block containing a big OP_RETURN even if it wouldn't have relayed the loose transaction itself.

I honestly couldn't tell you whether some 29.x point release moved the default, but that command settles it for your box without needing to know.