Author: filipv
Date: 2022-12-16
Synopsis
Temp check voting should open upon a proposal’s submission. Multisig discretion in execution should be clarified. Links to Notion should be replaced with links to Juicetool.
Motivation/Rationale
- Temperature checks can feel rushed right now. Authors can submit proposals before temperature checks begin, but feedback is usually sparse until temperature checks formally open. Enabling voting upon a proposal’s submission encourages early discussion (and earlier submission), which will lead to better proposals.
- Multisig discretion is not explicitly formalized in the governance process. The DAO should be clear and transparent when documenting its processes.
Specification
| Original sentence | Modified sentence |
|---|---|
Proposals can be submitted to the Proposals Database at any time. Once a proposal is ready for discussion, authors can change the proposal status from Draft to Discussion, which will automatically create a discussion thread in the JuiceboxDAO Discord Server. | Proposals can be submitted on Juicetool at any time. Once a proposal is ready for discussion, authors can change the proposal status from Draft to Discussion, which will automatically create a discussion thread in the JuiceboxDAO Discord Server. |
| A 3 day temperature check (react-vote Discord poll) will be created for each proposal submitted by day 1 of each Governance Cycle. During the temperature check, authors can update or redact their proposals based on the DAO's feedback. Each verified Discord member may cast one vote in each poll. | A Discord temperature check poll will be created for each proposal submitted before the first day of each Governance Cycle. During the temperature check, authors can update or redact their proposals based on the DAO's feedback. Verified Discord members with JBX get one vote per poll. |
| Executable proposals which receive at least 10 affirmative votes amounting to at least 30% of total votes will proceed to the next stage. Proposals must clearly specify multisig actions to be deemed executable. | Proposals which receive at least 10 affirmative votes amounting to at least 30% of total votes will proceed to Snapshot. |
| A 4 day Snapshot vote (basic single choice) will be created for each proposal which passes temperature checks. Each Snapshot proposal must include the full proposal text and a link to an immutable (IPFS) copy of the proposal text. | A 4 day Snapshot vote will be created for each proposal which passes temperature checks. Each Snapshot proposal must include the full proposal text. |
| If two proposals have conflicting specifications, the more recently approved proposal takes precedence, but only for that conflicting part. If the conflicting proposals were approved in the same funding cycle, the proposal which received more affirmative votes takes precedence. Unless otherwise specified, proposals are considered effective at the time of their approval on Snapshot. | If two proposals have conflicting specifications, the more recently approved proposal takes precedence, but only for that conflicting part. If the conflicting proposals were approved in the same funding cycle, the proposal which received more affirmative votes takes precedence. Unless otherwise specified, proposals are considered effective at the time of their approval on Snapshot. If part of a proposal is impossible to execute as described, the multisig will not execute those parts of the proposal. The multisig may make minor and reasonable modifications to a proposal when interpreting it. |
Risks
Temperature checks can be stressful for some DAO members. Increasing their length may make them stressed longer.
Timeline
To be implemented upon this proposal’s Snapshot ratification.