The proposal aims to create a connection between wallets and the real world individual to make real world voting a viable option. Real world voting on blockchains could be a big usecase which could possibly be adopted by every government and other institution which is dependent on the opinion of their stakeholders. In addition to this could create easier ways to vote for currently unstable/ undeveloped nations because the whole organization isn´t dependent on voting offices who use much resources but just on digital infrastructure. Maybe this is currently not that easy to implement in undeveloped countries because of the technological standards, but it could be a viable option in the future the create a fairer world and gives everyone a voice in the politics. And thus matches some sustainability goals. In conclusion the proposal matches the challenge strongly.

Blockchain voting will, most likely, play a very important role in the future. There are several hurdles to overcome to get to that point in time, but it can be done, and is being worked on in several projects. One of those projects is Voteaire which is a Daap that is already up and running. This proposal looks at the current problem with blockchain voting, in that wallets, which are used for voting are not mapped to real-world individuals.

This proposal will increase the quality of the existing Voteaire platform by providing additional utility and use-cases beyond the traditional blockchain ecosystem which is firmly in alignment with the challenge it is located in. This would allow for corporations, and even governments to use the Cardano blockchain to do voting in due time. This would increase integration of the Cardano blockchain, as well as add utility. Furthermore this proposal would expand the use case of other projects on the Cardano blockchain depending on which identity solution they use, or multitude of identity solutions that they use.

The voter is looking at whether or not this adds to the ecosystem, can be easily expanded/scaled out to bigger use cases, and would bring integration of the chain to real-world use cases. All these are covered except expandability. It is important that they proposal detail just how easily this proposal can scale or not scale to meet bigger needs in the ecosystem as use case arrive. Other then that area, This proposal effectively addresses the challenge.

For lack of clearly identifiable uniqueness, I rank this section a 3. While there’s clearly identifiable reputability behind this project, the impacts section here doesn’t have enough substance to provide voters with a clear understanding of what competitive features are being brought to the table (appeal to innovation) and how this proposal links to its impacts. This section points out that it aims to increase the number of Dapps, increase the number of integrations, and improve the quality of existing Dapps/integrations but it doesn’t rationalize how this would accomplish that. There is also a reference to “Voteaire” as a platform that could be improved as a result of this proposal but it doesn’t explain how it would do that. One could draw that connection by doing more research on voteaire but I think it would be much more advantageous for proposers to do the additional work of explaining this platform and identifying the link to different increased capabilities.

The goal of this proposal is to add a decentralized ID to the Voteaire system. This fits within the goals of this challenge well. The purpose of this challenge is to further creative uses of decentralized applications on cardano. In addition to furthering this goal, this proposal would also further the goals of this fund by creating more people using wallets and making transactions on the network. By adding a DID system to the voting platform, the platform will be expanded and its usefulness would be increased. More transactions would be had on the network. More people could use this in more use cases. The team has done a good job of explaining the impact on this Challenge and shown that this proposal earned a score of 5.

The team is proposing to address the challenge by improving on an innovation the team has already created. This improvement would have a positive impact on the Cardano ecosystem as we are headed toward changes in governance structures. Multiple types of governance and voting is an essential part of creating decentralized solutions for Cardano. Advancing the ability to use Cardano for voting, especially with DID integration is an important step. Many projects are working on these solutions which will certainly result in a positive impact on the community as a whole. I appreciate the impact this team has already had on our ecosystem.

The problem defined in this proposal is that blockchain voting isn’t relevant in the real world unless there is a way to map wallets to real people. They explain the solution to this is to integrate a Decentralized Identity solution into their on-chain voting platform, Voteaire. I believe this aligns with the challenge well, as it seeks to integrate one of the already existing DID projects known as IAMX or Atala PRISM into their already existing voting platform. The proposal does a good job at explaining how this integration will allow for additional use cases of their voting platform, perhaps for more corporate and government applications.

I believe the KPIs provided, like number of end users of the application and total number of DIDs connected to application, align well with the KPIs of the challenge because they are good indicators to track if this integration was successful in bringing more users to their platform.

This proposal presents a very interesting concept that’s been talked about a lot in the blockchain space, which is blockchain voting. They want to utilize existing DID solutions such as Atala PRISM and IAMX and potentially integrate them into their platform Voteaire. They have a strong experienced team behind them but the main concern is that it seems they haven’t fully completed their initial reseach to be able to provide a full action plan. Due to this, there is a lack of clear metrics and goals in their solution procedure, leaving us unsure about how the actual project will proceed. Atala PRISM and IAMX both provide services that certainly can be useful for this project, and have been part of several other proposals in other funds. Personally I would recommend knowing more about what DID solution will be attempted before looking for funding for the entire project. Having experience with teams trying to integrate DID solutions it can be a very complicated process and it would therefore be a much stronger proposal if the details on how this process would look like could be provided in the description since this is a very technical topic. That said, this proposal targets the challenge objectives well and could very well turn out to be a successful project that provides a lot of value to the Cardano ecosystem.

Voting backed by blockchains has been a hot topic within the blockchain community almost all through its existence. The proposing team intends to explore different DID solutions to implement a solution that would allow for a fair and transparent voting process down the line. The Cardano ecospace could gather some great traction if it were to be a leader within DID voting, therefore it should be a high priority to explore projects and solutions related to this within Cardano. The proposal aligns great with the challenge setting and the authors even acknowledge this in their proposal. The score in terms of impact will be great as a result, 5 points.

The proposals problem statement has identified a current need to map real identities to wallets for blockchain based voting systems. Their proposed solution to research and integrate Atala Prism and/or IAMX into the Voteaire platform would allow multiple organizations to easily integrate blockchain voting systems on Cardano. This is directly aligned with the challenge to bring impactful use cases to Cardano ecosystem that help drive more adoption. Many people are now aware of the benefits of blockchain voting, however they lack a simple, low cost, and fast way to set up a voting system on the blockchain. By leveraging already completed work by Atala / IAMX and Voteaire, this proposal can offer a simple solution to many new users. The following metrics from the proposal are clearly aligned with onboarding new users: "Number of end users (voters) using the application Total number of DIDs connected to the application Total number of ballots created using the new functionality" This proposal has the potential to scale to multiple voting use cases, however I have given 4/5 stars for impact because the overall impact will likely be on smaller projects such as NFT communities or schools/organizations and others who's voting results are important, but likely not as critical as a nation state election. As security and auditability are critical for these larger projects with billions of dollars or lives at stake, it is likely that more experienced and larger teams will be required and they would most likely work directly with the Atala Prism team, as opposed to using the Voteaire software. There are also other potential options that could fill this use case, therefore it's not clear how much market share or use the Voteaire system will be able to secure as they have not included a marketing plan for this proposal.

The KPIs and metrics are devided into scrum metrics and completed application. The scum metrics are useflul to improve the team internally and the KPIs from the completed application measure the success of the new enhancement numerically. Therefore they are easy to measure. The target problem was clearly described and the solution solves it.

This proposal has listed what the projects team will be using to track standard scrum metrics, however the team has provided no way for people to track the progress of the proposal after it has received funding. There is no break down of a timeline, nor are there any milestones that can be used to gage where the proposal is in it's implementation and progress.

Some ideas for the proposer for future proposals would be to include a youtube channel with videos showcasing achievements along the way, a discord channel to communicate progress, a reddit, town hall meetings, or any number of other avenues to enable people to track the progress. Furthermore there should be information released when the team has researched out the various DID currently available, and who they chose to partner with or work with.

The proposal should take the timeline in the feasibility section and provide information to the public at each phase or at the end of major milestones of each phase. The voter wants to know that once funding has been received, and the proposal gets under way, that they will easily be able to track the progress of the project. As of the current state of this proposal it is not easily identifiable as to how the information provided is sufficient to audit the progress and success of this proposal. I would like to see more work put forth in future proposals as the request for funding is a very important part of project catalyst, and the cardano ecosystem. We want to fund projects, but those projects need to detail out everything for the voter to make an informed decision as to whether or not to vote to fund the proposal. Lacking detailed information in a proposal is not beneficial to the proposer, nor to the voter who is trying to determine if this proposal will be easy to track progress, be implemented successfully and bring value, products, and integration to the Cardano ecosystem.

For laying out a understandable starting framework for relevant KPIs, I rank this section a 4. From a voters perspective, there isn’t a lot of substance here to thoroughly evaluate the teams definition of success. While it does point out all of the right categories for KPIs, it does not take that extra step to further define these metrics with quantifiable targets. This would help voters understand that the proposers have a very specific definition of success and is committed to an objective level of performance/impact. I vote positively because I have everything I need to determine that the team’s attention is in the right place but I think this proposal could secure more confident positive reaction from voters with that additional quantification.

The team does plan to measure their progress and development. They are using a scrum metric approach. This approach appears to be feasible and clear. The goals of this proposal are clear: they are planning on investigating and implementing a DID system into their voting application. How they plan on going about it is also clear. There is not any mention in The Proposal of how they plan on allowing the community to be aware of their progress. However I assume they're planning on using an open coding system. And I believe that they will make regular reports to the Catalyst community as requested. They also plan to measure how their system is functioning. They plan to measure users (voters) using the application, they plan to number how many DIDs are connected. Overall I believe that these metrics are sound and this proposal is solid. There could have been more detail regarding exactly how they plan to report out to the community, but given what is here I believe this is auditible and has earned a score of 4.

The deliverables for this proposal are clear in delivering a voting system with DID integration. The team plans to report progress with "standard scrum metrics" and will also track KPIs upon launch of the product in users, DIDs connected and ballots created to give indication of the impact of this proposal. This team is well known in Cardano and would likely be responsive to requests for information from the community. This would make it relatively easy to audit the progress of the proposal should it be funded.

Even though there are no time estimations for when to expect certain milestones to be reached, the proposal does still provide some milestones to look out for when tracking development progress. The problem is there is no public channel provided for where to expect updates on development. There also is no statement about whether the team plans to provide updates during development. I believe a simple solution to this is providing a twitter account or discord that the community can watch for updates on this project. This would greatly help the community be able to track progress of this proposal.

One thing this proposal defines very clearly and sufficiently are the KPIs and metrics they plan to track. A scrum metric is a new term to me, but they seem like useful metrics to track during the development process.

I believe the team has shown they have clear ways of tracking progress for this proposal during development and post development, but I do not believe sufficient information has been provided for the community to track the progress alongside them. Therefore, my score remains neutral as I believe these two things sort of cancel each other out.

Auditability wise, the proposal presents a variety of good KPI’s that can measure and track the success of the platform. While these are great for auditing the success and usefulness of the platform, I would also say there is a lack of auditability in terms of the development leading up to the completion of the project, are there any KPI’s and measurements we can set for the initial planning and integrations, if so how do those look like etc. A great way of increasing auditability is also to add public channels where users can either follow updates or interact with the project development. I believe this project idea has good potential and the team seem knowledgable in how to present a reasonable plan and relevant KPI’s, it is just a very early stage to ask for funding for the complete procedure when there aren’t enough details to be put forward to help us understand exactly how this project would be carried out.

The proposers have provided a detailed plan along with milestones within each phase. Furthermore, they have included a set of relevant and good KPIs that makes it easy for the community to audit the progress. A suggestion is to add estimated goals to each KIP in order to make the evaluation easier. Another suggestion is to explicitly list where the progress updates will be provided and in what format this will be done. Will you write progress reports from the scrum metrics during development or just provide the raw data? Overall, the proposal is auditable but could be further refined, the total score will be good in terms of auditability, 4 points.

The proposal includes a roadmap with milestones and an estimated completion time of 8 weeks. They have not linked specific sub-tasks to time or budget estimates, but this may not be required for a project that is only 8 weeks in duration. The KPIs provided can be used to track and audit the success of this project. Unfortunately they have not included a plan to submit any progress reports to the Catalyst community, or information on how the Catalyst/Cardano community can observe or audit the development progress. There is no mention of Github or open source, so it's not clear if this will be accessible to the community during development. I would recommend the team provide at least 1 or 2 progress reports during the development phase to the Catalyst community that includes the KPI's in the proposal and % competed. Once the project is completed successfully it should be easy for Catalyst auditors to track the following KPIs: Number of end users (voters) using the application, Total number of DIDs connected to the application, Total number of ballots created using the new functionality. However, the team has not provided specific detail for how these metrics will be shared.