0 Members and 1 Guest are viewing this topic.
@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 XThose are pretty much the core functionality of any exchange's wallet wrappers, it would be nice to have an example of each
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).
Quote from: sirlo on October 10, 2015, 10:17:23 pmQuote from: jaran on October 10, 2015, 04:29:44 pmQuote from: profitofthegods on October 10, 2015, 11:33:55 amOn Windows 8.1, v0.9.3cI 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 towhether 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 manageone'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!
Quote from: jaran on October 10, 2015, 04:29:44 pmQuote from: profitofthegods on October 10, 2015, 11:33:55 amOn Windows 8.1, v0.9.3cI 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 towhether 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 manageone'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..:-)
Quote from: profitofthegods on October 10, 2015, 11:33:55 amOn Windows 8.1, v0.9.3cI 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...
On Windows 8.1, v0.9.3cI 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.
Thanks alot .. was upgrading the page not having slept after the flight .. I appologize .. I'll take your recommendation ..
Quote from: jakub on October 11, 2015, 02:49:37 pmOn 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
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.
wallet_export_keys keys.json
wallet_export_keys C:/Users/[your user name]/AppData/Roaming/BitShares/keys.json
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.
Quote from: habeler on October 11, 2015, 11:49:07 amI 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
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?
what would happen, if users do not export the wallet keys using the 0.9.3C version before migration deadline ?
This is very frustrating...It almost makes me want to leave my bts on the Exchanges....however they have given no indication as towhether or not they are going to migrate/upgrade..!?
Quote from: sudo on October 10, 2015, 02:10:56 pmyou need to use Code: [Select]wallet_export_keys c:\bts\bts.json contain pathThat works, thanks.
you need to use Code: [Select]wallet_export_keys c:\bts\bts.json contain path
wallet_export_keys c:\bts\bts.json
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.
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/testsudo apt-get update
sudo add-apt-repository ppa:ubuntu-toolchain-r/testsudo apt-get update
Quote from: liondani on October 08, 2015, 07:45:34 amQuote from: sudo on October 08, 2015, 07:39:30 amwhy 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
Quote from: sudo on October 08, 2015, 07:39:30 amwhy 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...
why not fix the GUI backup bug!!!!!!!!!!!!!!!!!!!!
So in a Nutshell:Go to https://bitshares.org/download/ and download BitShares 0.9.3Then, 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)
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.
Exactly my question why not just export your wallet? I have a Mac isn't the export wallet GUI feature sufficient? Quote from: sudo on October 07, 2015, 01:31:48 pmwhy not update 0.9.3cGUI?
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.
Quote from: bitsacer on October 07, 2015, 01:01:57 amOn 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 ..
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.
Quote from: wuyanren on October 05, 2015, 08:51:41 pmQuote from: emailtooaj on October 05, 2015, 08:06:26 pmI'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.JosnThanx 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???
Quote from: emailtooaj on October 05, 2015, 08:06:26 pmI'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
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!!
Quote from: xeroc on October 05, 2015, 10:07:53 amQuote from: fav on October 05, 2015, 09:40:48 amcorrect, the GUI backup is the old one... it's better to advice people to use the consoleagreed ... gonna deploy a new version today ..
Quote from: fav on October 05, 2015, 09:40:48 amcorrect, the GUI backup is the old one... it's better to advice people to use the consoleagreed ... gonna deploy a new version today ..
correct, the GUI backup is the old one... it's better to advice people to use the console
Quote from: clayop on October 05, 2015, 07:04:48 am0.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
For example, can you import the json file from 0.9.3c into the graphene cli?
Import_accounts <path to exported json> <password of wallet you exported from>
Import_balance <account name> <private key> true
Bitshares in Windows might need to be started as administrator, if writing to c:/ drive. "wallet_export_keys c:\keys.json"
What will happen to the 1.0 BTA yield? Will it be distributed at a shot when 2.0 starts?