> 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-tools/voltaire-govtool.md).

# Voltaire GovTool

Overview of the Voltaire Govtool

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

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

The Voltaire Govtool is a community tool that supports the key steps of Cardano's Governance process described in CIP1694. Govtool is part of the core governance tools.

Intersect has facilitated the bootstrapping of GovTool and supported the process to fully open source it, allowing community ownership for improvement and maintenance.

The Voltaire Govtool, together with the other core tools such as the Constitutional Committee Portal, is currently managed by the Intersect [Governance tools WG](https://intersect.gitbook.io/intersect-committees-groups/groups-overview/working-groups/governance-tools-working-group), the three existing pillars that make Govtool (Proposal Discussion, Delegation, and Voting) are developed and maintained by the WeDeliver Team, the Byron team and tested by the DQuadrand team.

## The four pillars of Govtool

The Voltaire Govtool architecture is divided into pillars, allowing the different maintainers to work with minimal dependencies on their respective applications while giving the end user one cohesive experience. This structure also allows for easier individual contribution and for easier expansion of these tools. Furthermore, because Govtool is fully open source, anyone can create their own version of Govtool, either the whole Govtool or just a pillar, making it better and then providing value back to the core tool.

<figure><img src="https://844111662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo50OuflyxfUMOt8hHPn2%2Fuploads%2Fgit-blob-653f1dfd3221a488490928dcc43032bd9f0d0c94%2FScreenshot%202024-08-08%20at%2020.34.02.png?alt=media" alt=""><figcaption></figcaption></figure>

## SanchoNet Govtool

In its first implementation, Govtool has been connected to the SanchoNet testnet allowing ADA holders to test the full governance features. The community can participate in testing on [sanchogov.tools](https://sanchogov.tools/), keep track of participation in the [participation dashboard](https://participation.sanchogov.tools/en), and track of development and feedback in the [github project](https://github.com/orgs/IntersectMBO/projects/30/views/14).

In its current implementation, SanchoNet Govtool has the following features:

* Proposal discussion
* DRep registration
* DRep delegation
  * Including delegation to Abstain and No-confidence
* Reviewing and Voting on active Governance Actions

Overall guides about the SanchoNet GovTool can be found [here](https://docs.sanchogov.tools/).


---

# 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-tools/voltaire-govtool.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.
