> 1. But this is making assumptions on why other people run nodes, right?
Yes. The specific assumption is: some people run a node with a mempool to help relay some other transactions on the network, but do not want to extend that help to spam transactions.
> I don't think you can honestly argue that 1MB of OP_RETURNS is worse for the performance of your node than 1MB (or more) of data in any other part of a block?
If the data was identical, and if I was excluded from using the argument about base space being more valuable than witness space (to be considered in the next paragraph), then I would not object to the statement that 1MB of OP_RETURNS do no further harm to a node's performance than the same data in another part of a block.
> Do you think spam will persistently outbid monetary transactions for block space?
I do not think so because I do not think I am a reliable predictor of the future. But if I thought I could reliably predict that nothing will change, then I would also predict that spam will often outbid monetary transactions in the future, because I think they often do so in the present.
Login to reply
Replies (2)
just love your work and eyeing up some of your projects for deployment #mustdeploy
Ok I think we’ve probably made it to the end of our argument tree: the “agree to disagree stage”!
I’ll post my responses; feel free to rebut them if you feel like you can and want to— or not. Up to you :)
1. Since both you and me run a node primarily for our own benefit, I think it’s reasonable to extrapolate that to other users as well. Since data in OP_RETURN would not discourage you or me from running a node (versus data in other parts of a transaction) I don’t think increasing the OP_RETURN relay default will have a centralizing effect.
2. I think over time monetary transactions will be outbid by other monetary transactions— spam will barely enter the equation, if at all. (Maybe if it’s very compact, Open Timestamps style, in which case it’s also not a big problem.) Also see: View quoted note →