Sākums Izpētīt Palīdzība
Reģistrēties Pierakstīties
Operations
/
community-repo
3
0
Atdalīts 0
Faili Problēmas 0 Izmaiņu pieprasījumi 0 Vikivietne
Atzars: daily-council-bot-jsstats
Atzari Tagi
community-repo
/
council
/
kpi
/
sumer
/
31.I-7
Joystream Stats b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
..
Offences.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
README.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-08-31.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-09-07.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-09-14.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-09-21.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-09-28.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-10-05.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-10-12.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-10-19.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-10-26.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
Validator_points_2021-11-02.md b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
filter_events.js b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
offences.json b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
offences.svg b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
package.json b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
points.json b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ
yarn.lock b253357b69 KPI 31.I-7 Joystream Node Issues 3 gadi atpakaļ

README.md

31.I-7 - Joystream Node Issues

  1. See Offences

  2. Rewards (generate as described in Verfify below)

  3. Offences shows no significant irregularities around blocks #2661218 and #2661813. Only 5CSbnQLeemPiiLBx99CPu3rRSxJqSiFcECygVegdH42Yf6De was offline before and after. However between era blocks #2661121 and #2661218 lie 97 blocks, 3 less than the usual 100 blocks, indicating that some blocks were delayed (possibly due to inresponsive validator(s)).

Rewards: Comparing the validator sets in blocks #2661074 (69 validators) and #2661282 (68 validators) revealed that 5FcKL1644dNevezrVCHmNEfPTX35LxqcwCAvEswp94iURA41 went offline at the time of the first incident at block #2661218. The next payout after #2661813 at #2662531 rewarded only 60 validators.

At 2664121 (60) and 2664127 (36) all points were divided between two addresses: 5FZ8vJhCLm8veh6MeqGmXMD19gVW3zjBaTqHaC7T4FyYhti5 and 5FYu2adiXmhpLzJr1hZsJeFLMxjJKcfd82WTm2WyyjCGV11u. This pattern repeated at several occations and can be confirmed inspecting the raw blocks.json.

Verify

Download and extract block_events.tar.xz to contributions/tech/report-generator/cache (or generate your own).

$ cd council/kpi/sumer/31.I-7
$ yarn
$ node filter_events.js ../../../../contributions/tech/report-generator/cache/2*
Loaded 1094389 blocks.