---
tags: SOP, checklist
---

# Platform seasonal roll over SOP and check list

THis is a two week event that happen once a quarter between seasons

> note: these are time sensitive executions with snapshots, so voting/grace should be taken into acount

## Map Activities:

### Part 1 (end of season)
proposals should be submitted one week before the end of the season to give time for voting/grace.
- [x] Verify that Open Staking is Paused (should be paused before retro sigsesh starts)
Create Proposals
- [x] **Transfer HAUS Token to the Reward Committee:**
- [ ] Create a proposal to transfer 4000 HAUS (~3% of total uncirculating supply) to the reward committee Safe https://app.hatsprotocol.xyz/trees/10/24?compact=true&hatId=24.3.2
- [ ] note: this will be transfered to stake claim after results
- [x] **Kick Off Retro Signal Session for the Current Season:**
- [ ] Create Proposal to start retro signal session https://signal.daohaus.fun/#/0xa/0xf5d6b637a9185707f52d40d452956ca49018247a
- [ ] the proposal should execute after the open staking has concluded and after fund transfer in step 1 and should run for 5 days
- [ ] notify with communication
- [ ] Use last seasons retro proposal as a template
- [x] **New open staking shaman**
- [ ] delpoy shaman (TODO: instruction on deployment)
- [ ] proposal to chreate new manager shaman
- [ ] summoner address https://optimistic.etherscan.io/address/0x748b854efbeadad9a9ed3bea54413b3403b48053#writeContract

3. **Notify Community:**
- [ ] Draft a clear and concise announcement message.
- [ ] Share the notification on Discord publichaus chat
- [ ] Start a forum post for the upcoming retro for people to share demos, recognize other members and "did a things".
- [ ] Monitor channels for any questions or concerns and respond promptly.

4. **Host Demo Day:**
- [ ] Plan and schedule the Demo Day event. 1 hr event held durring the weekly community call
- [ ] Coordinate with presenters and ensure they are prepared.
- [ ] Gather feedback and insights from the community during the event.
6. **Reward Winners Based on the Outcome (reward comittee):**
- [ ] Verify results from the Retro Signal Session.
- [ ] Determine and allocate rewards to the winners.
- [ ] to determin total distributed look at the total participation compared to the total staked. this % of 3% of total uncirculating haus is distributed to the winners based on the QV ranking.
- [ ] rewards are distributed using the stake claim contract https://optimistic.etherscan.io/address/0x22f09c11de8f059840fd8f60b11b8d60dea0e011#code
- [ ] stake claim address 0x22F09C11De8f059840FD8F60b11b8d60DeA0E011
- [ ] Communicate reward distribution to the recipients. include a spreadsheet of results, see previous season for example

### create proposals part 2

8. **Kick Off High-Level Objective Setting Signal Session:**
- [x] open staking should be started before execution
- [ ] rewards should be distributed before execution
- [ ] Schedule the High-Level Objective Setting Signal Session.
- [ ] Create an agenda outlining the objectives to be discussed.
- [ ] Use the SigSesh app to facilitate the session.
- [ ] Document the agreed-upon high-level objectives.
8. **Create a Document Outlining and Summarizing Results:**
- [ ] Compile information from the Retro Signal Session and High-Level Objective Setting Signal Session.
- [ ] Summarize key decisions, actions, and objectives.
- [ ] Share the document with the community through Discord and the forum.

### Document Inputs and Outputs:

- **Inputs:**
- [ ] Last season review document.
- [ ] Retro Signal Session summary.
- [ ] High-Level Objectives summary.

- **Outputs:**
- [ ] Comprehensive document outlining and summarizing results.

### Timeline and Duration:

- [ ] Plan for a 2-week period between seasons.

### Communication Channels:

- [ ] Utilize Discord publichaus chat and forum for community communication.

### Technology Used:

- [ ] Host Signal Sessions in the SigSesh app.