Author Topic: Delegates, start your engines!  (Read 54850 times)

0 Members and 1 Guest are viewing this topic.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
I received PM with a message that at least some of my delegate keys were included in initial delegate list. I rebuilt following instructions from
https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-initial-delegate-setup
and tried importing my keys. Getting errors on all 5. On first I get this error:


Code: [Select]
default (unlocked) >>> wallet_import_private_key <private key WIF format>
10
registered_account: the key must belong to a registered account or an account name must be specified
    {}
    th_a  wallet.cpp:791 import_private_key

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

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

    {}
    th_a  common_api_client.cpp:222 wallet_import_private_key

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

On the other 4 keys I get this error:

Code: [Select]
default (unlocked) >>> wallet_import_private_key <key goes here>
10
false: Error parsing WIF private key
    {}
    th_a  wallet.cpp:846 import_wif_private_key

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

    {}
    th_a  common_api_client.cpp:222 wallet_import_private_key

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

Xeldal

  • Guest
Just rebuilt, now I'm getting an error importing private key

Code: [Select]
Xeldal-1 (unlocked) >>> wallet_import_private_key 5xxxxxWIF-Private-keyxxxxxxxxxxxxxxxx
10
false: Error parsing WIF private key
    {}
    th_a  wallet.cpp:846 import_wif_private_key

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

    {}
    th_a  common_api_client.cpp:222 wallet_import_private_key

    {"command":"wallet_import_private_key"}
    th_a  cli.cpp:576 execute_command
Xeldal-1 (unlocked) >>>

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
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
I mean if I make a fork, So I am a cheatting delegate
the other nodes should deny me automatic.
Did this work?

Nope. Also just having a fork is not auto-fire condition I would think - signing two blocks is.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
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
I mean if I make a fork, So I am a cheatting delegate
the other nodes should deny me automatic.
Did this work?

Offline zhangweis

  • Sr. Member
  • ****
  • Posts: 305
    • View Profile
I guess I'm on a fork as I can see that I'm the only delegate generating blocks.

get_info
{
  "blockchain_head_block_num": 962,
  "blockchain_head_block_time": "20140609T214430",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 19.696969696969695,
  "network_num_connections": 7,
  "wallet_unlocked_seconds_remaining": 9999999343,
  "wallet_next_block_production_time": "20140609T215515",
  "wallet_seconds_until_next_block_production": 119,
  "wallet_local_time": "20140609T215316",
  "blockchain_random_seed": "3a3a9e5f0ac5b5ebbfa4aeb0294a0c152af8efad",
  "blockchain_shares": 9999979523473,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20181223T045058.320125",
  "wallet_version": 100
}

I have below logs, does that prevent me connecting to other normal nodes?

3208214ms       th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes                node.cpp:684
3208214ms       th_a                 bind ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                      tcp_socket.cpp:105
3208214ms       th_a           connect_to ] Failed to bind to desired local endpoint 0.0.0.0:45410, will connect using an OS-selected endpoint: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"tcp_socket.cpp","line":106,"method":"bind","hostname":"","thread_name":"th_a","timestamp":"20140609T215328.214711"},"format":"error binding to ${endpoint}: ${what}","data":{"endpoint":"0.0.0.0:45410","what":"bind: Address already in use"}}]}                  node.cpp:483

Edit:
I started the client with --clear-peer-database and --resync-blockchain and got the similar but the block size is 422 and blockchain_get_config is like below:
blockchain_get_config
{
  "blockchain_id": "964b38343dc7337f8d87a16323faaa7c63b95160c73739c6d0a276ef41f37312",
  "block_interval": 15,
  "max_block_size": 104857,
  "target_block_size": 52428,
  "block_reward": "0.104857 XTS",
  "inactivity_fee_apr": 10,
  "max_blockchain_size": 107374182400,
  "symbol": "XTS",
  "name": "BitShares XTS",
  "version": 101,
  "address_prefix": "XTS",
  "min_block_fee": 1,
  "delegate_num": 97,
  "delegate_reg_fee": 10485700,
  "delegate_reward_min": 104857,
  "name_size_max": 63,
  "symbol_size_max": 5,
  "symbol_size_min": 3,
  "data_size_max": 65536,
  "asset_reg_fee": 10485700,
  "asset_shares_max": 1000000000000000
}

I can see logs getting fork and switching but failed.
1861246ms       th_a       handle_message ] CLIENT: just received block 082e59b67949339ddaed7354ceadb965f9713f4b                      client.cpp:461
1861246ms       th_a         on_new_block ] Received block 1754 from the server, current head block is 427                      client.cpp:421
1861246ms       th_a      store_and_index ]            we already know about its previous: f38c12564894e1ac0deee676bd91b7ff957ddf97   chain_database.cpp:355
1861246ms       th_a       switch_to_fork ] switch from fork b7ea78344a5056476537428623d00899a3cead7d to 082e59b67949339ddaed7354ceadb965f9713f4b                      chain_database.cpp:425
1861246ms       th_a     get_fork_history ]                     chain_database.cpp:704
...
1861261ms       th_a           push_block ] attempt to switch to fork failed: 13
bad_weak_ptr:
    {"what":"bad_weak_ptr"}
    th_a  chain_database.cpp:756 pop_block

    {"block_id":"082e59b67949339ddaed7354ceadb965f9713f4b"}
    th_a  chain_database.cpp:438 switch_to_fork, reverting                      chain_database.cpp:1003
« Last Edit: June 09, 2014, 10:34:23 pm by zhangweis »
Weibo:http://weibo.com/zhangweis

Offline jae208

  • Hero Member
  • *****
  • Posts: 525
    • View Profile
Is anyone running their delegate on Digital Ocean servers?
http://bitsharestutorials.com A work in progress
Subscribe to the Youtube Channel
https://www.youtube.com/user/BitsharesTutorials

Offline wackou

Getting segfault on import of the keys I gave in the previous thread... All of the 5 give me a segfault.

https://github.com/BitShares/bitshares_toolkit/issues/253
Please vote for witness wackou! More info at http://digitalgaia.io

Offline HackFisher

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
importing wif keys doesnt work
Code: [Select]
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:222 wallet_import_private_key

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

EDIT: actualy it import key, but show this error
bytemaster fixed that issue earlier today ... see above

Just recompile or do as I stated above (somewhere)

Its on client build from git commit 91d857e916a4d8f9c54b11242ef86501a4a67af3
so its recompiled one

Would you please pull and try again? The Keyhotee imported info should be the same with you foundation registered, if you are importing a founder ID in genesis block.
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.

Offline welk1n

  • Jr. Member
  • **
  • Posts: 26
    • View Profile
I have found the 4 accounts 
They are  init-delegate-30   init-delegate-31  init-delegate-32  init-delegate-33.

And I check it with the command as follow, are they working well now?


welk1n (unlocked) >>> blockchain_get_account_record init-delegate-30
{
  "id": 30,
  "name": "init-delegate-30",
  "public_data": null,
  "owner_key": "XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx",
  "active_key_history": [[
      "19700101T000000",
      "XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx"
    ]
  ],
  "delegate_info": {
    "votes_for": 95353683578,
    "votes_against": 0,
    "blocks_produced": 36,
    "blocks_missed": 11,
    "pay_balance": 504042,
    "next_secret_hash": "f80e9fc97861a1c41c642065bdacef79627190c9",
    "last_block_num_produced": 1553
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null
}
welk1n (unlocked) >>> blockchain_get_account_record init-delegate-31
{
  "id": 31,
  "name": "init-delegate-31",
  "public_data": null,
  "owner_key": "XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj",
  "active_key_history": [[
      "19700101T000000",
      "XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj"
    ]
  ],
  "delegate_info": {
    "votes_for": 114694827064,
    "votes_against": 0,
    "blocks_produced": 38,
    "blocks_missed": 10,
    "pay_balance": 543807,
    "next_secret_hash": "8f90fc58b18a207ef2cae267c2ecfe95d05829f6",
    "last_block_num_produced": 1556
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null
}
« Last Edit: June 09, 2014, 09:02:39 pm by welk1n »

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
    "blocks_produced": 1,
    "blocks_missed": 12,
    "pay_balance": 2582,




Code: [Select]

pan2pan (locked) >>> wallet_get_account init-delegate-5
{
  "index": 5,
  "id": 5,
  "name": "init-delegate-5",
  "public_data": null,
  "owner_key": "XTS6tmvXdn2vJss4a4ADVUUi8GbAC37H6HJRcVeFyhzcsRUNyQJGE",
  "active_key_history": [[
      "19700101T000000",
      "XTS6tmvXdn2vJss4a4ADVUUi8GbAC37H6HJRcVeFyhzcsRUNyQJGE"
    ]
  ],
  "delegate_info": {
    "votes_for": 105200579812,
    "votes_against": 0,
    "blocks_produced": 1,
    "blocks_missed": 12,
    "pay_balance": 2582,
    "next_secret_hash": "06f80f24eed63854c49fbaf0769268815c81f94c",
    "last_block_num_produced": 148
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null,
  "account_address": "XTSDF8yKeZHAMeJbTM9YtGRaoMUXR1bUECWD",
  "trust_level": 0,
  "private_data": null
}

微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Could some of you attempt to use this API call to import your keyhotee IDs:

wallet_import_keyhotee <firstname> <middlename> <lastname> <brainkey> <keyhoteeid>                   

I tryed to do so. It said OK, but i didnt see any changes in wallet

try rescan

Did that. It should import alexxy as keyhotee id, but i already has such account

It was a bug to allow you to even create the account when one with that name was already registered. You'll probably have to wipe your wallet and then import your key again

Already tryed that. But it doesnt allow ti import keyhotee then. Saying that i should create account first

That is also a bug =P
filing now
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Could some of you attempt to use this API call to import your keyhotee IDs:

wallet_import_keyhotee <firstname> <middlename> <lastname> <brainkey> <keyhoteeid>                   

I tryed to do so. It said OK, but i didnt see any changes in wallet

try rescan

Did that. It should import alexxy as keyhotee id, but i already has such account

It was a bug to allow you to even create the account when one with that name was already registered. You'll probably have to wipe your wallet and then import your key again

Already tryed that. But it doesnt allow ti import keyhotee then. Saying that i should create account first
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
importing wif keys doesnt work
Code: [Select]
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:222 wallet_import_private_key

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

EDIT: actualy it import key, but show this error
bytemaster fixed that issue earlier today ... see above

Just recompile or do as I stated above (somewhere)

Its on client build from git commit 91d857e916a4d8f9c54b11242ef86501a4a67af3
so its recompiled one
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Could some of you attempt to use this API call to import your keyhotee IDs:

wallet_import_keyhotee <firstname> <middlename> <lastname> <brainkey> <keyhoteeid>                   

I tryed to do so. It said OK, but i didnt see any changes in wallet

try rescan

Did that. It should import alexxy as keyhotee id, but i already has such account

It was a bug to allow you to even create the account when one with that name was already registered. You'll probably have to wipe your wallet and then import your key again
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
importing wif keys doesnt work
Code: [Select]
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:222 wallet_import_private_key

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

EDIT: actualy it import key, but show this error
bytemaster fixed that issue earlier today ... see above

Just recompile or do as I stated above (somewhere)