Quote from: gwada971 on August 23, 2014, 01:10:54 PM

Quote from: makyoo on August 23, 2014, 11:21:31 AM

That's 72 hours since one of my transactions stuck in transaction pool.
http://chainradar.com/xdn/transaction/1d9b2f55f97c8f9e31b8525392e13dc1a536dfaa055c49634606b417a81f4958

Grrrrrrrrr!!!

And the number of those stuck transactions (with low fee) is growing:
13 transactions from 20.08
3 transactions from 22.08
and another 8 transactions from today 23.08

I'm afraid to withdraw any xdn from exchanges now. Sad

I had post what are the news with the last build, and my post was deleted !!!!

I know why now, seems that in the last build there are higher fees !!!!!!!!!!!!! I have a lot of this in the log of the last daemon.

2014-Aug-23 08:06:34.794790 [P2P9]transaction fee is not enought: 0.01000000, minumim fee: 0.10000000
2014-Aug-23 08:06:34.794866 [P2P9]Transaction verification failed:

duckNote default fees stay the same with last build and github commits - 0.1 XDN. Some users/exchanges try to send their transactions with lower fees. That transactions "stuck" in tx pool. Last build and github fixes do the following things:

1. duckNoted daemons, compiled from the latest duckNote source from github would not allow transactions with fee less than 0.1 XDN to be included in tx pool.
2. duckNoted daemons, compiled from the latest duckNote source from github will exclude all transactions that stay in tx pool for more than 24 hours, from tx pool
3. Next ducknotewallet GUI will not allow you to sent tx with fee lower than 0.1 XDN