Quote from: goatpig on July 31, 2018, 05:16:34 PM

This is a local thing, your own node is rejecting the tx. Fee logic is quite complicated actually, the age the utxo and the spent value in relation to the tx size as well as a min flat fee per tx all come into play. Lowering the minimum broadcast requirements below default for your node will allow you to push that tx to your node's mempool, but chances are it won't broadcast at all to the network.

These are the 2 settings you can mess with for Core:

Code:

minrelaytxfee
limitfreerelay

ok, here's a great example of the poor fee estimator from the node. as i showed you from the screenshot above, the error window from Armory was saying the minrelaytxfee was supposed to be 200 sat/b. to get around with having to fiddle with changing my bitcoind minrelaytxfee or limitfreerelay i decided to tack another low fee of 1.3 sat/b instead and broadcast the raw hex thru a block explorer. sure enough, i got a confirm in <10m.