Bitcoin Forum
May 10, 2024, 05:18:47 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin client backward compatible w/ older wallet.dat?  (Read 3091 times)
Stephen Gornick (OP)
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
December 18, 2010, 08:27:25 PM
 #1

Saw this Twitter status update:
  Does the #bitcoin protocol have a version number that allows to upgrade if someone leaves the system for 5 - 10 years?
  http://twitter.com/stephanwehner/statuses/16224034316361728

I think what is being asked is, if a client were not upgraded for a very long time, could it still communicate?

Either way, will the future clients be backward compatible as far as being able to access today's wallet.dat?

A lot can happen in 5 to 10 years. 

  IPv6, various vulnerabilities discovered, encrypted wallet.dat, etc.

(Incidentally, ... isn't the reason most who have left the system for 5 - 10 years due to being incarcerated?)

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


1715318327
Hero Member
*
Offline Offline

Posts: 1715318327

View Profile Personal Message (Offline)

Ignore
1715318327
Reply with quote  #2

1715318327
Report to moderator
In order to get the maximum amount of activity points possible, you just need to post once per day on average. Skipping days is OK as long as you maintain the average.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715318327
Hero Member
*
Offline Offline

Posts: 1715318327

View Profile Personal Message (Offline)

Ignore
1715318327
Reply with quote  #2

1715318327
Report to moderator
1715318327
Hero Member
*
Offline Offline

Posts: 1715318327

View Profile Personal Message (Offline)

Ignore
1715318327
Reply with quote  #2

1715318327
Report to moderator
1715318327
Hero Member
*
Offline Offline

Posts: 1715318327

View Profile Personal Message (Offline)

Ignore
1715318327
Reply with quote  #2

1715318327
Report to moderator
theymos
Administrator
Legendary
*
Offline Offline

Activity: 5194
Merit: 12982


View Profile
December 18, 2010, 08:42:37 PM
 #2

The public/private keys are in there, so it should always be possible to recover them, even if Bitcoin can't do it automatically.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Stephen Gornick (OP)
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
December 18, 2010, 10:40:14 PM
 #3

How would I merge the keys from an old wallet.dat into current.  If I can launch the client, I can just transfer to address from a new wallet, but is it possible to add those keys into another wallet?

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


theymos
Administrator
Legendary
*
Offline Offline

Activity: 5194
Merit: 12982


View Profile
December 19, 2010, 02:49:16 AM
 #4

Quote
is it possible to add those keys into another wallet?

It's possible, but Bitcoin doesn't do it. A future version of Bitcoin might do it, though. In any case, it will be possible to manually extract keys from an old wallet and insert them into a new one.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Stephen Gornick (OP)
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
June 16, 2011, 07:20:29 AM
 #5

A future version of Bitcoin might do it, though.

Just to bookend this thread:
  Pull #220, Wallet and key import and export
  - https://github.com/bitcoin/bitcoin/pull/220

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!