FIXED: Lost Bitcoin when transfering to different wallet!

[mik3]

Hi there i would really appreciate if any one could solve my problem or explain what has happened!

Yesterday (AUG/21/2011) i opened my main wallet in my usb drive and mounted to the bitcoin folder and opened and everything was perfect, blocks up to date. so i needed to take out 10coins from that wallet to my temp wallet so i used a valid key from the temp wallet that i previously used to deposit.
so as soon as i send the 10coins to the valid address i got the msg saying payment send! and -10 coin in transaction.
but when i mounted the temp wallet i didn't see the unconfirmed or anything regards to that transaction till now still nothing not even a gray notification NOTHING!

so i went and deleted the bitcoin folder and downloaded all the blocks again and mounted the wallet and still nothing. i used the wallet in different computer and nothing!

so i went back to my main wallet and in transaction it says the same -10 and 0 unconfirmed.

so i did another test using same valid address but for .50 coin and right away i saw the transaction in my temp wallet and after 1hour i got few confirmation.

NOW i need to know where the hell did that 10 coin went i copy and paste a valid address (checked it 50000times)

solution:
thx to PLATO

1. close the bitcoin from task.
2. run bitcoin from cmd (bitcoin.exe -rescan)
 
to avoid this problem dont close your wallet right away after transaction!!

[1714984273]

1714984273

[PLATO]

doesn't show up here:
http://blockexplorer.com/address/1AWfEBQmneu44YhpQszeVditvQ9GnzqmTx

put the first wallet file back. exit bitcoin. launch bitcoin.exe from the command line with the launch option -rescan

[mik3]

doesn't show up here:
http://blockexplorer.com/address/1AWfEBQmneu44YhpQszeVditvQ9GnzqmTx

put the first wallet file back. exit bitcoin. launch bitcoin.exe from the command line with the launch option -rescan

oka so you mean put the wallet that i sent the coin From?! or the wallet that i send the coin to!?

if that is the case i will try to see what happens i let you know

thx

[jackjack]

doesn't show up here:
http://blockexplorer.com/address/1AWfEBQmneu44YhpQszeVditvQ9GnzqmTx

put the first wallet file back. exit bitcoin. launch bitcoin.exe from the command line with the launch option -rescan

oka so you mean put the wallet that i sent the coin From?! or the wallet that i send the coin to!?

if that is the case i will try to see what happens i let you know

thx

The wallet you sent the coins from
Actually you didn't sent them, for some reason the transaction hasn't been broadcasted (you closed the client too early or didn't give enough fee or whatever)

[PLATO]

the wallet that you sent the coin from. it didn't actually go through, or it would be in the blockchain.

open a command line using start > run > cmd

type cd "C:\Program Files\Bitcoin" or wherever you installed it... you need the quotes if you have spaces anywhere in the file path
type bitcoin.exe -rescan

[SgtSpike]

You probably closed the wallet before it had time to properly broadcast the transaction.  I'd leave it open for a few minutes after hitting "Send" to be sure it really does get propagating through the nodes.

[mik3]

i did a rescan and its fixed i think when i closed it fast that's why! and the only solution that worked it was the rescan i did everything else re-downloaded the chain and nothing, only fixed with -rescan

i think this option should be integrated in the bitcoin program under help or something.

 

[SgtSpike]

i did a rescan and its fixed i think when i closed it fast that's why! and the only solution that worked it was the rescan i did everything else re-downloaded the chain and nothing, only fixed with -rescan

i think this option should be integrated in the bitcoin program under help or something.

 

Hah, that it should!  It'd be one step closer to making Bitcoin intuitive for even the newest of users.

[Pieter Wuille]

It is very unlikely that -rescan helped - all recent versions of bitcoin do rescanning automatically when necessary.

My guess is that you switched to the second wallet before the transaction from the first wallet made its way into the block chain. When switching back, it resubmitted, and the second wallet got it.

[SgtSpike]

It is very unlikely that -rescan helped - all recent versions of bitcoin do rescanning automatically when necessary.

My guess is that you switched to the second wallet before the transaction from the first wallet made its way into the block chain. When switching back, it resubmitted, and the second wallet got it.

How does the recent client determine when rescanning is necessary?

[Pieter Wuille]

It is very unlikely that -rescan helped - all recent versions of bitcoin do rescanning automatically when necessary.

My guess is that you switched to the second wallet before the transaction from the first wallet made its way into the block chain. When switching back, it resubmitted, and the second wallet got it.

How does the recent client determine when rescanning is necessary?

It stores some hashes of blocks in the current tip of the block chain in the wallet file. On startup, the latest common ancestor of the block chain database and the wallet file is searched for, and a rescan starting at that point is performed.

I believe this was added in 0.3.21 or 0.3.22.