Is that your transaction? It's the only unconfirmed transaction for 80 BTC.

Doesn't look like the address he listed at all.

Yea, I know it doesn't look like it.... but it's the only unconfirmed 80 BTC transaction currently out there.

Nah, that's not it.

I forgot to mention that I can't see the transaction on my receiving wallet/address/computer at all, not even as 0/unconfirmed. I hope that's a good sign.Anyhow I'm rescanning the blockchain right now, will update here on any progress or failure.

Is that your transaction? It's the only unconfirmed transaction for 80 BTC.

Doesn't look like the address he listed at all.

Yea, I know it doesn't look like it.... but it's the only unconfirmed 80 BTC transaction currently out there.

Nah, that's not it.

I forgot to mention that I can't see the transaction on my receiving wallet/address/computer at all, not even as 0/unconfirmed. I hope that's a good sign.Anyhow I'm rescanning the blockchain right now, will update here on any progress or failure.

If the -rescan fails at first, move the wallet to a new client/computer/fresh install, and rescan there.

You can't have lost the bitcoins. If the transaction never gets committed, the 80 BTC never left. Your client just thinks they did. If the transaction does get committed, the 80 BTC will arrive at their destination.

Worst case, you can do the following:

1) Note the transaction ID.2) Stop the client that sent the transaction.3) Make sure the transaction is not in the block chain.4) Make sure the transaction is not in the list of pending transactions. (Available here: http://bitcoincharts.com/bitcoin/ )5) On the client you stopped, make a backup of the 'wallet.dat' file. Put it in one or more safe places.6) db_dump the wallet.dat file to a text file.7) Remove the wallet.dat file.8 ) Search the text file for the *reversed* transaction ID. So if the txid start 1234567890..., search for 9078563412.9) Remove the line starting with 02 and the following line, such that those two lines contain the transaction.10) db_load the text file into the wallet.dat file.11) Restart the client passing it the '-rescan' flag. The transaction should be gone.12) Double-check the transaction is not in the block chain or list of pending transactions. If it is, stop your client and revert to the saved 'wallet.dat' file.

You're done. You're now in sync.

In the future, leave transaction fees at their defaults.

Alternatively, if you're in no hurry, just wait many hours with the client running. The coins will age and the transaction will gradually gain priority.

(The client really needs a way to delete an unconfirmed transaction.)

I am an employee of Ripple.1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN

A while ago I had a strange thing happen which might help this situation. I transferred to another wallet, then shut down the receiving client as soon as it received the transaction. The transaction was NOT in the blockchain at this point, it had simply been broadcast throughout the network, including to the receiving machine.

Now, before restarting the receiving wallet.dat again, I had in the interim updated the blockchain with another wallet.dat. So I restored the original receiving wallet.dat (with the 0/unconfirmed coins) and started with -rescan. No luck. At this point the transaction *was* in the blockchain, the client *was* rescanning, but those coins stubbornly stayed at 0/unconfirmed and I couldn't spend them.

I gathered eventually that rescanning doesn't work so well for 0/unconfirmed transactions and the only solution I found was to start a new client and either download the whole blockchain from the start, or use a blockchain that hadn't yet downloaded the block I needed.

After all that, though, if your transaction is neither in the blockchain nor the pending transactions, then it would seem the coins were never sent. Don't know what to do there, sorry!

It should be noted that you can never actually lose funds this way, only have them trapped by the wallet, a little bit of effort on the part of someone who knows what they're doing and the funds would be available again.

Sorry for bumping this but I just wanted to update and say that I got my coins back.First i tried to rescan and download the blockchain on the same computer and on several other computer by just copying my wallet, but with no luck.

Then I tried to do the same with an older version of the same wallet and it worked like a charm! Thanks for the help everybody!

I had the same problem once (on OSX client, which is buggy). What I think happened was that my block chain got somehow corrupted - or even my wallet.dat. Do you have an earlier backup of the wallet.dat?

How I fixed the issue:

1) shut down bitcoin client / daemon2) take a backup of your current wallet.dat (you could backup the block chain DBs as well, for later debug or what not)3) delete the current wallet.dat and all block chain data (usually in the same folder)4) replace only the wallet.dat to the folder (I used an older backup, I'd recommend that since I suspected that the stale transaction was already written to it. You could try the current wallet.dat as well if you don't have backups).5) restart bitcoin and redownload the block chain (on OSX this can be _really_ slow. I mounted a RamFS for this purpose.)6) Once the block chain is up to date, you should have a balance that includes the 80 BTC you thought you lost.

Sorry for bumping this but I just wanted to update and say that I got my coins back.First i tried to rescan and download the blockchain on the same computer and on several other computer by just copying my wallet, but with no luck.

Then I tried to do the same with an older version of the same wallet and it worked like a charm! Thanks for the help everybody!

Could you please update the title to say that it was solved? All these threads of losing bitcoins are not good for the image of bitcoin. Thank you !

But this is not is not an optimal solution. This guy now has two wallet.dats with more-or-less the same info. But now if he tries to send those 80BTC again, they won't necessarily come from the same source addresses from the backup wallet.dat (he might have spent other coins in the interim and received change which the client would prefer to spend first).

So now he must either completely empty all coins from both wallet.dats or continue using both in parallel, and each client will miss transactions generated by the other, not to mention that the cache of 100 addresses will be different.

Or... maybe... does -rescan also capture *outgoing* transactions on the addresses in a wallet? I seem to remember that it doesn't, but that it would soon.

I think the client needs to have a separate file for private keys and transaction data, if the wallet file does contain transaction data. a consolidate button would be nice too. that way, once or twice a month we could do that and have the coins in 1 neat and tidy address, so overall we would use less space in the blocks. sometimes i look in the explorer and see like 10 addresses give me like 1BC combined,kind of wasteful.