Score Management Committee - Results for week ending 10/08/2025

Mainnet
1

This is the 18th 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 here, we need to take no action and your validator score remains: 1.0 (full payment, claimable each epoch).

Scores below 1

  • GoodLabs (0x134ec18a2C8a6d12A57C77F336c7615000A5A78D), RPC downtime for the week was at 100%, keep score at 0 (slash when possible)

  • huglester (0x5e69Cca114a77AB0a5804108FAF0cD1E1C802A5e), RPC downtime for the week was at 100%, keep score at 0 (slash when possible)

  • missionquorum-0 (0x39b01620ecdEB8347270ee78dC962b0EA583b57a), RPC downtime for the week was at 100%, keep score at 0 (slash when possible)

  • missionquorum-2 (0xdb2e80840f40033761A5cdFa3B09fE24f95a4aaa), RPC downtime for the week was at 100%, keep score at 0 (slash when possible)

  • censusworks.3 (0xB9a188Db0aFc72dCb817E20ff5A2F247718aAbF3), RPC downtime for the week was above 20%, score set to 0.8

  • Bi23 (0x997490F08B9b99dB00657e2B1BbEc180Cf804A27), RPC downtime for the week was above 20%, score set to 0.8

Scores back to 1

  • AGx1-Arnold (0x943e9a5c750adcc467575F4fE81bf6b1C3A2aeD7), RPC downtime for the week was above the required threshold, set score back to 1.0

  • AGx2-Bruce (0xa2393Abeeea68558C70Ac8641C442F096e0530D4), RPC downtime for the week was above the required threshold, set score back to 1.0

  • AGx3-Chuck (0xBC1E19291b7582d1199ca0D73512d93A41CB4d80), RPC downtime for the week was above the required threshold, set score back to 1.0

  • CypherCore-2 (0x53EE2F047A2F12a2d0792a33BBA1F20396f8d590), RPC downtime for the week was above the required threshold, set score back to 1.0

  • Eat Pray Validate 2 (0x9F49E9Ec7199455Dda0B116785470fbAfb4C0B50), RPC downtime for the week was above the required threshold, set score back to 1.0

  • impactMarket-1 (0x8d1A5eF84252586f0f841a9fCF4E31f23c4c21E0), RPC downtime for the week was above the required threshold, set score back to 1.0

  • impactMarket-2 (0xDF9121AFFb220e9095C875a79c3D1fA3EBEE4105), RPC downtime for the week was above the required threshold, set score back to 1.0

  • impactMarket-4 (0x5b9F5239b10f1d74Ea89F88FE3d50db7eCD6e450), RPC downtime for the week was above the required threshold, set score back to 1.0

  • PlusV N2 (0x52949f71f71f6E5A6EfCab0f16C8fF6711A84780), RPC downtime for the week was above the required threshold, set score back to 1.0

  • team-rpc-node-2 (0x8204B94EDCdd3130E709515F690eC99f623aE6aA), RPC downtime for the week was above the required threshold, set score back to 1.0

  • v0 (0xB29438f402da218180bBa79fbc0fAdD3e9E151aa), RPC downtime for the week was above the required threshold, set score 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. Those changes will apply for another week until we review the scores again on 17/08/2025.

2 Likes
2

How some body can be part of scoring system

3

can I have celo support e-mail, I would like to be connected to score system

thank you

Jean

4

Execution

Transaction was executed: Celo Mainnet transaction 0x42e2641d12a1459322a6d7f0ebab3240f045a25d41df4d62b7deccb84f93f41b | Blockscout

1 Like
5

Thanks for your interest! During the CELO migration to Layer 2, a Score Management Committee was created to oversee the scoring system. This group is already in place and there are currently no plans to change its members.