pull down to refresh
84 sats \ 2 replies \ @028559d218 8h \ parent \ on: Quick questions about OP_RETURN? Quick answers here. bitcoin
With all due respect, and I mean this totally neutrally...
Is there any way to get Citrea to just stop? Like hey, 'cut it out'?
Some of the criticisms I've heard are specifically that one company wants to make use of larger op_return data fields... so why change mempool policy for one company specifically? What if another company in the future wants to do something else, even if in the spirit of harm reduction, should we change mempool policy just for a company to play defi?
Another question: how many unprunable outputs are we talking about from Citrea? Hundreds? Thousands? Tens of thousands? Is this something really core to their business model? Is there any other way of them doing what they want to do, without requiring such a change? How polluting would they (or the others to follow them) really be for the network?
Finally, since LibreRelay works with only a limited number of nodes in the network available... why don't they just use LibreRelay? That way they could have larger op_returns without necessitating unprunable outputs.
THANK YOU
Is there any way to get Citrea to just stop? Like hey, 'cut it out'?
In this particular case, definitely not. Even with the "prove your bytes aren't arbitrary data" soft fork proposal they're doing something valuable enough to make grinding bytes feasible.
why don't they just use LibreRelay?
Because this type of Citrea transaction is time sensitive. Only two major mining pools mine oversized OP_Returns right now. That means there's a decent chance this type of Citrea transaction – a tx that responds to fraud – would fail to be mined.
reply
deleted by author