Bitcoin Forum
May 24, 2017, 04:39:18 AM *
News: If the forum does not load normally for you, please send me a traceroute.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Pitfall using the same block chain data with different wallets  (Read 1159 times)
Astrohacker
Full Member
***
Offline Offline

Activity: 156



View Profile WWW
June 14, 2011, 04:26:46 PM
 #1

I use multiple wallet.dat files with the same block chain data. (By "block chain data" I mean all the data in the .bitcoin directory other than the wallet.) Apparently, this method does not work perfectly with the standard client. I tried sending BTC from one wallet to another, by switching the wallet file, and the BTC never showed up in the new wallet. However, it showed up on block explorer, so I knew the transaction was successful. So I deleted the block chain data and downloaded it again, and then the BTC showed up in the new wallet.

Lesson learned: If you use more than one wallet, it appears to be necessary to keep block chain data separately for each wallet, otherwise your transactions might not show up.
1495600758
Hero Member
*
Offline Offline

Posts: 1495600758

View Profile Personal Message (Offline)

Ignore
1495600758
Reply with quote  #2

1495600758
Report to moderator
1495600758
Hero Member
*
Offline Offline

Posts: 1495600758

View Profile Personal Message (Offline)

Ignore
1495600758
Reply with quote  #2

1495600758
Report to moderator
1495600758
Hero Member
*
Offline Offline

Posts: 1495600758

View Profile Personal Message (Offline)

Ignore
1495600758
Reply with quote  #2

1495600758
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1495600758
Hero Member
*
Offline Offline

Posts: 1495600758

View Profile Personal Message (Offline)

Ignore
1495600758
Reply with quote  #2

1495600758
Report to moderator
1495600758
Hero Member
*
Offline Offline

Posts: 1495600758

View Profile Personal Message (Offline)

Ignore
1495600758
Reply with quote  #2

1495600758
Report to moderator
1495600758
Hero Member
*
Offline Offline

Posts: 1495600758

View Profile Personal Message (Offline)

Ignore
1495600758
Reply with quote  #2

1495600758
Report to moderator
kokojie
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
June 14, 2011, 04:38:57 PM
 #2

yes, this is why the bitcoin wiki recommend that you delete blockindex.dat file each time you switch wallet

If my post has been helpful, send me some love -> BTC: 1kokojUapmWqCqPw3Ch2rjcVh57tJEzka | PPC: PDyXAgA8eH47gokVW6zVZPSuu15aao5nZF | Bitshares: kokojie
My reputation
Insti
Sr. Member
****
Offline Offline

Activity: 294


Firstbits: 1duzy


View Profile
June 14, 2011, 04:43:46 PM
 #3

Or you could just use the -rescan command line option which will go through the block chain and find your missing transactions without having to re-download the block chain.

Code:
-rescan            Rescan the block chain for missing wallet transactions



joan
Jr. Member
*
Offline Offline

Activity: 56



View Profile
June 14, 2011, 08:05:00 PM
 #4

Did you completely close the client when swapping wallets ?

As far as I understand, it should work. Each wallet keeps a pointer to the last block it knows about. During the application initialization, the last block in the blockchain file is compared to what the wallet is aware of, and a partial rescan is performed if needed.

If I swap my wallet with an older copy, it takes a bit longer than usual to start, but the new transactions to/from my wallet are visible right away. (Not tested with two completely different wallets though)

There was a thread about a similar problem recently, so maybe there's an issue somehow.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!