Importing Keys into Graphene

[svk]

Well, I finally got my accounts imported. 8 days of trying and trying and trying.
thanks to @Chryspano in  https://bitsharestalk.org/index.php/topic,19299.0.html for the proper syntax
and http://docs.bitshares.eu/migration/howto-importing-wallet.html for the importing balances syntax

my 55000 keys only took up 500mb in the back ups.

SYNTAX SYNTAX SYNTAX seems to be the key with this process. I think the key to easier implementation would be a wiki for the cli that has the exact syntax need to execute commands.

We have a tool in development that will filter your keys from BTS 1 in order to only keep the ones that are actually relevant for BTS 2. This will make your json file much smaller, import time shorter, and reduce the time it takes to open the wallet afterwards (you may have noticed longer initial loads after importing that wallet, that definitely happened for me).

This tool just needs some testing, I'll be trying it out on my main wallet which has 95,000 keys and that I've not been able to import yet.

[JWF]

Well, I finally got my accounts imported. 8 days of trying and trying and trying.
thanks to @Chryspano in  https://bitsharestalk.org/index.php/topic,19299.0.html for the proper syntax
and http://docs.bitshares.eu/migration/howto-importing-wallet.html for the importing balances syntax

my 55000 keys only took up 500mb in the back ups.

SYNTAX SYNTAX SYNTAX seems to be the key with this process. I think the key to easier implementation would be a wiki for the cli that has the exact syntax need to execute commands.

[EstefanTT]

Here is an official statement for anyone having problem importing into the 2.0.

We just need to be a little more patient. It's taking care of

http://bitsharestalk.org/index.php?topic=19243.msg248294.msg#248294

[BunkerChainLabs-DataSecurityNode]

Want everyone to know I finally managed to get access to my accounts today.. I will be posting a full step by step tonight... I could not use openledger in the end though.

curious how many keys you had to import. I've 55000 and I have yet to get my balances to show in the light wallet. I started this import attempt at 8:35am this morning at block 57050 and still nothing now 6 hours later at block 64250. This shouldn't just be a problem I'm having as there must be others with large numbers of keys.

I'm dumb... just actually looked at above posts...

so I'm curious to see what it took for you.

This article tells how to import large wallets:

https://github.com/bitshares/bitshares-2/wiki/Import%20BitShares-0.9.3c%20wallets%20into%20BitShares%202.0%20CLI%20wallet

It was linked to right from the release docs here:

https://github.com/bitshares/bitshares-2/releases

Unfortunately it requires a user to be savvy enough to compile the CLI wallet OR use windows CLI tools.

I wish I had time to go step by step but its going on 3am now and I need some sleep.. ug.. not enough time in a day.

In addition to what BM shared there is something else you need to do, you need to setup a cronjob that will delete files every minute, or have a MASSIVE hard drive to handle all the backup files that will be generated. My import generated well over 1TB in backup files being created, which filled my drive until I figured out that the filling up was happening at a rate of approximately 4GB per minute.

So follow the instructions BM gives, but then setup something like this in your Ubuntu 14.04 CLI:

Code: [Select]

crontab -e
Select 2
* * * * * rm -rf /ubuntu_user/bitshares-2/programs/cli_wallet/before-import-key-*
crtl-x
then proceed to import the accounts as the instructions provide.

You need a full node setup to do this, and there is some information available on how to do that here: http://docs.bitshares.eu/installation/Build.html#ubuntu-14-04
http://docs.bitshares.eu/apps/Witness.html << Full Node

There is something confusing me a bit though.. and maybe someone can clarify for me.

I managed to get one account out of my wallet to import into openledger and I was able to claim my balances from open ledger.. but now in my wallet on my full node I have that same account that imported successfully. I am able to view the same account both on my full node as well as on openledger. Even my recent activity on my full node showed up on openledger.. I know there is no backup yet for full node wallet.. but can accounts exist like this in multiple places in the network or is there something bad that can happen? Or could running accounts like this cause network issues?

[tbone]

another question: I originally logged into the wallet from my Chrome browser, where I can see the top menu items ACCOUNT, EXPLORER, EXCHANGE and TRANSFER. Then I tried to open the wallet from a different browser, expecting to get a login challenge. Instead, if I go to my wallet link in Firefox (  https://graphene.bitshares.org/#/account/werneo/overview )  I can see everything in the wallet with the exception of the top menu choices.  There is also a NEW menu item called LINK/UNLINK in the sidebar of firefox. Not sure what that does. So does this mean that everyone's wallet is viewable so long as the user name is known?

Yes, until we get support for blinded transactions all balances and transactions will be visible to everyone.

Also, wallets are per browser, so if you create a wallet in Chrome you cannot access that wallet in Firefox unless you export it from Chrome then import it in Firefox.

What if you want to move the Chrome wallet to Firefox but already have a wallet in Firefox?  Assuming you don't want or need the Firefox wallet, can the Chrome wallet overwrite it or does it have to be removed first?

[speedy]

I am getting this when I try to start the cli_wallet:

Code: [Select]

Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2219225ms th_a       main.cpp:160                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:436 fc::http::detail::websocket_client_impl::{ctor}::<lambda_a9259faf4b61f0851fe6641174ca8528>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:621 fc::http::websocket_client::connect
Is this something I am doing wrong?

Is your witness up and running (guess)?

I get this no matter what. with or without witness or light wallet open. may try wiping everything again and start with a fresh install of the cli tools

Did you run you witness_node with --rpc-server="127.0.0.1:8090" ?

yes, I have it run with the --rpc-server="127.0.0.1:8090" but still get the same error from the cli. the witness node is current to recent block from what it says

I setup my witness node's rpc-endpoint setting by editing config.ini:
http://docs.bitshares.eu/apps/Witness.html

[JWF]

I am getting this when I try to start the cli_wallet:

Code: [Select]

Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2219225ms th_a       main.cpp:160                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:436 fc::http::detail::websocket_client_impl::{ctor}::<lambda_a9259faf4b61f0851fe6641174ca8528>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:621 fc::http::websocket_client::connect
Is this something I am doing wrong?

Is your witness up and running (guess)?

I get this no matter what. with or without witness or light wallet open. may try wiping everything again and start with a fresh install of the cli tools

Did you run you witness_node with --rpc-server="127.0.0.1:8090" ?

yes, I have it run with the --rpc-server="127.0.0.1:8090" but still get the same error from the cli. the witness node is current to recent block from what it says

[bytemaster]

I am getting this when I try to start the cli_wallet:

Code: [Select]

Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2219225ms th_a       main.cpp:160                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:436 fc::http::detail::websocket_client_impl::{ctor}::<lambda_a9259faf4b61f0851fe6641174ca8528>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:621 fc::http::websocket_client::connect
Is this something I am doing wrong?

Is your witness up and running (guess)?

I get this no matter what. with or without witness or light wallet open. may try wiping everything again and start with a fresh install of the cli tools

Did you run you witness_node with --rpc-server="127.0.0.1:8090" ?

[JWF]

I am getting this when I try to start the cli_wallet:

Code: [Select]

Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2219225ms th_a       main.cpp:160                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:436 fc::http::detail::websocket_client_impl::{ctor}::<lambda_a9259faf4b61f0851fe6641174ca8528>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:621 fc::http::websocket_client::connect
Is this something I am doing wrong?

Is your witness up and running (guess)?

I get this no matter what. with or without witness or light wallet open. may try wiping everything again and start with a fresh install of the cli tools

[speedy]

I am getting this when I try to start the cli_wallet:

Code: [Select]

Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2219225ms th_a       main.cpp:160                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:436 fc::http::detail::websocket_client_impl::{ctor}::<lambda_a9259faf4b61f0851fe6641174ca8528>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:621 fc::http::websocket_client::connect
Is this something I am doing wrong?

Is your witness up and running (guess)?

[speedy]

I guess I also need to know what T is.  Can post the full error?

Here you go (T = fc::stringstream::impl):

Code: [Select]

[ 22%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/io/sstream.cpp.o
In file included from home/me/source/bitshares/libraries/fc/src/io/sstream.cpp:2:0:
home/me/source/bitshares/libraries/fc/include/fc/fwd_impl.hpp: In instantiation of ‘void fc::check_size() [with long unsigned int RequiredSize = 392ul; long unsigned int ProvidedSize = 368ul]’:
home/me/source/bitshares/libraries/fc/include/fc/fwd_impl.hpp:63:43:   required from ‘fc::fwd<T, S, Align>::fwd(U&&) [with U = std::__cxx11::basic_string<char>&; T = fc::stringstream::impl; unsigned int S = 368u; Align = double]’
home/me/source/bitshares/libraries/fc/src/io/sstream.cpp:24:8:   required from here
home/me/source/bitshares/libraries/fc/include/fc/fwd_impl.hpp:58:25: error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
     void check_size() { static_assert( (ProvidedSize >= RequiredSize), "Failed to reserve enough space in fc::fwd<T,S>" ); }
                         ^
libraries/fc/CMakeFiles/fc.dir/build.make:583: recipe for target 'libraries/fc/CMakeFiles/fc.dir/src/io/sstream.cpp.o' failed

Thanks BM!

[JWF]

Want everyone to know I finally managed to get access to my accounts today.. I will be posting a full step by step tonight... I could not use openledger in the end though.

curious how many keys you had to import. I've 55000 and I have yet to get my balances to show in the light wallet. I started this import attempt at 8:35am this morning at block 57050 and still nothing now 6 hours later at block 64250. This shouldn't just be a problem I'm having as there must be others with large numbers of keys.

I'm dumb... just actually looked at above posts...

so I'm curious to see what it took for you.

This article tells how to import large wallets:

https://github.com/bitshares/bitshares-2/wiki/Import%20BitShares-0.9.3c%20wallets%20into%20BitShares%202.0%20CLI%20wallet

It was linked to right from the release docs here:

https://github.com/bitshares/bitshares-2/releases

Unfortunately it requires a user to be savvy enough to compile the CLI wallet OR use windows CLI tools.

I am getting this when I try to start the cli_wallet:

Code: [Select]

Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2219225ms th_a       main.cpp:160                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:436 fc::http::detail::websocket_client_impl::{ctor}::<lambda_a9259faf4b61f0851fe6641174ca8528>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:621 fc::http::websocket_client::connect
Is this something I am doing wrong?

[bytemaster]

Im trying to compile tag bts/0.9.3d so that I can export my wallet backup to Graphene, but FC is failing to compile:

Code: [Select]

/home//source/bitshares/libraries/fc/include/fc/fwd_impl.hpp:58:25: error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
     void check_size() { static_assert( (ProvidedSize >= RequiredSize), "Failed to reserve enough space in fc::fwd<T,S>" ); }
Any ideas?

Yeah, it looks like you are using a new version of GCC.   Try installing a slightly older version or using CLANG.     If you can tell me what the RequiredSize was (should be in the extended error message) then I can update FC to make it work for you.

Lol I upgraded my distro to compile Graphene

Here is the extended error message with the RequiredSize:

Code: [Select]

/home/source/bitshares/libraries/fc/include/fc/fwd_impl.hpp: In instantiation of ‘void fc::check_size() [with long unsigned int RequiredSize = 392ul; long unsigned int ProvidedSize = 368ul]’:

I guess I also need to know what T is.  Can post the full error?

[speedy]

Im trying to compile tag bts/0.9.3d so that I can export my wallet backup to Graphene, but FC is failing to compile:

Code: [Select]

/home//source/bitshares/libraries/fc/include/fc/fwd_impl.hpp:58:25: error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
     void check_size() { static_assert( (ProvidedSize >= RequiredSize), "Failed to reserve enough space in fc::fwd<T,S>" ); }
Any ideas?

Yeah, it looks like you are using a new version of GCC.   Try installing a slightly older version or using CLANG.     If you can tell me what the RequiredSize was (should be in the extended error message) then I can update FC to make it work for you.

Lol I upgraded my distro to compile Graphene

Here is the extended error message with the RequiredSize:

Code: [Select]

/home/source/bitshares/libraries/fc/include/fc/fwd_impl.hpp: In instantiation of ‘void fc::check_size() [with long unsigned int RequiredSize = 392ul; long unsigned int ProvidedSize = 368ul]’:

[bytemaster]

Want everyone to know I finally managed to get access to my accounts today.. I will be posting a full step by step tonight... I could not use openledger in the end though.

curious how many keys you had to import. I've 55000 and I have yet to get my balances to show in the light wallet. I started this import attempt at 8:35am this morning at block 57050 and still nothing now 6 hours later at block 64250. This shouldn't just be a problem I'm having as there must be others with large numbers of keys.

I'm dumb... just actually looked at above posts...

so I'm curious to see what it took for you.

This article tells how to import large wallets:

https://github.com/bitshares/bitshares-2/wiki/Import%20BitShares-0.9.3c%20wallets%20into%20BitShares%202.0%20CLI%20wallet

It was linked to right from the release docs here:

https://github.com/bitshares/bitshares-2/releases

Unfortunately it requires a user to be savvy enough to compile the CLI wallet OR use windows CLI tools.

[bytemaster]

Im trying to compile tag bts/0.9.3d so that I can export my wallet backup to Graphene, but FC is failing to compile:

Code: [Select]

/home//source/bitshares/libraries/fc/include/fc/fwd_impl.hpp:58:25: error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
     void check_size() { static_assert( (ProvidedSize >= RequiredSize), "Failed to reserve enough space in fc::fwd<T,S>" ); }
Any ideas?

Yeah, it looks like you are using a new version of GCC.   Try installing a slightly older version or using CLANG.     If you can tell me what the RequiredSize was (should be in the extended error message) then I can update FC to make it work for you.

[speedy]

Im trying to compile tag bts/0.9.3d so that I can export my wallet backup to Graphene, but FC is failing to compile:

Code: [Select]

/home//source/bitshares/libraries/fc/include/fc/fwd_impl.hpp:58:25: error: static assertion failed: Failed to reserve enough space in fc::fwd<T,S>
     void check_size() { static_assert( (ProvidedSize >= RequiredSize), "Failed to reserve enough space in fc::fwd<T,S>" ); }
Any ideas?

[JWF]

Want everyone to know I finally managed to get access to my accounts today.. I will be posting a full step by step tonight... I could not use openledger in the end though.

curious how many keys you had to import. I've 55000 and I have yet to get my balances to show in the light wallet. I started this import attempt at 8:35am this morning at block 57050 and still nothing now 6 hours later at block 64250. This shouldn't just be a problem I'm having as there must be others with large numbers of keys.

I'm dumb... just actually looked at above posts...

so I'm curious to see what it took for you.

[BunkerChainLabs-DataSecurityNode]

Want everyone to know I finally managed to get access to my accounts today.. I will be posting a full step by step tonight... I could not use openledger in the end though.

[svk]

We are aware of it for sure, James is the main man on this subject though and he's been travelling today.

Now I have an idea, not sure it'll work or not, but assuming the encrypted private keys and public keys are all in order in the json file, wouldn't it be possible to split the file into several smaller json files? That way you could import 1/10 of your keys at a time for example?

And if you have several different accounts in one file then I'm fairly certain you could separate them and make one file per account, just keep the password checksum at the top for each file.

@xeroc does that make sense?

[EstefanTT]

I'm still having a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)" in the light client. It seems that it can't finished the process of importing the keys or balances,

It seems that I won't be able to veify that that keys.json work properly and I'm able to import my balances correctely before 2.0.

Are we the only ones with Xeldal to have this issue ? Is that gonna be solve when we launch the 2.0 ? Do I have to worry (more) ?

I guess the issue here is that your old wallets have a ton of keys, maybe because you've been trading. We used to display the number of keys in a wallet, is that still there? I remember trying my main wallet and it had 95k keys, it took a while to import but got there in the end.

Maybe the easiest solution for you is to simply transfer your balances to another account with less keys before the snapshot, then import that instead. I assume you could import the private key only from the account with too many keys in order to regain control of it in 2.0, but not 100% sure on that.

I am not clear what you mean here.. but I am having a similar problem where all my accounts are over 30k in private keys. the import function finally gets through them all to display them.. but when I attempt to import it times out. To make matters worse, when I do see the list of account to import I see this at the end:

Unclaimed balances belonging to these keys:
ASSET TOTALS
No Balances

Which is wrong.

Every single active account I have is like this.. I cannot import into a regular wallet or into a witness wallet with CLI.

What can be done to make this work?

This is just a small sample below of all the accounts in the wallet.. which is why the private keys dont add up to what is shown in the image.

I have the exact same problem in two different computers with two different set of accounts and different keys.json

I found in the forum threads several persons in the same situation but no solution. Is this beeing solved by the devs or are they aware of it ?

[svk]

James is looking into it

https://github.com/cryptonomex/graphene-ui/issues/319

[BunkerChainLabs-DataSecurityNode]

Yea so you have 130k keys and I guess your computer isn't fast enough to finish the import in a reasonable time. The solution I outlined should work but hopefully someone like @jcalfee or @bytemaster could confirm that.

I did suggest to James at one point that he could use web workers for the number crunching, might be time to look into that as well in order to use more cores.

Well.. I attempted to import my wallet into a testnet witness node .. the problem I had though is that my drive space kept on filling up with the backup wallet data before it could finish.

I ended up setting up a cron job to delete the files every minute while the import proceeded.

It has now been 3 1/2 hours and it has deleted well over 1TB in backup files as the import has proceeded. This all came out of a 22mb wallet_export_keys json file for about 14 accounts.

It'st still processing.. so we'll see if it works in the end.

If I am having this much processing going on for my wallet others might have similar trouble.

Ouch! I didn't know it wrote backups like that, but you're right, most likely lots of people will have issues like this. I'm scared to import my delegate wallet now, after all those feed transactions it must have tons of keys too.

I'll make sure James sees this thread since he's the one writing all the wallet and key handling code.

It ran for another hour.. at the end of the process these were some of the final messages I had on my screen:

Code: [Select]

1554884ms th_a       wallet.cpp:2650               import_accounts      ] successfully imported 37518 keys for account payment.datasecuritynode-com
1554884ms th_a       wallet.cpp:2646               import_accounts      ] Couldn't import key due to exception 18 aes_exception: AES error
error during aes 256 cbc decrypt final
    {"s":"error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length"}
    th_a  aes.cpp:263 aes_decrypt
1554885ms th_a       wallet.cpp:438                copy_wallet_file     ] backing up wallet test6 to before-import-key-3c4b00c1.wallet
1555347ms th_a       wallet.cpp:727                save_wallet_file     ] saving wallet to file test6
1559695ms th_a       wallet.cpp:438                copy_wallet_file     ] backing up wallet test6 to after-import-key-3c4b00c1.wallet
1559719ms th_a       wallet.cpp:2650               import_accounts      ] successfully imported 1 keys for account start-now
1559719ms th_a       wallet.cpp:2652               import_accounts      ] failed to import 1 keys for account start-now
1559721ms th_a       wallet.cpp:438                copy_wallet_file     ] backing up wallet test6 to before-import-key-ac40e213.wallet
1559862ms th_a       wallet.cpp:727                save_wallet_file     ] saving wallet to file test6
1563951ms th_a       wallet.cpp:438                copy_wallet_file     ] backing up wallet test6 to after-import-key-ac40e213.wallet
1563978ms th_a       wallet.cpp:2646               import_accounts      ] Couldn't import key due to exception 18 aes_exception: AES error
error during aes 256 cbc decrypt final
    {"s":"error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length"}
    th_a  aes.cpp:263 aes_decrypt
1563979ms th_a       wallet.cpp:2650               import_accounts      ] successfully imported 1 keys for account starts-now
1563979ms th_a       wallet.cpp:2652               import_accounts      ] failed to import 1 keys for account starts-now
[[
    "",
    false
  ],[
    "bitshares-ca",
    true
  ],[
    "bunkermining",
    true
  ],[
It looks as though some did not work while others did.

This is a bit concerning now.

The reason I went this route is because of the tens of thousands of keys I couldn't follow the regular procedure of pulling the owner keys and then getting the balance keys etc because I have no idea out of the 30k+ keys to an account which one actually has the balance. I know that xeroc has a python script to help find this..but that is only good if you are running linux.. this is with the windows client.

The few that appear to have worked in importing when I did a dump_private_keys command actually spit out all 30K or so keys back at me. So it seems like all that bloat is just getting dumped back in. Couldn't the process perhaps check for balances and then import with only those keys?

[svk]

Yea so you have 130k keys and I guess your computer isn't fast enough to finish the import in a reasonable time. The solution I outlined should work but hopefully someone like @jcalfee or @bytemaster could confirm that.

I did suggest to James at one point that he could use web workers for the number crunching, might be time to look into that as well in order to use more cores.

Well.. I attempted to import my wallet into a testnet witness node .. the problem I had though is that my drive space kept on filling up with the backup wallet data before it could finish.

I ended up setting up a cron job to delete the files every minute while the import proceeded.

It has now been 3 1/2 hours and it has deleted well over 1TB in backup files as the import has proceeded. This all came out of a 22mb wallet_export_keys json file for about 14 accounts.

It'st still processing.. so we'll see if it works in the end.

If I am having this much processing going on for my wallet others might have similar trouble.

Ouch! I didn't know it wrote backups like that, but you're right, most likely lots of people will have issues like this. I'm scared to import my delegate wallet now, after all those feed transactions it must have tons of keys too.

I'll make sure James sees this thread since he's the one writing all the wallet and key handling code.

[BunkerChainLabs-DataSecurityNode]

Yea so you have 130k keys and I guess your computer isn't fast enough to finish the import in a reasonable time. The solution I outlined should work but hopefully someone like @jcalfee or @bytemaster could confirm that.

I did suggest to James at one point that he could use web workers for the number crunching, might be time to look into that as well in order to use more cores.

Well.. I attempted to import my wallet into a testnet witness node .. the problem I had though is that my drive space kept on filling up with the backup wallet data before it could finish.

I ended up setting up a cron job to delete the files every minute while the import proceeded.

It has now been 3 1/2 hours and it has deleted well over 1TB in backup files as the import has proceeded. This all came out of a 22mb wallet_export_keys json file for about 14 accounts.

It'st still processing.. so we'll see if it works in the end.

If I am having this much processing going on for my wallet others might have similar trouble.

[Pheonike]

You gonna need to max out the specs on the VPS machines for the web wallets. They are going be doing lot of crunching when everyone is importing their wallets for the launch.  Or least have some kind of progress indicator so ppl want assume it has stalled.

[svk]

Yea so you have 130k keys and I guess your computer isn't fast enough to finish the import in a reasonable time. The solution I outlined should work but hopefully someone like @jcalfee or @bytemaster could confirm that.

I did suggest to James at one point that he could use web workers for the number crunching, might be time to look into that as well in order to use more cores.

[BunkerChainLabs-DataSecurityNode]

I'm still having a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)" in the light client. It seems that it can't finished the process of importing the keys or balances,

It seems that I won't be able to veify that that keys.json work properly and I'm able to import my balances correctely before 2.0.

Are we the only ones with Xeldal to have this issue ? Is that gonna be solve when we launch the 2.0 ? Do I have to worry (more) ?

I guess the issue here is that your old wallets have a ton of keys, maybe because you've been trading. We used to display the number of keys in a wallet, is that still there? I remember trying my main wallet and it had 95k keys, it took a while to import but got there in the end.

Maybe the easiest solution for you is to simply transfer your balances to another account with less keys before the snapshot, then import that instead. I assume you could import the private key only from the account with too many keys in order to regain control of it in 2.0, but not 100% sure on that.

I am not clear what you mean here.. but I am having a similar problem where all my accounts are over 30k in private keys. the import function finally gets through them all to display them.. but when I attempt to import it times out. To make matters worse, when I do see the list of account to import I see this at the end:

Unclaimed balances belonging to these keys:
ASSET TOTALS
No Balances

Which is wrong.

Every single active account I have is like this.. I cannot import into a regular wallet or into a witness wallet with CLI.

What can be done to make this work?

This is just a small sample below of all the accounts in the wallet.. which is why the private keys dont add up to what is shown in the image.

[svk]

I'm still having a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)" in the light client. It seems that it can't finished the process of importing the keys or balances,

It seems that I won't be able to veify that that keys.json work properly and I'm able to import my balances correctely before 2.0.

Are we the only ones with Xeldal to have this issue ? Is that gonna be solve when we launch the 2.0 ? Do I have to worry (more) ?

I guess the issue here is that your old wallets have a ton of keys, maybe because you've been trading. We used to display the number of keys in a wallet, is that still there? I remember trying my main wallet and it had 95k keys, it took a while to import but got there in the end.

Maybe the easiest solution for you is to simply transfer your balances to another account with less keys before the snapshot, then import that instead. I assume you could import the private key only from the account with too many keys in order to regain control of it in 2.0, but not 100% sure on that.

[EstefanTT]

I'm still having a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)" in the light client. It seems that it can't finished the process of importing the keys or balances,

It seems that I won't be able to veify that that keys.json work properly and I'm able to import my balances correctely before 2.0.

Are we the only ones with Xeldal to have this issue ? Is that gonna be solve when we launch the 2.0 ? Do I have to worry (more) ?

[EstefanTT]

Is the backup file necessary ? I read earlier in one thread that it doesn't work and the better way to do it was to create a new wallet and import the keys.json in it.

Right, I only listed for reference.  keys.json is what you need.

Ok, cool. I'll wait to see if it ends working. Tell me if it works for you

[Xeldal]

Is the backup file necessary ? I read earlier in one thread that it doesn't work and the better way to do it was to create a new wallet and import the keys.json in it.

Right, I only listed for reference.  keys.json is what you need.

[EstefanTT]

Hey guys,

I finally could get the keys.json (from 0.09.3c through the console / windows 10) and I tried to import it in the light (destop client).

I created a new wallet and imported the keys,json file. After a while I coudl see my balances and I hit the "import" button.

I had a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)". I wait for hours and finally close the client.

I tried through the browser client but it told me me that I couldn't import because "this wallet have already beel imported".

So, I came back to the desktop light client, went through the steps to import, saw my balances, click on "import" and I am stuck again with the "Wallet Management Console - Importing Keys (waiting gif icon spinning)"

Did I do something wrong or missed something in the process ?

I have the same experience.  I've let it sit for over 24 hrs and still nothing.  My keys.json file is over 15MB. backup.json is over 530MB

Is the backup file necessary ? I read earlier in one thread that it doesn't work and the better way to do it was to create a new wallet and import the keys.json in it.

[Xeldal]

Hey guys,

I finally could get the keys.json (from 0.09.3c through the console / windows 10) and I tried to import it in the light (destop client).

I created a new wallet and imported the keys,json file. After a while I coudl see my balances and I hit the "import" button.

I had a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)". I wait for hours and finally close the client.

I tried through the browser client but it told me me that I couldn't import because "this wallet have already beel imported".

So, I came back to the desktop light client, went through the steps to import, saw my balances, click on "import" and I am stuck again with the "Wallet Management Console - Importing Keys (waiting gif icon spinning)"

Did I do something wrong or missed something in the process ?

I have the same experience.  I've let it sit for over 24 hrs and still nothing.  My keys.json file is over 15MB. backup.json is over 530MB

[EstefanTT]

Hey guys,

I finally could get the keys.json (from 0.09.3c through the console / windows 10) and I tried to import it in the light (destop client).

I created a new wallet and imported the keys,json file. After a while I coudl see my balances and I hit the "import" button.

I had a black sceen with "Wallet Management Console - Importing Keys (waiting gif icon spinning)". I wait for hours and finally close the client.

I tried through the browser client but it told me me that I couldn't import because "this wallet have already beel imported".

So, I came back to the desktop light client, went through the steps to import, saw my balances, click on "import" and I am stuck again with the "Wallet Management Console - Importing Keys (waiting gif icon spinning)"

Did I do something wrong or missed something in the process ?

[xiahui135]

1. First of all I am stuck synching @ 3711503.. Does this matter? Can I still
create the necessary JSON file backup or do I need to synch first? (i.e. delete
everything in bitshares folder except chain and wallet and try again?)

You can still export the wallet. Only thing is, if you have not synced
completely, you will miss funds that have send to you after your last full sync.
not sure if you expect any.

2. I typed in the console wallet_export keys <a name> I got a message ok. I am
looking for that name in my pc and I can't find it. I have looked at
%appdata%bitshares and it is not there...

It sometimes needs more time for the export to complete. The "OK" unfortunatelly
does not indicated success and completion.

Try with some more patiance ..

it is a big problem the older transaction will not be included when import a not-synched wallet.
One just can import a old wallet, and spend twice.

[xeroc]

1. First of all I am stuck synching @ 3711503.. Does this matter? Can I still
create the necessary JSON file backup or do I need to synch first? (i.e. delete
everything in bitshares folder except chain and wallet and try again?)

You can still export the wallet. Only thing is, if you have not synced
completely, you will miss funds that have send to you after your last full sync.
not sure if you expect any.

2. I typed in the console wallet_export keys <a name> I got a message ok. I am
looking for that name in my pc and I can't find it. I have looked at
%appdata%bitshares and it is not there...

It sometimes needs more time for the export to complete. The "OK" unfortunatelly
does not indicated success and completion.

Try with some more patiance ..

[fav]

@fav thank you very much. i can see the file now..

I misinterpreted the simple instructions

 

[mf-tzo]

@fav thank you very much. i can see the file now..

I misinterpreted the simple instructions

[maqifrnswa]

I've exported keys, but when I try to import it says the wallet has the wrong chain id. The info command shows the correct chain, and i started the cli_wallet with the correct chain id. Is there something else I should be doing?

[fav]

I am trying to save my backup file json using fav's instructions and 0.9.3c. Apparently I am doing something wrong...

1. First of all I am stuck synching @ 3711503.. Does this matter? Can I still create the necessary JSON file backup or do I need to synch first? (i.e. delete everything in bitshares folder except chain and wallet and try again?)

2. I typed in the console wallet_export keys <a name> I got a message ok. I am looking for that name in my pc and I can't find it. I have looked at %appdata%bitshares and it is not there...

I knew I am going to have problems with this.Any help is appreciated. Please very very stupid instructions...

you have to set the full folder name like

C:\Users\YOURUSERNAME\AppData\Roaming\BitShares\keys.json

as explained in the blog post.

[mf-tzo]

I am trying to save my backup file json using fav's instructions and 0.9.3c. Apparently I am doing something wrong...

1. First of all I am stuck synching @ 3711503.. Does this matter? Can I still create the necessary JSON file backup or do I need to synch first? (i.e. delete everything in bitshares folder except chain and wallet and try again?)

2. I typed in the console wallet_export keys <a name> I got a message ok. I am looking for that name in my pc and I can't find it. I have looked at %appdata%bitshares and it is not there...

I knew I am going to have problems with this.Any help is appreciated. Please very very stupid instructions...

[xeroc]

Dumb question:

If I import my wallet from v0.9.3c to graphene
am I supposed to import also the keys manually? Are they not automatic also imported with the wallet import?
(because I see everywhere wallet import + keys import)

I guess it is shoud read   "wallet import / keys import"

[liondani]

Dumb question:

If I import my wallet from v0.9.3c to graphene
am I supposed to import also the keys manually? Are they not automatic also imported with the wallet import?
(because I see everywhere wallet import + keys import)

[svk]

another question: I originally logged into the wallet from my Chrome browser, where I can see the top menu items ACCOUNT, EXPLORER, EXCHANGE and TRANSFER. Then I tried to open the wallet from a different browser, expecting to get a login challenge. Instead, if I go to my wallet link in Firefox (  https://graphene.bitshares.org/#/account/werneo/overview )  I can see everything in the wallet with the exception of the top menu choices.  There is also a NEW menu item called LINK/UNLINK in the sidebar of firefox. Not sure what that does. So does this mean that everyone's wallet is viewable so long as the user name is known?

Yes, until we get support for blinded transactions all balances and transactions will be visible to everyone.

Also, wallets are per browser, so if you create a wallet in Chrome you cannot access that wallet in Firefox unless you export it from Chrome then import it in Firefox.

[werneo]

another question: I originally logged into the wallet from my Chrome browser, where I can see the top menu items ACCOUNT, EXPLORER, EXCHANGE and TRANSFER. Then I tried to open the wallet from a different browser, expecting to get a login challenge. Instead, if I go to my wallet link in Firefox (  https://graphene.bitshares.org/#/account/werneo/overview )  I can see everything in the wallet with the exception of the top menu choices.  There is also a NEW menu item called LINK/UNLINK in the sidebar of firefox. Not sure what that does. So does this mean that everyone's wallet is viewable so long as the user name is known?

[werneo]

I was able to import the keys, but unfortunately the import into graphene does not match what is in my 0.9.3c wallet...

Here is what was imported into the new graphene wallet:
4,733 BROWNIE.PTS
320,920.62832 CORE

Here is what's actually in my 0.9.3c:
5,533.00 BROWNIE.PTS
400,243.76057 BTS

Note that when I exported the keys, the blockchain was up to date. So the export file SHOULD have reflected the exact numbers in the 0.9.3c wallet, but obviously some transactions are missing.

Also I don't see my 30 MKRCOIN in the graphene wallet.

Any thoughts on what's wrong and how to fix it?

I think they use an old snapshot for testing. wouldn't make sense to make a new snapshot every time a testnet starts

roger that.

[fav]

I was able to import the keys, but unfortunately the import into graphene does not match what is in my 0.9.3c wallet...

Here is what was imported into the new graphene wallet:
4,733 BROWNIE.PTS
320,920.62832 CORE

Here is what's actually in my 0.9.3c:
5,533.00 BROWNIE.PTS
400,243.76057 BTS

Note that when I exported the keys, the blockchain was up to date. So the export file SHOULD have reflected the exact numbers in the 0.9.3c wallet, but obviously some transactions are missing.

Also I don't see my 30 MKRCOIN in the graphene wallet.

Any thoughts on what's wrong and how to fix it?

I think they use an old snapshot for testing. wouldn't make sense to make a new snapshot every time a testnet starts

[werneo]

I was able to import the keys, but unfortunately the import into graphene does not match what is in my 0.9.3c wallet...

Here is what was imported into the new graphene wallet:
4,733 BROWNIE.PTS
320,920.62832 CORE

Here is what's actually in my 0.9.3c:
5,533.00 BROWNIE.PTS
400,243.76057 BTS

Note that when I exported the keys, the blockchain was up to date. So the export file SHOULD have reflected the exact numbers in the 0.9.3c wallet, but obviously some transactions are missing.

Also I don't see my 30 MKRCOIN in the graphene wallet.

Any thoughts on what's wrong and how to fix it?

[fav]

had the same issue in the current testnet.

just open a new account and import your keys - worked for me

[clayop]

Import keys are the correct option

[xeroc]

I click IMPORT BACKUP and attempt to import BitShares Wallet Backup.json, but get an "invalid format" error.

Weird .. if you are really using 0.9.3c then this should not happen .. I will point the webdevs here. I can recall that there have been some issues with the most recent grapehen deployment.
//edit: read the next post

[werneo]

Ok.... so I upgraded to wallet version 0.9.3c

I made TWO exports from the wallet:

1. Bitshares Wallet Backup.json, using FILE: EXPORT WALLET
2. mykeys.json, using the command wallet_export_keys from the console

Now... I want to import my wallet into the graphene test wallet to test the process out before version 2.0 is released on the 13th.

I go to the test wallet here: https://graphene.bitshares.org/

I click on EXISTING ACCOUNTS

There are two option this page: IMPORT BACKUP and IMPORT KEYS.

I click IMPORT BACKUP and attempt to import BitShares Wallet Backup.json, but get an "invalid format" error.

If I click IMPORT KEYS, a new pages opens that says CREATE A NEW WALLET, and prompts me for a password.

This is where I stop, because I am not sure what's going on. Is it prompting me for a NEW password or does it wants the OLD password for my 0.9.3c wallet? And why am I getting an INVALID FORMAT error when I try to import my backup?

Please let me know what I should do next!

(Note: When I made the backups, my 0.9.3c wallet was fully up to date an synched with the network. No problem with the wallet itself.)

[xeroc]

Hey there...
I'm looking to update to the 0.9.3 version from 0.9.2. 
I see 0.9.3d, but not the 0.9.3c on github.
Would someone mind linking to the latest build please 
From what I've been reading everyone is mentioning the "C" version and there's no mention of the "D".
Is the "D" version good to go?

Thanks in advance!

I don't see a *d version: https://github.com/BitShares/bitshares/releases

I've exported my 0.93c wallet, but when I try to import it into Graphene it says invalid format.
Not sure if it matters, but I've been unable to sync for over a month.. no matter what I do (uninstall, delete all files in Roaming folder, regedit) I still can't sync. Not with 0.92, not with 0.93, not with 0.93c.

Do not use the BACKUP function... but the export function .. it should be in the 0.9.3c menu bar ..

[pioneer]

I've exported my 0.93c wallet, but when I try to import it into Graphene it says invalid format.
Not sure if it matters, but I've been unable to sync for over a month.. no matter what I do (uninstall, delete all files in Roaming folder, regedit) I still can't sync. Not with 0.92, not with 0.93, not with 0.93c.

[emailtooaj]

Hey there...
I'm looking to update to the 0.9.3 version from 0.9.2. 
I see 0.9.3d, but not the 0.9.3c on github.
Would someone mind linking to the latest build please 
From what I've been reading everyone is mentioning the "C" version and there's no mention of the "D".
Is the "D" version good to go?

Thanks in advance!

[fav]

Thank you Fav. I appreciate your taking the time to post that.
Yes,with that command the file appeared immediately.The command you gave is complete and correct. It worked perfectly. You spelled it out and all a dimwit  like me had to do was to enter my name where you had \xxx\ and press enter.
I'm not nitpicking but some folks struggle with making files visible so as to find the appdata/roaming folder so as to...... etc etc.
Maybe someone could provide a dimwit no brainer menu option in desktop 0.9.3 to store backup wallet for migration to a default folder?
Meantime, mine are now stored safely. Thanks for the help 

spoiler: 0.9.3c has a wallet export in the menu. but BTS 1.0 is done, so we shouldn't waste time to improve anything beyond the current client.

[aragoon]

  Thank you Fav. I appreciate your taking the time to post that.
Yes,with that command the file appeared immediately.The command you gave is complete and correct. It worked perfectly. You spelled it out and all a dimwit  like me had to do was to enter my name where you had \xxx\ and press enter.
I'm not nitpicking but some folks struggle with making files visible so as to find the appdata/roaming folder so as to...... etc etc.
Maybe someone could provide a dimwit no brainer menu option in desktop 0.9.3 to store backup wallet for migration to a default folder?
Meantime, mine are now stored safely. Thanks for the help 

[fav]

tried again in 0.9.3c

Code: [Select]

> >> wallet_export_keys C:\Users\xxx\AppData\Roaming\BitShares\wallets\graphene.json

OK
file was visible immediately.  using win7

[aragoon]

My machine is set to show hidden files and folders. Search comes up empty. Files not in C:\ and not in roaming either. I still can't figure why. Did I input wrong commands? Interesting to find out . 

[fav]

Yes that's the guide I used. Still no files.  definitely more stupid than you. 

hum, tried a search for your name.json? maybe you got some files hidden on your drive?

edit: or try some other folders C:\Users\**YOURUSERNAME**\Downloads

[aragoon]

Yes that's the guide I used. Still no files.  definitely more stupid than you. 

[fav]

OK. Thanks. I'm stupid. 
To someone who uses wallets but never has to go to console, yes, it is harder and entering that "one line" is difficult.  I don't mind a challenge. I spent over a year trying to get 0.9.2 to work and never gave up. Of course  I got comments like "it works fine for me" which implied that I was the only one on the planet experiencing problems with it.  But maybe you're right, no need to do anything. It's obviously so easy already so just ignore people like me ie non-tech people who are enthusiastic about BTS and want to participate and support as much as possible.
Also, I entered the "one line" (actually a couple of different lines are offered in the guides) but can't find the files? How is that possible , it all being so easy I mean?
A humble request from a non-tech. I don't want to have to learn DOS commands just so as to protect my wallet files for migration to the future of banking. We should be beyond that stage. I hope BTS will get mass adoption sooner rather than later. 

hah! I'm non-tech too and probably more stupid than you

I figured it out, so can you! http://blog.smartcoin.pw/2015/09/bitshares-how-to-prepare-your-wallet.html

[aragoon]

OK. Thanks. I'm stupid. 
To someone who uses wallets but never has to go to console, yes, it is harder and entering that "one line" is difficult.  I don't mind a challenge. I spent over a year trying to get 0.9.2 to work and never gave up. Of course  I got comments like "it works fine for me" which implied that I was the only one on the planet experiencing problems with it.  But maybe you're right, no need to do anything. It's obviously so easy already so just ignore people like me ie non-tech people who are enthusiastic about BTS and want to participate and support as much as possible.
Also, I entered the "one line" (actually a couple of different lines are offered in the guides) but can't find the files? How is that possible , it all being so easy I mean?
A humble request from a non-tech. I don't want to have to learn DOS commands just so as to protect my wallet files for migration to the future of banking. We should be beyond that stage. I hope BTS will get mass adoption sooner rather than later. 

I guess I'm wanting to make the point that, at this stage in the development of wallets, it should be exceptional/optional  for anyone to use the console. It seems to be an unnecessary hurdle, however easy it really is for folks familiar with commands. Thanks.

[xeroc]

AFAIK, 0.9.3c(!!) has this menu item already ... at least that's what the RELEASENOTES say:

* Export Menu in GUI should now save Graphene compatible Backups

Also,  @aragoon, I recall someone saying that (even though the commandline returned 'OK') it may take some time to construct that file if you have many accounts/keys in your wallet.
Maybe just wait alittle

[fav]

I finally abandoned efforts to get 0.9.2 to work and tried 0.9.3 which works perfectly. I now have 0.9.3c running. I want to prepare to migrate wallet to 2.0 so

desktop win7 64bit ver 0.9.3c
chain and transactions fully up to date.
select:        account....advanced.....console.....
type:           wallet_export_keys C:\default.json   enter    returns     OK
type:           wallet_export_keys C:\name.json       enter   returns     OK
type:           wallet_export_keys json.name              enter   returns    OK
Look for files in C:\program files\bitshares                     not there
Look for files in .......appdata\roaming\bitshares           not there

Where are the files? Have I missed out a command or step?

Why not have 0.9.3d with menu option to export keys for migration to (select folder) ? Even basic commands are going to be a step too far for people who don't use console. Just a suggestion. Or you can wait for all the people to turn up asking how to use console. Confusion, lost wallets etc etc. 

it's literally one line in the console. that's not harder than finding and clicking to export keys via menu.

[mf-tzo]

Why not have 0.9.3d with menu option to export keys for migration to (select folder) ? Even basic commands are going to be a step too far for people who don't use console. Just a suggestion. Or you can wait for all the people to turn up asking how to use console. Confusion, lost wallets etc etc. 

I agree.Please make it easier..

[aragoon]

I finally abandoned efforts to get 0.9.2 to work and tried 0.9.3 which works perfectly. I now have 0.9.3c running. I want to prepare to migrate wallet to 2.0 so

desktop win7 64bit ver 0.9.3c
chain and transactions fully up to date.
select:        account....advanced.....console.....
type:           wallet_export_keys C:\default.json   enter    returns     OK
type:           wallet_export_keys C:\name.json       enter   returns     OK
type:           wallet_export_keys json.name              enter   returns    OK
Look for files in C:\program files\bitshares                     not there
Look for files in .......appdata\roaming\bitshares           not there

Where are the files? Have I missed out a command or step?

Why not have 0.9.3d with menu option to export keys for migration to (select folder) ? Even basic commands are going to be a step too far for people who don't use console. Just a suggestion. Or you can wait for all the people to turn up asking how to use console. Confusion, lost wallets etc etc. 

[svk]

If you're on Mac you can use this release: https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

If not you can build this branch: https://github.com/bitshares/bitshares/tree/bitshares

Like it says you need to use the new wallet_export_keys method.

[clayop]

I've been trying to import my wallets into graphene for a while but I always get the error that the json file is not the right format. I can import the json back from the hosted web wallet but can't import the json backup from the desktop application. Thanks for you're help in advanced @bytemaster, @jcalfee1

You should wait 0.9.3 or build it by yourself

[clout]

I've been trying to import my wallets into graphene for a while but I always get the error that the json file is not the right format. I can import the json back from the hosted web wallet but can't import the json backup from the desktop application. Thanks for you're help in advanced @bytemaster, @jcalfee1