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.