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.

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.

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.

Quote from: fluxer555 on May 03, 2017, 03:56:08 PM
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?

Can someone please help. I have posted in https://bitsharestalk.org/index.php/topic,24064.0/all.html

I successfully exported the keys.json file but I can't import the keys.json file into 2.0. It's supposed to work as per the Migration.

Quote from: fluxer555 on May 03, 2017, 03:03:05 PM

Quote"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

Quote from: fluxer555 on May 03, 2017, 02:20:04 PM
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.

Quote from: fluxer555 on May 03, 2017, 02:08:33 PM
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.

Quote from: fluxer555 on May 03, 2017, 02:04:45 PM
Here are the non-broken images for you:

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?

Quote from: chryspano on May 03, 2017, 07:29:29 AM

Quote from: bitcoinnoisseur on May 03, 2017, 03:44:44 AM

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/YnkYR

  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/vZxA0


How do I ""reclaim" my old BTS1.0, again through the settings menu."?

Sorry I can't get the images to show.

I am unable to register my 0.9.3c account. I get the following error: "invalid transaction expiration (31011)"

I tried to import my 0.9.3c wallet backup.json into my 2.0 wallet but I get the following error: "Please use a BTS 1.0 wallet_export_keys file instead" But the only way to export a wallet from 0.9.3 is a backup .json file.

I also tried sending BTS from 0.9.3c wallet to my 2.0 wallet and to Bittrex.

When I try to send to my registered 2.0 wallet I get the following error: "Unknown account".
When I try to send to Bittrex I get the following error: "invalid transaction expiration (31011)".

Can someone please explain to me what I have to do?

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

Quote from: Exergy on April 30, 2017, 06:20:10 PM
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)

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 don't grasp that Migration either. All I have is a wallet.dat file from Bitshares-PTS. I don't know how to import it into Bitshares 2.0.

I got the following reply in a different thread:

Quote from: xeroc ¯\_(ツ)_/¯ on February 01, 2015, 09:33:47 PM


There really is no link between your gmail account and the bitshares account .. AFAIK entering a valid mail address is only required as an entropy source for the random passphrase

There is NO association between your bitshares account and your gmail account ..
also note that NO ONE will ever be able to send you your passphrase as it is only stored in your brain .. no where else ..

so please take the backup advises serious

Quote from: xeroc ¯\_(ツ)_/¯ on February 01, 2015, 09:33:47 PM

Quote from: bitcoinnoisseur on February 01, 2015, 08:31:41 PM
I accidentally registered my BitShares wallet under my fathers gmail account as I was using his Mac. I wasn't aware he was signed into Google Chrome. There is also no warning of which gmail account will be registered. I assumed I would have to enter it and the password. I do not want his gmail associated with my BitShares wallet and neither does he. Is there a way to change this and if not, what are the implications? I will have no access to his gmail.

There really is no link between your gmail account and the bitshares account .. AFAIK entering a valid mail address is only required as an entropy source for the random passphrase

There is NO association between your bitshares account and your gmail account ..
also note that NO ONE will ever be able to send you your passphrase as it is only stored in your brain .. no where else ..

so please take the backup advises serious

Thank you and will do.