# Scoring Model

### Question-Level Scoring

The framework currently consists of **84 questions** distributed across:

* **2 Security sub-categories**
* **6 Strategy sub-categories**
* **4 Operations sub-categories**

<figure><img src="https://662549248-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgwsFkZ5TBNv0ypstUEQ1%2Fuploads%2F7CVwxHyDzMae0LesERzp%2FRisk-Flow.png?alt=media&#x26;token=1e741d32-e202-4bb1-854c-f2244f8030fd" alt=""><figcaption></figcaption></figure>

Each question is scored into one of three **risk groups**:

* **Lowest risk** → high score (e.g., 9 points)
* **Mid risk** → medium score (e.g,. 3 points)
* **Highest risk** → low score (e.g,. 1 point)

**Missing data is treated as the worst case and counted with 0 points.** \
In DeFi, transparency is a core part of risk: if you do not know, we assume that anything can happen.

### Aggregation

* Within each **sub-category**, question scores are aggregated into a **sub-category score**.
* Sub-categories are **equally weighted** within their pillar.
* Each pillar (Security, Strategy, Operations) contributes its **fixed weight** (40 / 30 / 30) to the total score.

#### Notation

* **Pillars** $$(p \in {\text{Sec}, \text{Strat}, \text{Ops}})$$
* **Pillar weights:** $$(w\_{\text{Sec}} = 0.40), (w\_{\text{Strat}} = 0.30), (w\_{\text{Ops}} = 0.30), with (\sum\_{p} w\_p = 1)$$
* **For each pillar** $$(p)$$:
  * $$(N\_p)$$: number of sub-categories in pillar $$(p)$$
  * Sub-categories indexed by $$(i = 1, \dots, N\_p)$$
  * $$(n\_{p,i})$$: number of questions in sub-category $$(i)$$ of pillar $$(p)$$
  * Question scores $$(q\_{p,i,j} \in {1, 3, 9}) for (j = 1, \dots, n\_{p,i})$$

#### Total Points

$$
\text{Points} =
\sum\_{p} w\_p \cdot
\left(
\frac{1}{N\_p}
\sum\_{i=1}^{N\_p}
\frac{1}{n\_{p,i}}
\sum\_{j=1}^{n\_{p,i}} q\_{p,i,j}
\right)
$$

Given the current structure, the **maximum total score** is **900 points**, corresponding to the lowest observable risk and thus an **AAA**-level profile under our scale. Lower scores map into lower rating bands (AA through D).

The exact mapping between numeric score ranges and rating bands is documented and versioned within the methodology and applied consistently across all protocols.

<figure><img src="https://662549248-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgwsFkZ5TBNv0ypstUEQ1%2Fuploads%2FmAD2guFZ66l06ai1S1OJ%2Fimage.png?alt=media&#x26;token=4ed31ad2-e931-4ccc-b2d1-0e83383cbbe4" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th>Score</th><th>Higher Bound</th><th data-type="number">Percentage</th></tr></thead><tbody><tr><td>AAA</td><td>900</td><td>100</td></tr><tr><td>AA+</td><td>894</td><td>99.33</td></tr><tr><td>AA</td><td>888</td><td>98.67</td></tr><tr><td>AA-</td><td>882</td><td>98</td></tr><tr><td>A+</td><td>876</td><td>97.33</td></tr><tr><td>A</td><td>870</td><td>96.67</td></tr><tr><td>A-</td><td>858</td><td>95.33</td></tr><tr><td>BBB+</td><td>846</td><td>94</td></tr><tr><td>BBB</td><td>834</td><td>92.67</td></tr><tr><td>BBB-</td><td>822</td><td>91.33</td></tr><tr><td>BB+</td><td>810</td><td>90</td></tr><tr><td>BB</td><td>785</td><td>87.22</td></tr><tr><td>BB-</td><td>760</td><td>84.44</td></tr><tr><td>B+</td><td>735</td><td>81.67</td></tr><tr><td>B</td><td>710</td><td>78.89</td></tr><tr><td>B-</td><td>685</td><td>76.11</td></tr><tr><td>CCC+</td><td>660</td><td>73.33</td></tr><tr><td>CCC</td><td>580</td><td>64.44</td></tr><tr><td>CCC-</td><td>500</td><td>55.56</td></tr><tr><td>CC</td><td>420</td><td>46.67</td></tr><tr><td>C</td><td>340</td><td>37.78</td></tr><tr><td>D</td><td>100</td><td>11.11</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stakingrewards.com/defi-ratings/rating-methodology/scoring-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
