Please describe your proposed solution.
RoundTable ( https://roundtable.theadao.io/ ) is an open source, decentralized multi-signature wallet dapp for Cardano developed and hosted by the ADAO Community. It is intended as a "Blockchain Public Good" and for that reason it is free to use or even run locally. The Code is open source (Apache 2.0) and therefore can be forked from the ADAO Community GitHub if developers wish to contribute. At time of writing there are 14 forks from the RoundTable repository and a total of 88 commits.
RoundTable is the first of kind "Decentralized" multi-sig dapp on Cardano due to fact that it uses Gun.js for coordination, removing the need for a centralized data base to store and coordinate signatures.
As adoption of RoundTable has grown the community of both users and developers have offered great feedback and insight. This feedback has been used to direct the next stage of development for RoundTable.
This proposal seeks to fund and incentivize the next stage of RoundTable multi-sig development. Developers from within ADAO and the greater Cardano community have teamed up to enable even more user friendly features for RoundTable.
More recently teams across Cardano from popular NFT marketplaces, DeFi protocols, and Metaverses have inquired about RoundTable multi-sig directly integrating with there platforms. This funding will also be used to incentivize this integration work.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
RoundTable is the leading multi-signature solution on Cardano today, used by a growing number of individuals and projects. This proposal will bring greater usability to the RoundTable dapp and attract even more users.
This proposal aims to encourage more contributions to the RoundTable code base from outside development teams and organizations. Utilizing the pre-existing bounty system developed within ADAO we can encourage more developers to work on the code base and reward them with fair compensation for doing so.
Multiple developers from within Cardano have already started to contribute and more are showing interest everyday, including, popular NFT market places and Metaverses who wish to implement RoundTable multi-sig directly into their platforms.
This proposal intends to not only bring new features to RoundTable the Dapp but also to bring Native RoundTable multi-sig support to the most popular Cardano Platforms and Metaverses.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
As you can see in the team description section, the people who are working on this proposal have experience in Project Catalyst and have already delivered working products. So we feel confident in being able to deliver what is outlined herein. However, we have outlined a few of the main risks and how we plan to mitigate them.
- Developers getting sick/injured: This proposal is for a tool after all, which requires developers to build it. If something were to happen to the ones who are leading and working on this project, then that would be a primary risk in its completion. However, ADAO has several qualified developers who could and have been collaboratively building this. If something unforeseen were to happen to one of them such as sickness, then the initial plan would be to wait until they get better and then continue the work but not hinder other developers on the project. If necessary or if it was something more permanent, then there are others who would be able to take their place.
- Lack of Interest: We could build an excellent tool, add amazing features but if nobody is interested or cares to implement it, then it is equivalent to never completing it in the first place. In order to mitigate this risk, we intend to work on educating the community about this tool and why it is beneficial. This serves a dual purpose of making dev teams aware that this is an option for them to use and it also helps the community understand what the tool is and why it matters that teams are using it. In both cases, it makes it more likely for the tool to be utilized and integrated.