DRC-08-(Improvement of DAOSquare Governance)

Poll Submitter: Typto DRC Author: haipi

#Short Description

Short Description (What) The purpose of this proposal is to optimize the governance mechanism of DAOSquare. As you know the goal of the Beta stage - to prepare for the governance work of DAOSquare after the official launch of the incubator - We need to continuously improve the mechanism, including the governance process, governors identity mechanism, governors reward mechanism, etc.

This proposal will focuses on simplifying the governance process and making the participation smoother. In the next step, I will propose a proposal for optimizing the governors identity mechanism and governors reward mechanism.

Motivation (Why) The current governance process is complex and cumbersome. In current governance process, a proposal requires one discussion and two Snapshot votes (DRC and DREO). This not only reduces efficiency but also lead more workload for voters. As the same time, the proposal process is also cumbersome, which raises the barrier for both proposers and voters. Furthermore, since proposals are submitted on the forum, voting on Snapshot, and most members are active on Discord. These three platforms are fragmented, that’s means members have to jump in between them, which further increases the difficulty of participation.

Specification (How) I propose optimizing the current governance process from the following.

1. Cancel the dual proposal structure (DRC and DRE) and unify them as DIP My suggestion is combine proposals to “DAOSquare Improvement Proposals”, know as DIP. The scope of DIP includes three categories: operation, treasury, and protocol.

Operation:

Operating mechanism, rules of marketplace, and others of DAOSquare Incubator (After going live). The operating mechanism of DAOSquare community, and management of DAOs in DAOSquare community. Improvement of DIP design. Note: The governance of operation scope is typically off-chain.

Treasury:

DAOSquare Incubator Protocol Fee distribution mechanism adjustment $RICE treasury management Note: Treasury governance is usually on-chain, meaning that the voting results will trigger asset transfers.

Protocol:

Updates to the DAOSquare Incubator protocol. Updates to the DAOSquare treasury smart contract. Updates to the smart contracts of the products and tools owned by the DAOSquare community. Note: Treasury and Governance Protocol will be launched after the DAOSquare Incubator goes live. Before that, we will organize relevant tests.

2. Adjusting the limitations of the proposer I suggest that any community member with a Passport identity can submit a new proposal, while the voters remain the same for now, meaning Cafeteria members have voting rights.

3. Set up a Governance Cycle A governance cycle can help governors and community members understand the rhythm of community governance and carry out relevant operations without constantly monitoring whether there are new proposals in the community that need to be addressed. Thanks to Nance for proposing the concept of Governance Cycle. The design of the Governance Cycle is as follows:

Temperature Check: Collect the community’s feedback on this proposal and measure the community’s enthusiasm for the proposal through a Poll. Vote: All proposals that have passed the Temperature Check will enter the Vote period. Execution: All proposals that have been approved in the Vote period will be executed during the Execution period. Delay: Proposals that have not been approved can be modified during the Delay period for resubmission in the next governance cycle. I suggest setting the Governance Cycle in a fixed time loop, as shown in the diagram below:

The parameters are as follows:

Cycle Start: 8 am UTC, Monday Temperature Check: 3 days Vote: 4 days Execution: 4 days Delay: 3 days This is a Governance Cycle that starts on 8 am UTC on Monday and lasts for two weeks. The first week, from Monday to Wednesday, is the Temperature Check period, followed by the Vote period from Thursday to Sunday. The second week, from Monday to Thursday, is the Execution period, followed by the Delay period from Friday to Sunday.

This means that all proposals can only be submitted on the first three days of the first week, from Monday to Wednesday, and voting can only occur from Thursday to Sunday of the first week. Apart from this, members do not have to worry about missing any governance work.

This setup allows us to walk the path of governance in an organized manner. Members do not need to constantly check for new proposal submissions or participate in new votes, but rather just need to maintain the rhythm.

4. Change proposal submission and storage space Turn off the existing Discourse forum (forum.daosquare.io) and move the submission and storage of Proposal content to daosquare Governance | Nance. This will allow us to use the governance workflow tools provided by Nance.

5. Use Nance Bot for proposal workflow reminders When a proposal is successfully submitted on Nance.app, Nance Bot will push notifications to the specified Discord channel (DIP). This includes reminders for new proposals, proposal modification notifications, and progress updates for proposals.

6. Use Nance Bot for community temperature check When a proposal in the Temperature Check period, Nance Bot will initiate a Temperature Check in the specified Discord channel (by creating a new Thread). During this period, all Passport members can comment on the proposal and show their support or opposition (using :+1: or :-1:). When the minimum threshold of :+1: is reached, the temperature check passes. This means that the proposal is allowed to proceed to the next period (Vote).

I suggest setting the minimum value for Temperature Check to: 10.

7. Use Nance Bot to automatically submit Snapshot votes. When a proposal passes the Temperature Check, Nance Bot will automatically initiate a vote on Snapshot at the start of the Voting period. This eliminates the repetitive work of the proposer.

Risks Nance is still in the early stage now, that mens there may be intermittent malfunctions related to Nance’s operations. Possible malfunctions include: notification function failure, Temperature Check failure, robot unable to submit proposals on Snapshot, proposal loss, and so on. I have direct contact with the dev team and can seek help from them promptly when encountering such problems.

Timeline Currently, the relevant preparations have been completed and deployed for test. Once the proposal is approved, the new governance mechanism can be immediately implemented.

---

On-Chain Voting Now Option 1: YES。（ Approval of governance improvements） Option 2: NO。（ Disapproval of governance improvements）