> For the complete documentation index, see [llms.txt](https://docs-safedao.curiahub.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-safedao.curiahub.xyz/metrics/voter.md).

# Voter

This section covers metrics related to Voter, such as their ranking, voting power, and participation behavior. It provides insights into the role of delegates within the governance process, highlighting their influence and activity over time.

***

## **Voter Table and Individual Delegate Card**:

**All Voter:** Delegate and Top 1,000 Holder

**Delegate**: Addresses with multiple delegators and a minimum of 5,000 Safe voting power.

**Top 1000 Holder by Voting Power**: Addresses that either without delegation or have a single delegator.

<div><figure><img src="/files/59O1UrpBvQjn2FovEkRw" alt=""><figcaption></figcaption></figure> <figure><img src="/files/3GuLvZTUXfvfYBa8K07T" alt=""><figcaption></figcaption></figure></div>

**Ranking**: Delegate ranking based on voting power.

**Voter:** Displays the name or ENS (Ethereum Name Service) address of the delegate.

**Delegated Token (% Voting Power):** This represent the percentage of total votable tokens that have been delegated to a specific delegate

**Delegating Address:** This number of delegators who have delegated their tokens to a particular delegate.

**Voting Turnout**: Tracks delegate engagement in proposals.

* **Active**: Voter who has participated in at least one voting session within the last 3 governance sprints
* **Inactive**: Voter who has not participated in any voting session within the last 3 governance sprints but has participated in at least one sprint since their first vote.
* **Ghost**: Voter who, despite receiving delegation, hasn't exercised their voting power.

**Most Recent Sprints**: Shows the latest 3 sprints voted/not voted by the voter.

**\*\*Sprints**: SafeDAO will change its decision-making process over a specified time frame and run several governance experiments (seasons). Seasons will consist of the following 4 sprints.

1. **Sprints 1-3:** The proposals of the first 3 sprints shall address all proposal types except constitutional and governance proposals (s. C.II. Proposal types). This design shall allow a focus on fostering the Safe ecosystem while avoiding distractions from governance proposals.
2. **Sprint 4: Review and governance amendment sprint:** As a counterpart to the restriction of governance proposals during the first 3 sprints, the 4th sprint is dedicated to governance review and governance proposals. During this time, no other proposals shall be submitted.

Notwithstanding the aforementioned, SEPs related to the implementation and execution of the milestones of SEP #3 are allowed to be voted on in any sprint until their completion.

3. **Guiding principles for timeline:** The guiding principles of the timing are (1.) to make the sprint processes predictable, (2.) to provide sufficient time for preparation and review tasks of relevant events and (3.) to strike a balance between Sprints 1-3 and Sprint 4 (review and governance amendment sprint).

<br>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs-safedao.curiahub.xyz/metrics/voter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
