Delegates, start your engines!

[muse-umum]

toast, I got your PM.

But I failed to import the WIF private keys.

try pulling/rebuilding

Tried. But I got errors when building

Code Select Expand


[ 96%] Building CXX object programs/client/CMakeFiles/bitshares_client.dir/main.cpp.o
Linking CXX executable bitshares_client
../../libraries/net/libbts_net.a(upnp.cpp.o): In function `operator()':
/root/bitshares_toolkit/libraries/net/upnp.cpp:78: undefined reference to `upnpDiscover'
/root/bitshares_toolkit/libraries/net/upnp.cpp:86: undefined reference to `UPNP_GetValidIGD'
/root/bitshares_toolkit/libraries/net/upnp.cpp:146: undefined reference to `freeUPNPDevlist'
/root/bitshares_toolkit/libraries/net/upnp.cpp:149: undefined reference to `FreeUPNPUrls'
/root/bitshares_toolkit/libraries/net/upnp.cpp:96: undefined reference to `UPNP_GetExternalIPAddress'
/root/bitshares_toolkit/libraries/net/upnp.cpp:125: undefined reference to `strupnperror'
/root/bitshares_toolkit/libraries/net/upnp.cpp:120: undefined reference to `UPNP_AddPortMapping'
/root/bitshares_toolkit/libraries/net/upnp.cpp:136: undefined reference to `UPNP_DeletePortMapping'
/root/bitshares_toolkit/libraries/net/upnp.cpp:138: undefined reference to `freeUPNPDevlist'
/root/bitshares_toolkit/libraries/net/upnp.cpp:139: undefined reference to `FreeUPNPUrls'
collect2: error: ld returned 1 exit status
make[2]: *** [programs/client/bitshares_client] Error 1
make[1]: *** [programs/client/CMakeFiles/bitshares_client.dir/all] Error 2
make: *** [all] Error 2


Then I wiped all the files and cloned the codes and built. But still the same.

[toast]

Hi TOAST,

since only partial delegate name shows on my list, could you please how to show full  delegate name on my screen.

many thanks

The most recent build does not clip the names.

If you don't want to rebuild, you can try to find your public keys in "blockchain_list_registered_accounts init-delegate"

[sfinder]

Hi TOAST,

since only partial delegate name shows on my list, could you please how to show full  delegate name on my screen.

many thanks

but not able to see full name (check in red ) under my "wallet_list_receive_accounts"

init-delega... (delegate)0.000000 XTS             XTS4u3cQJNLS9jDN1mCM9ynLNHQV9PuEVfwA2R95XnV7ZDNjJL89z           2014-06-01T00:00:00   0

why only one of account "pan2pan-05" showing in my "wallet_list_receive_accounts"? I did import 5 private key to 5 accounts that I created in my wallet

Code Select Expand




pan2pan (unlocked) >>> wallet_list_receive_accounts
NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL
pan2pan-05               0.000000 XTS             XTS8T5M76CG8PFopcuSoAkvTfzkGhZMR44Dckd6JB5zYxxde1vqaU           NO                    0
[b][color=red]init-delega... (delegate)0.000000 XTS [/color][/b]            XTS4u3cQJNLS9jDN1mCM9ynLNHQV9PuEVfwA2R95XnV7ZDNjJL89z           2014-06-01T00:00:00   0
init-delega... (delegate)0.000000 XTS             XTS5H3qwDsnjm8yoiN1CAQg6LKTnSNuXZDePeGAQSa5CiALSFRFQ8           2014-06-01T00:00:00   0
init-delega... (delegate)0.000000 XTS             XTS5vXkQbGLEwaye3ZsLAtMMEe6tkh724nr2zoGHHeAUCsvVeywvc           2014-06-01T00:00:00   0
init-delega... (delegate)0.000000 XTS             XTS6tmvXdn2vJss4a4ADVUUi8GbAC37H6HJRcVeFyhzcsRUNyQJGE           2014-06-01T00:00:00   0
"OK"



We only used 4 out of 5 keys for some of you.

[toast]

Can I still be  a delegate?
Or will be punished by the network?
What shall I do to get all blocks? I have stop one node, but the other node still can't get all blocks.

Nobody is really voting for now. If you're stuck in a bad state you could try wiping all data dirs and re-importing

[hasher]

i was late to paticipate in initial delegates network, what a pity

[alt]

Can I still be  a delegate?
Or will be punished by the network?
What shall I do to get all blocks? I have stop one node, but the other node still can't get all blocks.

[toast]

Fixing it would require adding logic for master/slave clients which would sync with each other and make sure not to sign the same blocks. I think that's best left as a infrastructure tool rather than building it into the client itself

[alt]

Oh no no, do NOT put your private key on two different clients or else you will cause a fork.
Shut down the one on the minority fork

What are some commands that I can use to verify that my delegates are producing blocks properly and not just on it's own fork.

I used blockchain_get_blockcount which is currently showing 97

default (unlocked) >>> info
{
  "blockchain_head_block_num": 1059,
  "blockchain_head_block_time": "20140609T150800"
}

If you are on a fork... then we need to do a better job detecting and reporting this.

If I run 2 clients with the same wallet, the block can be sent to only one instead of both?
here is output from 1 pc

Code Select Expand


delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 747,
  "blockchain_head_block_time": "20140609T155615",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 21.453187823090179,
  "network_num_connections": 0,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],
  "wallet_unlocked_seconds_remaining": 992993,
  "wallet_next_block_production_time": "20140609T160515",
  "wallet_seconds_until_next_block_production": 144,
  "wallet_local_time": "20140609T160251",
  "blockchain_random_seed": "4f6c48246305a9821a1ffb97c5179d3f5544b7c5",
  "blockchain_shares": 9999976500511,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140621T035244.949127",
  "wallet_version": 100
}

here is another

Code Select Expand


delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 446,
  "blockchain_head_block_time": "20140609T155845",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 13.440551407237219,
  "network_num_connections": 0,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],
  "wallet_unlocked_seconds_remaining": 992876,
  "wallet_next_block_production_time": "20140609T160315",
  "wallet_seconds_until_next_block_production": 17,
  "wallet_local_time": "20140609T160258",
  "blockchain_random_seed": "a7d1d2491731fe9b6c47e5967913c0aeea1a9689",
  "blockchain_shares": 9999973654990,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140621T035054.138282",
  "wallet_version": 100
}


wow, I have quit one...
but do we need to  fix this?

[toast]

Oh no no, do NOT put your private key on two different clients or else you will cause a fork.
Shut down the one on the minority fork

What are some commands that I can use to verify that my delegates are producing blocks properly and not just on it's own fork.

I used blockchain_get_blockcount which is currently showing 97

default (unlocked) >>> info
{
  "blockchain_head_block_num": 1059,
  "blockchain_head_block_time": "20140609T150800"
}

If you are on a fork... then we need to do a better job detecting and reporting this.

If I run 2 clients with the same wallet, the block can be sent to only one instead of both?
here is output from 1 pc

Code Select Expand


delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 747,
  "blockchain_head_block_time": "20140609T155615",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 21.453187823090179,
  "network_num_connections": 0,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],
  "wallet_unlocked_seconds_remaining": 992993,
  "wallet_next_block_production_time": "20140609T160515",
  "wallet_seconds_until_next_block_production": 144,
  "wallet_local_time": "20140609T160251",
  "blockchain_random_seed": "4f6c48246305a9821a1ffb97c5179d3f5544b7c5",
  "blockchain_shares": 9999976500511,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140621T035244.949127",
  "wallet_version": 100
}

here is another

Code Select Expand


delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 446,
  "blockchain_head_block_time": "20140609T155845",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 13.440551407237219,
  "network_num_connections": 0,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],
  "wallet_unlocked_seconds_remaining": 992876,
  "wallet_next_block_production_time": "20140609T160315",
  "wallet_seconds_until_next_block_production": 17,
  "wallet_local_time": "20140609T160258",
  "blockchain_random_seed": "a7d1d2491731fe9b6c47e5967913c0aeea1a9689",
  "blockchain_shares": 9999973654990,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140621T035054.138282",
  "wallet_version": 100
}


[alt]

What are some commands that I can use to verify that my delegates are producing blocks properly and not just on it's own fork.

I used blockchain_get_blockcount which is currently showing 97

default (unlocked) >>> info
{
  "blockchain_head_block_num": 1059,
  "blockchain_head_block_time": "20140609T150800"
}

If you are on a fork... then we need to do a better job detecting and reporting this.

If I run 2 clients with the same wallet, the block can be sent to only one instead of both?
here is output from 1 pc

Code Select Expand


delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 747,
  "blockchain_head_block_time": "20140609T155615",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 21.453187823090179,
  "network_num_connections": 0,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],
  "wallet_unlocked_seconds_remaining": 992993,
  "wallet_next_block_production_time": "20140609T160515",
  "wallet_seconds_until_next_block_production": 144,
  "wallet_local_time": "20140609T160251",
  "blockchain_random_seed": "4f6c48246305a9821a1ffb97c5179d3f5544b7c5",
  "blockchain_shares": 9999976500511,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140621T035244.949127",
  "wallet_version": 100
}

here is another

Code Select Expand


delegate (unlocked) >>> info
{
  "blockchain_head_block_num": 446,
  "blockchain_head_block_time": "20140609T155845",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 13.440551407237219,
  "network_num_connections": 0,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],
  "wallet_unlocked_seconds_remaining": 992876,
  "wallet_next_block_production_time": "20140609T160315",
  "wallet_seconds_until_next_block_production": 17,
  "wallet_local_time": "20140609T160258",
  "blockchain_random_seed": "a7d1d2491731fe9b6c47e5967913c0aeea1a9689",
  "blockchain_shares": 9999973654990,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140621T035054.138282",
  "wallet_version": 100
}


[toast]

^ that seems like a bug, filing now.
But you're all good as far as being a delegate

[alt]

It's weired, what's the different about blockchain_get_account_record and wallet_get_accout?

Code Select Expand


delegate (unlocked) >>> blockchain_get_account_record init-delegate-20
{
  "id": 20,
  "name": "init-delegate-20",
  "public_data": null,
  "owner_key": "XTS5iUxjeTmcdb2MrZBD32n73fLP1P1gBY4peWdaj1AZ6NrbBmr3y",
  "active_key_history": [[
      "19700101T000000",
      "XTS5iUxjeTmcdb2MrZBD32n73fLP1P1gBY4peWdaj1AZ6NrbBmr3y"
    ]
  ],
  "delegate_info": {
    "votes_for": 102044686731,
    "votes_against": 0,
    "blocks_produced": 29,
    "blocks_missed": 6,
    "pay_balance": 208463,
    "next_secret_hash": "4bd299df1efe25d68abec47f512dcf4af813d75c",
    "last_block_num_produced": 747
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null
}
delegate (unlocked) >>> wallet_get_account init-delegate-20
{
  "index": 9,
  "id": 20,
  "name": "init-delegate-20",
  "public_data": null,
  "owner_key": "XTS5iUxjeTmcdb2MrZBD32n73fLP1P1gBY4peWdaj1AZ6NrbBmr3y",
  "active_key_history": [[
      "19700101T000000",
      "XTS5iUxjeTmcdb2MrZBD32n73fLP1P1gBY4peWdaj1AZ6NrbBmr3y"
    ]
  ],
  "delegate_info": {
    "votes_for": 102044478268,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 3,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null,
  "account_address": "XTSGCyPiFjh7GicSTQFH7oDpTSAJM6qMCAnw",
  "trust_level": 0,
  "private_data": null
}


I have run about 12 hours with 2 computer,
but I still produce 0 block.
Is this correct?
my account is init-delegate-17, init-delegate-18,init-delegate-19,init-delegate-20

I see that you are producing blocks, where do you see that you produced 0?

This is probably because we don't expose the delegate's pay which is separate from their normal balance.  If delegates are looking for 'coinbase' transactions, they don't exist... your pay is a property of your account.

default (unlocked) >>> blockchain_get_account_record init-delegate-17
{
  "id": 17,
  "name": "init-delegate-17",
  "public_data": null,
  "owner_key": "XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM",
  "active_key_history": [[
      "19700101T000000",
      "XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM"
    ]
  ],
  "delegate_info": {
    "votes_for": 91796978110,
    "votes_against": 0,
    "blocks_produced": 18,
    "blocks_missed": 13,
    "pay_balance": 80020,
    "next_secret_hash": "8074d5a45dffa7031980c1188d853a514cab88c0",
    "last_block_num_produced": 655
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null
}

[toast]

toast, I got your PM.

But I failed to import the WIF private keys.

try pulling/rebuilding

[bytemaster]

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.

Try this now.

Tried but no go. For some of the delegates now I keep getting:

Code Select Expand


10
false: Error parsing WIF private key
    {}
    th_a  wallet.cpp:843 import_wif_private_key

    {"account_name":""}
    th_a  wallet.cpp:845 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

whereas others seem to be giving the same old "registered" address error.

Are you building with the latest code?  Because I updated code related to this today.

[muse-umum]

toast, I got your PM.

But I failed to import the WIF private keys.

Code Select Expand


(wallet closed) >>> wallet_create delegatewallet
new_passphrase:
new_passphrase (verify):
OK
delegatewallet (unlocked) >>> unlock 100000
passphrase:
OK


Three of them with errors like this:

Code Select Expand


delegatewallet (unlocked) >>> wallet_import_private_key 5JyfiiE2XXX
10
false: Error parsing WIF private key
    {}
    th_a  wallet.cpp:843 import_wif_private_key

    {"account_name":""}
    th_a  wallet.cpp:845 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


The other two with errors like this:

Code Select Expand


delegatewallet (unlocked) >>> wallet_import_private_key 5JCrrj3XXXX
10
registered_account: the key must belong to a registered account or an account name must be specified
    {}
    th_a  wallet.cpp:788 import_private_key

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

    {"account_name":""}
    th_a  wallet.cpp:845 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