I've been following this as best I can as a non technical person, but I don't think you need to be technical to see that the arguments in favor are weak when considering the potential tradeoff of allowing unlimited arbitrary data to be recorded on chain. I really get a sense that there is an ulterior motive from core devs and others pushing this change and they are not being honest about their reasoning.

Reply to this note

Please Login to reply.

Discussion

Mike Tidwell and I have collected a bunch of questions and answers around the OP_RETURN debate here: stacker.news/items/971277

I would hope that this collection helps with understanding the perspective of Bitcoin Core contributors.

These are way better explanations than anything I've found on nostr. Thank you for the link.

Is there currently a discussion going on about the witness discount as well, since it seems quite related to this whole saga?

These guys continuously move the goal posts. Once you bring up the fact that spammers are not going to voluntarily pay more to stuff spam in the OP_RETURN they shift the conversation.

How so? The observation that OP_RETURNs are more expensive for larger data payloads has been a central argument why "spam" is unlikely to increase overall by this change.

Spammers are not going to stop using SW for OP_RETURN. The UTXO sets will continue to bloat.

The only things this change will do is help spammers propagate their spam and create new types of spam.

Not that I know

I read through that and it made me less supportive of this change. The motivation of core devs is clearly to make spam cheaper at the request of a company that is paying the same core devs to make this change. These devs have sold out, plain and simple. It's disgusting.

Thanks guys, super usefull to get a quick summation of the situation.