« previous next »
Pages: [1]   Go Down

Author Topic: How to import wallet from a client that is older than 0.9.2  (Read 2376 times)

0 Members and 1 Guest are viewing this topic.

October 30, 2015, 07:24:13 pm Reply #9

Offline thezman007

  • Newbie
  • *
  • Posts: 8
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
Just wanted to say, this helped me too. Thanks!
Logged
October 25, 2015, 03:29:17 am Reply #8

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
Excellent.  You're most welcome.

Enjoy!
Logged
October 25, 2015, 02:29:49 am Reply #7

Offline widehazer

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
Providing the full path worked great!
I also got the exported 0.9.3c keys imported into 2.0.
Thank you so much for your help!
Logged
October 25, 2015, 12:56:28 am Reply #6

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
I believe the filename for the export is an absolute location, so what you did would export to the root of your filesystem.  The application may not be running with privileges to create files there, so try entering a full path in quotes instead.
Logged
October 25, 2015, 12:40:14 am Reply #5

Offline widehazer

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
I'm using OS X (10.10.5)
Logged
October 25, 2015, 12:12:55 am Reply #4

Offline JA

  • Hero Member
  • *****
  • Posts: 650
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
Quote from: widehazer on October 25, 2015, 12:04:29 am
Thank you for the help.
I was able to install 0.9.3c, but when I run the export command it never does anything.
I ran this command: wallet_export_keys btsKeyExport.json
Then I used spotlight to search for btsKeyExport.json and it does not exist on my computer.

Is this because the client program will not sync? If so, how can I get it to sync? (It says "Severe network problems" and it does not appear to be making progress.)
what os are you using?
Logged
October 25, 2015, 12:04:29 am Reply #3

Offline widehazer

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
Thank you for the help.
I was able to install 0.9.3c, but when I run the export command it never does anything.
I ran this command: wallet_export_keys btsKeyExport.json
Then I used spotlight to search for btsKeyExport.json and it does not exist on my computer.

Is this because the client program will not sync? If so, how can I get it to sync? (It says "Severe network problems" and it does not appear to be making progress.)
Logged
October 24, 2015, 09:47:31 pm Reply #2

Offline JA

  • Hero Member
  • *****
  • Posts: 650
    • View Profile
Re: How to import wallet from a client that is older than 0.9.2
Quote from: widehazer on October 24, 2015, 09:45:58 pm
I don't know what version my current bitshares client is, but I think it was from more than 6 months ago.
When I try to import the json file into Bitshares 2.0 it says "Invalid Format".
How can I recover my BitShares in this situation?
do a backup with your current client.
install 0.9.3c
https://github.com/bitshares/bitshares-0.x/releases
export via console
http://blog.smartcoin.pw/2015/09/bitshares-how-to-prepare-your-wallet.html
« Last Edit: October 24, 2015, 09:51:06 pm by jabbajabbaつ◕_◕つ »
Logged
October 24, 2015, 09:45:58 pm Reply #1

Offline widehazer

  • Newbie
  • *
  • Posts: 9
    • View Profile
How to import wallet from a client that is older than 0.9.2
I don't know what version my current bitshares client is, but I think it was from more than 6 months ago.
When I try to import the json file into Bitshares 2.0 it says "Invalid Format".
How can I recover my BitShares in this situation?
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.028 seconds with 28 queries.