Replying to Avatar sudocarlos

I feel like this article only makes the case for providing devs better guarantees of doing stuff that node runners dont agree with.

And while i can see how this provides incentives for good behavior, i dont see why devs wouldnt keep creating unspendable utxos.

I had seen some math showing that multiple opreturns might be cheaper up to a certain amount, but what happens above that?

Have any concerns come up about unknown unknowns? How is a node's processing efficiency impacted by larger opreturns and is there a greater chance for malicious payloads considering other software that node runners might be running like electrum and mempool?
Avatar
andrewtoth 8mo ago

Yes, only up to about 157 bytes (up from the current 80 bytes standard) will OP_RETURN be cheaper than using witness data to store data. And with OP_RETURN you can only make 1mb blocks. With inscriptions you can make 4mb. So if data enjoyers want to use OP_RETURN instead of inscriptions it will be less storage and bandwidth for nodes.

Reply to this note

Please Login to reply.

Discussion

Avatar
sudocarlos 8mo ago

Thanks for answering my questions. There should be a FAQ or chatbot to answer these because i doubt im the only one a bit confused. And things got dramatic so quickly.

Anyway, if you still dont mind 😬... does most of today's spam fit in the 157 bytes? The op_return i quoted, for example, is how large?

Avatar
andrewtoth 8mo ago

I'm not sure of the stats, but a lot of spam are large jpegs, which would always be cheaper as inscriptions.

The one you quoted I calculate as 139 bytes.