Why was op_return introduced in the first place?
Discussion
To prevent UTXO bloat from people embedding data in fake outputs that are probably unspensdable. OP_RETURN is explicitly probably unspensdable . So it doesn't enter the UTXO set. There is no way to stop people from embedding data on Bitcoin. It's not possible. So give them a place to do it that doesn't harm Bitcoin.
That's why it was added.
Provably *
So now, let's give them one more way to spam? So they have more options now? And hope that they use opreturn which is more expensive than segwit?
What's the new way to spam?
100kb opreturn, in addition to the existing taproot/segwit exploits (ordinals, brc20, jpegs)
Being able to make 100kb opreturn is not new. You've been able to do that since 2014 when the op code was enabled. Filtering keeps them out of your mempool. It may delay propagation but only for a few minutes at most if gossip works how it should on Bitcoin.
Ok, do you know how many non-standard tx that were not relayed by the nodes? We do not know because they did not get into the blockchain. If what you're saying is true, then you are saying that Mara's slipstream is economically stupid business idea. Spammers go to them for a reason, "because we are not relaying them for free". Shocking!
People use slipstream because they don't know how to use their own node. They will pick up your transaction if it's economicly feasible whether you send directly or not. They did get into the blockchain. Or could at least. The truth is there's not much point to large OP returns so people don't do them. It costs a lot to put data on Bitcoin. It's the most expensive database ever and poorly optimized to distribute large bits of data. It's not that people couldn't do it. It's that there was no incentive to do it in the first place. Almost like fee rate is Bitcoins spam prevention and not filters...
People use Slipstream because it's convenient and reliable. Anyway, I guess we will find out how all of this will play out once v30 is released.
Yes we do. Near 0.
How would we know the true number of non-standard txs if they're being sent directly to miners and not through the nodes? The "near 0" figure only shows that the public filter is working -- it doesn't show us the private market for hashrate that makes services like Slipstream a viable business.
It’s more fun when someone who doesn’t know the answer has to research it themselves 😂
Not exactly. OP_RETURN was never designed to actually *prevent* UTXO bloat... instead it provided an alternative that was at least financially neutral - if not cheaper - thus, successfully incentiivsing against UTXO bloat; making preventing it unnecessary.
Since then, that financial incentive has all but been completely destroyed by segwit & taproot. It's true that it's impossible to stop data being embedded on Bitcoin; but, it's pure hopium to expect most rationally self-interested people to choose to pay more to use OP_RETURN in order to avoid causing UTXO bloat. The more rational expectation is that the people who never would have gone through the trouble of constructing complex UTXO bloating transactions in the first place will soon have much easier to use arbitrary data storage available for them to bid on against the more conventional transactions' use of blockspace.
Because utxo bloat is much worse for node resources then data in op_return ( utxo set is loaded in ram as every new tx has to be compared to it. Op_return is sitting on disk unless you have some specific plugin using that data)