Score Management Committee - Results for week ending 13/04/2025

[Thylacine]

Score Management Committee Results

Week of 13/04/2025

This is the first of a weekly series of reports on our off-chain score keeping system for the elected validator / 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).

• Chorus One Validator1 (0x5098A28bFa2Da3183E36C009c7D63093b66441a5), RPC uptime for the week was 0%, set score to 0.0
• Keyko1 (0x233c06EDc757003cA4ec078012F517F21A24C55c), RPC uptime for the week was ~ 55%, set score to 0.6
• missionquorum-0 (0x39b01620ecdEB8347270ee78dC962b0EA583b57a), RPC uptime for the week was 0%, set score to 0.0
• missionquorum-2 (0xdb2e80840f40033761A5cdFa3B09fE24f95a4aaa), RPC uptime for the week was 0%, set score to 0.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. Those changes will apply for another week until we review the scores again on 20/04/2025.

[Thylacine]

Execution

• After no disputes the scores were updated as above
• Transaction: Celo Mainnet transaction 0x9d73cd959d42f5d0ae41841d0d5e2425cb6d05e399c7a3ede5efbaa5d34d8343 | Blockscout
• Verification: You can call the public/read method getValidatorScore on the ScoreManager contract here: ScoreManagerProxy | Address 0xef3B9CC0FA4717aF6f412d39dBcEb89bf92f603B | CeloScan

[asaoines]

Asa here from MissionQuorum, sorry we dropped the ball we had a bit of a misunderstanding with respect to the L2 migration. I will be working on getting our RPC nodes up this weekend.