Two copies of wallet, showing different balances, tried -rescan

Stephen Gornick

legendary

Activity: 2506

Merit: 1010

Quote from: 420 on November 09, 2012, 02:52:55 AM

Is the messed up info just contained in that wallet? Meaning I could use my new wallet and redo the transaction since it didn't go through anyway and nothing would be wrong?

Correct ... nodes will neither accept the transaction nor relay it if the transaction includes a double spend.

The client with the old wallet will continue to try to broadcast the transaction forever but it will never succeed. If you don't need the old wallet.dat anymore (i.e. all funds it had are also on your new wallet) then you can just abandon it.

420

hero member

Activity: 756

Merit: 500

Quote from: Stephen Gornick on November 09, 2012, 02:41:58 AM

Quote from: 420 on November 09, 2012, 01:58:56 AM

Old wallet has 'learned' the new transactions and listed them as happeneing all today. with the final one I actually made today not showing any confirmations

If the blockchain for the client running the old wallet has completed updating to the latest block and there still are no confirmations showing that could mean the client determined that the transaction is a double spend. (It could also mean that it just hasn't been confirmed yet, no miners have included it in a block yet).

Does the spend transaction appear on Blockchain.info for instance? If not, then it is likely a double spend and you'll need to perform a little wallet surgery to get the balance on the old wallet to reappear correctly (by using pywallet to delete the offending transaction, then -rescan.)

If it's double spend which now I believe it is, no confirmations, transaction ID doesn't exist

Is the messed up info just contained in that wallet? Meaning I could use my new wallet and redo the transaction since it didn't go through anyway and nothing would be wrong?

Stephen Gornick

legendary

Activity: 2506

Merit: 1010

Quote from: 420 on November 09, 2012, 01:58:56 AM

Old wallet has 'learned' the new transactions and listed them as happeneing all today. with the final one I actually made today not showing any confirmations

If the blockchain for the client running the old wallet has completed updating to the latest block and there still are no confirmations showing that could mean the client determined that the transaction is a double spend. (It could also mean that it just hasn't been confirmed yet, no miners have included it in a block yet).

Does the spend transaction appear on Blockchain.info for instance? If not, then it is likely a double spend and you'll need to perform a little wallet surgery to get the balance on the old wallet to reappear correctly (by using pywallet to delete the offending transaction, then -rescan.)

420

hero member

Activity: 756

Merit: 500

Quote from: juhakall on November 09, 2012, 12:59:14 AM

Start your client with -rescan option, that should scan the blockchain for missing transactions.

didn't work

Old wallet has 'learned' the new transactions and listed them as happeneing all today. with the final one I actually made today not showing any confirmations

also it's showing over 3 btc more than my new wallet did, which my new wallet was only missing one transaction for negative around 1btc so my new one looks like 4btc EXTRA. unless i've done this problem mistakenly before, I think it's incorrect

juhakall

sr. member

Activity: 658

Merit: 250

Start your client with -rescan option, that should scan the blockchain for missing transactions.

420

hero member

Activity: 756

Merit: 500

So I made the idiotic mistake of not deleting an old wallet when I used my wallet on another computer.

came back to the old wallet, opened and made a transaction

What should or could I do.

The client I opened the old wallet and made the transaction in was the 7.0 version

now using the new wallet that had my other new transactions minus the ONE transaction I just made...still loading blocks but it definitely doesn't show the transaction I made today in the list

Topic: Two copies of wallet, showing different balances, tried -rescan (Read 1097 times)