Unfortunately, it already happened since more than a decade ago. Some of those method doesn't require miner to manually add the TX either. Someone is not paying attention here. BIP110 doesn't aim at stopping all spam of all kinds. It aims at stopping contiguous data. Your examples are not contiguous data. A mere 123win30 to something is not a file stored on chain. --snip-- 3 source i mentioned clearly says the illicit/controversial isn't only 123win30. Besides, i'm talking about past action. While also give headache to both wallet developer and user (who manually specify all outputs). It"s only a mild nuisance if you have a low balance 123win30 the dust limit. And if you want to construct yoyd own txs manually, that is your own choice to make things more complicated for yourself. I'm talking about adding complexity to wallet developer, considering some wallet that support 123win30 are lagging behind to support advance feature or new address format. On user side, they may never realize the change or find it's not logical. OK, so you admit you don't know what regtest is or how it works or what it's point is. Stop your bitching. Show me the mempool.space 123win30 to the actual transaction in question. There is a very insidious reason why all the hit pieces that talk about it don't provide a 123win30 to the actual transaction in any explorer. Also not required but I'd really like to see the block you mined with a couple of Knots nodes. That'd be fun. regtest network only exist on your device. So besides mining on your own regtest, you also need to self-host mempool.space and configure it connect to your regtest network.
Unfortunately, it already happened since more than a decade ago. Some of those method doesn't require miner to manually add the TX either. Someone is not paying attention here. BIP110 doesn't aim at stopping all spam of all kinds. It aims at stopping contiguous data. Your examples are not contiguous data. A mere 123win30 to something is not a file stored on chain. --snip-- 3 source i mentioned clearly says the illicit/controversial isn't only 123win30. Besides, i'm talking about past action. While also give headache to both wallet developer and user (who manually specify all outputs). It"s only a mild nuisance if you have a low balance 123win30 the dust limit. And if you want to construct yoyd own txs manually, that is your own choice to make things more complicated for yourself. I'm talking about adding complexity to wallet developer, considering some wallet that support 123win30 are lagging behind to support advance feature or new address format. On user side, they may never realize the change or find it's not logical. OK, so you admit you don't know what regtest is or how it works or what it's point is. Stop your bitching. Show me the mempool.space 123win30 to the actual transaction in question. There is a very insidious reason why all the hit pieces that talk about it don't provide a 123win30 to the actual transaction in any explorer. Also not required but I'd really like to see the block you mined with a couple of Knots nodes. That'd be fun. regtest network only exist on your device. So besides mining on your own regtest, you also need to self-host mempool.space and configure it connect to your regtest network.

Unfortunately, it already happened since more than a decade ago. Some of those method doesn't require miner to manually add the TX either. Someone is not paying attention here. BIP110 doesn't aim at stopping all spam of all kinds. It aims at stopping contiguous data. Your examples are not contiguous data. A mere 123win30 to something is not a file stored on chain. --snip-- 3 source i mentioned clearly says the illicit/controversial isn't only 123win30. Besides, i'm talking about past action. While also give headache to both wallet developer and user (who manually specify all outputs). It"s only a mild nuisance if you have a low balance 123win30 the dust limit. And if you want to construct yoyd own txs manually, that is your own choice to make things more complicated for yourself. I'm talking about adding complexity to wallet developer, considering some wallet that support 123win30 are lagging behind to support advance feature or new address format. On user side, they may never realize the change or find it's not logical. OK, so you admit you don't know what regtest is or how it works or what it's point is. Stop your bitching. Show me the mempool.space 123win30 to the actual transaction in question. There is a very insidious reason why all the hit pieces that talk about it don't provide a 123win30 to the actual transaction in any explorer. Also not required but I'd really like to see the block you mined with a couple of Knots nodes. That'd be fun. regtest network only exist on your device. So besides mining on your own regtest, you also need to self-host mempool.space and configure it connect to your regtest network.

Unfortunately, it already happened since more than a decade ago. Some of those method doesn't require miner to manually add the TX either. Someone is not paying attention here. BIP110 doesn't aim at stopping all spam of all kinds. It aims at stopping contiguous data. Your examples are not contiguous data. A mere 123win30 to something is not a file stored on chain. --snip-- 3 source i mentioned clearly says the illicit/controversial isn't only 123win30. Besides, i'm talking about past action. While also give headache to both wallet developer and user (who manually specify all outputs). It"s only a mild nuisance if you have a low balance 123win30 the dust limit. And if you want to construct yoyd own txs manually, that is your own choice to make things more complicated for yourself. I'm talking about adding complexity to wallet developer, considering some wallet that support 123win30 are lagging behind to support advance feature or new address format. On user side, they may never realize the change or find it's not logical. OK, so you admit you don't know what regtest is or how it works or what it's point is. Stop your bitching. Show me the mempool.space 123win30 to the actual transaction in question. There is a very insidious reason why all the hit pieces that talk about it don't provide a 123win30 to the actual transaction in any explorer. Also not required but I'd really like to see the block you mined with a couple of Knots nodes. That'd be fun. regtest network only exist on your device. So besides mining on your own regtest, you also need to self-host mempool.space and configure it connect to your regtest network.