Delegates, start your engines!

[xeroc]

@sfinder  I will look at your issue tomorrow, I have to sleep now. I cannot reproduce it easily

check following link. problem was caused by hackfish committed cmakelist for Keyhotee. manually fix

https://github.com/BitShares/bitshares_toolkit/commit/c182d24ae7ee569f5c601a915bea317477d24c2c#diff-d3cc6a7d9369a54a5ed80c1cf4f996a7

that fixed it for me .. thx

Delegate up an running in a few minutes

[mauritso]

Create a wallet and import your keys:

Code: [Select]

(wallet closed) >>> wallet_create mywallet
passphrase:
passphrase (verify):
OK

mywallet (unlocked) >>> unlock 999999
passphrase:
OK

mywallet (unlocked) >>> wallet_import_private_key 5KdeCK6PcFuZqh9XBPBN2tYG2MsgXpYXG3vzPhLK1VA8ye6Ptwf
OK(repeat for each key - some will fail as we did not include all 5 for everyone)

Code: [Select]

mywallet (unlocked) >>> wallet_rescan_blockchain
...
Scan complete.
OK

Just followed the instructions and "(repeat for each key - some will fail as we did not include all 5 for everyone)" implies that all your keys will fail if you are not an initial delegate.

[xeroc]

What commands do you run? You should aleays be able to import privekys to an account!

[mauritso]

Also.  If there are any nix masters out there.  What is the purpose of splitting the screen -S and the running gdb?

It seems like I can get similar results from running
screen -S Bitshares ./bitshares_client
without the step of running gdb
from a theoretical viewpoint, I'd like to understand the difference.

**this is purely for my educational purposes, and is not at all important**

GDB is a debugger, if the client crashes for example GDB can give some meaningful info as to why that happened.

If all of my private keys give me:

Code: [Select]

10
registered_account:
    {}
    th_a  wallet.cpp:777 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:812 import_private_key

    {"account_name":""}
    th_a  wallet.cpp:831 import_wif_private_key

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:574 execute_command
mauritso (unlocked) >>>

That would mean that I am not an initial delegate right? (Is there a list somewhere?)

[JoeyD]

Drat I just missed the key-registering window when I finally was able to access my pc late last night. Are there still open spots for registering as a delegate or are those locked down now?

Also.  If there are any nix masters out there.  What is the purpose of splitting the screen -S and the running gdb?

It seems like I can get similar results from running
screen -S Bitshares ./bitshares_client
without the step of running gdb
from a theoretical viewpoint, I'd like to understand the difference.

**this is purely for my educational purposes, and is not at all important**

gdb is the debugger, so in case of an error, the codemasters know what to work on. Apparently it is a lot more useful than the ubiquitous "It doesn' t work" bug report.

[emski]

Why dont you state git revision the network should be used?
The head needs additional modification to make it work (see lib curses issue).

035357b7ffbcc394236fec5e2cb8d0e9bf707c97 seems to compile and run without issues on clean ubuntu server 14.04 installation and following the instructions.

[puppies]

Also.  If there are any nix masters out there.  What is the purpose of splitting the screen -S and the running gdb?

It seems like I can get similar results from running
screen -S Bitshares ./bitshares_client
without the step of running gdb
from a theoretical viewpoint, I'd like to understand the difference.

**this is purely for my educational purposes, and is not at all important**

[puppies]

wallet (unlocked) >>> enable_raw wallet get_receive_accounts
returns
wallet (unlocked) >>>
With no info. 
To find my delegate numbers I started with
wallet (unlocked) >>> blockchain_get_account_record init-delegate-1
and increased the integer at the end by one.  When you get to an return that does not list
 "next_secret_hash": "0000000000000000000000000000000000000000",
but instead has a hex key inside the final " " you should have the value of your delegate. 

Its possible that I am just stupid, and did not understand the instructions. (the brain power does fade this late at night)

**so.  I have just tested this and have gotten next_secret_hash from keys I probably shouldn't have.  Chances are I am the dumz.  I will retry in the morning with the firepower of this fully ARMED and OPERATIONAL battle station!**

[Harvey]

This is what I have so far：

harvey (unlocked) >>> wallet_list_receive_accounts
NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL
harvey-delegate-5        0.000000 XTS             XTS7ze619FTgRReQsYEKYj8CbuiWB17q629gCz34Q7aeqe4yMida5           NO                    0
harvey-delegate-4        0.000000 XTS             XTS7fzyfX657vDUP4UVXRHNxCMZsGpCCGkvP7rN5NKkuEjktg5sHd           NO                    0
harvey-delegate-3        0.000000 XTS             XTS6LDMYp9UNEYLUEdpCqx5dCEkWwrpP67LE5Zu3sSYqjP6LraqTW           NO                    0
harvey-delegate-2        0.000000 XTS             XTS7qQScYbuFqsffgH6AammYXWMkZ9jSYdsYW21zguc2k2N3hYnfN           NO                    0
harvey-delegate-1        0.000000 XTS             XTS7Bsi43JASDcPdgcLaXSLQ7mVNJReUvG4rcQYHHaJ3Ca7SLPYyq           NO                    0
"OK"

[welk1n]

How to be registered?         

NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL   
welk1n-d-5               0.000000 XTS             XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC           NO                    0             
welk1n-d-4               0.000000 XTS             XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA           NO                    0             
welk1n-d-3               0.000000 XTS             XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X           NO                    0             
welk1n-d-2               0.000000 XTS             XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj           NO                    0             
welk1n-d-1               0.000000 XTS             XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx           NO                    0             
"OK"

Looks like "registered" status is buggy.  Actually I see you made new accounts, you should not need to - if you just import your keys and rescan you will have pre-registered accounts "init-delegate-N". If you want to register new accounts you can use "wallet_account_register"

I just import the keys and rescan it, but the status is still no registered.

[welk1n]

@sfinder  I will look at your issue tomorrow, I have to sleep now. I cannot reproduce it easily

check following link. problem was caused by hackfish committed cmakelist for Keyhotee. manually fix

https://github.com/BitShares/bitshares_toolkit/commit/c182d24ae7ee569f5c601a915bea317477d24c2c#diff-d3cc6a7d9369a54a5ed80c1cf4f996a7

Yes ,  diff the two files , you will find it. 

[sfinder]

@sfinder  I will look at your issue tomorrow, I have to sleep now. I cannot reproduce it easily

check following link. problem was caused by hackfish committed cmakelist for Keyhotee. manually fix

https://github.com/BitShares/bitshares_toolkit/commit/c182d24ae7ee569f5c601a915bea317477d24c2c#diff-d3cc6a7d9369a54a5ed80c1cf4f996a7

[bitder]

I'm getting the same build problem as sfinder. (also on ubuntu 14.04)

The last merge seems to have caused it.

Code: [Select]

bitshares_toolkit$ git log 035357b..2f8e2b1
commit 2f8e2b19632603d398bf000ced29f0a0b79cffb8
Merge: 035357b 6102b44
Author: Nikolai Mushegian <nikolai.mushegian@gmail.com>
Date:   Sun Jun 8 23:04:12 2014 -0400

    Merge pull request #238 from HackFisher/master
   
    #233, import keyhotee id.

commit 6102b4478ef6d0d822383bcff81de7b5f09322f9
Author: HackFisher <hackfisher@gmail.com>
Date:   Sun Jun 8 21:09:38 2014 -0400

    modifile api description

commit c9dcc1c13fd975a1c2e333ad11be92ec28528bc3
Author: HackFisher <hackfisher@gmail.com>
Date:   Sun Jun 8 21:07:32 2014 -0400

    using keyhotee id as account name

commit 723e466ccb9dc87a08a3895a66c123e5aff529c8
Merge: c182d24 db48890
Author: HackFisher <hackfisher@gmail.com>
Date:   Sun Jun 8 20:53:09 2014 -0400

    Merge remote-tracking branch 'upstream/master'

commit c182d24ae7ee569f5c601a915bea317477d24c2c
Author: HackFisher <hackfisher@gmail.com>
Date:   Sun Jun 8 20:52:51 2014 -0400

    fixed 233, import keyhotee id.



[toast]

@sfinder  I will look at your issue tomorrow, I have to sleep now. I cannot reproduce it easily

[toast]

Code: [Select]

cgafeng (locked) >>> wallet_list_receive_accounts
NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL
cgafeng (delegate)       670.177299 XTS           XTS5V87vRKu7K9z3nBDEprCnyyxESaTZDZubUPVc9uhfEdY6hj4Us           2014-06-09T03:57:45   0
I use wallet_account_register to register as delegate, are my delegate name is cgafeng?
when i use blockchain_list_delegates, i don't find my name.

No, everyone was registered with names "init-delegate-NN". You do not need to make new accounts, just import and rescan exactly as in the guide.
Your new name is registered as a delegate, but it has not votes and will not make blocks.