-
Notifications
You must be signed in to change notification settings - Fork 0
Proposal and Voting Mechanisms
-
Pre-Proposal Dialogue (Temperature Check): Initially, members are encouraged to discuss their proposal ideas within the relevant channels (Official Telegram group and Discussions on GitHub). This step allows for a comprehensive understanding of the proposal, enabling members to make informed decisions and offer constructive feedback, potentially refining the proposal before its official submission.
-
Formal Submission on Colony: Following the preliminary discussions, the proposal is formally submitted on the Colony platform. Depending on its nature, it can be categorized either as a Decision Proposal or a Motion, each adhering to specific guidelines to ensure clarity and purpose.
-
Mandatory Submission of Proposal Links: Immediately after the proposal's creation on the Colony platform, the proposer must share a direct link to the proposal in the Fairdrive DAO's official channels, specifically the Telegram group and Discussions on GitHub under the Proposals category. This step is critical to enhance proposal visibility, ensuring all DAO members have the opportunity to actively review, object to, or support proposals. Failure to share the proposal link in the official channels within two hours of its submission on Colony will result in the proposal being considered unsuccessful by default.
-
Objection Period for Lazy Consensus: Upon submission and mandatory link sharing, a 72-hour objection period commences, embodying the Lazy Consensus model. This critical window allows members to review the proposal and, if necessary, raise objections. The absence of objections implies a collective agreement, allowing the proposal to proceed without a formal vote.
-
Voting Triggered by Objections: Should objections arise, a vote is initiated, with DAO members casting their votes in alignment with their reputation. This ensures that voting power is equitably distributed, reflecting each member’s contribution and engagement within the DAO.
-
Determination of Proposal Outcome: The voting outcome dictates the proposal’s fate—whether it is to be implemented or shelved. This final step marks the culmination of the proposal process, seamlessly integrating member input and the foundational principles of Fairdrive DAO governance.
To maintain a streamlined and effective governance process, Fairdrive DAO adopts a structured approach to proposal submissions, leveraging the Colony platform's capabilities. Proposals are categorized into two main types: Decision Proposals and Project Work Proposals, each with its specific template and submission requirements.
-
Decision Proposals focus on governance decisions and should include:
- The issue or decision at hand
- Rationale for the proposal
- Potential advantages and disadvantages
- Mitigation strategies for identified disadvantages
-
Project Work Proposals are detailed in a Project Canvas, outlining:
- Project goals and expected outcomes
- Required resources and timeline
- Involved team members and roles
- Risk assessment and mitigation strategies
See the template for Decision Proposals (to be added soon). See the template for Work Proposals (to be added soon).
All proposals must be submitted via the Colony platform, adhering to the respective template guidelines.
Fairdrive DAO employs a Lazy Consensus model for most decisions, where proposals can proceed without formal voting if no objections are raised within a specified timeframe. This model is complemented by:
- Motions: For actions that can be automatically executed on the blockchain, requiring reputation-weighted staking for support.
- Simple Decisions: For non-automatable decisions, using reputation-weighted governance for yes/no questions.
Reputation plays a crucial role in the governance process, influencing a member's voting power and ability to participate in decision-making. Reputation is earned through contributions (e.g., completing tasks, participating in governance) and decays over time to emphasize ongoing engagement. It is non-transferable and serves as a measure of a member's influence within the DAO.
Proposals are first vetted against the submission guidelines and templates. Once submitted, they enter the objection period, where DAO members have 72 hours to raise objections. This period is critical for ensuring community awareness and participation.
- For Motions: If fully staked and unopposed, the action is executed. If objections are raised, it may trigger a reputation-weighted vote.
- For Simple Decisions: A similar process applies, with the potential for a vote if objections are substantial.
The evaluation of proposals and the subsequent voting (if necessary) are based on the principles of transparency, fairness, and community consensus. Successful proposals are implemented according to the outlined plan in the Project Canvas or decision proposal, with continuous monitoring and reporting to the community.