• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Shutter DAO 0x36Shutter DAO 0x36by0x057928bc52bD08e4D7cE24bF47E01cE99E074048gov.daoplomats.eth

[RFP] Governance V0 for Shutter DAO 0x36

Voting ended about 2 years agoSucceeded

[RFP] Governance V0 for Shutter DAO 0x36

Authors: DAOplomats.eth (@Baer_DAOplomats)

Draft Date: 2023-01-24.

Summary:

This proposal proposes the following.

  1. Adopt and formalise the Governance V0 and proposal lifecycle for ShutterDAO.
  2. Adopt a standardised general proposal template for Improvement Proposals.
  3. Adopt a temp check mechanism to streamline the on-chain proposals.
  4. Implement voting strategies for the Tempcheck.

Motivation.

Being a truly decentralised DAO launched after the Shutter Blueprint, the DAO lacks the basic processes needed for proper functioning. We currently lack a temperature check mechanism. The Proposal strategy does not have any spam filtration mechanism for proposals, as the proposal threshold is set to 0.

Furthermore, it is currently unclear how long a proposal should be discussed before it's moved to vote, or even if it should be posted to the forum before it's on-chain.

This proposal aims to determine the best way for a proposal to move from an idea to a formal proposal and a ShutterDAO Improvement Proposal (SIP). This proposal seeks to combine information posted in the DAO launch blueprint and the best practices in the DAO ecosystem to set this DAO up for success.

Background

Setting the stage

The governance discussion for ShutterDAO 0x36, a ShutterDAO implementation, will be hosted on https://shutterdao.discourse.group/ or on the forum officially approved by the DAO. ShutterDAO utilises on-chain executable proposals through the Fractal framework and Safe. Anyone can sign up for the Governance forum or Discord and engage in the conversation.

Current parameters

  • Voting strategy: simple majority (50% + 1 smallest unit of a token)
  • Quorum: 3% of all tokens
  • The minimum amount of tokens required to propose: 1
  • Voting period length: 72 hours
  • Execution period: 72 hours
  • Cooldown period: None

DAO Governance Proposals [SGPs]

The DAO currently doesn't have a standardised proposal template, but any members can take part in the discussion on the forums. The token holders then vote on the proposals.

Specification

The Proposal Lifecycle.

This proposal aims to adopt a general proposal template to standardise the proposals for the DAO, and divide the proposal lifecycle into temp checks and ShutterDAO Proposals (SIP)s.

Proposal Lifecycle

[Idea] ➡️ [Draft RFC] ➡️ [RFC Formalised] ➡️ [Temp check Poll] ➡️ [On/Offchain SIP] ➡️[Accepted/Rejected]

image

Phase 0: Ideation

The purpose of this phase is to gather community sentiment on the author's idea. Unique ideas can use the #idea tag on the forum and have their thread. Phase 0 proposals are generally ideated in informal settings like Discord chat or Telegram groups. This phase could include gathering community support on the specifications of a potential RFC with multiple in-text polls.

Time: Open

Phase 1: Request for Comment

During this phase, proposal authors could request official community sentiment by formulating the idea in a Request for Comment (RFC). RFCs should follow the prescribed template.

[Link to template]. (Pending DAO Approvals)

During the draft stage of the RFC, the author shall include community feedback and update the proposal accordingly. The Draft RFC status aims to gather adequate feedback and support to attain soft consensus, allowing us to proceed confidently with a formal proposal without the risk of it being immediately rejected.

Time: Open

Off-chain Temperature check through Snapshot

This proposal suggests adopting a snapshot space for temperature checks with the following parameters.

  • Voting strategy: simple majority (50% + 1 smallest unit of a token)
  • Quorum: 1% of all tokens
  • The minimum amount of tokens required to propose: 1000
  • Voting period length: 72 hours

Since Snapshot is off-chain and gasless, there is a higher chance of spam, which can be mitigated with a minimum token requirement.

After completing Phase 1, the author can move an RFC to a Shutter Improvement Proposal, an SIP.

Phase 2 SIP Proposals

Depending on the nature of the SIP, be proposed on-chain using the Fractal framework of off-chain with Snapshot. For more info see the table below

Proposal Platform Proposal type
[OnChian]. Fractal
Changes to governance processes, e.g Quorum, Proposal thresholds etc
Modifications to on-chain voting parameters
Updates to Keyper set parameters
Transfer of funds
[Off-chain]. Snapshot
Temperature checks
Requests For Proposals (RFPs)
Letter of Intents with non-binding outcomes
Proposals which don't have any on-chain consequences to ShutterDAO 0x36, eg: Shutter Integration supports, use of 0x36 Brand, etc

Current parameters

  • Voting strategy: simple majority (50% + 1 smallest unit of a token)
  • Quorum: 3% of all tokens
  • The minimum amount of tokens required to propose: 1
  • Voting period length: 72 hours
  • Execution period: 72 hours
  • Cooldown period: None

Depending on the voter turnover and weight, the minimum amount of tokens required to propose can be increased.

Next Steps

  1. Gain community sentiment
  2. Move to Snapshot voting.

Disclaimer

No Guarantee of Results; and Limitation of Liability:

This proposal is neutrally presented based on current community sentiment.

DAOplomats are not compensated for this proposal in any manner. We are not associated with any of the parties mentioned in the proposal above.

Given the evolving nature of DAOs, there’s no assurance that the proposed changes will yield the intended results.

The author(s) and associated parties are not liable for any outcomes or damages from this proposal’s implementation or lack thereof.


Copyright

Copyright and related rights waived via CC0.

Off-Chain Vote

For
29.3M SHU83.3%
Against
920.77K SHU2.6%
Abstain
4.97M SHU14.1%
Quorum:117%
Download mobile app to vote

Discussion

Shutter DAO 0x36[RFP] Governance V0 for Shutter DAO 0x36

Timeline

Feb 07, 2024Proposal created
Feb 07, 2024Proposal vote started
Feb 10, 2024Proposal vote ended
Jul 04, 2025Proposal updated