How does it lower the bar for spam?

Reply to this note

Please Login to reply.

Discussion

Right now to inscribe a 4mb donkey dick butt pic a user would have to go directly to miner and negotiate an out of ban transaction. By removing the limit it makes it easier for anyone to do this. The result would be more spam, not that difficult to understand.

They don't have to go directly to a miner. They can run their own node that will hold the tx in their mempool. If you're trying to go to a miner to get your tx included in a block for any other reason than paying the most then you'll always have to go to a miner. If someone wants to inscribe a 4mb jpeg they can do it right now without going directly to a miner by paying 3 sats per vbyte. Paying a high fee IS going to the miner. The willingness to pay the fee is the economic signal to the miner. There is no need to reach out directly.

This is kind of false. If you broadcast a tx that’s over the 80 byte OP_RETURN limit as it stands today bitcoin core nodes will not propagate the tx.

The limit is not a bug it’s a feature.

Core nodes will not accept it. That's the whole point. Other nodes can and will accept it.

Only nodes that have removed the limit which today is few and far in between.

Sure, but they exist. They always will because there is no concensous issues with how large the return data is.

That’s fine but it’s not the standard. Core wants to force this as the standard with no way to opt out from within core.

Doing nothing is opting out... You never had to opt in, in the first place.

If core changes their policy every core node runner running the new version will be forced to accept it.

Bro... You can literally do nothing if your a core node runner and nothing changes. It takes a user to update. They don't just roll out automatically to everyone running core.

That’s a good solution tell everyone to run an old version and don’t update lol

You are downplaying the situation. Node service providers like umbrel and start 9 will give users some scary warning messages about updating their node.

Why is that not a good solution? I don't understand the issue with running an older version of core?