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.