**Grant Proposal for Public HAUS**

**Client:** DAO Masons

**Champions:** Boiler, Dekan

**Project Lead:** UI369

**Product Manager:** Jord

**Engineers:** Dekan, Jord

**BizDev:** Boiler

**UI:** Sun

### Funding Request

We are requesting 15,000 ARB and 3,000 HAUS tokens to support the development and implementation of the Stem protocol. This funding will enable us to develop a general-purpose voting system that can be integrated into various dApps, aligning with Public HAUS' mission to move toward a decentralized, autonomous future. The HAUS tokens in this proposal will be delegated and used to participate in Public HAUS governance.

### Alignment with Public HAUS

This project represents a new opportunity to expand the Public HAUS governance modularity and footprint. Stem introduces a new set of contracts that complement DAOhaus' existing toolkit. Public HAUS already uses a successful TCR module internally, and Stem aims to build on this by making token-weighted voting more accessible. This project will provide:

- **Improved Decision-Making:** By moving beyond simple Y/N votes, Stem allows for more nuanced and effective decision-making processes.
- **Customizable Voting:** DAOs can tailor their voting mechanisms to fit their specific needs, from who can vote to how votes are counted and executed.
- **Trustless Execution:** Ensures the integrity of the voting process with automated, trustless execution of vote outcomes.
- **Alignment with Public HAUS' Quarterly Objectives:** The second-highest choice in the recent objectives was for a "Signal Session reboot and Product." The STEM protocol meets this objective.

### Project Overview

**Role Structure:**

1. **Project Lead:** Oversees project management, communication, and accountability.
2. **Smart Contract Developers:** Write and test contracts (Stem modules, contest contracts, factories).
3. **Maintainers:** Manage the repository, workflow, and external contributions.
4. **Indexer Developers:** Implement indexers for Grant Ships Voting, compare technologies, and write configurations.
5. **FE Developer:** Build two applications using STEM, including the Grant Ships voting interface and a general-purpose beta client.
6. **Project Manager:** Track progress, coordinate efforts, and manage communication.
7. **UI Designer:** Design the UI for the voting interfaces.
8. **QA:** Test the applications and contracts for bugs and UX issues.
9. **Copywriter:** Create public-facing content and internal documentation.
10. **BizDev:** Write grants, build connections, and find integration prospects.
11. **Devrel & Integrations:** Ensure usability and adoption by external developers.
12. **Product Designer:** Develop product ideas and outlines using Stem.

### Key Outcomes

1. **Core Contracts:**
- Develop and test contest contracts and necessary modules.
- Enable DAOs to deploy Stem implementations.
- Create a recursive voting implementation.
- Develop an execution model for vote outcomes.
2. **Voting Application Layer:**
- Implement an indexer.
- Build a front-end page on app.grantships.fun.
- Build a general-purpose front-end.
3. **Community Building:**
- Inspire external teams to use Stem.
- Achieve contributions and reviews from external developers.
- Engage with potential user projects.
4. **Signal Sessions:**
- Host feedback sessions.
- Demonstrate the codebase.
- Develop a design concept for Public HAUS.
5. **Product Specs:**
- Design five new product specifications using Stem.
- Ensure these specs solve existing problems in the space.

### Key Deliverables

- STEM contract framework
- Voting interface/indexer for Grant Ships
- Signal Sessions proposal, POC mock, and product spec
- Four additional product specs
- Open-source general-purpose indexer
- General-purpose front-end

### Timeline

Much of this project is already retroactive. Significant work has been done on the contracts, with plans to implement a front-end and live vote on the Grant Ships app starting June 7.

### Ongoing Processes

- Weekly all-hands meetings
- Regular updates and social media posts
- Developer and BD & Marketing meetings (if traction is gained)

### DAO Mechanism to Track Progress

- Utilize a passive check-in system with PR submissions.
- Log hours worked and descriptions in individual log files.
- Team lead reviews and merges PRs for progress tracking.

### Case Study: Grant Ships

**Grant Ships: An Evolutionary Grants Framework for the Arbitrum Ecosystem**

**TLDR:** The Grant Ships platform allows multiple teams (aka Grant Ships) to do grant allocation under one DAO's umbrella. The sponsor DAO puts grant funds into one fund, then it is split among the multiple teams.

### Case Study: Public HAUS Signal Sessions

**TLDR:** Public HAUS and RaidGuild teams have used Signal Sessions for the past year. This offers valuable lessons learned, validation, and feedback from the participants.

### Adjacent Tools

We have found other similar products validate the use case but fall short in some of our requirements of modularity and extendability. Our users would need to go to another app to use them. We needed a way to build weighted voting directly into custom app solutions and multiple diverse clients. While one might think that web3 should have this by now, it doesn't. Stem provides a more integrated and seamless solution, giving DAOs a more robust set of tools for voting, beyond Yes/No.

### Conclusion

STEM aims to revolutionize on-chain decision-making with customizable and trustless voting mechanisms. This proposal requests support to build a foundational tool that will benefit DAOs and the broader decentralized community, aligning with Public HAUS' goals of enhancing governance structures.

For further details and access to the contracts, please visit our [GitHub repository](https://github.com/stem-voting/protocol) or check the on-chain [deployments](https://hackmd.io/A26lTAIOS1qWwppF8ndDKQ).