Please describe your proposed solution.
THE ORIGIN
Here is a true event that happened to me, that made me realize the importance of this solution. I was trying to structure a DAO that we will be onboarding to the Cardano ecosystem, and I needed a structure for the treasury of this DAO. Unlike most DAO this DAO is such that a certain percentage of their members' earnings as predetermined by the member goes directly to the treasury. The members don't need to at every time send in their contributions to this DAO, it ought to be automated and smart, I searched for tools and smart contracts in the ecosystem that could help me achieve this goal but couldn't find one, in the absence of finding one, I decided its time to build one, to help as many DAOs currently and in the future who will need this tool. And to make it open source so that others can adapt this solution according to their use cases. This is the origin of the project.
THE PLEDGE SUBSCRIPTION MODEL
This model of an automated transfer of earnings to a particular DAOs may seem novel but in reality, it is not, it is an age-long model that communities, organizations, and even some social businesses have long operated with, these kinds of organizations are gradually coming into the DAO community like the organization I was trying to move in, and it is getting obvious that we are not well ready for them. For example, this model is what some social businesses operate in when they say For every shoe sold 10% goes to charity, assuming this kind of social business moves into the DAO for the sake of transparency, once there is a sale, the deduction of 10% to the common treasury ought to be automatic and traceable by the buyer, this model is also what some individuals do when they pledge to split commissions earned on a business transaction with an organization or person. Another use case that is related to my personal example is a DAO where they all work as a group to get a project done, but payments are made individually to all members of the DAO, all members of the DAO are committed to a certain percentage to the treasury but in the absence of a smart contract, this process can be so tasking and inefficient. I call this use cases and model the pledge subscription model and is gradually coming into the Cardano DAO we need to prepare for it by developing opensource smart contracts that can be adapted for different types of this kind of use cases
HOW IT WILL WORK
Smart Contract Initialization:
- The DAO initiates the smart contract by deploying it on the Cardano blockchain platform
- The contract includes configurable parameters such as the treasury address, contribution percentage, and any additional rules or conditions.
Member Registration and Pledge Subscription:
- DAO members who wish to contribute a percentage of their earnings to the treasury register their addresses with the smart contract.
- Each member specifies the percentage they want to contribute from their earnings, which is stored within the contract.
- Members can update or revoke their pledge subscription at any time, adjusting the contribution percentage or opting out entirely.
Earnings Tracking and Contribution Calculation:
- Members' earnings are monitored either through direct integration with their wallets or by manual reporting.
- The smart contract periodically checks or receives updates on the members' earnings and calculates the contribution amount based on the specified percentage.
- The contract holds a record of the total contributions made by each member.
Automatic Contribution to the Treasury:
- At predetermined intervals upon reaching a certain threshold, the smart contract triggers the automatic transfer of the calculated contribution amounts from each member's address to the DAO treasury address.
- The contract executes the transactions on the blockchain, ensuring transparency and traceability.
Transparency and Auditability:
- The smart contract maintains a transparent record of contributions, providing a verifiable and immutable history of transactions.
- The contribution details, including the member's address, amount, and timestamp, are recorded and can be audited by anyone on the Cardano blockchain.
Contract Upgradability and Adaptability:
- As an open-source project, the smart contract will be designed to be upgradable and adaptable to different use cases and requirements.
- Community feedback and contributions will help enhance the contract's features, security, and functionality over time.
How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?
This proposal is exactly what this challenge seeks and the Cardano community as well. Here is why in the challenge setting this is what it says.
Cardano needs:
- Similar tools offer superior features to those offered on other chains.
So many chains lack this tool and this will make DAOs to consider our chain when choosing a DAO to use.
- Effective Collaboration Management Platforms to Organize Community Intentions and Actions:
This tool will help DAOs manage the treasury problem and give a better organizational structure to how the treasury operates.
- Additional not yet existing tools to give Cardano a distinct advantage:
This tool is yet an existing tool and will Cardano a distinct advantage.
- Tools for prospective organizations to use in evaluating the features available in Cardano DAOs
- DAO community collaboration
- DAO creation
- DAO operation
- DAO governance.
Specifically this tool will help DAOs governance and treasury and even community collaboration since it is open source.
How do you intend to measure the success of your project?
- The deployment of smart contracts on the blockchain
- The number of DAOs that will adopt and use the smart contract
- The number of DAO tools that will integrate the smart contract into their solution
- The number of forks on GitHub
- The volume of transaction done through the smart contract
Please describe your plans to share the outputs and results of your project?
Code Development and Testing
Time period: 3 Months
Documentation and Code Review
Time Period: 1 Month
Community Outreach and Education
Time Period: 1 Month
Deployment and Initial Adoption
Time Period: 1 Month
iterative Improvements and Updates
Time Period: 1 month