Where or where have my bitcoins gone?

[wachtwoord]

I should have gone to bed but got distracted and am still up.

TA e1238453753dfba0a55bd7365ef7b231fa56b27aea383a810ec8e5e5bb014abe
has 1 input:
TA1. dd1a611ebe28bead424620e395c1e61130e98e468c43f750dfadeef6ab6739ce which is in the Blockchain (16.090234 BTC)

TD 308732ce601c5b029d71f55786b7e4236b872da0d866a6e49c3319319bafd3df
has 1 input:
TD1. 033a6b55dc8df532b007e19a630ef785518999660c01bb8fc864b112278f9b01 which is in the Blockchain (12.274 BTC)

However both TA1 AND TD1 have already been spend in another transaction.
http://blockchain.info/tx-index/57438804/dd1a611ebe28bead424620e395c1e61130e98e468c43f750dfadeef6ab6739ce
http://blockchain.info/tx-index/57442378/033a6b55dc8df532b007e19a630ef785518999660c01bb8fc864b112278f9b01

So none of these transactions are ever going to confirm (you are trying to spend funds which are alreay spend). And we are going to have to remove these transactions (that you only have locally). I'll have to look up how to do that.
I'm pretty sure deleting and redownloading the blockchain would do it but that can take a while, so I'll check it out later.

But when I started to make the list of addresses where the coins reside right now I ran into something odd. TB and TC from above show that in the following addresses reside:

1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj http://blockchain.info/address/1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj 10.023 BTC
1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY http://blockchain.info/address/1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY 15.889734 BTC

So then I traversed the spend inputs (TA1 and TD1) and found that they are indeed the inputs of TB and TC! Yes the rejected transaction was trying to turn 25.912734 BTC into 54.276968 BTC via some weird circular transaction.
I'm sure you didn't do it on purpose but I have no clue how you even achieved this without issuing raw transactions by hand.


So there are .. things we are going to do:

1) Is it possible (by your own accounting) that you only have 25.912734 BTC left?
2) Let's at least make certain you own 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj and 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY. This is what I was trying to achieve with the last command but that did something completely different.

a. Again open run the deamon and start the other command prompt
b. <optional if you have encrypted your wallet>. Run: bitcoind walletpassphrase PASSWORD TIMEOUT (where PASSWORD is your password and timeout is the time in second to unlock your wallet so we can attempt the next step, 20 seconds per address should suffice)
c. Run: bitcoind signmessage 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj test
d. Run: bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test  (note: if you are to slow you may need to repeat step b)

If c and d where successful (do not return an error code) you are certain you own the respective addresses and can access the 25.912734 BTC.

[1715482653]

1715482653

[1715482653]

1715482653

[donbenosee]

I should have gone to bed but got distracted and am still up.

TA e1238453753dfba0a55bd7365ef7b231fa56b27aea383a810ec8e5e5bb014abe
has 1 input:
TA1. dd1a611ebe28bead424620e395c1e61130e98e468c43f750dfadeef6ab6739ce which is in the Blockchain (16.090234 BTC)

TD 308732ce601c5b029d71f55786b7e4236b872da0d866a6e49c3319319bafd3df
has 1 input:
TD1. 033a6b55dc8df532b007e19a630ef785518999660c01bb8fc864b112278f9b01 which is in the Blockchain (12.274 BTC)

However both TA1 AND TD1 have already been spend in another transaction.
http://blockchain.info/tx-index/57438804/dd1a611ebe28bead424620e395c1e61130e98e468c43f750dfadeef6ab6739ce
http://blockchain.info/tx-index/57442378/033a6b55dc8df532b007e19a630ef785518999660c01bb8fc864b112278f9b01

So none of these transactions are ever going to confirm (you are trying to spend funds which are alreay spend). And we are going to have to remove these transactions (that you only have locally). I'll have to look up how to do that.
I'm pretty sure deleting and redownloading the blockchain would do it but that can take a while, so I'll check it out later.

But when I started to make the list of addresses where the coins reside right now I ran into something odd. TB and TC from above show that in the following addresses reside:

1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj http://blockchain.info/address/1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj 10.023 BTC
1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY http://blockchain.info/address/1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY 15.889734 BTC

So then I traversed the spend inputs (TA1 and TD1) and found that they are indeed the inputs of TB and TC! Yes the rejected transaction was trying to turn 25.912734 BTC into 54.276968 BTC via some weird circular transaction.
I'm sure you didn't do it on purpose but I have no clue how you even achieved this without issuing raw transactions by hand.


So there are .. things we are going to do:

1) Is it possible (by your own accounting) that you only have 25.912734 BTC left?

This is quite possible. Upon reflection I think that's what I probably SHOULD have, in addition to the 13.137 etc in my qt client balance (ie confirmed). When I looked at all the transactions, it does seem there was a jump of 25-odd BTC which I cant quite account for..

2) Let's at least make certain you own 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj and 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY. This is what I was trying to achieve with the last command but that did something completely different.

a. Again open run the deamon and start the other command prompt
b. <optional if you have encrypted your wallet>. Run: bitcoind walletpassphrase PASSWORD TIMEOUT (where PASSWORD is your password and timeout is the time in second to unlock your wallet so we can attempt the next step, 20 seconds per address should suffice)
c. Run: bitcoind signmessage 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj test
d. Run: bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test  (note: if you are to slow you may need to repeat step b)

If c and d where successful (do not return an error code) you are certain you own the respective addresses and can access the 25.912734 BTC.

EDIT: Both seemed successful - no error code but some long alphanumeric mumbojumbo was displayed after each signmessage was run

[wachtwoord]

Well then the good news is you have access to those 25.912734 BTC the bad news it is not ~50 like you thought (but then it never were).

The problem is these flawed transactions (you actually tried to double spend you cheeky bugger ) are in limbo. If you  want to check see http://bitcoincharts.com/bitcoin/txlist/ . That is a list of all unconfirmed transactions and if you control+f for T1, T2, T3, TA, TD (well the codes for them of course) you'll see them in the list (since March 1st).

To be honest I am not 100% sure how we can fix this (I am very sure we can though) so I'm going to suggest some options which in the very worst case won't work.

1) Do you have an old backup of your wallet.dat? If so, this is what we'll do:

A) Close Bitcoin-qt
B) In the C:\Users\me\AppData\Roaming\Bitcoin directory rename the wallet.dat (do not delete it to be safe, just rename it).
C) Copy and paste the backup wallet.dat to this directory
D) Start Bitcoin-qt with the rescan command
E) If all your Bitcoins show up as confirmed, create a new address and send them all there. (We do this because eventually your client would receive all transactions from the network even unconfirmed ones and then you would again be unable to spend the Bitcoins)

If you do not have a backup or step 1 didn't work we'll do the following:

2) We're going to export the private keys from 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj and 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY , create a new wallet, import the keys into the new wallet and move the coins.

a. Again open run the deamon and start the other command prompt
b. <optional if you have encrypted your wallet>. Run: bitcoind walletpassphrase PASSWORD TIMEOUT (where PASSWORD is your password and timeout is the time in second to unlock your wallet so we can attempt the next step, 20 seconds per address should suffice)
c. Run: bitcoind dumpprivkey 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj
d. Run: bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test  (note: if you are to slow you may need to repeat step b)
e. Copy and paste the two private keys to a notepad file
f. Stop the daemon command
g. In the C:\Users\me\AppData\Roaming\Bitcoin directory rename the wallet.dat (do not delete it to be safe, just rename it).
h. Start the daemon thread (do NOT copy a backup wallet.dat to the folder, there should be not file named wallet.dat there so the client will create a new wallet)
i. Run the following command: bitcoind importprivkey privkey1 (the first private key you copied to the notepad file)
j. Run the following command: bitcoind importprivkey privkey2
NOTE i and j may take a while
k. Now see if you have access to the funds, if so create a new Bitcoin address and send all your funds there for reasons explained above.

Hopefully one of these two methods will give you access to your coins again.

Beware:

1) Do NOT share your private keys on this forum. Anyone who has them can take your coins
2) Do NOT save the notepad file with the private keys as this poses a security risk. May be it's best to just avoid using these addresses anyway.

Finally: How did you guess wachtwoord was Dutch (it's Dutch for password)? Dutch relatives?

[donbenosee]

Well then the good news is you have access to those 25.912734 BTC the bad news it is not ~50 like you thought (but then it never were).

The problem is these flawed transactions (you actually tried to double spend you cheeky bugger ) are in limbo. If you  want to check see http://bitcoincharts.com/bitcoin/txlist/ . That is a list of all unconfirmed transactions and if you control+f for T1, T2, T3, TA, TD (well the codes for them of course) you'll see them in the list (since March 1st).

To be honest I am not 100% sure how we can fix this (I am very sure we can though) so I'm going to suggest some options which in the very worst case won't work.

1) Do you have an old backup of your wallet.dat?

Unfortunately I don't..

 

If you do not have a backup or step 1 didn't work we'll do the following:

2) We're going to export the private keys from 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj and 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY , create a new wallet, import the keys into the new wallet and move the coins.

a. Again open run the deamon and start the other command prompt
b. <optional if you have encrypted your wallet>. Run: bitcoind walletpassphrase PASSWORD TIMEOUT (where PASSWORD is your password and timeout is the time in second to unlock your wallet so we can attempt the next step, 20 seconds per address should suffice)
c. Run: bitcoind dumpprivkey 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj
d. Run: bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test  (note: if you are to slow you may need to repeat step b)

Is this correct or should I dumprivkey from BOTH transactions?

 

e. Copy and paste the two private keys to a notepad file
f. Stop the daemon command
g. In the C:\Users\me\AppData\Roaming\Bitcoin directory rename the wallet.dat (do not delete it to be safe, just rename it).
h. Start the daemon thread (do NOT copy a backup wallet.dat to the folder, there should be not file named wallet.dat there so the client will create a new wallet)
i. Run the following command: bitcoind importprivkey privkey1 (the first private key you copied to the notepad file)
j. Run the following command: bitcoind importprivkey privkey2
NOTE i and j may take a while
k. Now see if you have access to the funds, if so create a new Bitcoin address and send all your funds there for reasons explained above.

Hopefully one of these two methods will give you access to your coins again.

Beware:

1) Do NOT share your private keys on this forum. Anyone who has them can take your coins
2) Do NOT save the notepad file with the private keys as this poses a security risk. May be it's best to just avoid using these addresses anyway.

Thanks. It's happening now and I'll let you know the result when it completes.

 

Finally: How did you guess wachtwoord was Dutch (it's Dutch for password)? Dutch relatives?  

I was actually born in Eindhoven, but left Holland when I was three and came to Australia. My Dutch is pretty rusty but I can muddle my way through some of it

[/quote]

[donbenosee]

Okay, as I sort of suspected, the second importprivkey didn't work. I assume that is because step (c) was incorrect in your guide? I won't do any mor till you let me know.

[wachtwoord]

Yes you should, I made a "copy-paste-edit" mistake.

d should be: bitcoind dumpprivkey 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY

sorry

[donbenosee]

Yes you should, I made a "copy-paste-edit" mistake.

d should be: bitcoind dumpprivkey 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY

sorry

I'm in awe of how much you know about this, don't apologise

When I tried to dum that key I got:
error: {"code":-4,"message":"Private key for address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfm
njs8MSY is not known"}

I had a bit of a look at my new wallet and it has 10.023 BTC, with none unconfirmed

[wachtwoord]

I had a bit of a look at my new wallet and it has 10.023 BTC, with none unconfirmed

The 10.023 are from 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj http://blockchain.info/address/1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj  (1060 confirmations). Did you mean they are unconfirmed? Then this little trick didn't work. You can try another rescan later, but first:

When I tried to dum that key I got:
error: {"code":-4,"message":"Private key for address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfm
njs8MSY is not known"}

Did you remember to switch back to your own wallet when attempting to dump the second key ( 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY )? The new wallet is not going to have that key. You need to switch back to your 'real' wallet, dump the private key. The switch back to the freshly generated wallet and import the key.

[donbenosee]

I had a bit of a look at my new wallet and it has 10.023 BTC, with none unconfirmed

The 10.023 are from 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj http://blockchain.info/address/1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj  (1060 confirmations). Did you mean they are unconfirmed? Then this little trick didn't work. You can try another rescan later, but first: [/qyuote]

No, sorry, I meant they are confirmed.

Did you remember to switch back to your own wallet when attempting to dump the second key ( 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY )? The new wallet is not going to have that key. You need to switch back to your 'real' wallet, dump the private key. The switch back to the freshly generated wallet and import the key.

How do I switch, just rename the wallet.dat files?

[wachtwoord]

Great that they are confirmed

Yes, to switch simply rename. It always uses the file named wallet.dat.

[donbenosee]

I tried doing that in the debug console withing the qt client (with the previous wallet) and got this:

Private key for address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY is not known (code -4)

[wachtwoord]

I tried doing that in the debug console withing the qt client (with the previous wallet) and got this:

Private key for address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY is not known (code -4)

In post #68 you ran this command:

bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test

and it returned okay. So:

1) Can you repeat: bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test
2) Are you sure you unlocked your wallet if encrypted (bitcoind walletpassphrase PASSWORD TIMEOUT)
3) Are you sure you put the correct wallet.dat back?

[donbenosee]

In post #68 you ran this command:

bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test

and it returned okay. So:

1) Can you repeat: bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test

It replied with ILZjvMYaAaQWvXQPUx9bsnTFLyCFkA6asSkLb6mqTORYzHZv8x24FvojoqNadM/4lmBbJWagtt9NfzGS
iX8U3qg=

2) Are you sure you unlocked your wallet if encrypted (bitcoind walletpassphrase PASSWORD TIMEOUT)

Yes

3) Are you sure you put the correct wallet.dat back?

Yes.

Sorry about the delay in replying, had some visitors i couldn't get rid of

[donbenosee]

In post #57 you wrote:

(10 of your Bitcoins are here at least: http://blockchain.info/address/1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj )

Hmm, how do I get my BTC out of that address?

[wachtwoord]

It replied with ILZjvMYaAaQWvXQPUx9bsnTFLyCFkA6asSkLb6mqTORYzHZv8x24FvojoqNadM/4lmBbJWagtt9NfzGS
iX8U3qg=

2) Are you sure you unlocked your wallet if encrypted (bitcoind walletpassphrase PASSWORD TIMEOUT)

Yes

3) Are you sure you put the correct wallet.dat back?

Yes.

I checked and you signed the message test with the Bitcoin address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY. Therefore I am 100% certain you own the private key (and therefore the funds). As you answered yes to my two questions above there is only one possibility left: You mistyped it (maybe you added a space?) should be:

bitcoind dumpprivkey 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY

(be sure to unlock your wallet first (bitcoind walletpassphrase PASSWORD TIMEOUT).

(and after you get this working import the private key in the second wallet you created)

Sorry about the delay in replying, had some visitors i couldn't get rid of

No worries

In post #57 you wrote:

(10 of your Bitcoins are here at least: http://blockchain.info/address/1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj )

Hmm, how do I get my BTC out of that address?

Very simple. Just start bitcoin with the wallet.dat to which you imported the private key and send the funds to a new Bitcoin address. Try to export/import the other address first though.

[donbenosee]

[
I checked and you signed the message test with the Bitcoin address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY. Therefore I am 100% certain you own the private key (and therefore the funds). As you answered yes to my two questions above there is only one possibility left: You mistyped it (maybe you added a space?) should be:

bitcoind dumpprivkey 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY

I copied and pasted it but I'm still getting error: {"code":-4,"message":"Private key for address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfm
njs8MSY is not known"} And I'm certain this is my original wallet, because the second one you had me create has no encryption, so if I try walletpassphrase with that one it tells me the passphrase doesn't apply..

Very simple. Just start bitcoin with the wallet.dat to which you imported the private key and send the funds to a new Bitcoin address. Try to export/import the other address first though.

Could you please explain that ? Is that the first private key which I dumped earlier?

[wachtwoord]

[
I checked and you signed the message test with the Bitcoin address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY. Therefore I am 100% certain you own the private key (and therefore the funds). As you answered yes to my two questions above there is only one possibility left: You mistyped it (maybe you added a space?) should be:

bitcoind dumpprivkey 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY

I copied and pasted it but I'm still getting error: {"code":-4,"message":"Private key for address 1LkJVtqoVLKKMsUFrCLnqZ8Vxfm
njs8MSY is not known"} And I'm certain this is my original wallet, because the second one you had me create has no encryption, so if I try walletpassphrase with that one it tells me the passphrase doesn't apply..

This is very very weird. Can you please confirm that if you run the commands:

bitcoind dumpprivkey 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY
and
bitcoind signmessage 1LkJVtqoVLKKMsUFrCLnqZ8Vxfmnjs8MSY test

consecutively (so without switching wallets or restarting th deamon or anything. Just right after each other), the first command fails and the second succeeds?

If so, I'll have to look into this more because then something happens which to me is inherently impossible (the private key is required for both these commands, how can one succeed and the other fail?)

Very simple. Just start bitcoin with the wallet.dat to which you imported the private key and send the funds to a new Bitcoin address. Try to export/import the other address first though.

Could you please explain that ? Is that the first private key which I dumped earlier?

You imported the private key to the first address ( 1CVX2A8dEPJnV62ey7kEuoNhuAUKvJrDLj ) into the second wallet file. So when you have the second wallet file loaded (where you can see the Bitcoins for this address as confirmed and available) you have access to these coins and can move them. So if you create a new address (under receive) you can send them there for instance. Another option is to create a new address in your original wallet file and send the coins there. By moving the coins you actually prove to yourself you have access to the coins again

[donbenosee]

I must have fat fingers, I got a private key that time..<shakes head>

Let me just check somthing pls

[donbenosee]

Okay, let me guess...stop the daemon, change to the newer wallet file and import the second private key?

EDIT: That did it:)

Okay, I now have 25.912734 confirmed BTC in my new wallet .Many thanks, once I get this all sorted I shall donate some to you.

Now, I have another small problem. Yesterday I decided to move my remaining 13-something BTC from the old wallet to a new one created in Armory. Unfortunately, that transaction hasn't confirmed yet, so I have 13.612 more BTC in limbo somewhere. Can you help me find them? I promise I'll do nothing else after that lol

The transaction details are:
Status: 0/unconfirmed
Date: 8/03/2013 14:43
To: 17hzeZ8gKwLAHASyh85S5FSNYAFsexPAyk
Debit: -13.612 BTC
Net amount: -13.612 BTC
Transaction ID: 3ea177ce0db93b9bbbdc2286f5ca08e038a364db704205250d253d704a67d6a1

[wachtwoord]

Okay, let me guess...stop the daemon, change to the newer wallet file and import the second private key?

EDIT: That did it:)

Okay, I now have 25.912734 confirmed BTC in my new wallet .Many thanks, once I get this all sorted I shall donate some to you.

Great that worked out. You're welcome and thanks for the donation

Now, I have another small problem. Yesterday I decided to move my remaining 13-something BTC from the old wallet to a new one created in Armory. Unfortunately, that transaction hasn't confirmed yet, so I have 13.612 more BTC in limbo somewhere. Can you help me find them? I promise I'll do nothing else after that lol

The transaction details are:
Status: 0/unconfirmed
Date: 8/03/2013 14:43
To: 17hzeZ8gKwLAHASyh85S5FSNYAFsexPAyk
Debit: -13.612 BTC
Net amount: -13.612 BTC
Transaction ID: 3ea177ce0db93b9bbbdc2286f5ca08e038a364db704205250d253d704a67d6a1

I'll look into this tomorrow, got my birthday party to head down to first