BitShares Forum
Main => Technical Support => Topic started by: Exergy on April 30, 2017, 05:25:43 pm
-
Hi All,
I've been away from BitShares for a few years.
I had a holding in BitSharesX at the time (2014 this would be).
I'm struggling to understand the history of what has happened since then and when I import my original wallet I seem to have zero balance.
Are BTSX no longer accessible / irrelevant?
Thanks All
-
Ok I figured it out. For the benefit of others - As far as I can tell, BitSharesX were renamed to just BitShares, so they are effectively the same thing.
Further complicating things, Bitshares 1.0 (which is what BitSharesX became) was upgraded to BitShares 2.0 and Wallet files are incompatible - looks like it is a whole new blockchain in fact.
My issue was that my backups were from 0.4.27.2 which is incompatible with the last version of the original BitShares 0.9.3.c.
So first, I had to download 0.4.27.2, import my wallet files, then install 0.9.3c on top.
Within 0.9.3c, I then had to export my private keys using the console command wallet_export_keys (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client (http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client))
This then gave me a json file of my keys which I could import into the new Bitshares 2.0 client, via the settings menu.
Once imported, I then had to "reclaim" my old BTS1.0, again through the settings menu.
Finally, I can see my original holding.
Hope this helps someone.
-
Ok I figured it out. For the benefit of others - As far as I can tell, BitSharesX were renamed to just BitShares, so they are effectively the same thing.
Further complicating things, Bitshares 1.0 (which is what BitSharesX became) was upgraded to BitShares 2.0 and Wallet files are incompatible - looks like it is a whole new blockchain in fact.
My issue was that my backups were from 0.4.27.2 which is incompatible with the last version of the original BitShares 0.9.3.c.
So first, I had to download 0.4.27.2, import my wallet files, then install 0.9.3c on top.
Within 0.9.3c, I then had to export my private keys using the console command wallet_export_keys (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client (http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client))
This then gave me a json file of my keys which I could import into the new Bitshares 2.0 client, via the settings menu.
Once imported, I then had to "reclaim" my old BTS1.0, again through the settings menu.
Finally, I can see my original holding.
Hope this helps someone.
A nobel example of determination to overcome adversity!
-
You figured that out quick. You should make a tutorial of what you did.
-
I was heavily incentivised by the recent pump :)
-
Ok I figured it out. For the benefit of others - As far as I can tell, BitSharesX were renamed to just BitShares, so they are effectively the same thing.
Further complicating things, Bitshares 1.0 (which is what BitSharesX became) was upgraded to BitShares 2.0 and Wallet files are incompatible - looks like it is a whole new blockchain in fact.
My issue was that my backups were from 0.4.27.2 which is incompatible with the last version of the original BitShares 0.9.3.c.
So first, I had to download 0.4.27.2, import my wallet files, then install 0.9.3c on top.
Within 0.9.3c, I then had to export my private keys using the console command wallet_export_keys (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client (http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client))
This then gave me a json file of my keys which I could import into the new Bitshares 2.0 client, via the settings menu.
Once imported, I then had to "reclaim" my old BTS1.0, again through the settings menu.
Finally, I can see my original holding.
Hope this helps someone.
I tried (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client).
When I clicked enter I got the following message: ">> wallet_export_keys C:\Users\My Name\Desktop\keys.json OK.
However no file was created on my computer. Did you have to do anything different?
-
I tried (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client).
When I clicked enter I got the following message: ">> wallet_export_keys C:\Users\My Name\Desktop\keys.json OK.
However no file was created on my computer. Did you have to do anything different?
send me your private keys?
;D
-
I tried (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client).
When I clicked enter I got the following message: ">> wallet_export_keys C:\Users\My Name\Desktop\keys.json OK.
However no file was created on my computer. Did you have to do anything different?
Maybe try to run the wallet as administrator
-
I tried (see http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html#bitshares-1-0-full-client).
When I clicked enter I got the following message: ">> wallet_export_keys C:\Users\My Name\Desktop\keys.json OK.
However no file was created on my computer. Did you have to do anything different?
Maybe try to run the wallet as administrator
I ran as an administrator and I think I was able to import keys.json. I don't know what to do now.
Here are screenshots of what happens:
(http://imgur.com/a/cBinl) http://imgur.com/a/cBinl
(http://imgur.com/a/YnkYR) http://imgur.com/a/YnkYR
(http://imgur.com/a/7fndZ) http://imgur.com/a/7fndZ
When I go to my account and click on View
Keys this happens:
(http://imgur.com/a/6dlQv) http://imgur.com/a/6dlQv
(http://imgur.com/a/vZxA0) http://imgur.com/a/vZxA0
How do I ""reclaim" my old BTS1.0, again through the settings menu."?
Sorry I can't get the images to show.
-
Here are the non-broken images for you:
(http://i.imgur.com/j3jbcIj.png)
(http://i.imgur.com/TnHk0sm.png)
(http://i.imgur.com/Ahe68Rd.png)
(http://i.imgur.com/fupozVQ.png)
(http://i.imgur.com/JxxaLq4.png)
-
This looks like a bug in the latest wallet.
-
Here are the non-broken images for you:
(http://i.imgur.com/j3jbcIj.png)
(http://i.imgur.com/TnHk0sm.png)
(http://i.imgur.com/Ahe68Rd.png)
(http://i.imgur.com/fupozVQ.png)
(http://i.imgur.com/JxxaLq4.png)
Thank you. You beat me to it.
I read in another thread that you "recently had to jump through a bunch of hoops in order to upgrade to 2.0 from my old 1.0 backup"
Can you help me?
-
This looks like a bug in the latest wallet.
Didn't you use the same version? How did the migration work for you? And what did you have to do after importing the keys?
I would really appreciate any help you can give me. Thank you.
-
You're basically there already. I don't know why the 2.0 wallet isn't importing your funds, and giving that TypeError.
My best guess right now would be to rescan your wallet in 0.9.3c, then re-export the keys, and try importing them again.
I found old documentation by using archive.org that helped me. Here is the info (converted to GitHub markdown):
https://gist.github.com/flux627/f16ad0daf02c3fe7fe58ce9d39b753ee
In my case, I had to do everything here except the last step (wallet_recover_transaction)
-
You're basically there already. I don't know why the 2.0 wallet isn't importing your funds, and giving that TypeError.
My best guess right now would be to rescan your wallet in 0.9.3c, then re-export the keys, and try importing them again.
I found old documentation by using archive.org that helped me. Here is the info (converted to GitHub markdown):
https://gist.github.com/flux627/f16ad0daf02c3fe7fe58ce9d39b753ee
In my case, I had to do everything here except the last step (wallet_recover_transaction)
I tried to follow but am very confused using the console. I have never used any console before yesterday.
When I tried to "rescan" I got the OK but when I entered "getinfo" I did not get The relevant return line is "wallet_scan_progress". I got this:
{
"blockchain_head_block_num": 1356229,
"blockchain_head_block_age": "2 years 4 months old",
"blockchain_head_block_timestamp": "2014-12-26T05:30:20",
"blockchain_head_block_id": "c0187a684f9a5348a938b726ab74a5715fc09890",
"blockchain_average_delegate_participation": "0.00 %",
"blockchain_share_supply": "2,498,586,471.66562 BTS",
"blockchain_blocks_left_in_round": 100,
"blockchain_next_round_time": "at least 17 minutes in the future",
"blockchain_next_round_timestamp": "2017-05-03T14:58:30",
"blockchain_random_seed": "7751a26e03131e6ebed7a8bd28348f11c9df89d5",
"client_data_dir": "C:/Users/My Name/AppData/Roaming/BitShares",
"client_version": "0.9.3c",
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2017-05-03T14:41:52",
"ntp_time_error": "0.654131000000",
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2017-05-15T04:25:57",
"wallet_last_scanned_block_timestamp": "2014-08-11T01:39:10",
"wallet_scan_progress": "3.51 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
I also noted there is this function: wallet_rescan_blockchain [start_block_num] [limit] [scan_in_background]. I don't know if I need to use that instead of just "rescan" but I don't know what parameters to use if I did.
I have tried to re-export the keys but it says the file already exists even if I change the name to keys2.json.
I don't understand why this is so difficult. I know I am so close.
-
"wallet_scan_progress": "3.51 %",
You'll have to wait now. You may have to wait after each step. It's what I did, find a book to read or some other activity, it took me about an hour each time :)
-
"wallet_scan_progress": "3.51 %",
You'll have to wait now. You may have to wait after each step. It's what I did, find a book to read or some other activity, it took me about an hour each time :)
The scanning is complete. Don't know what to do next.
Do I have to have the account registered? I was only able to register the 2.0 wallet.
I don't understand what this means: "If the scan is complete (100%) and you funds are not back yet please proceed to the next step." My funds were there to begin with. Do I have to check something else before trying to export the .json again? Do I need to delete the .json that I wasn't able to import in to 2.0? I always get a file already exists message.
I apologize for asking so many questions but I truly don't know what else to do.
I got this message after trying to recover accounts: >> wallet_recover_accounts 10
0
-
if you got "0" from recover accounts, that means there were no addition accounts recovered. That's ok. Run "wallet_regenerate_keys ACCOUNT-NAME 1000" (with ACCOUNT-NAME replaced with your account name), let it rescan again, and then try exporting the wallet.
I don't know why it would say it already exists. Sounds like it may be a bug. Make sure that you have permissions to write to where you want to save it (maybe need to run wallet as administrator as others have said).
-
Check the filesize of the wallet that failed to import, then check the filesize of the newly exported wallet. If they are different, then that means the content changed, and you should try re-importing it into the 2.0 wallet.
-
if you got "0" from recover accounts, that means there were no addition accounts recovered. That's ok. Run "wallet_regenerate_keys ACCOUNT-NAME 1000" (with ACCOUNT-NAME replaced with your account name), let it rescan again, and then try exporting the wallet.
I don't know why it would say it already exists. Sounds like it may be a bug. Make sure that you have permissions to write to where you want to save it (maybe need to run wallet as administrator as others have said).
I received this message: >> wallet_regenerate_keys bitcoinnoisseur-2 1000
4000
What does 4000 mean?
I am rescanning. I have been running as administrator. Is it a problem that my acct isn't registered? Do I need to delete the keys.json I created before trying to export it again?
-
PROBLEM SOLVED
fluxer555 and I worked yesterday and today to recover all my BTS plus some extra I was unaware of. He was relentless in his pursuit to solve all the problems I had and there were many. If anyone has any problems with moving their BTS from old outdated wallets to 2.0 then fluxer555 is your man. He is super knowledgeable and super easy to work with. I chose to compensate him very well for all the great work he did. It was well worth it.
-
Glad you got it resolved.
I actually think I had the same error as you when I initially tried to recover my funds, but I tried again and it didn't happen the second time - seems yours wasn't so simple!
-
Is anyone seeding the 0.9.3.c. chain data? There is a torrent link in the documentation but there don't seem to be any peers seeding it. Any other options for getting the full 0.9.3.c. chain?
-
this is what I was referring to:
http://docs.bitshares.eu/bitshares/migration/legacy-blockchain.html
-
Check your PMs blahblah7up
-
I have never imported my files from Genesis. I do have the private keys from my BTC wallet that i used to donate in angel shares. It kept saying import successful but there is 0 balance. I did try the look up balance but it did not work as well.