> 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/funding-administration-archive/intersect-administration-services/2025-apply-for-tender/open-tenders/civics-committee/intersect-stake-based-voting-tool.md).

# Intersect Stake-Based Voting Tool

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

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

Intersect, a community-driven organization dedicated to supporting the Cardano ecosystem, requires a robust and versatile voting tool to facilitate stake-based voting events throughout the year. These processes include Constitutional Committee elections.

We're seeking a community builder to repurpose an existing open-source voting tool to be used for various stake-based voting events, starting with the upcoming Constitutional Committee (CC) elections in Q2 2025. The expected outcome is to have a reusable solution - accessible to the entire ecosystem and adaptable to current and future needs.

By issuing this tender, Intersect aims to leverage the expertise of community builders to customize an existing open-source voting tool, ensuring it aligns with Intersect's present and future voting requirements.

### Project Scope:

Develop an open-source voting tool based on an existing open-source platform, customized to meet the following requirements:

#### Key Requirements:

* Foundation: Existing open-source voting platform (e.g., [Cardano Ballot](https://github.com/cardano-foundation/cf-cardano-ballot)).
* Customization: Adaptable to various voting scenarios.
* Voting Types: Support for:
  * Simple Majority
  * Simple Majority Multi-Selection
  * Ranked Choice
* Security & Transparency: Secure and transparent voting process.
* Open Source: Final product must be open source for use within the Cardano ecosystem.

By fulfilling these requirements, the chosen community builder will empower Intersect and the broader Cardano community with a valuable tool for democratic governance and decision-making.

#### Deliverables:

* Functional and documented voting tool.
* Open-source code repository.

### Application Process:

Interested developers should submit their application [here](https://mpc.intersectmbo.org/funding-application).

### Information Sessions:

Two open calls will be held to answer questions regarding the application process:

* [Tuesday, February 18th, 10:00 AM UTC](http://meet.google.com/xsf-ojeg-npd)
* [Tuesday, February 18th, 5:00 PM UTC](http://meet.google.com/som-uvmr-hfx)

### Contact:

For further inquiries, please contact <constitution@intersectmbo.org>


---

# 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/funding-administration-archive/intersect-administration-services/2025-apply-for-tender/open-tenders/civics-committee/intersect-stake-based-voting-tool.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.