Please describe your proposed solution

Having built a multi-sig DAO previously on Plutus, we have first hand experience of the limitation of the computation resources (memory/cpu) and tx size while trying to make the DAO scalable.

While it is possible to use simple multi-sig transaction that can scale relative better than the plutus based multi-sig, the flexibility to add or remove participants on the multisig/DAO is limited or requires ugly workarounds.

Our proposal is to leverage Schnorr signatures to build a multi sig DAO that can scale well among the hundreds of participants with the following features:

• Add/remove participants on the DAO
• Support for proposals and voting actions
• On-chain and off-chain signing support

Please define the positive impact your project will have on the wider Cardano community

Multi-sig/DAO has their own uses on Cardano and beyond. This project besides the original purpose of having an scalable DAO that benefits the cardano community, it also showcases what can be done Cardano using the cryptographic primitives that are available now and on Plutus v3.

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

The proposing team is KuberIDE team, who has a track record of development of projects like KuberIDE, mempool explorer, Plutus contracts and NFT marketplaces, many of which are open source.

For this project specifically, we have first hand experience on the limitations and how we can resolve those limitation. We have internally done a proof of concept to understand the feasibility of the solution. Now, we would like to build a proper reference implementation to open-source so that broader developer community can benefit.

What are the key milestones you need to achieve in order to complete your project successfully?

Milestone 1: Milestone 1: Planning and Documentation

Deliverables:

• Document showing how the solution works, what cryptographic primitives and protocols are used and how

Output:

• Planning document
• Architecture document

Intended outcome:

• Architecture document is published
• Development has started

Milestone 2: Milestone 2: Development

Deliverables:

• Multi-sig/DAO contracts
• ReadMe document

Output:

• Initial working multisig contracts
• Readme documentation

Intended outcome:

• Multi-sig contracts are working
• Testing the contracts with 100 signatures

Final Milestone: Milestone 2: Development

Deliverables:

• Multi-sig/DAO contracts are published on Github
• Project completion report and video

Output:

• Multi-sig/DAO contracts are published on Github
• Project completion report and video

Intended outcome:

• Multi-sig/DAO contracts are published on Github

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

Sandip Pandey, Project Manager

Sudip Bhattarai, Lead System designer/DevOps

Nabin Pokharel, Haskell developer

The team consists of the members of the KuberIDE team who has previously worked on the smart contracts for multisig DAO contracts.

Please provide a cost breakdown of the proposed work and resources

Development (2)

Resources: 2 Haskell developers

Timeline: 3 month

Budget: 90,000 Ada

Project Management (1)

Timeline: 4 months

Budget: 9,000 Ada

No dependencies

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

Multi-sig/DAO has their own uses on Cardano and beyond. This project besides the original purpose of having an scalable DAO that benefits the cardano community, it also showcases what can be done Cardano using the cryptographic primitives that are available now and on Plutus v3.