ChainSafe / ChainSafe/gossamer-parity

Implement consensus reward statistics collector subsystem

Open
#22 3 comments 0 reactions 1 assignee Claimed by @EclesioMeloJunior View on GitHub
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Issue summary

> In an epoch $e$, each validator $u$ counts of the number $\alpha_{u,v}$ of votes they *used* from each validator $v$, including themselves. Any time a validator marks a candidate approved, they increment these counts appropriately.

We should create a subsystem capable of collect useful approvals usage and availability distribution downloads and uploads

## DoD

- [x] Create the subsystem collection
- [x] Collect useful approvals
- [x] Collect downloaded chunks
- [x] Collect uploaded chunks
- [x] Metrics should include how much storage will tally take in case of on-chain reward calcualtion to fulfill this issue #43
- [x] Implement tests for consensus statistics collector subsystem
- [x] Implement tests for the changes in the approval voting subsystem
- [x] Publish data from consensus statistics collector subsystem through prometheus
- [ ] Implement Zombienet tests with Malus nodes to test no-shows stats collections

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.