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

Mainnet
1

This is the 13th 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).

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

  • Mantalabs (0xaC6492D439b3b812e822d1e975338f48bDD0B1f2), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Figment Networks 1 (0x0e47ea88480788289bDa37D8Ae0C2CD680623cfA), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Figment Networks 4 (0x12125D1b7f01F32b3A741A6b97CB46f714f273aA), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Ledger by Figment 1 (0x1C13efCBaeCCC17D41F4a23Da5CAC15167675B96), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Ledger by Figment 2 (0xd818F03476eF422BedDF720adDf5B3D3fd8353FE), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Ledger by Figment 3 (0x572BD94eEF29D104F266e82b0781bC4b07086648), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Anchorage (0x112fF12927CD6f924d80b9Aba32E531733B602fF), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Anchorage (0x1F15d4210e34DfeeEc087C906b426509da1b01f1), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Anchorage (0x48dE6c6668c24e5Bd113d5C46d813C50fE2204D1), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Anchorage (0x43fbd2B45Ef5C042F821D24E14933C570e05Ef78), RPC uptime for the week was above the required threshold, set score back to 1.0

  • Anchorage (0xadBE75cBD14f92BA2D233b6b81E80D4634fAbB2a), RPC uptime for the week was above the required threshold, set score back to 1.0

  • team-rpc-node-3 (0x43fc11B02bF067eBfE234dC5Fb25527326444A6a), 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 on 13/07/2025.

4 Likes
2

Execution

We have executed the score changes as above with the transaction: Celo Mainnet transaction 0xfa075ef1415fe8bb4073e2f37b28be71599a016f9a42e9444648c1166b005980 | Blockscout, with some minor updates noted below.

Addendum

Our original post on Sunday 06/07/25 had an error related to nodes being technically “up” and responding to requests, but in an unsynced state, with a block number very far behind head.

Due to our communication mistake we will re-open the dispute period for the following validators only:

  • Mantalabs “Rose” (0xaC6492D439b3b812e822d1e975338f48bDD0B1f2) was lagging significantly behind head for appromixately 93% of the week, and score should be set to 0.0
  • Mantalabs “Rey” (0xc627459BFc70cD7B6719d5b8030C3beA7825CA7e) was lagging significantly behind head for appromixately 94% of the week, and score should be set to 0.0

Next Steps

The dispute period for only these two validators is now open for approximately 24 hours, after which, we will execute the above score changes if there are no challenges.

Future Scoring Changes

We will be formalizing both the code and rules for RPCs which are not in sync soon to clarify some of the discussions recently.

2 Likes