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

Mainnet
1

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

  • team-rpc-node-1 (0x88551845c76056518E16935e85C9b4b57813cA9E), RPC downtime for the week was above 85%, set score to 0

  • Mantalabs (0x7328B986cF7e7a1Baf62E257aAFa66abdA4109Ce), RPC downtime for the week was above 60%, set score to 0.4

  • Mantalabs (0xaC6492D439b3b812e822d1e975338f48bDD0B1f2), RPC downtime for the week was above 60%, keep score at 0.4

  • AGx1-Arnold (0x943e9a5c750adcc467575F4fE81bf6b1C3A2aeD7), RPC downtime for the week was above 40%, set score to 0.6

  • AGx2-Bruce (0xa2393Abeeea68558C70Ac8641C442F096e0530D4), RPC downtime for the week was above 40%, set score to 0.6

  • AGx3-Chuck (0xBC1E19291b7582d1199ca0D73512d93A41CB4d80), RPC downtime for the week was above 40%, set score to 0.6

  • dedatalabs-val-2 (0x4aF806c873eb793EA95EF59811964F1Bde05Fb89), RPC downtime for the week was above 40%, set score to 0.6

  • dedatalabs-val-3 (0xC24baEda4Ca0121F07b29CB1c3C44f8516051450), RPC downtime for the week was above 40%, set score to 0.6

  • dedatalabs-val-4 (0x7e1158879D7CC3d18A39A7ffD63Dbd7133248b9f), RPC downtime for the week was above 40%, set score to 0.6

  • Eat Pray Validate 2 (0x9F49E9Ec7199455Dda0B116785470fbAfb4C0B50), RPC downtime for the week was above 40%, set score to 0.6

  • huglester (0x5e69Cca114a77AB0a5804108FAF0cD1E1C802A5e), RPC downtime for the week was above 40%, set score to 0.6

  • missionquorum-0 (0x39b01620ecdEB8347270ee78dC962b0EA583b57a), RPC downtime for the week was above 40%, set score to 0.6

  • missionquorum-2 (0xdb2e80840f40033761A5cdFa3B09fE24f95a4aaa), RPC downtime for the week was above 40%, set score to 0.6

  • PlusV N2 (0x52949f71f71f6E5A6EfCab0f16C8fF6711A84780), RPC downtime for the week was above 40%, set score to 0.6

  • v0 (0xB29438f402da218180bBa79fbc0fAdD3e9E151aa), RPC downtime for the week was above 40%, set score to 0.6

  • Keyko-1 (0x233c06EDc757003cA4ec078012F517F21A24C55c), RPC downtime for the week was above 20%, set score to 0.8

Scores back to 1

  • Mantalabs “Rey” (0xc627459BFc70cD7B6719d5b8030C3beA7825CA7e), RPC uptime 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 next week.

2 Likes