Under 0.11.2 I never had a problem creating a 0-tx fee. But after upgrading to 0.12, I always get the error "mempool min fee not set" when I try to send it. There's an ugly workaround of calling prioritisetransaction as described here: https://git.io/vabUJ. But that doesn't work if the mempool is already full, so I first have to restart the daemon to clear the mempool, before I can send the reprioritised tx.Is there a workaround that doesn't require restarting the daemon?
Many people see creating 0-fee tx as wrong. It just clogs the network as you can do 0.00000001 sends in bulk amounts.
so just pay the minimum 0.00005 isn't that cheap enough for you?
Or are you looking to do many sends of 0.00000001 for free?
It won't. Nodes do not care about the amount of each individual outputs as long as it fits their criterias to be relayed.
The easiest solution would be to add more coins and transfer it out or to use several addresses and spend the UXTOs from all of them. You can also convince miners to mine them since it won't be propagated well over the network due to it being classified as non standard on reference implementations.
Burnt coins and lost private keys would cost more Bitcoins than the owners of addresses with dust and are unwilling to spend them.
