This is the 31st 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.
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
- 0x88551845c76056518E16935e85C9b4b57813cA9E (team-rpc-node-1), RPC downtime for the week was above 20%, score set to 0.8
- 0x8204B94EDCdd3130E709515F690eC99f623aE6aA (team-rpc-node-2), RPC downtime for the week was above 20%, score set to 0.8
- 0x9d4b7EE0b21B4aE50143499D5A7f4833B7f07a56 (rpc-3.celopg.eco), RPC downtime for the week was above 20%, score set to 0.8
- 0x4E3c453b4897451E6f84C6869f533cA04250259a (galactic-validator-c1), RPC downtime for the week was above 20%, score set to 0.8
Scores back to 1
- 0x474df04481f778b46Fc71204C72B6A8BE396F0FF (Zanshin-v0), RPC downtime below threshold, score set back to 1.0
- 0x307d958d9f0235058fE0a7e7e717A63d5aD6B143 (Zanshin-v1), 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 09/11/2025.