Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: sergio on March 15, 2012, 08:03:09 AM



Title: how to migrate wallet to older bitcoin client?
Post by: sergio on March 15, 2012, 08:03:09 AM
I have updated my wallet to version 0.603 of bitcoin, and it works, however that version of bitcoin is very unstable, and crashes frequently, I have used version 0.502 and it is very stable.

The problem is that my wallet will not work with version 0.502 now that it has been used with version 0.603.

Any recommendations on how to migrate the wallet from version 0.603 to version 0.502?
Moving the bitcoins is simple, but how do I move the keys, or migrate the wallet to the older version?

 


Title: Re: how to migrate wallet to older bitcoin client?
Post by: btctrader22 on March 15, 2012, 08:11:33 AM
I have updated my wallet to version 0.603 of bitcoin, and it works, however that version of bitcoin is very unstable, and crashes frequently, I have used version 0.502 and it is very stable.

The problem is that my wallet will not work with version 0.502 now that it has been used with version 0.603.

Any recommendations on how to migrate the wallet from version 0.603 to version 0.502?
Moving the bitcoins is simple, but how do I move the keys, or migrate the wallet to the older version?

 

I would like to know too


Title: Re: how to migrate wallet to older bitcoin client?
Post by: jake262144 on March 15, 2012, 10:08:47 AM
Wallets created with this version of bitcoin will use 33-byte 'compressed' public keys instead of 65-byte public keys, resulting in smaller transactions and less traffic on the bitcoin network. The shorter keys are already supported by the network but wallet.dat files containing short keys are not compatible with earlier versions of Bitcoin-Qt/bitcoind.
+1

Use a recent wallet backup.
Also, as a general piece of advice, please don't use unstable (beta, release candidate,...) software for mission-critical tasks.

While I do have bitcoind 60003 up and running here, it's only a test server with a total of 1 BTC to play with.
When the version 6 client gets the final status it's the authors way of telling you that it should be safe for production environment.


Title: Re: how to migrate wallet to older bitcoin client?
Post by: sergio on March 15, 2012, 11:50:38 AM
Thanks for the advice, I will try to use an old backup.

As far as being beta versions, my understanding is that at present all versions are currently beta until 1.0 is released.

Maybe the less stable ones should be labeled "alpha" instead of "beta", that was how it used to be done in the software industry in the past.

Based on the post here it appears that a backup is the only solution to this problem, anyway I believe I have old backups and will used them.

When using an old backup, will the block chain need to be rescanned or will it be as simple as replacing the wallet?





Title: Re: how to migrate wallet to older bitcoin client?
Post by: sergio on March 15, 2012, 12:18:53 PM
Good news, using an old backup solved the problem.


Title: Re: how to migrate wallet to older bitcoin client?
Post by: Pieter Wuille on March 15, 2012, 04:50:45 PM
If 0.6.0rc3 is unstable for you, can you please file a bug report? Thanks!


Title: Re: how to migrate wallet to older bitcoin client?
Post by: sergio on March 15, 2012, 06:03:20 PM
where do I file the bug report? , I posted a message on this forum with the error logs so that it could be seen by the developers, this forum is probably not the proper place.
If you can tell me where to file the bug report I will, if you can provide me a link that will even be better.


Title: Re: how to migrate wallet to older bitcoin client?
Post by: mila on March 15, 2012, 10:01:37 PM
where do I file the bug report?

for sure here: https://github.com/bitcoin/bitcoin/issues


Title: Re: how to migrate wallet to older bitcoin client?
Post by: sergio on March 17, 2012, 10:23:20 AM
thanks, I have submitted a bug report.
Also I have found out that this bug relates to the wallet, with a fresh new clean wallet this bug does not occur, or at least it did not occur during the testing.