Replying to Avatar Sourcenode

1. There is not, from my perspective. The relay policy for OP_RETURN takes minimal effort to maintain and has no risks.

2. Lazy developers that want to store less than 1KB of data on-chain. With inscriptions, they need 2 TX, while now they can do 1 TX.

Otherwise, large inscriptions still are 4x cheaper if done with SegWit instead of OP_RETURN, so no one will stop doing that for jpegs.

3. There are none so far I am aware of that do not involve the sole purpose of data storage or tokens.

Current use cases such as OpenTimestamps, Silent Payments, etc can all operate within 80 bytes.

Reply to this note

Please Login to reply.

Discussion

Very funny to see your reply now because I was scrolling your feed after your last note to see if you took a public stance.

While I'm not super technical I can see the incentives and I agree with what you said here. I might add that miners could potentially benefit by increasing demand for block space using non-financial (shitcoin) activity. All seems hypocritical and dangerous in my opinion. Even the accidental loophole created by Taproot caused a big mess for a short period of time. This seems like it would open the floodgates.

I'm still having a hard time understanding why anyone wants to increase OP Return or support Core's desire to do so, but I'm remaining open to hearing an explanation that doesn't sound like nonsense.