OP_RETURN up to 80 Bytes have been allowed for decade to be able to attach small data (that does not abuse Bitcoin Monetary network) for additional purposes like a hash for example or a link. That has some good use cases. 100 000 Bytes is abuse of the Bitcoin Monetary network because all full nodes must store that data in their blockchain.

Replies (2)

Viktor's avatar
Viktor 2 weeks ago
80 → 100 k is a 125 000 % jump, not a “tweak”. if you need a whole jpeg on-chain, use a drivechain or stamp your hash & host the blob elsewhere; don’t force every rasp-node to lug around library-of-congress-size utxo for eternity. but the fix shouldn’t be dev diktat either — soft-forks are opt-in; if super-majority *wants* the bloat they’ll signal, if not they’ll reject. market plus hash-power decides, not twitter polls or github commit access.
This has some "good" usecases by the definition of who? Yes, YOUR definition. Bitcoin is not YOU though. You are a part of it and you should accept that different people have different opinions, usecases and values. And do not forget that I can aso send 0 bitcoin and pay a fee for that, is that also spam that we should filter out? Why? That alongside the argument, that using OP_RETURN for data already is NOT economically viable when you can use inscriptions instead. So all the spam and csam people like you are afraid of can long be ON the chain over inscriptions, for way cheaper. Your computer might have 2 drives, C and D. C is faster and there you download your CSAM to have quicker access. But now all of a sudden you want to make it impossible to download that CSAM to your D drive, because you fear that the government won't like it. The government will confiscate your computer though, not only your D drive. This is why all of you people are wrong about this topic, not a SINGLE spam transaction will be avoided with restricting OP_RETURN, as it's already possible and way cheaper with inscriptions. All the government cares about is you hosting illegal content, not the drive you store it on. You have been lied to and you were mislead, but so was I. And I was kind of happy, because I learned a lot through all of the discussions. This whole thing is a huge nothing-burger and you make something out of it that is simply not there. Otherwise you would need to rollback pre-taproot and sacrifice access the lightning network and other tools in the process. If you want that, go ahead. We will be there for you when you come back. :)