Score Management Committee - Results for week ending 28/09/2025

Mainnet
1

This is the 25th 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

  • 0x5665D72AC368124d496995EaAEDF9998e080Fc11 (CeloPG), RPC downtime for the week was above 20%, score set to 0.8
  • 0x31f3245beA3A104478498c88D295CBf12c210ee8 (CeloPG-2), RPC downtime for the week was above 20%, score set to 0.8
  • celvaly-1 (0x989F3F2684F96B8cDeC308B4E7538A5a062890f0), RPC downtime for the week was above 20%, score set to 0.8
  • Projecttent 1 (0xCDd88f80ed52AfEc9D670f5a6Da8940EEe716f45), RPC downtime for the week was above 20%, score set to 0.8
  • v0 (0xB29438f402da218180bBa79fbc0fAdD3e9E151aa), RPC downtime for the week was above 20%, score set to 0.8
  • coinwar (0xC4C51aACa587F16006E9a5F6ccc74a99eBEB37A1), RPC downtime for the week was above 20%, score set to 0.8
  • missionquorum-2 (0xdb2e80840f40033761A5cdFa3B09fE24f95a4aaa), RPC downtime for the week was above 20%, score set to 0.8
  • missionquorum-0 (0x39b01620ecdEB8347270ee78dC962b0EA583b57a), RPC downtime for the week was above 50%, score set to 0.6

Scores below 1 with SLASHING

  • GoodLabs (0x134ec18a2C8a6d12A57C77F336c7615000A5A78D), RPC downtime for the week was above 80%, score set to 0 and will be SLASHED
  • TDlabs (0x92aAe14a531086A665DAFF6eEdb5B71E00aCC6d1), RPC downtime for the week was above 80%, score set to 0 and will be SLASHED
  • Volt (0xdD8067c6BB86C0f755188362C7089c1ACd42b60d), RPC downtime for the week was above 80%, score set to 0 and will be SLASHED
3 Likes
2

Scores back to 1

  • Bi23 (0x997490F08B9b99dB00657e2B1BbEc180Cf804A27), RPC downtime below threshold, score set back to 1.0
  • celvaly-0 (0xe8302a78c4eB56Ac1cd1d6aee25719dC54C63E59), RPC downtime below threshold, score set back to 1.0
  • celvaly-2 (0x9038D66a9b101C32Bd661e8861B8e61086A74c52), RPC downtime below threshold, score set back to 1.0
  • Keyko-1 (0x233c06EDc757003cA4ec078012F517F21A24C55c), previously slashed, RPC downtime now below threshold, score set back to 1.0
  • Validator.Capital2 (0x07adF41F00dD7Ec9C63c445f3faD5cCbdc2a7c85), RPC downtime below threshold, score set back to 1.0
  • Validator.Capital3 (0x3ABE54fe87f77D18b472e47920934CE63b1F6bfc), 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. Those changes will apply for another week until we review the scores again on 05/10/2025.

2 Likes
3

Execution

Transactions were executed on Monday 29/09/2025 as the following:

4

gm @Thylacine @kamikazechaser
We never saw our score going back to 1 (or maybe we missed it), but we assume we are on 1 at the moment is that right? or we are still under 1.0?

Our Validator Group: 0xd42Bb7FE32cDf68045f49553c6f851fD2c58B6a9

5

Your score is 100% so no worries, we might have just got our reporting mixed up. I’ll confirm in the morning.

6

Just confirmed, you were set back to 1.0 a few weeks ago: Score Management Committee - Results for week ending 07/09/2025

1 Like