BitShares Forum
Main => General Discussion => Topic started by: busygin on November 08, 2014, 03:16:18 pm
-
(http://i.imgur.com/W8r5mmU.png)
I had the same issue in 0.4.23.1-90-gbb33f21:
https://bitsharestalk.org/index.php?topic=11075.0
-
Looking into it: https://github.com/BitShares/bitshares/issues/929
-
Actually, I cancelled it successfully yesterday. And there was enough both BTS and bitUSD for the fee. I have no idea what has changed between yesterday and the first time I tried it.
Looking into it: https://github.com/BitShares/bitshares/issues/929
-
Just a wild guess, I had a few other transactions in between, so maybe it's related to addresses (private keys) it looks up to get funds for fees. Maybe it doesn't see all the addresses (private keys) with funds that can be used to deduct the fee.
Again, it's just a wild guess, I didn't look into your code.
Actually, I cancelled it successfully yesterday. And there was enough both BTS and bitUSD for the fee. I have no idea what has changed between yesterday and the first time I tried it.
Looking into it: https://github.com/BitShares/bitshares/issues/929
-
Did you make a lot of transactions in a short period of time? What is your wallet default transaction fee set to?
-
Did you make a lot of transactions in a short period of time?
No, only creating a bunch of orders and then trying to cancel one of them. And it was spread throughout hours.
What is your wallet default transaction fee set to?
I didn't change the default 0.5 BTS.
-
It's possible that other nodes on the network were broadcasting a high number of pending transactions to you, which would temporarily increase your local relay fee and result in this error. I haven't looked too deeply yet but that is the only other obvious possibility I can see. Has this problem re-appeared at all since the first times?
-
Has this problem re-appeared at all since the first times?
No, everything works fine for now.