> 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-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/drep-campaign-platform.md).

# DRep campaign platform

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

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

{% hint style="info" %}
**This grant category closed on 11th December 2023.**
{% endhint %}

With on-chain governance introduced by [CIP-1694,](https://www.1694.io/) ada holders will be able to delegate their voting power to Delegate Representatives (DReps), community members representing other ada holders in voting. This concept is the central element of liquid democracy in the age of Voltaire.

To support the delegation process and increase informed decision-making when delegating, ada holders need a common space to discover and explore registered DReps. Building on the feedback captured in the community-led CIP-1694 workshops, it’s imperative that ada holders can identify a DRep’s domain of expertise, their perspectives and interests, how they voted in the past, and much more. Equally, DReps need a place where they can share their profile and credentials, and campaign for ada holders to delegate their voting power to them.

### The DRep campaign platform

To support this goal, Intersect is opening up a grant opportunity to fund the development of a DRep campaign platform, a tool to enrich the vital role DReps and delegation play in Cardano’s on-chain governance.

\\

\\


---

# 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-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/drep-campaign-platform.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.