Score Management Committee - Results for week ending 29/06/2025

Mainnet
1

This is the 12th 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), newly elected validator with 0 uptime, set score to 0

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

  • Figment Networks 1 (0x0e47ea88480788289bDa37D8Ae0C2CD680623cfA), RPC downtime for the week was above 40%, set score to 0.6

  • Figment Networks 4 (0x12125D1b7f01F32b3A741A6b97CB46f714f273aA), RPC downtime for the week was above 40%, set score to 0.6

  • Ledger by Figment 1 (0x1C13efCBaeCCC17D41F4a23Da5CAC15167675B96), RPC downtime for the week was above 40%, set score to 0.6

  • Ledger by Figment 2 (0xd818F03476eF422BedDF720adDf5B3D3fd8353FE), RPC downtime for the week was above 40%, set score to 0.6

  • Ledger by Figment 3 (0x572BD94eEF29D104F266e82b0781bC4b07086648), RPC downtime for the week was above 40%, set score to 0.6

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

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

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

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

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

  • team-rpc-node-3 (0x43fc11B02bF067eBfE234dC5Fb25527326444A6a), RPC downtime for the week was above 20%, set score to 0.8

Scores back to 1

  • StakeCapital (0xbe505Db3e26655cd0a5488f396E391BFA523BeA4), RPC uptime for the week was above the required threshold, set score back to 1.00

  • TPT2 (0xea11740878D662A4d4e9b9f0c7C04378ACf1E869), RPC uptime for the week was above the required threshold, set score back to 1.00

  • TPT3 (0x3a8431fa7810dE768c6468Dd0dB83E695c3BaEC9), RPC uptime for the week was above the required threshold, set score back to 1.00

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 6/07/2025.

3 Likes