> For the complete documentation index, see [llms.txt](https://holdr.gitbook.io/holdr-protocol-overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://holdr.gitbook.io/holdr-protocol-overview/ecosystem/governance.md).

# Governance

{% hint style="warning" %} <mark style="color:orange;">**This page is a work in progress. If you want to help us to make this page better, please consider contributing on GitHub.**</mark>
{% endhint %}

## Overview

Holdr Governance is the heart and brain of Holdr Protocol.

Anyone can be part of the Holdr Governance Process, and anyone with HLDR voting power can vote on proposals. Governance makes decisions about new features and directions of where the Holdr Protocol should go. Governance is the ultimate decision body for the Holdr Protocol; no one can override vote results.

## HOLDR Governance Token

Voting power for the Holdr Protocol is derived from the Holdr Governance Token (HLDR). HLDR holders vote on proposals relevant to the protocol. These proposals are wide ranging, from Governable Protocol Fees to how HLDR Tokens themselves are distributed into the future.

##


---

# 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://holdr.gitbook.io/holdr-protocol-overview/ecosystem/governance.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.