Viewing a response to: @lukestokes/re-biteosdev-eos-bp-block-tracking-report-20180720-20180720t194952200z
You are probably right on the latency issue , it was something I was concerned some time ago , but did not look to be an issue till now This report dont really show missed blocks , but produced blocks , I know it is a thick approach , but may alert on some problems I am working on make a more accurate reports , based on the blocks a BP should have produced for each production schedule change .I am setting up the mongo database and will code the logic
author | biteosdev |
---|---|
permlink | re-lukestokes-re-biteosdev-eos-bp-block-tracking-report-20180720-20180721t082921973z |
category | eos |
json_metadata | {"tags":["eos"],"app":"steemit/0.1"} |
created | 2018-07-21 08:28:24 |
last_update | 2018-07-21 08:28:24 |
depth | 2 |
children | 0 |
last_payout | 2018-07-28 08:28:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 458 |
author_reputation | 64,421,466,767 |
root_title | " EOS BP Block Tracking Report 20180720" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 65,454,140 |
net_rshares | 0 |