> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/governance-roles/delegated-representatives-dreps.md).

# Delegated Representatives (DReps)

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

Delegated Representatives (DReps) are a new role introduced in the Age of Voltaire as part of the governance model proposed under CIP-1694. DReps, stake pool operators, and the Constitutional Committee are responsible for voting on governance actions. Any ada holder can register as a DRep.

DReps will play a crucial role in the decision-making process within the Cardano ecosystem, contributing to the democratic nature of the governance model. Ada holders may delegate their ada voting power to representatives who they feel are best equipped (for example, through deeper technological expertise) to best represent their interests.

***

Check the guides to:

{% content-ref url="/spaces/qBJxNzoywC55SZXT5Tv2/pages/jng2cC9ZSQCs0DirfMay" %}
[Register as a DRep](https://docs.gov.tools/cardano-govtool/using-govtool/dreps/register-as-a-drep)
{% endcontent-ref %}

{% content-ref url="/spaces/qBJxNzoywC55SZXT5Tv2/pages/dHifTYvfzCCpFiZbRPQn" %}
[Delegate to a DRep](https://docs.gov.tools/cardano-govtool/using-govtool/delegating/delegate-to-a-drep)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/governance-roles/delegated-representatives-dreps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.