---
# System prepended metadata

title: PubHaus
tags: [Project Proposal Engine]

---

---
###### tags: `Project Proposal Engine`
---

# PubHaus

### 1. Name or working title of the project
PubHaus

### 2. A logline (one sentence description of the product)
Pubhaus is a dao app for managing content and publications 

### 3. Details

Pubhaus is a publishing platform that allows communities to use DAO governance to manage content. Users can vote on publishing proposals to decide whether or not content is considered published or within canon. Users can also manage voting shares, onboarding, and their publication's funding/treasury/revenue. 

On the reader side, data stored in the subgraph can be hooked up to Static Site Generators to create simple, fast-loading, and easy to read interfaces. This allows DAO communities to attract readers with better SEO and ease of use, while abstracting away the DAO and governance complexity. 

#### who will use this 

- Writers in Web3
- Editors in Web3
- Readers in Web3
- Other DAOs looking to publish releases or newsletters

#### why would it be useful

- Content creators are beginning to form DAOs. Currently, tooling is either way too complicated or too centralized to actually help DAOs manage their content. 
- Community input. Because DAOs are free to configure their own governance, a pub DAO would be able to gather and utilize community input in content creation. 
- Community Contribution. Unlike many Web3 or DAO tools, PubHaus has the ability to actually simplify the publishing process. 
- Monetization. Built into the platform would be the ability leverage revenue streams. Token gating content, minting content into NFTs, streaming memberships, DAOs will be able to leverage the revenue stream of their choice. While these tools have existed for some time, it has yet to be bundled with hard, onchain community governance. 
- Interop. The uniformity of the underlying protocol would allow content DAOs to interoperate in ways that would not have been possible before.  
- Censorship Resistance. All posts are published on IPFS. 

#### what problem is it solving
- Real governance in content DAOs. Since many content creators are non-technical, early content creators have had to use lesser means of governance (off-chain polls, Discord, dictators, shouting) to decide on what gets published. PubHaus will be designed to be as UX forward as possible. 
- Content Capture. More important than anything, a community should retain freedom and autonomy over their own content. All too often, we're seeing censorship from platforms, regulators, even from editor-dictators with a conflict of interest. PubHaus is decentralized by default. 
- The attention economy. By aggegating the best in Web3 monetization, removing the complexity and friction, and opening it up to a real DAO with real governance, we can begin to piece together a content monetization strategy that is superior to the AI/Advertising monstrosity known as the 'attention economy'. 
- Interaction with the users.  


#### how can it be built with our tooling
- We use our existing tooling to create a publishing dashboard. Many of the proposals created here will interact with Poster for content posting and organization. 
- We use SSGs templates to generate user-facing apps. These remove any trace of the complexity that we see on the backend. 
- Our dashboard can provision new publishing related services. 
- Content NFTs are probably better off being bought and sold on an existing marketplace (open to discussion). 


#### why the timing is good

- Currently there's a rush in interest in using crypto beyond financial applications
- Many of these applications require some focus on lore, narrative, or content distribution
- Existing tools make decentralized mgmt nearly impossible. 

#### how it might generate revenue

- NFT mint, fee split
- SSG frontend templates
- Fee split for memberships and token gating


#### anything else you feel is important.

This needs a big edit