1171
General Discussion / Re: Dry Run 5: The Final Countdown
« on: June 25, 2014, 07:09:11 am »Strange that my delegates too-young and too-simple are always missing blocks. They are among the top 101.wallet_enable_delegate_block_production ?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Strange that my delegates too-young and too-simple are always missing blocks. They are among the top 101.wallet_enable_delegate_block_production ?
I just noticed a block with a timestamp almost 30 seconds in the future... very curious.Wasnt me, at least not intentionally. My server's time is synchronized via ntp.
emski (unlocked) >>> info
{
"blockchain_head_block_num": 2948,
"blockchain_head_block_time": "20140625T061600",
"blockchain_head_block_time_rel": "53 seconds old",
"blockchain_confirmation_requirement": 303,
"blockchain_average_delegate_participation": 58.550724637681157,
"network_num_connections": 31,
"ntp_time": "20140625T061653.296005",
"ntp_error_seconds": 0.001075,
"wallet_unlocked_seconds_remaining": 999998940,
"wallet_next_block_production_time": "20140625T061900",
"wallet_seconds_until_next_block_production": 127,
"wallet_local_time": "20140625T061653",
"blockchain_random_seed": "b0f162d7132eff5f36b57b5302fd9836386540b6",
"blockchain_shares": 199999115209829,
"network_num_connections_max": 200,
"network_protocol_version": 103,
"wallet_open": true,
"wallet_unlocked_until": "19100126T011737",
"wallet_version": 100
}
emski (unlocked) >>> blockchain_list_forks
[
1842,
2577,
2631,
2938,
2940,
2943
]
--- there are now 30 active connections to the p2p network
emski (unlocked) >>> pure virtual method called
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
what(): receive_from: Resource temporarily unavailable
Aborted (core dumped)
Is someone doing some spam testing?Me, results posted above.
emski (unlocked) >>> info
{
"blockchain_head_block_num": 2941,
"blockchain_head_block_time": "20140625T060600",
"blockchain_head_block_time_rel": "45 seconds old",
"blockchain_confirmation_requirement": 303,
"blockchain_average_delegate_participation": 58.720930232558139,
"network_num_connections": 32,
"ntp_time": "20140625T060645.437978",
"ntp_error_seconds": 0.001075,
"wallet_unlocked_seconds_remaining": 999999548,
"wallet_next_block_production_time": "20140625T061000",
"wallet_seconds_until_next_block_production": 195,
"wallet_local_time": "20140625T060645",
"blockchain_random_seed": "1cf580c025e9d7d048da0307920d80b6d256c3e8",
"blockchain_shares": 199999133938247,
"network_num_connections_max": 200,
"network_protocol_version": 103,
"wallet_open": true,
"wallet_unlocked_until": "19100126T011737",
"wallet_version": 100
}
--- in sync with p2p network
emski (unlocked) >>> blockchain_list_forks
[
1842,
2577,
2631,
2938,
2940
]
--- there are now 33 active connections to the p2p network
--- in sync with p2p network
emski (unlocked) >>> about
{
"bitshares_toolkit_revision": "c0a8c268cd65dd7a7e4a7af0ef6f5c6c1ef763f8",
"bitshares_toolkit_revision_age": "32 minutes ago",
"fc_revision": "87a93940d046cc6715b67d9380dd280c27bdd867",
"fc_revision_age": "10 hours ago",
"compile_date": "compiled on Jun 25 2014 at 08:57:10"
}
The client seems to be responsive now.
appears a lot of people haven't updated since fork resolution code:
bts101/2/3
emski ?
immortal ?
wackou?
asia?
taolj?
Dan just pushed a possible fix for the forking issue, please updateThen I went to sleep. I'll update again now and test.
Hi core team,Dont you want to wait an hour to see if the network decides the correct branch?
Could you please make a formal public announcement about the fork issue? The cause, the status, the difficult part, or what are being tried.
Thanks.
Am I correct?You are! Maybe in a few more weeks we can run this through TOR itself .. that would be AWESOME!
emski (unlocked) >>> wallet_account_balance
emski:
142,111.51466 XTS
angel:
10.00000 XTS
batman:
100.00000 XTS