Im trying to research this a bit, do you have any additional thoughts on this?
To my current understanding its better to store data in opreturn since it is prunable. Otherwise the dickpicks end up in the multisig tx outputs which are then unspendable and bloat the utxo set. Is my understanding correct?
Refrencing to this https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.9.0.md
OP_RETURN and data in the block chain
On OP_RETURN: There was been some confusion and misunderstanding in the community, regarding the OP_RETURN feature in 0.9 and data in the blockchain. This change is not an endorsement of storing data in the blockchain. The OP_RETURN change creates a provably-prunable output, to avoid data storage schemes -- some of which were already deployed -- that were storing arbitrary data such as images as forever-unspendable TX outputs, bloating bitcoin's UTXO database.
Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere.
From a 1 dimensional viewpoint, what you said is true. However both are still available whether you nuke the OP_RETURN filter or not.
Bitcoin is money, and the idea of facilitating and accommodating spammers is the most anti-cypher punk thing I have ever heard. Any type of spam can be mitigated with a filter, don't be gaslight to believe otherwise. It's just one game of whack-a-mole we need core to play here.
Keep learning man, you're doing the work that most won't bother to do 💪
Do you maybe know what is meant by the opreturn being provably prunable? Does that mean only pruned nodes discard this data? Or do all nodes ditch it at some point?
Or in other words, a new node that is syncing, will it fetch this data or ignore it?
Still didn't figure this part out :)
The UTXOs are definitely never going to be spent, known as 'provably unspendable', so can effectively be forgotten about by a pruned node. A full node would still store them on the other hand.
A new node syncing will check through everything including the provably unspendable utxos, but once verifying the transaction information eg signatures etc, it will remove the data from memory.
