# \[RFC\] Voting Cycles Updates **URL:** \ **Category:** SD 0x36 Proposals\ **Created:** [March 3, 2025, 3:46pm UTC](https://shutternetwork.discourse.group/t/rfc-voting-cycles-updates/635 "2025-03-03T15:46:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Baer\_DAOplomats](https://dub1.discourse-cdn.com/flex017/user_avatar/shutternetwork.discourse.group/baer_daoplomats/32/203_2.png) [@Baer\_DAOplomats](https://shutternetwork.discourse.group/u/Baer_DAOplomats)\ **Post date:** [March 3, 2025, 3:46pm UTC](https://shutternetwork.discourse.group/t/rfc-voting-cycles-updates/635/1 "2025-03-03T15:46:02Z")
# Summary > This proposal seeks to refine the **[Shutter 0x36 DAO’s governance cycle](https://shutternetwork.discourse.group/t/temp-check-introducing-voting-cycles/503)** based on community feedback. > > The proposal introduces **structured governance “seasons” (2 weeks each) with three 1-week sprints** to further streamline decision-making: > > 1. **Sprint 1:** Draft proposals (“RFC”) are shared for feedback. > 2. **Sprint 2:** Proposals with consensus move to **Snapshot** for voting. > 3. **Temperature Checks:** Non-binding votes can happen anytime without quorum requirements. > > [DAOplomats](https://DAOplomats.com) will aim to advance proposals on **Tuesdays of Sprint 2** for efficiency. `No on-chain changes are needed. No funds are distributed.` # Motivation The adoption of governance cycles has streamlined the voting process within the Shutter 0x36 DAO, leading to increased participation from token holders and delegates. The structured approach has enabled the community to provide constructive feedback on proposals during their development, before they reach maturity. Since implementing these cycles, the DAO has consistently achieved quorum through a predictable and well-organized process that balances ecosystem growth with governance enhancements. Building on this success, we aim to improve the governance cycle by integrating feedback from delegates, token holders, and contributors. # Specification This proposal pertains to governance guidelines and does not require on-chain actions or protocol changes. The proposed adjustments will be implemented socially. Governance in the DAO will be organized into decision-making cycles called seasons, each consisting of three sprints. Each season will last approximately two weeks, with each sprint spanning one week. - **Sprint 1: Draft Creation and Feedback Phase** Draft proposals titled “[RFC] Proposal Name” will be created and shared for feedback from the community and delegates. - **Sprint 2: On/Off-Chain Proposal Phase** Proposals that have gained sufficient consensus will be submitted to the main Snapshot space, titled “[SIP-XX] Proposal Name,” for an on-chain vote. - **Temperature Checks** Proposals with no on-chain impact or changes to social protocols may be posted on Snapshot at any time during a sprint. These “temperature check” votes must be clearly labelled as “[tempchecks]” and are not subject to quorum requirements. | Seasons | 2 weeks | | --- | --- | | On Proposals | During Sprint 2 | | Off-chain proposal on Snapshot | During Sprint 2 | | Temp checks on Snapshot | Independent of sprints | * * * `DAOplomats will aim to advance matured proposals on Tuesdays of every Sprint 2 to streamline the process.` # Next Steps - Gather feedback from the DAO about the next steps. - If the proposal passes, the [Shutter DAO public calendar](https://calendar.google.com/calendar/u/0/embed?src=c_1d55bd843b76d574d150f6ea02c383282de4460cc43c5ba7553b18f635d2aeef@group.calendar.google.com&ctz=Europe/Berlin) will be updated. # Copyright Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). ---
**Author:** ![5pence](https://dub1.discourse-cdn.com/flex017/user_avatar/shutternetwork.discourse.group/5pence/32/217_2.png) [@5pence](https://shutternetwork.discourse.group/u/5pence)\ **Post date:** [March 15, 2025, 5:49pm UTC](https://shutternetwork.discourse.group/t/rfc-voting-cycles-updates/635/2 "2025-03-15T17:49:35Z")
> [@Baer\_DAOplomats](#): > > DAOplomats will aim to advance matured proposals on Tuesdays of every Sprint 2 to streamline the process. Thanks @Baer_DAOplomats - Can you help me understand what this part 👆means? Also, just to be clear, this suggests that both Temp Check proposals and Social proposals would be done on Snapshot, but proposals that are labeled Temp Check would not be binding and could be posted at any time outside the cycle? Is the assumption then that if the non-binding temp check passes it would be put back up again as a social vote that would be binding? ---
**Author:** ![Baer\_DAOplomats](https://dub1.discourse-cdn.com/flex017/user_avatar/shutternetwork.discourse.group/baer_daoplomats/32/203_2.png) [@Baer\_DAOplomats](https://shutternetwork.discourse.group/u/Baer_DAOplomats)\ **Post date:** [March 17, 2025, 8:31am UTC](https://shutternetwork.discourse.group/t/rfc-voting-cycles-updates/635/3 "2025-03-17T08:31:46Z")
> [@5pence](#): > > Thanks @Baer_DAOplomats - Can you help me understand what this part 👆means? DAOplomats have sufficient voting power and technical abilities to move proposals to Snapshot and On Chain, instead of scattering votes across multipledays on the voting sprint, we can coordinate and upload the proposals on a singular DAO. - benefits, voters don’t have to check the voting portals multiple times during the week, but simply scroll and vote. > [@5pence](#): > > Is the assumption then that if the non-binding temp check passes it would be put back up again as a social vote that would be binding? Temp check are just to check the overall vibe of the community or prick a single choice from multiple options. there should always be a final binding proposal on chain or otherwise. ---
**Author:** ![Ricosworksa](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@Ricosworksa](https://shutternetwork.discourse.group/u/Ricosworksa)\ **Post date:** [March 17, 2025, 5:13pm UTC](https://shutternetwork.discourse.group/t/rfc-voting-cycles-updates/635/4 "2025-03-17T17:13:45Z")
Bad idea IMHO - adds useless complexities, no value. However, if the work is done pro-bono, meaning not remunerated, why not. ---
**Author:** ![Baer\_DAOplomats](https://dub1.discourse-cdn.com/flex017/user_avatar/shutternetwork.discourse.group/baer_daoplomats/32/203_2.png) [@Baer\_DAOplomats](https://shutternetwork.discourse.group/u/Baer_DAOplomats)\ **Post date:** [March 17, 2025, 5:55pm UTC](https://shutternetwork.discourse.group/t/rfc-voting-cycles-updates/635/5 "2025-03-17T17:55:30Z")
Hmmmmmm, The proposal aims to reduce the number of days it takes for a proposal to go to vote. We have introduced a 3-week cycle before, but now we propose reducing it to 2 weeks. > [@Ricosworksa](#): > > if the work is done pro-bono, meaning not remunerated, why not. We are not paid by any entity associated with Shutter to make this proposal. This is a natural follow-up of our [governance cycle proposal from October 2024](https://shutternetwork.discourse.group/t/temp-check-introducing-voting-cycles/503).