Dry Run 2: The Real Deal

[Xeldal]

Fresh rebuild with latest in ubuntu 14.04

Code Select Expand

"bitshares_toolkit_revision": "b81f9ac56623a4ae8bbc608b8a1f819e48938ac1",
  "bitshares_toolkit_revision_age": "70 minutes ago",
  "fc_revision": "9002b024693a8ac749a4d5f0b64821b2a1e8eab9",
  "fc_revision_age": "6 hours ago",
  "compile_date": "compiled on Jun 17 2014 at 21:08:07"

I've got connections droping and joining back and forth, very actively

Code Select Expand

}
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- syncing with p2p network, 11207 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- syncing with p2p network, 11210 blocks left to fetch
--- there are now 7 active connections to the p2p network
--- there are now 8 active connections to the p2p network
--- syncing with p2p network, 11212 blocks left to fetch
--- syncing with p2p network, 11213 blocks left to fetch
--- there are now 7 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- syncing with p2p network, 11214 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network


and a "block count left to fetch" that just keeps increasing

Code Select Expand

--- syncing with p2p network, 11212 blocks left to fetch
--- syncing with p2p network, 11213 blocks left to fetch


stuck on block 6410

Code Select Expand

"blockchain_head_block_num": 6410,
  "blockchain_head_block_time": "20140618T010915",
  "blockchain_head_block_time_rel": "28 minutes old",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 5.6297156123041203,
  "network_num_connections": 9,
  "ntp_time": "20140618T013657.384359",
  "ntp_error_seconds": -0.082447000000000006,
  "wallet_unlocked_seconds_remaining": 998505,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140618T013657",
  "blockchain_random_seed": "a2de675ff3e5ae6032860b538e21793d78960fb0",
  "blockchain_shares": 10000142881983,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140629T145842",
  "wallet_version": 100


[muse-umum]

I'm eagerly awaiting dry run 3.  The new chain hasn't launched yet has it?

Waiting for updates from Eric.

Will the next dry run go with GUI? 

[bytemaster]

I'm eagerly awaiting dry run 3.  The new chain hasn't launched yet has it?

Waiting for updates from Eric.

[puppies]

I'm eagerly awaiting dry run 3.  The new chain hasn't launched yet has it?

[cgafeng]

blockchain_list_forks not work

Code Select Expand


(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
    {"block_id":"f54461de391b568340f93083999858a32613a438"}
    th_a  chain_database.cpp:1574 get_block_num

    {}
    th_a  common_api_client.cpp:222 blockchain_list_forks

    {"command":"blockchain_list_forks"}
    th_a  cli.cpp:570 execute_command
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
  "bitshares_toolkit_revision_age": "18 hours ago",
  "fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
  "fc_revision_age": "25 hours ago",
  "compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>


Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564

It works on windows.

[alt]

Great!
But I can't test this, because the chain database is clear and redownload  after upgrade.

blockchain_list_forks not work

Code Select Expand


(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
    {"block_id":"f54461de391b568340f93083999858a32613a438"}
    th_a  chain_database.cpp:1574 get_block_num

    {}
    th_a  common_api_client.cpp:222 blockchain_list_forks

    {"command":"blockchain_list_forks"}
    th_a  cli.cpp:570 execute_command
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
  "bitshares_toolkit_revision_age": "18 hours ago",
  "fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
  "fc_revision_age": "25 hours ago",
  "compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>


Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564

[vikram]

blockchain_list_forks not work

Code Select Expand


(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
    {"block_id":"f54461de391b568340f93083999858a32613a438"}
    th_a  chain_database.cpp:1574 get_block_num

    {}
    th_a  common_api_client.cpp:222 blockchain_list_forks

    {"command":"blockchain_list_forks"}
    th_a  cli.cpp:570 execute_command
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
  "bitshares_toolkit_revision_age": "18 hours ago",
  "fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
  "fc_revision_age": "25 hours ago",
  "compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>


Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564

[alt]

load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .

Code Select Expand


Creating default config file "/home/alt/.BitSharesXTS/config.json"


Default directory was restored to the ~/.BitSharesXTS on Linux per: https://github.com/BitShares/bitshares_toolkit/issues/291

Linux users will want to move their wallets from ~/.BitShares\ XTS to ~/.BitSharesXTS.

thx
for user who run in linux, pay attention, rename the dir name when you update client.

[vikram]

load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .

Code Select Expand


Creating default config file "/home/alt/.BitSharesXTS/config.json"


Default directory was restored to the ~/.BitSharesXTS on Linux per: https://github.com/BitShares/bitshares_toolkit/issues/291

Linux users will want to move their wallets from ~/.BitShares\ XTS to ~/.BitSharesXTS.

[alt]

load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .

Code Select Expand


Creating default config file "/home/alt/.BitSharesXTS/config.json"


[toast]

my delegate "crazybit " still in the inactive list ,could anyone pls give me some trust, would like to test the block generation.

putting you in dry run 3

[alt]

blockchain_list_forks not work

Code Select Expand


(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
    {"block_id":"f54461de391b568340f93083999858a32613a438"}
    th_a  chain_database.cpp:1574 get_block_num

    {}
    th_a  common_api_client.cpp:222 blockchain_list_forks

    {"command":"blockchain_list_forks"}
    th_a  cli.cpp:570 execute_command
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
  "bitshares_toolkit_revision_age": "18 hours ago",
  "fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
  "fc_revision_age": "25 hours ago",
  "compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>


[crazybit]

my delegate "crazybit " still in the inactive list ,could anyone pls give me some trust, would like to test the block generation.

[bytemaster]

Here is the actual console output:

Code Select Expand


--- in sync with p2p network
--- there are now 29 active connections to the p2p network
--- syncing with p2p network, 246 blocks left to fetch
--- there are now 29 active connections to the p2p network
--- there are now 29 active connections to the p2p network
emski (unlocked) >>> get_info
{
  "blockchain_head_block_num": 16429,
  "blockchain_head_block_time": "20140617T201115",
  "blockchain_head_block_time_rel": "24 seconds old",
  "blockchain_confirmation_requirement": 1,
  "blockchain_average_delegate_participation": 77.106518282988873,
  "network_num_connections": 29,
  "ntp_time": "20140617T201139.063736",
  "ntp_error_seconds": 4.4679169999999999,
  "wallet_unlocked_seconds_remaining": 2891931396,
  "wallet_next_block_production_time": "20140617T201530",
  "wallet_seconds_until_next_block_production": 231,
  "wallet_local_time": "20140617T201139",
  "blockchain_random_seed": "e2436f9c12cce0ef0198c92e2ae5458d2f9c56e0",
  "blockchain_shares": 10000642668612,
  "network_num_connections_max": 60,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "19691231T235959",
  "wallet_version": 100
}
--- in sync with p2p network



Was I on a fork just before the message:
"--- syncing with p2p network, 246 blocks left to fetch"
And then synchronized ?

Yes that is a confusing message, but Eric says it is ok (just misleading)

[zhangweis]

Today the delegates are incentive to produce blocks by getting reward and punished only by votes.

I guess people are lazy to vote and I think we can further punish the delegate for missing blocks like this:

The reward for each block will be (normal reward)*(blocks produced in last 10000 blocks)/(blocks should have produced in last 10000 blocks). This means the more you miss, the less you can get the reward. Of course, you can be recovered if you continuously produce blocks for 10000 blocks (100 turns).