Delegates, start your engines!

Started by toast, June 09, 2014, 01:54:36 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bytemaster

Quote from: xeroc on June 09, 2014, 01:09:01 PM
Importing my PTS/BTC privkeys only worked after doing the following steps

1.) get wif for pts/btc address
2.) go to brainwallet and convert Base65Check privkey to hex
3.) use key_to_wif to convert brainwallet hex key to privkey
4.) Both priv keys differ in the last view bytes (i suspect thats the Check-part)

@Devs: Please doublecheck the CHECK-procedure of your WIF formats in the code!!!

Thanks for the notice I will look into this: https://github.com/BitShares/bitshares_toolkit/issues/241
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

bytemaster

Quote from: JoeyD on June 09, 2014, 08:14:49 AM
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?


Not too late, you can register as a delegate on the chain.. this is just a dry run to see what problems delegates have so we can smooth it out.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

xeroc

Importing my PTS/BTC privkeys only worked after doing the following steps

1.) get wif for pts/btc address
2.) go to brainwallet and convert Base65Check privkey to hex
3.) use key_to_wif to convert brainwallet hex key to privkey
4.) Both priv keys differ in the last view bytes (i suspect thats the Check-part)

@Devs: Please doublecheck the CHECK-procedure of your WIF formats in the code!!!

emski

Quote from: networker on June 09, 2014, 12:46:29 PM
Quote from: emski on June 09, 2014, 12:42:41 PM
Quote from: networker on June 09, 2014, 12:38:38 PM
Quote from: sfinder on June 09, 2014, 03:33:00 AM
daniel@ubuntu:~/bitshares_toolkit$ cmake /V
cmake version 2.8.12.2

Quote from: toast on June 09, 2014, 03:31:00 AM
What is your cmake --version?

cmake version 2.8.12.2

May need to Temporarily set CURSES_USE_NCURSES to TRUE to force the use of NCURSES, rather than letting CMake try to find CURSES.
When I use "cmake ." try to build bitshare toolkit,  I met the problem" Could not find Curses(missing: CURESES_LIBRARY CURSES_INCLUDE_PATH)
How can I fix it ?
How to set CURSES_USE_NCURSES to TRUE?

Try to checkout this revision: 035357b7ffbcc394236fec5e2cb8d0e9bf707c97  .
It works for me without modifications.
What does revision mean? I can't understand 0353......7c97
Sorry

git checkout 035357b7ffbcc394236fec5e2cb8d0e9bf707c97

It should give you the repository state as of this commit:
https://github.com/BitShares/bitshares_toolkit/commit/035357b7ffbcc394236fec5e2cb8d0e9bf707c97
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

networker

Quote from: emski on June 09, 2014, 12:42:41 PM
Quote from: networker on June 09, 2014, 12:38:38 PM
Quote from: sfinder on June 09, 2014, 03:33:00 AM
daniel@ubuntu:~/bitshares_toolkit$ cmake /V
cmake version 2.8.12.2

Quote from: toast on June 09, 2014, 03:31:00 AM
What is your cmake --version?

cmake version 2.8.12.2

May need to Temporarily set CURSES_USE_NCURSES to TRUE to force the use of NCURSES, rather than letting CMake try to find CURSES.
When I use "cmake ." try to build bitshare toolkit,  I met the problem" Could not find Curses(missing: CURESES_LIBRARY CURSES_INCLUDE_PATH)
How can I fix it ?
How to set CURSES_USE_NCURSES to TRUE?

Try to checkout this revision: 035357b7ffbcc394236fec5e2cb8d0e9bf707c97  .
It works for me without modifications.
What does revision mean? I can't understand 0353......7c97
Sorry

changematey

Well looks like none of my private WIF keys are working. The public key list:
https://bitsharestalk.org/index.php?topic=4913.msg64544#msg64544

I guess missed the bus for this initial test.

emski

Quote from: networker on June 09, 2014, 12:38:38 PM
Quote from: sfinder on June 09, 2014, 03:33:00 AM
daniel@ubuntu:~/bitshares_toolkit$ cmake /V
cmake version 2.8.12.2

Quote from: toast on June 09, 2014, 03:31:00 AM
What is your cmake --version?

cmake version 2.8.12.2

May need to Temporarily set CURSES_USE_NCURSES to TRUE to force the use of NCURSES, rather than letting CMake try to find CURSES.
When I use "cmake ." try to build bitshare toolkit,  I met the problem" Could not find Curses(missing: CURESES_LIBRARY CURSES_INCLUDE_PATH)
How can I fix it ?
How to set CURSES_USE_NCURSES to TRUE?

Try to checkout this revision: 035357b7ffbcc394236fec5e2cb8d0e9bf707c97  .
It works for me without modifications.
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

networker

Quote from: sfinder on June 09, 2014, 03:33:00 AM
daniel@ubuntu:~/bitshares_toolkit$ cmake /V
cmake version 2.8.12.2

Quote from: toast on June 09, 2014, 03:31:00 AM
What is your cmake --version?

cmake version 2.8.12.2

May need to Temporarily set CURSES_USE_NCURSES to TRUE to force the use of NCURSES, rather than letting CMake try to find CURSES.
When I use "cmake ." try to build bitshare toolkit,  I met the problem" Could not find Curses(missing: CURESES_LIBRARY CURSES_INCLUDE_PATH)
How can I fix it ?
How to set CURSES_USE_NCURSES to TRUE?

networker

Quote from: toast on June 09, 2014, 04:58:07 AM
Quote from: cgafeng on June 09, 2014, 04:55:07 AM

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.
Can I join dry test now if I missed the init delegate part?

xeroc

I also have just 2 working keys ..

coolspeed

Quote from: taoljj on June 09, 2014, 11:35:34 AM
Quote from: coolspeed on June 09, 2014, 11:22:34 AM
HELP!!

My first 4 importing of private keys were all OK. But when I import my 5th private key, it reported the following errors:

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

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

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

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:576 execute_command



Can anyone tell me how I can fix this, or whether fixing this is a must.
Since the document syas:
If you want to stay voted in, you should probably create a new delegate to campaign as, as a nameless initial delegate is unlikely to stay a delegate for long.
and the "DPOS Registering Names And Delegates " is not completed yet.

FYI, my fifth public key is:
XTS7XDCb4BEeEtbPtHWGCvx9xW3r5SGTrHr8PjnH3VbhtUFWsjArm

dan imported 4keys for one account

Thank you.
If I did not get you wrong, you mean it is all OK.
:)
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

taoljj

Quote from: coolspeed on June 09, 2014, 11:22:34 AM
HELP!!

My first 4 importing of private keys were all OK. But when I import my 5th private key, it reported the following errors:

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

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

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

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:576 execute_command



Can anyone tell me how I can fix this, or whether fixing this is a must.
Since the document syas:
If you want to stay voted in, you should probably create a new delegate to campaign as, as a nameless initial delegate is unlikely to stay a delegate for long.
and the "DPOS Registering Names And Delegates " is not completed yet.

FYI, my fifth public key is:
XTS7XDCb4BEeEtbPtHWGCvx9xW3r5SGTrHr8PjnH3VbhtUFWsjArm

dan imported 4keys for one account
BTS      Witness: delegate.taoljj

coolspeed

#38
HELP!!

My first 4 importing of private keys were all OK. But when I import my 5th private key, it reported the following errors:

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

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

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

    {}
    th_a  common_api_client.cpp:212 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:576 execute_command



Can anyone tell me how I can fix this, or whether fixing this is a must.
Since the document syas:
If you want to stay voted in, you should probably create a new delegate to campaign as, as a nameless initial delegate is unlikely to stay a delegate for long.
and the "DPOS Registering Names And Delegates " is not completed yet.

FYI, my fifth public key is:
XTS7XDCb4BEeEtbPtHWGCvx9xW3r5SGTrHr8PjnH3VbhtUFWsjArm
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

coolspeed

Quote from: xeroc on June 09, 2014, 08:35:33 AM
Quote from: sfinder on June 09, 2014, 05:14:51 AM
Quote from: toast on June 09, 2014, 04:59:34 AM
@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

+5% me too. Thx sfinder.
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

welk1n

Quote from: mauritso on June 09, 2014, 08:17:03 AM
Quote from: puppies on June 09, 2014, 06:55:49 AM
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:

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?)

Maybe you can find the old wallets dir and copy it to the new wallets dir.
Then you can use command
>>> wallet_open $wallet_name

I just do like this, and now is working well.