seems like i'm on fork also

  "blockchain_head_block_num": 5543,
  "blockchain_head_block_time": "20140611T160700",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 28.877642155403393,
  "network_num_connections": 3,


Quote from: alexxy on June 10, 2014, 02:44:33 pm

Any idea WTF this is. Its happend after latest git pull

Code: [Select]

alexxy (unlocked) >>> wallet_list_receive_accounts
NAME                               BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL   
rob                                XTS5UEnYkxWvjHRX4qe16KpYRdwiEBfK51TNJe9UB8FKKjmBkN9cw           2014-06-01T00:00:00   0             
richard                            XTS75TAiDdzhZJQbw8aDtvXGwM1QV3PqbUgjwbEzQQqggJ5EQmiE5           2014-06-01T00:00:00   0             
qq-com                             XTS7Jr9XcHVrvJYGek2FLaRrxz4xkzTyLkDyxVE998EHhwxTz1M1A           2014-06-01T00:00:00   0             
init-delegate-7 (delegate)         XTS5H3qwDsnjm8yoiN1CAQg6LKTnSNuXZDePeGAQSa5CiALSFRFQ8           2014-06-01T00:00:00   0             
init-delegate-3 (delegate)         XTS7bUdQ41J4vhNVBkmbqDKGiftrmQNrL1vCx881Fg4R2hE5r6P2Z           2014-06-01T00:00:00   0             

Seems like its non uniq priv keys!

This is a wallet sync bug. You don't actually own those key =P
But the bad news is that you will have to wipe your wallet after we fix it.

Seems like bitder found the bug:

Quote

This is a problem/bug with the wallet account mixing up the "id" and "index".
All my delegates (26,27,28,29) had the id=(26,27,28,29) but the index=(3,5,7,9) so when the client is restarted they load with the wrong id (because it's using the index).

Sure its a bug =D there should be one fresh generated key. and 4 init-delegates-{78-81} keys

I think its better to use founder code for keyhotee import =\

Quote from: alexxy on June 09, 2014, 07:09:57 pm

Quote from: toast on June 09, 2014, 07:06:16 pm

Quote from: alexxy on June 09, 2014, 07:05:20 pm

Quote from: bytemaster on June 09, 2014, 02:28:13 pm

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

importing wif keys doesnt work
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

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

Ok. My host is xeon.gentoo.ru port 8764
I set max number of connections to 64