How to send 0-fee tx in 0.12?

[bachus]

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?

[achow101]

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?

With Bitcoin Core 0.12, the wallet will never create transactions less than the minimum relay fee. That value has a default which I think is 0.00005. You can use -mintxfee=0 flag in the startup command to set the minimum relay fee to 0 but that will also have the effect of your node also relaying transactions with no fees.

Also, why are you trying to create free transactions? You know that they will probably not get confirmed.

[philipma1957]

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?

[bachus]

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?

Satoshi certainly didn't think that: https://bitcointalk.org/index.php?topic=994.msg12168#msg12168
The spam argument is uninformed, since free transactions work via priority, which is based on age, amount and size of the transaction. Once an input is spent, its age and priority are wiped out, so a spammer can't continue spamming, without paying a large fee, which is what they do now anyhow.

[Patatas]

I agree with the above comment.But recent discussions about Blocks being full and all the halving predictions,you must pay miner fees if you want your transactions to be accepted by the nodes.If not,they will appear under least priority over the transactions which pay sufficient amount of transaction fees.Mining is not profitable anymore ,its genuine you'd need to pay some miners fee .

[shorena]

I agree with the above comment.But recent discussions about Blocks being full and all the halving predictions,you must pay miner fees if you want your transactions to be accepted by the nodes.If not,they will appear under least priority over the transactions which pay sufficient amount of transaction fees.Mining is not profitable anymore ,its genuine you'd need to pay some miners fee .

No, you just have to accept that it will take longer. High priority TX are still possible to get confirmed without a fee.

[ranochigo]

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 is impossible to do that. Free transactions requires the criteria of free transactions to be fufilled to get relayed. Bitcoin Core does not relay transactions with outputs less than the minimum amount of 2730* satoshis. This would effectively render these kinds of spam useless.
*correction

[btvGainer]

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 is impossible to do that. Free transactions requires the criteria of free transactions to be fufilled to get relayed. Bitcoin Core does not relay transactions with outputs less than the minimum amount of 546 satoshis. This would effectively render these kinds of spam useless.

Will not that make some Satoshi's useless for ever.I have 1000 Satoshi in one wallet and now I dont use that wallet anymore.Although it is a small amount but I once tried to move it to my new wallet but was unable to do because this amount is less than minimum prescibed amount.If everyone of us has some amount left in our abondoned wallet,will not this make lots of coins out of use?

[shorena]

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 is impossible to do that. Free transactions requires the criteria of free transactions to be fufilled to get relayed. Bitcoin Core does not relay transactions with outputs less than the minimum amount of 546 satoshis. This would effectively render these kinds of spam useless.

Will not that make some Satoshi's useless for ever.I have 1000 Satoshi in one wallet and now I dont use that wallet anymore.Although it is a small amount but I once tried to move it to my new wallet but was unable to do because this amount is less than minimum prescibed amount.If everyone of us has some amount left in our abondoned wallet,will not this make lots of coins out of use?

No you can still combine it with other inputs[1]. It is also not true that nodes do not relay "free" transactions. For one each node operator can configure their node to consider 1 satoshi the "free" limit and not the default 2730 satoshi (546 is no longer the dust limit) and its also possible to increase the number of "free" transactions that get relayed. E.g. I currently allow up to 150,000 free TX with a free limit of 100 satoshi.

[1] like, e.g. here https://www.blocktrail.com/BTC/tx/bb02b06bb38799ab02560b52cd7eec7973e046b58c2682336b5d986fdfcf24d6

[ranochigo]

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 is impossible to do that. Free transactions requires the criteria of free transactions to be fufilled to get relayed. Bitcoin Core does not relay transactions with outputs less than the minimum amount of 546 satoshis. This would effectively render these kinds of spam useless.

Will not that make some Satoshi's useless for ever.I have 1000 Satoshi in one wallet and now I dont use that wallet anymore.Although it is a small amount but I once tried to move it to my new wallet but was unable to do because this amount is less than minimum prescibed amount.If everyone of us has some amount left in our abondoned wallet,will not this make lots of coins out of use?

I corrected it as 2730 satoshi as minimum output value.

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.