Author Topic: Migration Guide for 1.0 to 2.0  (Read 5401 times)

0 Members and 1 Guest are viewing this topic.

jakub

  • Guest
Re: Migration Guide for 1.0 to 2.0
« Reply #45 on: October 10, 2015, 04:41:28 pm »
On Windows 8.1, v0.9.3c

I just tried to export keys from the console. Its says "ok" in the console but there is no sign of the keys.json file in the appdata/roaming/bitshares folder.

I had to run as administrator to get it to save the file on windows.  I tried entering in full path etc and nothing worked until i ran as admin.

I really dont know why this has not been fixed its going to cause so many problems come the 2.0 launch...

For me it's also quite incredible that the problem has been raised so many times on this forum and CNX has been unable to supply a simple fix for this issue.
We are shooting ourselves in the foot in a very critical moment.

Offline hadrian

  • Sr. Member
  • ****
  • Posts: 467
    • View Profile
  • BitShares: hadrian
Re: Migration Guide for 1.0 to 2.0
« Reply #46 on: October 10, 2015, 05:17:54 pm »
you need to   use
Code: [Select]
wallet_export_keys c:\bts\bts.json  contain  path

That works, thanks.

This worked for me also - thanks
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline sirlo

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: Migration Guide for 1.0 to 2.0
« Reply #47 on: October 10, 2015, 10:17:23 pm »
On Windows 8.1, v0.9.3c

I just tried to export keys from the console. Its says "ok" in the console but there is no sign of the keys.json file in the appdata/roaming/bitshares folder.

I had to run as administrator to get it to save the file on windows.  I tried entering in full path etc and nothing worked until i ran as admin.

I really dont know why this has not been fixed its going to cause so many problems come the 2.0 launch...


I am having the same problem..except I've got Win 7 Professional..even run as administrator did not help..
Is there a reason why the json file does not show up in the "appdata/roaming/bitshares" folder..?  However when I tried to do it again whether using the full path name or not.. the console says"  File already exists!!...

Does anyone know what is the command to use in the console to delete this "invisible" in Windows explorer" file?
Or does it not matter and I should just save a version of keys.json in some other location to be imported after the 13th?

This is very frustrating...It almost makes me want to leave my bts on the Exchanges....however they have given no indication as to
whether or not they are going to migrate/upgrade..!?   

I think the value of BTS will increase significantly if one did not feel such apprehension and nervousness when trying to manage
one's crypto assets...(I've already given up trying to figure out what to do with some PTS left in a webwallet..)

Thanks

P.S.. As an "Average Joe" I don't comment much on the forum but I do visit as often as I can to try and keep up with what's going on...but I wish things like this migration was easier to accomplish and less nerve wracking..:-)


Offline liondani

  • Hero Member
  • *****
  • Posts: 3733
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: Migration Guide for 1.0 to 2.0
« Reply #48 on: October 11, 2015, 01:32:27 am »
This is very frustrating...It almost makes me want to leave my bts on the Exchanges....however they have given no indication as to
whether or not they are going to migrate/upgrade..!?   
Poloniex have made an official announcement that they will migrate.

Offline emailtooaj

Re: Migration Guide for 1.0 to 2.0
« Reply #49 on: October 11, 2015, 02:00:02 am »
On Windows 8.1, v0.9.3c

I just tried to export keys from the console. Its says "ok" in the console but there is no sign of the keys.json file in the appdata/roaming/bitshares folder.

I had to run as administrator to get it to save the file on windows.  I tried entering in full path etc and nothing worked until i ran as admin.

I really dont know why this has not been fixed its going to cause so many problems come the 2.0 launch...


I am having the same problem..except I've got Win 7 Professional..even run as administrator did not help..
Is there a reason why the json file does not show up in the "appdata/roaming/bitshares" folder..?  However when I tried to do it again whether using the full path name or not.. the console says"  File already exists!!...

Does anyone know what is the command to use in the console to delete this "invisible" in Windows explorer" file?
Or does it not matter and I should just save a version of keys.json in some other location to be imported after the 13th?

This is very frustrating...It almost makes me want to leave my bts on the Exchanges....however they have given no indication as to
whether or not they are going to migrate/upgrade..!?   

I think the value of BTS will increase significantly if one did not feel such apprehension and nervousness when trying to manage
one's crypto assets...(I've already given up trying to figure out what to do with some PTS left in a webwallet..)

Thanks

P.S.. As an "Average Joe" I don't comment much on the forum but I do visit as often as I can to try and keep up with what's going on...but I wish things like this migration was easier to accomplish and less nerve wracking..:-)

Hey sirlo,
Under Windows, that particular json (keys file) gets dumped into the C:/Program File section... or where ever you located/installed your Bitshares.exe file too. 
It does not dump/store into the appdata/roaming folder like your normal wallet "export" does.
Hope this helps!
   
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

Offline Overthetop

Re: Migration Guide for 1.0 to 2.0
« Reply #50 on: October 11, 2015, 03:36:23 am »
what would happen, if users do not export the wallet keys using the 0.9.3C version before migration deadline ?

个人微博账号: Overthetop_万里晴空
“块链创新与创业”交流群: 330378613

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Re: Migration Guide for 1.0 to 2.0
« Reply #51 on: October 11, 2015, 04:10:06 am »
what would happen, if users do not export the wallet keys using the 0.9.3C version before migration deadline ?

They will still be able to open 0.9.3 and export.  even if the chain is dead.  Someone could also write a tool that will change an old style backup to a graphene compatible backup.  It is beyond my abilities though.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline CalabiYau

Re: Migration Guide for 1.0 to 2.0
« Reply #52 on: October 11, 2015, 06:32:30 am »
On Windows 8.1, v0.9.3c

I just tried to export keys from the console. Its says "ok" in the console but there is no sign of the keys.json file in the appdata/roaming/bitshares folder.

I had to run as administrator to get it to save the file on windows.  I tried entering in full path etc and nothing worked until i ran as admin.

I really dont know why this has not been fixed its going to cause so many problems come the 2.0 launch...


I am having the same problem..except I've got Win 7 Professional..even run as administrator did not help..
Is there a reason why the json file does not show up in the "appdata/roaming/bitshares" folder..?  However when I tried to do it again whether using the full path name or not.. the console says"  File already exists!!...

Does anyone know what is the command to use in the console to delete this "invisible" in Windows explorer" file?
Or does it not matter and I should just save a version of keys.json in some other location to be imported after the 13th?

This is very frustrating...It almost makes me want to leave my bts on the Exchanges....however they have given no indication as to
whether or not they are going to migrate/upgrade..!?   

I think the value of BTS will increase significantly if one did not feel such apprehension and nervousness when trying to manage
one's crypto assets...(I've already given up trying to figure out what to do with some PTS left in a webwallet..)

Thanks

P.S.. As an "Average Joe" I don't comment much on the forum but I do visit as often as I can to try and keep up with what's going on...but I wish things like this migration was easier to accomplish and less nerve wracking..:-)

Whoever is looking for his "console export file" in windows, produced like e.g.

wallet_export_keys C:\desktop\export-keys.json

in explorer search for ".json"

and the file will show up.


Offline habeler

Re: Migration Guide for 1.0 to 2.0
« Reply #53 on: October 11, 2015, 11:49:07 am »
I used 0.9.3 Windows GUI to export, and now I read that it is wrong. Does that mean that I am screwed? I have a copy of the wallet too.

I am travelling and won't have access to my PC till Wednesday. Its shocking that I used the latest version and apparently it is not the correct way.

I bought some on Poloniex recently and now I think I wil leave it there. Are there any other airderops which I wil miss out by keeping it there?
1LeQTkxdpvZFU23qA22xas2zvqzTHMa48T
bts-habeler876

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4273
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
Re: Migration Guide for 1.0 to 2.0
« Reply #54 on: October 11, 2015, 12:14:37 pm »
I used 0.9.3 Windows GUI to export, and now I read that it is wrong. Does that mean that I am screwed? I have a copy of the wallet too.

I am travelling and won't have access to my PC till Wednesday. Its shocking that I used the latest version and apparently it is not the correct way.

I bought some on Poloniex recently and now I think I wil leave it there. Are there any other airderops which I wil miss out by keeping it there?

you have to use console how to: http://blog.smartcoin.pw/2015/09/bitshares-how-to-prepare-your-wallet.html
Join us on Telegram: https://t.me/btstalk

jakub

  • Guest
Re: Migration Guide for 1.0 to 2.0
« Reply #55 on: October 11, 2015, 12:24:00 pm »
I used 0.9.3 Windows GUI to export, and now I read that it is wrong. Does that mean that I am screwed? I have a copy of the wallet too.

I am travelling and won't have access to my PC till Wednesday. Its shocking that I used the latest version and apparently it is not the correct way.

I bought some on Poloniex recently and now I think I wil leave it there. Are there any other airderops which I wil miss out by keeping it there?

you have to use console how to: http://blog.smartcoin.pw/2015/09/bitshares-how-to-prepare-your-wallet.html

@habeler, if you are unable to redo the export process using the console before 13/10, nothing is lost as you can still do it after that date.
The export/import process will still work after 13/10 when the old BTS blockchain is no be longer operational.

jakub

  • Guest
Re: Migration Guide for 1.0 to 2.0
« Reply #56 on: October 11, 2015, 02:49:37 pm »
On Windows 7 using the console command wallet_export_keys with the file name only:
Code: [Select]
wallet_export_keys keys.jsondid not produce any file (it definitely was not in the %APPDATA%\Roaming\BitShares, searching the whole drive did not bring any result either)

But when I entered the full path:
Code: [Select]
wallet_export_keys C:/Users/[your user name]/AppData/Roaming/BitShares/keys.jsonit worked fine.

Also, the migration guide could explicitly state that syncing the blockchain beforehand is not required. You can do the export with the wallet unsynced.
I can see that people are struggling to sync the blockchain after upgrading to 0.9.3 which I believe is unnecessary.
« Last Edit: October 11, 2015, 03:46:45 pm by jakub »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12907
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: Migration Guide for 1.0 to 2.0
« Reply #57 on: October 12, 2015, 02:41:25 am »
On Windows 7 using the console command wallet_export_keys with the file name only:
Code: [Select]
wallet_export_keys keys.jsondid not produce any file (it definitely was not in the %APPDATA%\Roaming\BitShares, searching the whole drive did not bring any result either)

But when I entered the full path:
Code: [Select]
wallet_export_keys C:/Users/[your user name]/AppData/Roaming/BitShares/keys.jsonit worked fine.
Fixed it ... thanks

Quote
Also, the migration guide could explicitly state that syncing the blockchain beforehand is not required. You can do the export with the wallet unsynced.
I can see that people are struggling to sync the blockchain after upgrading to 0.9.3 which I believe is unnecessary.
That is not true for everbody ... if you may have received funds you have not yet scanned for, you will not be able to export/import them. hence you need a complete sync.

Anyway, I assume we will see a torrent with the "final" bts1 blockchain so that people need only do the reindex/rescan!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline merockstar

Re: Migration Guide for 1.0 to 2.0
« Reply #58 on: October 12, 2015, 03:57:19 am »
My "last block was synced" count down is going up in 0.9.3c

Offline detect

  • Newbie
  • *
  • Posts: 2
    • View Profile
  • BitShares: detect
Re: Migration Guide for 1.0 to 2.0
« Reply #59 on: October 12, 2015, 05:17:33 am »
I needed to specify a path for the Mac client as well.