Week of 27/04/2025
This is the third of a weekly series of reports on our off-chain score keeping system for the elected validator / community RPC set. Each week on Sunday we will publish our next actions for the score management multi-sig, and open up the dispute period.
Changed Scores
We will only report any deviations from a full score. If you are not listed here, we need to take no action and your validator score remains: 1.0 (full payment, claimable each epoch).
-
missionquorum-0 (
0x39b01620ecdEB8347270ee78dC962b0EA583b57a), RPC downtime for the week was ~ 65%, set score to 0.4 -
missionquorum-2 (
0xdb2e80840f40033761A5cdFa3B09fE24f95a4aaa), RPC downtime for the week was ~ 65%, set score to 0.4
Notable changes to score reporting
Elapsed downtime will be calculated as a percentage of the week. Thus, validators elected for a partial week will have the same downtime limits in hours. Scoring has been adjusted to now measure downtime instead of uptime. As a result, the score starts at 1.0 and counts down the duration of downtime over the course of a full week.
Next Steps
The dispute period is now open for approximately 24 hours, after which, we will execute the above score changes if there are no challenges. Those changes will apply for another week until we review the scores again on 04/05/2025.
Updates to Vido
Weekly score summaries are now integrated into the Vido CELO Metrics section. The Vido CELO Community RPC section now offers the option of using different backend API endpoints, allowing users to fetch and display measurements from various score management committee members. Thanks, @thylacine!