Migration Guide for 1.0 to 2.0

[xeroc]

@xeroc - as an example which might help exchanges who want to integrate with graphene, here is a list of API functions that metaexchange needs, and which could do with an example of how to get each one, in the doc:

* GetBalance - of an account
* SendFunds - simple transfer of asset
* GetBlockCount - height of best block
* ListSinceBlock - list all transactions on an account since block X

Those are pretty much the core functionality of any exchange's wallet wrappers, it would be nice to have an example of each

thanks .. gonna add those here:
http://docs.bitshares.eu/integration/OftenUsedCalls.html
writing them now (except maybe the latter since that would work a little differently afaik .. maybe @bytemaster can add a call for that .. otherwise you would go with balance operations from the 1.11.X space

[monsterer]

@xeroc - as an example which might help exchanges who want to integrate with graphene, here is a list of API functions that metaexchange needs, and which could do with an example of how to get each one, in the doc:

* GetBalance - of an account
* SendFunds - simple transfer of asset
* GetBlockCount - height of best block
* ListSinceBlock - list all transactions on an account since block X

Those are pretty much the core functionality of any exchange's wallet wrappers, it would be nice to have an example of each

[puppies]

You mention needing to sync in the event that there have been transactions since the last time you synced. Is this actually necessary? It's my understanding that 2.0 will have all of the accounts and balances properly based upon the 1.0 chain. Personally, I haven't been able to get either the Mac or the PC wallet to fully sync in over 2 months.

So here is my question. Can I just download the 0.9.3c wallet and perform the export on OSX without a successful sync? It appears that all my accounts are there, but the transactions will likely never catch up due to Network Congestion (whatever that means).

My understanding is that you will need to sync and scan.  Titan transactions generate new 1 time keys for transfers, and if your wallet is not synced those keys will not be in your wallet, and cannot be exported. 

If you are having a hard time getting the wallet synced, I would suggest the cli wallet.  It is much more stable, and you will be able to export from it easily.

[sirlo]

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!
 

Thanks emailtooaj..!

That worked...I was able to find the keys (json) file and make the necessary offline backups...Let's hope the
"IMPORT" process goes a little smoother..:-)....

and I noticed that Poloniex, etc.. made an announcement but not BTER??  I'm assuming that they will upgrade to 2.0 but in the absence of any written instructions or reassurances.. I did not want to risk leaving serious amounts of BTS in their hands...Let's hope everything goes OK..

[jakub]

You mention needing to sync in the event that there have been transactions since the last time you synced. Is this actually necessary? It's my understanding that 2.0 will have all of the accounts and balances properly based upon the 1.0 chain. Personally, I haven't been able to get either the Mac or the PC wallet to fully sync in over 2 months.

So here is my question. Can I just download the 0.9.3c wallet and perform the export on OSX without a successful sync? It appears that all my accounts are there, but the transactions will likely never catch up due to Network Congestion (whatever that means).

I'm not sure myself but this is what xeroc replied when I suggested that syncing might not be necessary:
https://bitsharestalk.org/index.php/topic,18714.msg243319.html#msg243319

[jakub]

Thanks alot .. was upgrading the page not having slept after the flight .. I appologize .. I'll take your recommendation ..

You are welcome

And please note that BM is probably going to fix the Windows bug soon as he's now aware of the issue.
https://bitsharestalk.org/index.php/topic,18909.0.html

[wmbutler]

You mention needing to sync in the event that there have been transactions since the last time you synced. Is this actually necessary? It's my understanding that 2.0 will have all of the accounts and balances properly based upon the 1.0 chain. Personally, I haven't been able to get either the Mac or the PC wallet to fully sync in over 2 months.

So here is my question. Can I just download the 0.9.3c wallet and perform the export on OSX without a successful sync? It appears that all my accounts are there, but the transactions will likely never catch up due to Network Congestion (whatever that means).

[xeroc]

Thanks alot .. was upgrading the page not having slept after the flight .. I appologize .. I'll take your recommendation ..

[jakub]

@xeroc, below is my proposal of the Exporting Your Wallet section of the guide.
I've made an attempt to be more verbose and consolidate all known issues I've seen people asking on the forum.
Note: I'm missing examples of the command line for Mac and Linux
-----------------------------------------------------------------------------------------------------------------------

Firstly, you need to upgrade your BitShares client to version 0.9.3c. To do the upgrade you need to:
- download the installation file from this URL: https://bitshares.org/download/
- uninstall your previous version of the BitShares client
- install the new version

Once you've upgraded you might want to perform two actions, which might be optional depending on your judgement:
- attempt to sync with the blockchain (this is only necessary with if you think that since the last time you did the syncing there have been some new transactions involving any of your accounts)
- send all your funds to yourself (this is only necessary if you want to tidy up and consolidate your accounts before importing them to BTS 2.0, this is optional as everything will be fine if you skip this step)

Since BitShares 0.9.3c, we have a Graphene compatible Export Keys function that can be accessed in two ways:
- by accessing it in the main menu
- by issuing a command in the console.

Note:
Due to a known bug, if you are on Windows the only option that will work for you is the console command - the file exported using the menu will not be compatible with BTS 2.0. This refers to Windows only.

Using the main menu
Just select File -> Export Wallet and you'll be asked to select a file location where the keys will be exported. 

Using the console
- navigate to the console: Account List -> Advanced Settings -> Console
- type: wallet_export_keys [full path to the file]/[file name].json
e.g. on Windows: wallet_export_keys C:\Users\[your user name]\Desktop\keys.json
e.g. on Mac:
e.g. on Linux:
- and hit Enter

Note:
The exported wallet file will be encrypted with your pass phrase! Make sure to remember it when trying to use that file again!

Note:
If you are on Windows and your file path tries to access the C drive directly (e.g. C:\keys.json) you might need to run the BitShares client as an administrator. So the least complicated option will be to aim for the desktop as in the example above.

[jakub]

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

It's nice you've updated the guide but... now everything is described only from the Windows perspective.
It should be more universal or the command line with a full path example should come in all three flavors: Mac, Win and Linux.
As it is now, if I was a Mac user I'd be confused.

[detect]

I needed to specify a path for the Mac client as well.

[unreadPostsSinceLastVisit]

My "last block was synced" count down is going up in 0.9.3c

[xeroc]

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

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!

[jakub]

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.

[jakub]

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.

[fav]

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]

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?

[CalabiYau]

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.

[puppies]

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.

[Overthetop]

what would happen, if users do not export the wallet keys using the 0.9.3C version before migration deadline ?

[emailtooaj]

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!
   

[liondani]

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.

[sirlo]

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..:-)

[hadrian]

you need to   use

Code: [Select]

wallet_export_keys c:\bts\bts.json  contain  path

That works, thanks.

This worked for me also - thanks

[jakub]

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.

[jaran]

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...

[profitofthegods]

you need to   use

Code: [Select]

wallet_export_keys c:\bts\bts.json  contain  path

That works, thanks.

[sudo]

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.

you need to   use

Code: [Select]

wallet_export_keys c:\bts\bts.json  contain  path

[profitofthegods]

I don't think it was created, windows search brought up a GUI backup I did a couple of days ago but no new file.

[fav]

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.

try windows search for .json - maybe you'll find it

[profitofthegods]

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.

[xeroc]

The guide could do with a section on what to do between Installation and User Guide - i.e. what to actually run which gets built by the previous step.

Absolutely .. I just recently started with the User Guide

[monsterer]

The guide could do with a section on what to do between Installation and User Guide - i.e. what to actually run which gets built by the previous step.

[xeroc]

http://docs.bitshares.eu/installation/Build.html doesn't mention that g++-4.9 isn't available for 14.04 LTS, you need to do this first:

Code: [Select]

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update

thanks .. updating ..

[monsterer]

http://docs.bitshares.eu/installation/Build.html doesn't mention that g++-4.9 isn't available for 14.04 LTS, you need to do this first:

Code: [Select]

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update

[xeroc]

Yes .. I noticed that too.. I have no idea who is responsible for the windwos builds and why it takes so long for them to rebuild that wallet into a *d version .. I'll try to contact the devs more aggressively now ..

[jakub]

why not fix the GUI backup bug!!!!!!!!!!!!!!!!!!!!

 

it will confuse many if not fixed...
and it will be counterproductive for the members that must explain to newbies what to do every time....
and the most important, it's bad PR/marketing just a few days before the release...

That's the reason (if you haven't noticed) .. why the migration guide still tells people to use the console

But what is the reason 0.9.3c cannot be replaced with 0.9.3d where the whole issue can easily be fixed?
There is more and more confusion, e.g. in the recent Muse announcement:

So in a Nutshell:

• Go to https://bitshares.org/download/ and download BitShares 0.9.3
• Then, if you have Notes on an external/centralized exchange, go to that/those exchanges and transfer all Notes to your own wallet (version 0.9.3.)
• Once your Notes are in your possession, in your new desktop wallet, click “File” and “Export Wallet” and save that .json file to your computer (or somewhere super duper trooper safe)
  

[xeroc]

why not fix the GUI backup bug!!!!!!!!!!!!!!!!!!!!

 

it will confuse many if not fixed...
and it will be counterproductive for the members that must explain to newbies what to do every time....
and the most important, it's bad PR/marketing just a few days before the release...

That's the reason (if you haven't noticed) .. why the migration guide still tells people to use the console

[liondani]

why not fix the GUI backup bug!!!!!!!!!!!!!!!!!!!!

 

it will confuse many if not fixed...
and it will be counterproductive for the members that must explain to newbies what to do every time....
and the most important, it's bad PR/marketing just a few days before the release...

[sudo]

why not fix the GUI backup bug!!!!!!!!!!!!!!!!!!!!

[xeroc]

I have a general remark: the navigation bar at the top is very counterintuitive. It took me a while to understand the logic behind it.
The convention is to show the path leading to the currently viewed content.

Thanks for the input .. it's not breadcrums .. and I had the same issue at first .. it's a sphinx-feature and I will thing about a way to make it more clear that it is "<pre - top - next>"

[bitacer]

Exactly my question why not just export your wallet? I have a Mac isn't the export wallet GUI feature sufficient?

why not update 0.9.3cGUI?

0.9.3c has two kinds of json files. (1) one from GUI export, (2) one from command line export. You cannot import (1) in Graphene. You should use (2). I am sure 0.9.3d will have identical json files with these two methods.

[jakub]

I have a general remark: the navigation bar at the top is very counterintuitive. It took me a while to understand the logic behind it.
The convention is to show the path leading to the currently viewed content.

[Marketorder]

Exactly my question why not just export your wallet? I have a Mac isn't the export wallet GUI feature sufficient?

why not update 0.9.3cGUI?

[sudo]

why not update 0.9.3cGUI?

[bitacer]

I wrote the Full path name Users/../Desktop/..keys.json  and it worked thanks.

[bitacer]

Yeah that did it thanks 

[bitacer]

On my mac using 0.9.3c I am trying to export keys using the console . Do I just name the file or should it be with a path . Because for some reason I cannot find the file anywhere mentioned before. thanks guys.

In that case I would recommend a full path .. like /Users/<me>/Desktop .. or so ..

Ok I will try that , thank you.

[xeroc]

On my mac using 0.9.3c I am trying to export keys using the console . Do I just name the file or should it be with a path . Because for some reason I cannot find the file anywhere mentioned before. thanks guys.

In that case I would recommend a full path .. like /Users/<me>/Desktop .. or so ..

[bitacer]

On my mac using 0.9.3c I am trying to export keys using the console . Do I just name the file or should it be with a path . Because for some reason I cannot find the file anywhere mentioned before. thanks guys.

[xeroc]

I'm on Windows 10, updated wallet from 0.9.2 to 0.9.3c and exported the wallet by GUI and command line.  I'm getting an "invalid Format" when importing the command line back up file.  I've also tried with the GUI backup file... same results.
I'm using Chrome web browser primarily but I also tried it in I.E. and got same results. 
Any suggestions on what I'm doing wrong or is this a bug that still needs worked out for Windows?

Thanks!!

I think you should add a suffix.Such as.Josn

Thanx wuyanren! But unfortunately I've tried that, along with various other ways, still with no luck.  Still keep getting "invalid format" error.
I even downloaded and installed the new Lite Wallet with same errors.
I've followed Xeroc's doc (Which by the way @Xeroc +10 on those!) for Exporting wallet to the "T" with the same results.  I'm using admin privileges correctly in Windows, so not sure what the deal is for getting these error messages.  It seems other Window users have been successful with their imports???

Could you open the exported file in notepad and send me the first few lines in a PM? Make sure to remove the content for all "encrypted_*"-whatsoever fields ..

[emailtooaj]

I'm on Windows 10, updated wallet from 0.9.2 to 0.9.3c and exported the wallet by GUI and command line.  I'm getting an "invalid Format" when importing the command line back up file.  I've also tried with the GUI backup file... same results.
I'm using Chrome web browser primarily but I also tried it in I.E. and got same results. 
Any suggestions on what I'm doing wrong or is this a bug that still needs worked out for Windows?

Thanks!!

I think you should add a suffix.Such as.Josn

Thanx wuyanren! But unfortunately I've tried that, along with various other ways, still with no luck.  Still keep getting "invalid format" error.
I even downloaded and installed the new Lite Wallet with same errors.
I've followed Xeroc's doc (Which by the way @Xeroc +10 on those!) for Exporting wallet to the "T" with the same results.  I'm using admin privileges correctly in Windows, so not sure what the deal is for getting these error messages.  It seems other Window users have been successful with their imports???

[wuyanren]

I'm on Windows 10, updated wallet from 0.9.2 to 0.9.3c and exported the wallet by GUI and command line.  I'm getting an "invalid Format" when importing the command line back up file.  I've also tried with the GUI backup file... same results.
I'm using Chrome web browser primarily but I also tried it in I.E. and got same results. 
Any suggestions on what I'm doing wrong or is this a bug that still needs worked out for Windows?

Thanks!!

I think you should add a suffix.Such as.Josn

[emailtooaj]

I'm on Windows 10, updated wallet from 0.9.2 to 0.9.3c and exported the wallet by GUI and command line.  I'm getting an "invalid Format" when importing the command line back up file.  I've also tried with the GUI backup file... same results.
I'm using Chrome web browser primarily but I also tried it in I.E. and got same results. 
Any suggestions on what I'm doing wrong or is this a bug that still needs worked out for Windows?

Thanks!!

[ripplexiaoshan]

Great documentation!

[Thom]

0.9.3c has two kinds of json files. (1) one from GUI export, (2) one from command line export. You cannot import (1) in Graphene. You should use (2). I am sure 0.9.3d will have identical json files with these two methods.

That's confusing. What puppies said also highlights a stumbling block, that "import_account" doesn't import balances. I also posted elsewhere concerning the expected migration. BM said on one mumble regarding migration that "you don't need to do anything if your balance is NOT on an exchange, everything will be migrated automatically for you".

If that is indeed the case it seems like xeroc's efforts to document a migration process is only important before Oct 13. And in that case the process is rather cumbersome. In my case I found a balance and followed xeroc's guide for importing the balance but it didn't work. I posted the error I received here: https://bitsharestalk.org/index.php/topic,18717.msg240991.html#msg240991. So far nobody has replied with why.

Believe it or not I have yet to fire up the GUI. I've built it, but my focus has been on the witness / cli code and just haven't taken the time to do it.

Am I to understand that there is also a graphene web wallet (GUI) at https://graphene.bitshares.org/ ? Does that use the testnet or a separate network of witness nodes dedicated for GUI testing? I suspect the later, as I have not seen any posts that coordinate efforts between GUI testing and testnet testing, and I would think clayops "spam" tests might make it difficult to work through a GUI test plan.

[liondani]

correct, the GUI backup is the old one... it's better to advice people to use the console

agreed ... gonna deploy a new version today ..

the problem persist only for the windows version?

[clayop]

correct, the GUI backup is the old one... it's better to advice people to use the console

agreed ... gonna deploy a new version today ..

[xeroc]

correct, the GUI backup is the old one... it's better to advice people to use the console

agreed ... gonna deploy a new version today ..

[fav]

0.9.3c has two kinds of json files. (1) one from GUI export, (2) one from command line export. You cannot import (1) in Graphene. You should use (2). I am sure 0.9.3d will have identical json files with these two methods.

The purpose of the "c" release was to put the correct backup function into the main menu bar .. However, the windows binaries did not include that patch

correct, the GUI backup is the old one... it's better to advice people to use the console

[xeroc]

0.9.3c has two kinds of json files. (1) one from GUI export, (2) one from command line export. You cannot import (1) in Graphene. You should use (2). I am sure 0.9.3d will have identical json files with these two methods.

The purpose of the "c" release was to put the correct backup function into the main menu bar .. However, the windows binaries did not include that patch

[clayop]

0.9.3c has two kinds of json files. (1) one from GUI export, (2) one from command line export. You cannot import (1) in Graphene. You should use (2). I am sure 0.9.3d will have identical json files with these two methods.

[puppies]

For example, can you import the json file from 0.9.3c into the graphene cli?

I don't know about that particular questions .. but I'll research
[/quote]

You most certainly can import the 0.9.3 json into the cli_wallet.  Use

Code: [Select]

Import_accounts <path to exported json> <password of wallet you exported from>

The issue is that this doesn't automatically claim the balances these keys hold.  They have to be imported one by one (unless this has been updated recently) I think the proper syntax is

Code: [Select]

Import_balance <account name> <private key> true
But I always import my accounts and then use the gui to import my balances cause it's way easier.

[xeroc]

For example, can you import the json file from 0.9.3c into the graphene cli?
[/quote]
I don't know about that particular questions .. but I'll research

[Thom]

I think this page needs far more detail: http://docs.bitshares.eu/migration/howto-importing-wallet.html

For example, can you import the json file from 0.9.3c into the graphene cli?

The export pages is nice with good detail, but the other half needs work.  I made some comments related to this in the testnet thread but nobody addressed those points.

[xeroc]

Bitshares in Windows might need to be started as administrator, if writing to c:/ drive. "wallet_export_keys c:\keys.json"

Thx for the info .. i'll add it to the guide

[xeroc]

What will happen to the 1.0 BTA yield? Will it be distributed at a shot when 2.0 starts?

Very good question .. i have no idea @bytemaster ?

[betax]

Bitshares in Windows might need to be started as administrator, if writing to c:/ drive. "wallet_export_keys c:\keys.json"

[zhangweis]

What will happen to the 1.0 BTA yield? Will it be distributed at a shot when 2.0 starts?

[xeroc]

Hey there,

As some of you already know, I am currently writing some documentation. I would love some input with respect to the
Migration Guide here:
http://docs.bitshares.eu/migration/

In the end, we should have this thing finished a few days before the launch.

Please tell me:
* what is missing
* what needs to be stated more clearly
* how the migration can be made easier for the people to understand
* is everything correct?

Thanks for your input