Quote from: alexxy on June 13, 2014, 09:38:47 PM
Btw seems like importing keyhotee id doent work. It always said

Code Select Expand


10 assert_exception: Assert Exception
!"Account name is already registered under a different key":
    {}
    th_a  wallet.cpp:817 add_contact_account


Yep, there are apparently issues here as this code was implemented quickly without testing.

Quote from: alexxy on June 13, 2014, 09:21:35 PM
@bytemaster can you share you connected nodes ip? I still have only one connection

I think the problem is all nodes with a public IP are filled up.   If you are running a public node set the "--maximum-number-of-connections" argument to something higher than 12.

I too am only seeing 1 connection from my local computer.

Btw seems like importing keyhotee id doent work. It always said

10 assert_exception: Assert Exception
!"Account name is already registered under a different key":
    {}
    th_a  wallet.cpp:817 add_contact_account


@bytemaster can you share you connected nodes ip? I still have only one connection

Quote from: alexxy on June 13, 2014, 09:17:36 PM
After blockchain resync

Code Select Expand


  "blockchain_head_block_num": 2166,
  "blockchain_head_block_time": "20140613T211630",


Btw does keyhotee id import works?

{
  "blockchain_head_block_num": 2166,
  "blockchain_head_block_time": "20140613T211630",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 42.395104895104893,
  "network_num_connections": 6,
  "wallet_unlocked_seconds_remaining": 2892273106,
  "wallet_next_block_production_time": "20140613T212815",
  "wallet_seconds_until_next_block_production": 706,
  "wallet_local_time": "20140613T211629",
  "blockchain_random_seed": "4f489d9f2842b59467d9fdec51913a1fd565178e",
  "blockchain_shares": 9999952247143,
  "network_num_connections_max": 100,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "19691231T235959",
  "wallet_version": 100
}

After blockchain resync


  "blockchain_head_block_num": 2166,
  "blockchain_head_block_time": "20140613T211630",


Btw does keyhotee id import works?

Quote from: alexxy on June 13, 2014, 08:32:37 PM
Am I on fork?

Code Select Expand


  "blockchain_head_block_num": 1395,
  "blockchain_head_block_time": "20140613T203115",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 27.556818181818183,



{
  "blockchain_head_block_num": 1577,
  "blockchain_head_block_time": "20140613T204045",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 30.417058639071808,
  "network_num_connections": 22,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140613T204435",
  "blockchain_random_seed": "7a2a2b3fecebb31be4824a1624877493c8bbf0d0",
  "blockchain_shares": 9999914511592,
  "network_num_connections_max": 100,
  "network_protocol_version": 101,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100
}

Am I on fork?


  "blockchain_head_block_num": 1395,
  "blockchain_head_block_time": "20140613T203115",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 27.556818181818183,



We have some significant forking still going on at this point in time.  We are working very hard over here to identify the cause.

Some of the steps we have take to mitigate (but not solve) the problem is by increasing the required connection count before a delegate will start producing blocks.

Now we need to solve a bug where a node just stops receiving (or processing) blocks. 

My delegate node (bitcoiners) seems to be inactive. Please vote for it, so it starts producing blocks.

get_info
{
  "blockchain_head_block_num": 1998,
  "blockchain_head_block_time": "20140613T193245",



default (unlocked) >>> blockchain_get_account_record bitcoiners
{
  "id": 299,
  "name": "bitcoiners",
  "public_data": null,
  "owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
  "active_key_history": [[
      "20140613T030845",
      "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
    ]
  ],
  "delegate_info": {
    "votes_for": 0,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140613T030845",
  "last_update": "20140613T031130",
  "meta_data": null
}


default (unlocked) >>> blockchain_list_delegates
...

** Inactive:
...
304         puppies                  17531378            0                   0.000175315 %       0               0               
297         bts101                   5000000             0                   5.00003e-05 %       0               0               
299         bitcoiners               0                   0                   0 %                 0               0             


FYI

Restarted the client and I am now stuck on 1393.

I think I'm back on the main chain.  Actived delegates 13,14,15, and 16.  Inactive delegate puppies (I'm gonna have to change that name before this goes live.)

I've got the qt wallet compiled and running on Ubuntu.  First time I run it, it runs great.  Creates a wallet for me, and has most functions working correctly.  I had to close it due to the fork, and now I don't know how to unlock my wallet from within Qt wallet.  Does anyone know how to wallet_open in Qt client?

how can i transfer xts from wallet A to wallet B？

The test network seems to be working fine now.
I am running delegate 96 in two separate clients. Let's see what'll happen.

Someone try sending test funds to me again please.  I has none.

xeldal-del                         XTS8M923ocWMSb1UF3iA883tYcjCBfWdFK9cJH1YjNNpWJdARy9G4           NO                    0