# Score Management Committee - Results for week ending 20/04/2025

**URL:** <https://forum.celo.org/t/score-management-committee-results-for-week-ending-20-04-2025/11030>\
**Category:** Mainnet\
**Tags:** governance, technical\
**Created:** [April 20, 2025, 4:08pm UTC](https://forum.celo.org/t/score-management-committee-results-for-week-ending-20-04-2025/11030 "2025-04-20T16:08:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![clemens](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.celo.org/clemens/32/7162_2.png) [@clemens](https://forum.celo.org/u/clemens)\
**Post date:** [April 20, 2025, 4:08pm UTC](https://forum.celo.org/t/score-management-committee-results-for-week-ending-20-04-2025/11030/1 "2025-04-20T16:08:23Z")

</div>

### Week of 20/04/2025

This is the second of a weekly series of reports on our off-chain score keeping system for the elected validator / 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).

- Keyko1 (`0x233c06EDc757003cA4ec078012F517F21A24C55c`), RPC uptime for the week was above 80%, 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 27/04/2025.

---

<div class="post-metadata">

**Author:** ![Thylacine](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.celo.org/thylacine/32/6703_2.png) [@Thylacine](https://forum.celo.org/u/Thylacine)\
**Post date:** [April 21, 2025, 12:53pm UTC](https://forum.celo.org/t/score-management-committee-results-for-week-ending-20-04-2025/11030/2 "2025-04-21T12:53:10Z")

</div>

## Execution

- After no disputes the scores were updated as above
- Transaction: [Celo Mainnet transaction 0x60cae80694cdf957527efdde20c463ca9e916084300afb1b1b085dc0216771ab | Blockscout](https://celo.blockscout.com/tx/0x60cae80694cdf957527efdde20c463ca9e916084300afb1b1b085dc0216771ab)
- Verification: You can call the public/read method **getValidatorScore** on the ScoreManager contract here: [ScoreManagerProxy | Address 0xef3B9CC0FA4717aF6f412d39dBcEb89bf92f603B | CeloScan](https://celoscan.io/address/0xef3B9CC0FA4717aF6f412d39dBcEb89bf92f603B#readProxyContract)
