-snip-
right, and that's why you should put .00011 or .000101 or so, if you don't want to wait an extra hour
Now I get it. The "I play a little more fee than you" race allready started. Judging from the source[1][2] though the default setting is still to sort by priority first. Since priority is determined by age and size of the inputs the network currently gets either more expensive or slower. I havent actually noticed it while send btc, but the longer I look at the recent graphs the more I see that its now normal to wait a block or two even though you pay a fee. The strange thing is that the blocks are not full even though they could be, even with transactions paying fees. Is this miners afraid of an orphaned block due to slow propagation?
[1]
https://github.com/bitcoin/bitcoin/blob/master/src/miner.cpp#L229[2]
https://github.com/bitcoin/bitcoin/blob/master/src/miner.cpp#L255In the next release of bitcoin core (0.10) it will be added the "floating fees" function :
"The wallet code in the next major release of Bitcoin Core (version 0.10) will be much smarter about transaction fees.
Instead of using hard-coded rules for what fees to pay, the code observes how long transactions are taking to confirm and then uses that data to estimate the right fee to pay so the transaction confirms quickly– or decides that the transaction has a high enough priority to be sent for free but still confirm quickly.
There is a new option that lets you control how quickly you’d like your transactions to confirm: txconfirmtarget. The default value is 1, meaning “I’d like my transactions to be sent with enough fee or priority so they are very likely to be included in the next block.” Set it to 6 and it will take on average six blocks for your transactions to get their first confirmation."
It will help a lot the people to set the "correct" fee for each transaction. More info here :
-
http://blog.bitcoinfoundation.org/floating-fees-for-0-10/