Quote from: kenCode on January 05, 2016, 07:11:34 pm

Site is down:
 
We're sorry, but something went wrong.
------------------------------------------------
If you are the application owner check the logs for more information.

Thanks Ken.. looking into it. witness_node was frozen, and I'm having trouble getting it running again..

Code: [Select]

3229214ms th_a       witness.cpp:86                plugin_initialize    ] witness plugin:  plugin_initialize() begin
3229214ms th_a       witness.cpp:96                plugin_initialize    ] key_id_to_wif_pair: ["......","....."]
3229214ms th_a       witness.cpp:114               plugin_initialize    ] witness plugin:  plugin_initialize() end
3229214ms th_a       application.cpp:354           startup              ] Replaying blockchain on user request.
3229214ms th_a       application.cpp:292           operator()           ] Initializing database...
3243588ms th_a       db_management.cpp:48          reindex              ] reindexing blockchain
3243590ms th_a       db_management.cpp:101         wipe                 ] Wiping database
3243620ms th_a       object_database.cpp:84        wipe                 ] Wiping object database...
3243643ms th_a       object_database.cpp:86        wipe                 ] Done wiping object databse.
3243643ms th_a       object_database.cpp:91        open                 ] Opening object database from /home/bitshares-2/witness_node_data_dir/blockchain ...
3243643ms th_a       object_database.cpp:97        open                 ] Done opening object database.
3257917ms th_a       db_debug.cpp:82               debug_dump           ] total_balances[asset_id_type()].value: 12205723874026 core_asset_data.current_supply.value: 253409943611989
3257951ms th_a       db_management.cpp:55          reindex              ] !no last block
3257951ms th_a       db_management.cpp:56          reindex              ] last_block:
3258068ms th_a       thread.cpp:95                 thread               ] name:ntp tid:140271469905664
3258080ms th_a       thread.cpp:95                 thread               ] name:p2p tid:140271448925952
3258091ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 83.221.132.47:1776
3258130ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 7706 us
3258170ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 188.40.91.213:1776
[....]
3258535ms th_a       application.cpp:173           reset_p2p_node       ] Adding seed node 109.73.172.144:50696
3258536ms th_a       application.cpp:184           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:56537
3258542ms th_a       application.cpp:234           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
3258543ms th_a       witness.cpp:119               plugin_startup       ] witness plugin:  plugin_startup() begin
3258543ms th_a       witness.cpp:136               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
3258543ms th_a       witness.cpp:137               plugin_startup       ] witness plugin:  plugin_startup() end
3258543ms th_a       main.cpp:176                  main                 ] Started witness node on a chain with 0 blocks.
3258543ms th_a       main.cpp:177                  main                 ] Chain ID is 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8
[end of output]
Haven't seen this before,, any ideas?

Sometimes when I had this "can't start" issue is because another witness_node process is running and listening on the same port.

@xeroc latest version (commit 3c7b2ca1b68e33fbf47aa9d66005613b83ca1f51) with Btc38's BTS/BTC market enabled by default causes a 10% off on BTS/CNY price.
|  CNY   | 0.02429415 | 0.02342230 (+3.72%) | 0.02433542 (-0.17%) | 0.02429415 (+0.00%) |  0.03% ( 5)  | 0.02209000 (+9.98%) | 0.02209988 (+9.93%) | 1:48:02.671795 ago |    X    |
blame file here: https://drive.google.com/open?id=0B3xrm70jSHn4V2dBX1duaEZ5OEE

Another minor error on my server:
Error fetching results from Ccedk! ('bool' object is not subscriptable)


好像有点道理。
不过我觉得，交易所可能不愿来掺和社区的事情，宁愿默默地赚钱。

FYI we had some discussions about how to efficiently pay dividends long time ago, a claim model.
https://bitsharestalk.org/index.php?topic=14785.msg191711#msg191711

Basically, distributing fees among referrers/registrars is an operation which cost linear to the amount of operations within a maintenance interval, but distributing funds among asset holders is linear to the amount of holders. The former is doable in the maintenance interval, but the latter is not.

Exchanges should be notified individually of things like this if you want them to keep up to date. How difficult is it to send an email?

It's easy. After click the "notify" button above/below a thread, you'll get an email when there is a new reply in that thread.

Quote from: abit on January 05, 2016, 10:11:19 am

Quote from: cube on January 05, 2016, 01:10:56 am

I think the review period is before the proposal expiration and no one can vote during the review period.

I don't think so. If no one can vote, how to "review"?

The review period is for shareholders to review their vote for their committee members and they can vote out the active members and vote in other non-active members.

You are correct. I've updated my post.

FYI the new seed node 114.92.254.159:62015 which has been added in last patch (2.0.160103) is mine, located in China. I'm not sure if it's better to use a domain name though, currently the node will crash if failed to resolve a domain name.

The purpose of this BSIP is to minimize the cost incurred by the network doing unnecessary operations every maitenance interval.

Every hour votes are tallied and 99% of the time there is no meaningful change. Under this proposal, votes would only be tallied when requested by a user and at most once per maintenance interval. The fee for tallying votes would be around $5.

Users of the system can determine whether or not there is a $5 difference in votes that would justify a re-tally. A worker, witness, or committee member who got voted in would pay $5 to have the vote counted.

The side effect of this behavior would be to greatly improve reindexing performance, the vast majority of which is spent tallying votes that never change.

Witnesses producing blocks on the maintenance interval can pre-tally the votes and compare them to the last value. They can then indicate whether or not anything changed significantly in the block they produce.

If there is no one who stands to benefit by more than $5 then chances are it is an unnecessary update to the voting totals.

Ideas to improve performance are always good.
However, to implement this BSIP, it's needed to implement "Maintain Proxy Voting Totals ($3000)" (https://github.com/cryptonomex/graphene/issues/454) first, otherwise a common user may have no way to check who would be voted in on next maintenance interval, then she would perhaps trigger that every hour.