Replying to Avatar :P

I will gladly civilly debate anyone on the OP_RETURN saga over audio. I believe I have found the ulterior motive for why these spammers want to force their limitless OP_RETURN policy settings on as many nodes as possible and can clearly articulate why this BIP should be closed for good and never be opened again.

Right now for a spammer to get a tx with over 80 bytes in the OP_RETURN they would have to go out of band to miner that will include their transactions in the next block they find. The miners that offer this service to spammers only find a small percentage of blocks which means these spam transactions can only occur every so often. If all bitcoin core node runners were to remove the OP_RETURN limits then all miners would see these spam transactions and include them in their block template making the spam occur regularly.

These guys can fork core and make this change but that doesn’t help because they NEED as many nodes as possible to propagate their txs so they have a higher chance of it being included in the next block.
Avatar
sedited 8mo ago

I'm yet to meet a single Bitcoin Core developer who enjoys that arbitrary data is embedded on chain. The PR under consideration is still in review. Many Core developers have voiced concerns over disabling the option. This has led to a new pull request being opened that only changes the default, but keeps the default. There is no BIP under consideration here.

Making OP_RETURN outputs standard is not likely to effect the amount of data embedding. It gives people who do this the option to do so in a way that reduces harm to node runners. Stopping all data embedding is impossible. You will always be able to embed data in fake key outputs, which is also the worst way to do it in terms of negative externalities to node runners.

Reply to this note

Please Login to reply.

Discussion

No replies yet.