> For the complete documentation index, see [llms.txt](https://docs.hydra-voting.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.hydra-voting.intersectmbo.org/cc-elections-2026/cc-election-2026-faqs.md).

# CC Election 2026 - FAQs

This page answers the most common questions about the 2026 Constitutional Committee election, including eligibility, voting, process, and requirements.

## General Questions

<details>

<summary><strong>What is the Constitutional Committee (CC)?</strong></summary>

The Constitutional Committee is a governance body responsible for assessing whether governance actions comply with the Cardano Constitution.

It acts as a safeguard to ensure that decisions made through on-chain governance adhere to constitutional rules and principles.

</details>

<details>

<summary><strong>What is the purpose of the CC election?</strong></summary>

The election allows the community, through Delegated Representatives (DReps), to select candidates to serve as members of the Constitutional Committee.

</details>

<details>

<summary><strong>Does this election directly appoint CC members?</strong></summary>

No.

The election determines the preferred candidates. These candidates are then included in an Update Committee governance action, which must be ratified on-chain before they formally assume their roles.

</details>

<details>

<summary><strong>Who can participate in the election?</strong></summary>

* **Candidates**: Individuals, organisations, or consortia
* **Voters**: DReps (stake-weighted voting)
* **Community members**: Can review candidates and participate in discussions

</details>

<details>

<summary><strong>Is participation mandatory?</strong></summary>

No. Participation is voluntary for both candidates and voters.

</details>

## Candidates & Eligibility

<details>

<summary><strong>Who can run as a candidate?</strong></summary>

Anyone who meets the eligibility requirements defined by the Constitution and completes the registration process.

There are three tracks:

* Individual
* Organisation
* Consortium

</details>

<details>

<summary><strong>What is required to register as a candidate?</strong></summary>

All candidates must provide:

* A cold credential (key or script)
* Contributions to Cardano
* Motivation
* Views on decentralised governance
* Constitutional familiarity and interpretation
* Transparency approach

Additional requirements apply depending on the selected track.

</details>

<details>

<summary><strong>Is candidate information public?</strong></summary>

Yes, most of it.

**Public:**

* Name or alias
* Biography and governance statements
* Contributions and experience
* Social links
* Cold credential hash

**Private:**

* Contact email
* Declaration checkboxes

</details>

<details>

<summary><strong>Can candidates edit their application?</strong></summary>

Yes, until the voting period begins.

Once voting starts, profiles are locked.

</details>

<details>

<summary><strong>Can a candidate withdraw?</strong></summary>

Yes.

If a top candidate withdraws before the final governance action is submitted, the next ranked candidate may be selected.

</details>

<details>

<summary><strong>Is the CC role compensated?</strong></summary>

The role is currently **uncompensated**, and future compensation is yet to be determined.

</details>

## 🔐 Cold Credentials (Critical Requirement)

{% hint style="danger" %}

## **Important**

Cold credentials are mandatory for all candidates.
{% endhint %}

<details>

<summary><strong>What is a cold credential?</strong></summary>

A cold credential is an on-chain identifier (key or script) used to authorise governance actions.

It represents the authority a Constitutional Committee member uses when voting.

</details>

<details>

<summary><strong>Why are cold credentials mandatory?</strong></summary>

Because the role requires immediate operational capability.

CC members must actively participate in governance decisions. Without a valid credential, they cannot perform their duties.

This requirement ensures:

* Candidates are technically capable
* No delays after election
* Immediate participation in governance
* Seamless transition between members
* Continuity of the Constitutional Committee

It also prevents a critical failure scenario: a candidate is elected but cannot serve.

</details>

<details>

<summary><strong>Why must credentials be prepared in advance?</strong></summary>

Credentials are verified before approval to ensure all candidates are:

* Genuine
* Prepared
* Able to act if elected

This avoids operational risks and removes uncertainty for voters.

</details>

<details>

<summary><strong>Can credentials be changed after submission?</strong></summary>

Credentials are expected to remain stable once submitted and verified.

Any changes may require re-verification and must follow platform rules.

</details>

***

## Voting

<details>

<summary><strong>Who can vote?</strong></summary>

Only Delegated Representatives (DReps).

</details>

<details>

<summary><strong>How does voting work?</strong></summary>

* Stake-weighted voting
* Each DRep may vote for up to four candidates
* Conducted on Intersect’s Hydra-based voting platform

</details>

<details>

<summary><strong>How is voting power determined?</strong></summary>

Voting power is based on the amount of ada delegated to each DRep.

A snapshot is taken at the end of the voting period to determine final voting weight.

</details>

<details>

<summary><strong>How are winners selected?</strong></summary>

Candidates are ranked by total stake-weighted support.

The top four candidates are selected and included in the Update Committee governance action.

</details>

<details>

<summary><strong>Can DReps change their vote?</strong></summary>

Yes

</details>

<details>

<summary><strong>What happens if a voted candidate withdraws</strong></summary>

If a top-ranked candidate withdraws before the Update Committee governance action is submitted:

→ The highest-ranked runner-up candidate will be selected instead.

</details>

## Election Process

<details>

<summary><strong>What are the phases of the election?</strong></summary>

1. Registration
2. Promotion
3. Voting
4. Results and audit
5. On-chain submission

</details>

<details>

<summary><strong>What happens after the election?</strong></summary>

* Results are finalised
* Governance action is submitted
* DReps and SPOs vote on-chain
* If ratified, new members take office

</details>

### Intersect's role in the process

<details>

<summary><strong>What is Intersect’s role?</strong></summary>

Intersect facilitates the process by:

* Providing the voting platform
* Managing registration
* Verifying applications
* Coordinating execution

Intersect does not control the outcome.

</details>

<details>

<summary><strong>What is the role of the Civics Committee?</strong></summary>

Provides oversight, including:

* Reviewing flagged applications
* Ensuring process integrity
* Supporting fairness and transparency

</details>

### Integrity & Safeguards

<details>

<summary><strong>How is the integrity of the election ensured?</strong></summary>

* Mandatory credential verification
* Public candidate profiles
* Stake-weighted voting
* Profile lock during voting
* Independent audit
* Separation between facilitation and decision-making

</details>

<details>

<summary><strong>Can applications be rejected or hidden?</strong></summary>

Yes.

If an application is incomplete, not genuine, or violates terms:

* Intersect may contact the applicant
* If unresolved, the Civics Committee may hide the application

Applications are not deleted, and decisions are documented publicly.

</details>


---

# 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.hydra-voting.intersectmbo.org/cc-elections-2026/cc-election-2026-faqs.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.