error: {u'message': u'TX rejected', u'code': -22}

[oldbushie]

But that doesn't make any sense. How else am I supposed to extract money from a wallet that's continually receiving newly minted BTC more than once a day?

Freezing the mining address doesn't do a whit of good because that's the only source of transactions. It just states (correctly) that there's insufficient balance if I do that.

Is there any chance of this working correctly for Electrum in the future? Or will I have to set up a regular Bitcoin-QT instance just to move coins out? Or will I see the same problem with the base client?

I have no clue where to even start with manual transactions on a Windows PC and I don't want to accidentally screw something up. I can't follow atweiden's command prompt instructions because they are not allowed on Windows yet.

The "minus a bit more" was so there would be a buffer between the mature and newly minted coins. I just took the wallet total, subtracted the value of the last two transactions, subtracted a little bit more, and then tried to send to my main wallet.

[1713506354]

1713506354

[1713506354]

1713506354

[1713506354]

1713506354

[1713506354]

1713506354

[btcven]

Try opening an issue on github (check if there is not already one about newly mined coins and this error). Then try on the IRC channel #electrum about this specific issue and how to make it work on Windows.

If you are tied to that address as your only source, you'll find the same problem almost on any bitcoin client. Maybe 0.9 with CoinControl would save you? I don't know the answer.

[ImI]

But that doesn't make any sense. How else am I supposed to extract money from a wallet that's continually receiving newly minted BTC more than once a day?

Freezing the mining address doesn't do a whit of good because that's the only source of transactions. It just states (correctly) that there's insufficient balance if I do that.

Is there any chance of this working correctly for Electrum in the future? Or will I have to set up a regular Bitcoin-QT instance just to move coins out? Or will I see the same problem with the base client?

i had the same problem. fortunately the problem ocurred while i tried to do an umimportant transaction. if that would have been a time-sensitive issue i would have gone mad.

i switched to the base client and the problem is gone.

[oldbushie]

A friend suggested I try Armory to see if that works better with newly minted coins, so I'm giving that a go. Just need to get bitcoind up to date on my main pc...

I'll try asking on the irc channel as well, thanks.

Edit: Issue #355 opened.

[opentoe]

A friend suggested I try Armory to see if that works better with newly minted coins, so I'm giving that a go. Just need to get bitcoind up to date on my main pc...

I'll try asking on the irc channel as well, thanks.

Edit: Issue #355 opened.

God no, The Armory is even worse. Their latest version you need at least 64bit OS with over 8GB of memory for it to even start working properly. I've been using Multibit with great success.

[EagleTM]

This issue should be fixed in 1.9.3 - Win/Mac builds will be available some time this week.

[oldbushie]

Just a quick note that I haven't seen this error anymore. HOWEVER, the ! shortcut key is not smart about automatically detecting all spendable coins. It just grabs everything in my wallet, even transactions that haven't completed yet and coins that were just generated an hour ago.