funded
DripDropz Open Source Voting Petition Management
Current Project Status
In Progress
Amount
Received
₳114,100
Amount
Requested
₳153,500
Percentage
Received
74.33%
Solution

DripDropz will add petition management features to its existing Open Source Voting stack.

Problem

Cardano does not currently have an open source petition management tool for adding candidates or issues to a voting platform.

Impact / Alignment
Feasibility
Value for money

DripDropz

1 member

DripDropz Open Source Voting Petition Management

Please describe your proposed solution.

This proposal will add additional features to the DripDropz Open Source Voting tool. For this proposal, The DripDropz team will build a petitions management tool. This tool will allow the voting system to accept petitions which lead to votes. There will be two main uses for this iteration of the petitions management system: Candidate Qualification and Proposal Raising.

Example 1: Candidate Qualification: A community can set a vote which will accept all valid candidates for an office. That community can utilize the petitions system to manage which candidates are able to appear on the ballot. Candidates are provided a form to collect basic information. Candidates are provided a page to collect digital signatures to reach a threshold.

Example 2: Proposal Raising: A community can have an open vote system where an issue or proposal can be raised for a vote. In this example a DAO can allow anyone to raise a proposal with enough signatures. The proposer is provided a form to collect the necessary basic information. The Proposer is provided a page to collect digital signatures to reach a threshold.

Thresholds can be set to any number by the voting system admin. Signature collection occurs within the system, and different requirements can be set. Initial requirements are any of: amount of ADA held, amount of a configurable native asset held, Specific NFT Policy ID held.

How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

The challenge calls out a few areas where this proposal fits. Our Voting system can be implemented as a governance system, and also can be seen as a business solution. As a governance system, we see the potential to implement our tool in clubs, organizations, homeowners associations, and board rooms. As a business solution, the tool can be used to raise issues or proposals into an organization, and allow the affected parties to vote. The Cardano ecosystem benefits from advanced voting tools and increased chain volume. This tool provides both.

How do you intend to measure the success of your project?

Our project will be successful when the new features are added to the open source repository and available to the public.

Please describe your plans to share the outputs and results of your project?

The outputs of this project will mostly take the form of github commits to the maintained open source repository. There will be additional explainer videos and documentation that will be produced.

What is your capability to deliver your project with high levels of trust and accountability?

DripDropz has a proven track record of delivering high quality products to the Cardano Community. Our core product services nearly 10,000 wallets every 5 days. Team members have provided a wealth of open source software, as well as powerful tools such as Phyrhose and BuffyBot. We are active in the community and are present at all of the major Cardano events, such as NFTxLV, Rare Evo, Cardano Summit, and the Governance workshops.

What are the main goals for the project and how will you validate if your approach is feasible?

The goal of this project is to increase the functionality of the open source voting tool to improve its usability for a wider community and new users. Our approach is feasible because we have received community requests for the features listed here, and we are confident that we can deliver them.

We believe that these changes will make the voting tool more accessible and usable for a wider range of people. We are confident that we can deliver on these promises because we have a team of experienced developers who are passionate about open source software.

We are also committed to working with the community to ensure that the voting tool meets the needs of all users.

We believe that this project has the potential to make a real difference in the way that people vote. We are excited to get started and we look forward to working with the community to make this project a success.

Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

This project has four milestones. We will begin immediately with the UI/UX implementation phase, as we already have user feedback to guide our design. In this phase, we will:

  • Research existing solutions to see what other projects have done in terms of user interface and user experience.
  • Build out a user journey, which is a map of the steps that a user will take to interact with the system.
  • Implement a UI that reflects the user journey and meets the needs of users.

Once the UX/UI is complete, we will move into the code implementation phase. In this phase, we will:

  • Code the user interface based on the UI that we have implemented.
  • Code the backend logic that powers the system.

After the code is implemented, we will move into the documentation and testing phase. In this phase, we will:

  • Create documentation for the system, including user guides, API documentation, and code comments.
  • Test the system to ensure that it works as expected. This will involve manual testing, as well as automated testing.

Finally, we will release the system to the main branch of the code base. This will make the system available to users.

Please describe the deliverables, outputs and intended outcomes of each milestone.

Milestone 1: UX/UI Implementation will have a deliverable of a UI created in a Figma document and shared publicly with the community.

Milestone 2: The following modules will be added to the Github repository in a pull request:

  • Candidates Qualification Module
  • Proposal Raising Module
  • petitions management - admin interface
  • Frontend

Milestone 3: Documentation and Testing will show documentation updates within the code that describe the new functionality.

Final Milestone: Release will include the pull request merged back into the main code base, with functionality available to all.

Please provide a detailed budget breakdown of the proposed work and resources.

This project makes use of our UI design resources, media team, engineering resources, and management resources.

Milestone 1:

UX/UI Designer: 30000

Lead Developer: 10000

Management: 2000

Milestone 2:

UX/UI Designer: 10000

Lead Developer: 60000

Management: 2000

Milestone 3:

Lead Developer: 10000

Support Staff: 2000

Management: 2000

Final Milestone:

Lead Developer: 4000

Support Staff: 2000

Management: 2000

Administrative Overhead for Catalyst Fund Reporting Administration: 17500

Total Budget: 153500

Who is in the project team and what are their roles?

The project team is always kept up to date at <https://dripdropz.io/about-us>. Each team member is public, and available via social media for any questions you may have. The Team member roles are also described at the above link.

How does the cost of the project represent value for money for the Cardano ecosystem?

By providing easy to use open source tooling to the community, we believe that immense value is created for the Cardano ecosystem. Having an approachable voting tool that a user can implement on their own is valuable to the entire range of projects building in Web 3. The fact that this tool uses mainnet transactions also means that the community benefits from the increased transaction volume, which results in a growing treasury to help allow for more innovation in the space.

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00