This is the 32st in a series of weekly 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.
Note: This post was delayed due to some issues with measurement collection related to some Celo CLI debugging. We will extend the regular dispute period from now for 24 hours and execute the transactions on Tuesday 11th November.
Changed Scores
We will only report any deviations from a full score. If you are not listed below, no action is needed and your validator score remains 1.0 (full payment, claimable each epoch).
Scores below 1
- Hashkey Cloud (0x758d1000fB3d37F88cE3BA880882898a3B0ca3aB), RPC downtime for the week was above 40%, score set to 0.6
Scores back to 1
-
0x88551845c76056518E16935e85C9b4b57813cA9E (team-rpc-node-1), RPC downtime below threshold, score set back to 1.0
-
0x8204B94EDCdd3130E709515F690eC99f623aE6aA (team-rpc-node-2), RPC downtime below threshold, score set back to 1.0
-
0x9d4b7EE0b21B4aE50143499D5A7f4833B7f07a56 (rpc-3.celopg.eco), RPC downtime below threshold, score set back to 1.0
-
0x4E3c453b4897451E6f84C6869f533cA04250259a (galactic-validator-c1), RPC downtime below threshold, score set back to 1.0
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. These changes will apply for another week until we review the scores again on 11/11/2025.