Delegates, start your engines!

[Xeldal]

"blockchain_head_block_num": 4360,
  "blockchain_head_block_time": "20140611T151115",

[bitcoinerS]

My stats:
 "blockchain_head_block_num": 5562,
  "blockchain_head_block_time": "20140611T150630",

here is mine..

get_info
{
  "blockchain_head_block_num": 2892,
  "blockchain_head_block_time": "20140611T151500",

[emski]

My stats:
 "blockchain_head_block_num": 5562,
  "blockchain_head_block_time": "20140611T150630",

[Harvey]

Am I still on the main block chain?

harvey (unlocked) >>> get_info
{
  "blockchain_head_block_num": 846,
  "blockchain_head_block_time": "20140611T144330",
  "blockchain_confirmation_requirement": 290,
  "blockchain_average_delegate_participation": 5.7433808553971488,
  "network_num_connections": 1,
  "wallet_unlocked_seconds_remaining": 99999999841,
  "wallet_next_block_production_time": "20140611T145845",
  "wallet_seconds_until_next_block_production": 235,
  "wallet_local_time": "20140611T145450",
  "blockchain_random_seed": "5d454f22e86c8eeb0ac1505e1b70b68351a101ff",
  "blockchain_shares": 9999977806267,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "19880505T134930.027953",
  "wallet_version": 100
}

[sfinder]

FYI.
dumpprivkey function does not work. 

[toast]

I filed it, thanks for letting us know

[Xeldal]

Have you rescanned since the fix?
Rescan and then watch for changes - if it still gets out of sync then file an isse

After

Code: [Select]

Xeldal (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK

I still get

Code: [Select]

Xeldal (unlocked) >>> blockchain_get_account_record_by_id 42
{
  "id": 42,
  "name": "init-delegate-42",
  "public_data": null,
  "owner_key": "XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit",
 ...~
    "blocks_produced": 20,
    "blocks_missed": 103,
    "pay_balance": 647337,
 
}
Xeldal (unlocked) >>> wallet_get_account init-delegate-42
{
  "index": 4,
  "id": 42,
  "name": "init-delegate-42",
  "public_data": null,
  "owner_key": "XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit",
...~
    "votes_for": 88888017429,
    "votes_against": 0,
    "blocks_produced": 8,
    "blocks_missed": 25,
    "pay_balance": 76161,


I would file an issue but Im not at all familiar with how that is done.

[toast]

I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

I thought this was fixed, are you on latest?

Code: [Select]

Xeldal (unlocked) >>> about
{
  "bitshares_toolkit_revision": "26d5341e0fc5bf34971259141bec7e2468b862af",
  "bitshares_toolkit_revision_age": "4 hours ago",
  "fc_revision": "51de9e6abf1bc2fbd31794f7b625d83a82f67d3d",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jun 10 2014 at 18:24:51"
}


Have you rescanned since the fix?
Rescan and then watch for changes - if it still gets out of sync then file an isse

[Xeldal]

I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

I thought this was fixed, are you on latest?

Code: [Select]

Xeldal (unlocked) >>> about
{
  "bitshares_toolkit_revision": "26d5341e0fc5bf34971259141bec7e2468b862af",
  "bitshares_toolkit_revision_age": "4 hours ago",
  "fc_revision": "51de9e6abf1bc2fbd31794f7b625d83a82f67d3d",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jun 10 2014 at 18:24:51"
}


[bytemaster]

Hi,

i wonder why do the net votes for delegates never change? Since some delegates producing blocks without missing a single opportunity, other delegates never produced a block at all.
I had the impression that delegate election is forced by the network itself?

It is because there is almost no transaction volume by regular use.

[toast]

I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

I thought this was fixed, are you on latest?

[Xeldal]

I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

[wackou]

PSA: for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)

[alexxy]

Does importing keyhotee works?

[toast]

Hi,

i wonder why do the net votes for delegates never change? Since some delegates producing blocks without missing a single opportunity, other delegates never produced a block at all.
I had the impression that delegate election is forced by the network itself?

Eventually it will be done by the client, and will be configurable per-user. There are no fixed blockchain rules.