Add techne (ObolNetwork#368)

* add peer score to FAQs * Update peer_score.md * fix title * add new alerts + update to use overview dashboard (ObolNetwork#356) * add new alerts + update to use overview dashboard * Update docs/advanced/monitoring.md Co-authored-by: Luke Hackett <[email protected]> * chores: content suggestions --------- Co-authored-by: Luke Hackett <[email protected]> * Update CLI reference to be in line with the latest rc candidate * update sdk docs (ObolNetwork#364) * update sdk docs * update sdk examples lines * default expand classes * "Get ENR" dappnode tab * Tweak copy * Add explainer image for OWR and contract addresses (ObolNetwork#365) * fix headings --------- Co-authored-by: Luke Hackett <[email protected]> Co-authored-by: Oisín Kyne <[email protected]> Co-authored-by: HananINouman <[email protected]> Co-authored-by: Maeliosa <[email protected]> Co-authored-by: Oisín Kyne <[email protected]>
iiamscarface · May 31, 2024 · cae2643 · cae2643
1 parent 87bdf5c
commit cae2643
Showing 1 changed file with 7 additions and 5 deletions.
diff --git a/docs/faq/peer_score.md b/docs/faq/peer_score.md
@@ -3,7 +3,9 @@ sidebar_position: 5
 description: Measuring Individual Performance in Distributed Validators
 ---
 
-# Introduction
+# Peer Score
+
+## Introduction
 
 Validator effectiveness is a critical metric for assessing the health of a rated network. It determines how well validators perform their attestation and block proposal duties. Existing solutions, like RAVER (Rated Validator Effectiveness Rating), provide a effectiveness score of a validator. In a monolithic validator that is run by a single operator, validator effectiveness can be considered as a proxy for the effectiveness or “score” of that operator. However, this approach falls short when dealing with distributed validators (DVs) maintained by multiple operators.
 
@@ -16,27 +18,27 @@ Peer Score v0 addresses this limitation by introducing a method to evaluate the
 - **Peer Score:** A metric reflecting the performance of a peer within a DV, calculated as the ratio of completed duties to expected duties.
 - **Operator Score:** An aggregated metric representing the overall effectiveness of an operator across multiple DVs (planned for future iterations).
 
-# Challenges with RAVER in DVs
+## Challenges with RAVER in DVs
 
 RAVER assigns a single effectiveness score to the entire DV. This score doesn't reflect the individual contributions of operators within the group. For example, a DV with 95% effectiveness maintained by four operators (A, B, C, and D) doesn't guarantee that each operator has a 95% effectiveness score. It's possible that even if operator D is frequently offline, the remaining operators (A, B, and C) can maintain the overall DV effectiveness.
 
-# Peer Score v0 Calculation
+## Peer Score v0 Calculation
 
 Peer Score v0 utilizes a straightforward formula:
 
 `Peer Score = (Total duties completed by peer) / (Total duties expected by peer)`
 
 This ratio reflects the peer's adherence to its assigned duties within the DV.
 
-# Future Iterations
+## Future Iterations
 
 Peer Score v0 lays the foundation for a more comprehensive evaluation system. Planned advancements include:
 
 - **Weighted Duties:** Assigning varying weights to different duties based on their significance to the network.
 - **Decentralization Scores:** Integrating metrics that consider the decentralization of clients and operator locations.
 - Peer rating: an anonymous rating peers can give to their other peers to grade their social co-ordination.
 
-# Use Cases
+## Use Cases
 
 Peer Score offers valuable insights for various stakeholders: