Quote from: alt on June 17, 2014, 11:34:43 pm

blockchain_list_forks not work

Code: [Select]

(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

以下是windows下的界面，因为界面只是在qt里面嵌了一个浏览器控件，所以和直接用浏览器看到的界面是一样的。
1、创建钱包界面


2、帐号界面


3、转账界面


4、地址簿界面，这里可以查询到所有注册的名称


5、代理界面

There are 5 pages of comments that I haven't caught up on, but I wanted to post an update on where we are:

1) Clock drift is causing some nodes to fail to validate blocks.  Apparently it can drift by as much as 5 seconds or more per day and we only do NTP sync on launch.   Blocks were failing because their time was 'in the future' and this would cause forks.

2) We found a bug where transactions on forks are not saved and thus we fail to switch to the fork.  This would exasperate #1

3) If your client is the one with the bad clock then you can get stuck because once block is 'failed' it will never retry.  This will leave you stuck until you re-sync.

We are preparing fixes for these issues now which should be relatively straight forward and should have it all resolved today.