---
# System prepended metadata

title: 'DAOhaus Product Sprint #1 Output'
tags: [Product]

---

---
tags: Product
---

![](https://i.imgur.com/TdwREHE.png)

# DAOhaus Product Sprint #1 Output

# Overview

### Summary of output
Feel free to dig into these more below in the Sprint documentation.

- Community personas and their needs/desires
- Competitive Analysis
- Methodology for collecting and implementing stakeholder feedback
- Generalized 30/60/90 plan with detail on first 30
- Theat Analysis = xDAI UX and migration explorations
- Exploration into subgraph working with Molochs not launched through DAOhaus
- Beginnings of Boost infrastructure (types/methods)
- View of Ragequits in Pokemol

### Growth Strategy
Our current community is an array of all communities that are on DAOhaus, use (or are looking to use) Molochs as their coordination mechanism. Our goal is to ensure they have what they need, when they need it, and we are not there yet. When current community needs are approaching fulfillment, we can begin to stretch out to other user/community types.

North Star => More Actively, Engaged DAOs. Are there more and if so, how much? Persevere, Pivot, or Perish.

### Existential Threats
- Gas Prices: Work with stakeholders to (minimally) optimize xDAI as a bandaid while communicating directly with L2 providers to battle test for future-friendly Eth2 migration
- Crypto onboarding: For now, we're focusing on current communities which have or know how to get & interact with Eth, but will need to be cognizant of this problem as it arises more frequently with n00bs.

### Endgame
Our product targets by end of runway.  
- Boosts proliferated (Target Amount of revenue = 5k?)
- DAO Experience Solid & Gamified (Ux, Ui, Content, Feedback)
- Get L2/Eth2 ready and battle test along the way
- Modulation of Moloch to expand growth vectors to other communities
- Smooth ongoing contributor experience
- Traction Metrics (10x DAOs/Users WeeklyActive, MonthlyActive)

#### 30

BUIDL FOCUS: REFACTOR + REVAMP

1. Usability. Build for our users. Make DAOHaus more fun and easy.
    - Pokemol + Daohaus integration
    - Pokemol UX improvements
    - Branding & Styleguide basics + implementation
    - xDai UX
    - Refine target users/personas

2. Revenue. Build for our investors. A focus on boost infrastructure definition and initial development.
    - Boost UX - Purchasing and Activating
        - Maybe 2 boost packs - IDO and Theme+
    - Start infrastrucutre to activate in-app boosts (off-chain activation storage)

3. The HAUS. Build for our contributors. Clear tech debt and prep the code base for greater contribution and speedy future development.
    - Define Stakeholder Feature Input flow
        - Input -> Triage -> Roadmap
    - Develop QA process with RG wine cellar
    - Pokemol code refactor
    - Foundations for future contributors

4. Contract audits

#### 60

BUIDL FOCUS: CHARGING EARLY AND OFTEN

1. Usability.
    - Continuous user testing
    - UX/UI iteration and continue from above
    - v2x/future moloch UX 
    - xDai implementation
    - Subgraph infra updates to enable factory upgrades
        - Enable v2x and get ready for v3 molochs
        - Ability to pull in non-DAOhaus summoned molochs (be the front door to the world of moloch)
    
2. Revenue.
    - Launch 1st in-app boosts allowing users to give us money 
        - Theme+ boost pack
    - Develop implementation plans for other boost
        - 3rd party boost with abridged - notification or permissioned chat
        - Design and begin developing onchain boost infrastructure and IDO boost pack

3. The HAUS
    - Learn from previous month and refine/optimize

#### 90+

BUIDL FOCUS: BOOST PROLIFERATION

1. Usability.
    - Continuous user testing
    - UX/UI iteration based on user feedback
    

2. Revenue.
    - Onchain boost infrastructure development
        - Packs + single boost purchases
    - Implement 3rd party boost with abridged - notifications or permissioned chat 
    - Implement IDO Boost pack
    - Add features to Theme+ boost pack

3. The HAUS
    - Learn from previous month and continue to refine/optimize
    

---
### Personas / Profiles
Six key personas were analyzed according to their expected membership size, bank size, chain needs, capital source, key priorities, unique feature needs and historical DAO types. A common scenario and success metric is provided for each:
1.     Grants / Accelerators
1.     Ventures / Investments
1.     Guilds / Services
1.     Clubs / Social
1.     Non-profit / Impact
1.     Product / Project

#### **Common Themes:**
Common themes found among all persona / profile types:
```
Community
Shared expertise
Network effects
Common interest
Like-minded
Alignment
Value-first
```
#### Budget

There is a lot to design and build 😅 





---

# Sprint Documentation

---


# DAOhaus Stakeholder Input

## Objectives
Develop a process and/or mechanism to
1. **Elicit valuable and frequent feedback, input, and ideas from stakeholders**
2. **Triage it for action**

We want to maximize the amount and quality of input we receive from all stakeholders and the market, with the goal of optimizing our collective decision-making about what to build, how to bring it to market, and how to manage the community.

In the long run, as governance and control over DAOhaus decentralizes, this will likely need to develop into formal mechanisms for incentivizing and curating input and ideas. For now, we should use the simplest tools to get the job done; but we should also formulate our process with an eye towards future decentralization.

## Who counts as a stakeholder?
- DAOhaus core team ("War Camp")
    - e.g. from other circles
- DAOhaus lootholders
- DAO summoners and participants
    - includes Molochs as well as other dao frameworks
- Prospective DAO summoners and participants
- Eventually: $HAUS holders
- Market trends & conditions
    - While no single entity represents these trends, they, like honeybadgers everywhere, DGAF; we are beholden to them whether we like it or not, so we need to learn from them.


## Elicitation & intake
### Desired properities
- submission is publicly accessible
- relatively easy to acccess / submit
    - minor amount of friction is fine -- reduces spam
- flexibility to handle both quick ideas and more fleshed out thoughts
    - title (w/ reasonable character limit)
    - longer description (optional)
    - link to additional content (optional)
    - tags? labels? categories?



### Short term
- basic submission

#### potential intake venues
- #bright-ideas
- public-facing discord channel
- twitter
- github issues
- google sheets or forms
- typeform
- airtable form
    - https://discordapp.com/channels/709210493549674598/740299170589704364/743575439188033547

### Long term
- incentivization for good ideas
- auto-logging bot (discord emoji?)

## Triage
### Goals
- decide what to work on and when
    - importance and urgency
    - alignment to mission and strategy
- make available in a timely and actionanable manner to inform real decisions

### Potential formats
- kanban-ish (now, next, later, never)
- scoring
- categorization

### Potential communication venues
must be viewable by stakeholders
- github project board
- airtable base
- trello

### Curation
We need some way to collectively deal with the incoming ideas without a centralized decision-maker

#### Short term
1. **Initial routing**: categorize by relevancy to circles (paladins, alchemists, rangers, magesmiths)
    - would be slightly easier if submissions included some kind of category
3. **Secondary triage**: Each circle then applies their chosen [format](#formats)
4. **Cross-pollination**: For any important items that would impact other circles, present to full War Camp to reach consensus
    - War Camp "market listening" agenda item

Given our distributed structure, long-form writing will likely be useful to support positions for/against ideas.

#### Long term possibilities
- proofed curation market
    - stake $HAUS on ideas, get rewarded for ideas used to ship something (new tech, communications, etc.)
- sourcecred
- futarchy

___

# DAOHaus Divergent Spitball

## 30 days

![](https://i.imgur.com/eZFXGIn.jpg)


Refactor + Revamp

Focus on the these categories.

1. Usability. Build for our users. Make DAOHaus fun and easy.

2. Revenue. Build for our investors. A focus on boost infrastructure definition and initial development.

3. The HAUS. Build for our contributors. Clear tech debt and prep the code base for greater contribution and speedy future development.

- list refactor areas
    - remove all sdk artifacts
    - beef up eslintrc + .prettierrc and enforce usage
    - refactor proposal forms
    - refactor userwalletsf
    - sk sweep
    - move repos
    - dev instructions/readme pass/gitflow
    - bug sweeps
    - staging setup
    - create roadmap to further contrib (ie. more styled components, oss flows)
- Try out Wine cellar QA
- xdai prep - see release - network switcher, hire rg for token bridge
- boost prep - context / offchain implementation of theme boost
- 
- dh + pokemol
    - https://moloch.daohaus.club/dao/0xbeb3e32355a933501c247e2dbde6e6ca2489bf3d




## Quick wins
Tight cycles - value getting features to users - real world feedback

![](https://i.imgur.com/Fb1kRbm.jpg)

🖕🖕 Rage quit history 🖕🖕
http://localhost:3000/dao/0x0a8c334b3131a5b8ecf1d4feaa4078cfcf2ab362/rage

![](https://i.imgur.com/ddZrdYm.png)




## Hard problems
Subgraph dependency
- allow new factories or updated factories
- index events for daos not launched from our factories

https://thegraph.com/explorer/subgraph/skuhlmann/daohaus?selected=playground
https://api.thegraph.com/ipfs/api/v0/cat?arg=QmcHRzKNYmHYomf9jiAdapqV9wAFgb9BibhXQGAdEj5DFo

```javascript
export function handleSummonCompleteMoloch(event: SummonComplete): void {
  // gets all registered doas from ipfs
  MolochV1Template.create(event.address);

  let hash = "QmcHRzKNYmHYomf9jiAdapqV9wAFgb9BibhXQGAdEj5DFo";
  let data = ipfs.cat(hash);

  if (data !== null) {
    let value = json.fromBytes(<Bytes>data);

    // if (value.kind == JSONValueKind.ARRAY) {
    let addresses = value.toArray();

    addresses.forEach((address) => {
      let hexAddress = address.toString();
      MolochV1Template.create(Address.fromString(hexAddress));
    });
    // }
  }

  handleSummonComplete(event);
}
```


## Boost Implementation types

![](https://i.imgur.com/ogZZpiz.jpg)


#### In-app
- Code for the feature lives in the main react app
- Boost context can turn it on-off
- Likely implemented by product team initially as it's tightly coupled to main app code

ex: 3box chat
- components would live in the app
- boost context would toggle on/off


#### Config based/In-app
- Metadata that hydrates a feature can live outside the app, but code for the featue is in-app

ex: Custom theme
- css values can live in a config (maybe in ipfs?)
- Boost context can grab and put into the app based on some custom code that reads those css values 


#### Outside app
- Some service or tool independent of the core app
- Might need access to the boost registry to see if a dao has activated the boost
- Various implementation paths

ex: Notifications
- Some other app looks at registry and does something if the boost is activated

ex: Permissioned chat
- Needs to check boost registry AND user eth address and dao contract to verify membership


#### In-app/Outside app hybrid
- Features in app interact with other apps or contracts
- Boost implementation might require a separate app launch or contract deployments
- Boost context can turn UI elements on/off
- Might need configuration somewhere to track outside app details, ie) contract addresses or 3rd party app urls


ex: Transmutation raise boost
- Requires minion/transmutation/trust contracts and factory to launch
- Configuration stoted in subgraph
- Boost registry/context turn ui element on/off

## Components

#### Boost context
- Pokemol context to query boost registry and toggle in-app features on/off

#### Boost registry
- Some datasource to track boost types and dao activations of the boosts

#### Boost bank
- $$ daos pay for boosts

___

# **Daohaus Profiles / Personas**


### **Grants / Accelerators**
Smart distribution of funds leveraging the expertise of members.

	
**Membership:** Small - Medium 
**Bank:** Medium - Large
**Chain:** Mainnet
**Capital Source:** Membership, grants, donations
**Priorities:** Fair voting, transparency, usability, visibility. 
**Unique Features:** _
**Historical DAO Types:** Moloch

**Scenario:** A community spots a need for early-stage exploration around new ideas and forms a group to allocate resources and expertise. 
**Success:** Multiple successful projects are launched through the early incubation provided by the group.


### **Ventures / Investments**
Profitable investment of funds by leveraging expertise, dealflow of members.


**Membership:** Small - Medium
**Bank:** Large
**Chain:** Mainnet
**Capital Source:** Membership investment.
**Priorities:** Legal protection, auditability, security.
**Unique Features:** Dividends, smart distribution
**Historical DAO Types:** Moloch, DAO Stack (DXDAO)

**Scenario:** A group allocates resources and forms a community around a series of opportunities to grow capital. Profits are shared amongst the group.
**Success:** Membership investments are profitable.


### **Guilds / Services**
Working groups with team network effects that enhance value.


**Membership:** Small - Large
**Bank:** Small - Medium
**Chain:** Sidechain or Mainnet
**Capital Source:** Membership, grants, member taxes / dues.
**Priorities:** Enhanced coordination, legal protection, auditability.
**Unique Features:** automatic tax, NFTs, gamified engagement (bots), escrows, client engagement features, storefronts, signups, forms, ptokens.
**Historical DAO Types:** Moloch, DAOStack

**Scenario:** Individuals with complementary skill sets form a community to better deliver value. Clients provide resources for services, which members return in part to grow the bank.
**Success:** Members receive steady work and help grow the guild bank. The brand is reputable and trusted.


### **Clubs / Social**
Aligned membership based on a common interest or goal.


**Membership:** Medium - Large
**Bank:** Small - Medium
**Chain:** Sidechain
**Capital Source:** Membership, grants, donations
**Priorities:** Enhanced coordination, transparency, inclusion, customization.
**Unique Features:** NFTs, gamified engagement, profiles, rewards, chat / ptoken, social connections
**Historical DAO Types:** Moloch

**Scenario:** Individuals align based on common interest or goal to coordinate and allocate resources amongst themselves. Opportunities are shared amongst the group.
**Success:** Members develop personally, establish friendships and achieve individual goals.


### **Non-profit / Impact**
Coordinated change around a common cause.


**Membership:** Small - Large
**Bank:** Medium - Large
**Chain:** Sidechain or Mainnet
**Capital Source:** Grants, donations
**Priorities:** Transparency, auditability, inclusion
**Unique Features:** Subscription, NFTs / rewards, visibility
**Historical DAO Types: _**

**Scenario:** A community eforms around a need for change and a shared vision on how to enact it. As the bank grows, resources are allocated to impact initiatives.
**Success:** Measurable change is made and additional funds are raised to scale impact.


### **Product / Project**
Product creation through alignment of like-minded builders.


**Membership:** Small - Medium
**Bank:** Medium - Large
**Chain:** Sidechain or Mainnet
**Capital Source:** Member investment, external investment, grants.
**Priorities:** Enhanced coordination, customization.
**Unique Features:** Transmutation contract, Escrow, community feedback features, access to web2 building tools (HackMD, GitHub)
**Historical DAO Types:** Moloch, Aragon

**Scenario:** A team forms to build a product based around a shared vision. The ownership is spread among members and the work is completed in startup fashion.
**Success:** A product is delivered with product-market fit. Additional funds are raised for next milestones. Member equity vests with growth multipliers.


## **Common Themes:**
Community
Shared expertise
Network effects
Common interest
Like-minded
Alignment
Value-first
    

# Competitive Analysis

Right now, Moloch is by most metrics the second-most popular DAO framework on Ethereum behind Aragon. The most successful Moloch DAOs fall into the Venture and Grant personas (MCVC, LAO, MC, Moloch), though some of the more emergent DAOs like MGD and MachiX are more like social clubs and Raid Guild is proving out the guilds / services use-case. 

Landscape Analysis: 
https://airtable.com/tblXfRTeqFKwDkept/viwPGJeJHh7l83pjL?blocks=hide

**TODOs**
- Add Gnosis to comparisons (similar utility)
- Matrixed together with personnas. Like, which personas are gravitating to which dao frameworks, and why

---

Pokemol UX Revamp + Boosts (WIP)
https://www.figma.com/file/DyuLU9SbCf8BWNrUMnSXsi/DAOHaus-v2-UX?node-id=409%3A826

--- 

# xDAI 

**TODOs**
- Discuss more Friday and refine following

## UX/Design Thinking

## Test 1
Dao summoned on xDAI. No need for a mainnet DAO. Users just bridge in/out to tribute/withdraw tokens

### Invite members
- If need tribute, then some bridging for each token required
- If no Tribute, then just Shares/Loot with no bridging. Well bridge for wxDAI, but that can be automated potentially

### Member Prop

Request Shares/Loot 
Submit Tribute
- DAI => xDAI => wxDAI
- ETH => Dai => Approve => xDAI => wxDAI => Approve => 
- pToken, and rando tokens => Multi-token xDAI bridge?
DepositToken (default all to wrapped xDAI?)

### Ragequit

Member gets % Tokens on xDAI
- wxDAI => xDAI => DAI
- wxDAI => xDAI => DAI => Eth
- pToken, and rando tokens => Multi-token xDAI bridge out

### Funding Prop

10000 wxDAI proposed and passes
Member withdraws from 'internal balances'
- wxDAI => xDAI => DAI
- wxDAI => xDAI => DAI
- pToken, and rando tokens => Multi-token xDAI bridge out

### Pain Points:
Withdrawing should be well incentivized financially, so Tributing into the DAO would seem to be the largest pain point. Dream UX would involve a multitoken bridge out to mainnet that accepts an array of `[tokens, balances]` and bridges them back to their mainnet counterparts.


## Test 2
Dao summoned on Mainnet. Perform all activity on xDAI and mirror back to Mainnet.

Problems to solve for:
- If running xDAI for voting only, seems impossible or irrelevant to mirror on mainnet. 
- Possibility to watch and store all transactions over a time period (voting + grace for example) and once every period, batch all transactions in the mainnet dao to save gas? I don't think so, as cannot send funds from another user's address, which maybe could be fixed with a permissioned relayer, but still seems wildly complex and dangerous with .
- Possible to use a multisig on mainnet instead, which watches the state on xDAI to drop mainnet funds when relevant? See Minion use-case in Test 5

## Test 3
Dao summoned on xDAI (wxDAI only)
- autowrap xDAI into wxDAI and vice versa like v2x
 
Using wxDAI only, all functionality should be preserved with only the need to bridge one token back n forth when tributing/withdrawing

## Test 4
Mainnet DAO with a shit ton of tokens - RG, MCV

Problem to solve for: 
Migrating many tokens to xDAI

### Power Move:
multitoken bridge that accepts an array of `[tokens, balances]` and bridges them to xDAi counterparts and distributes to xDAI guildBank 

Problems:
Tokens like LPs? Programmatic distribution
Verification of token pairs (xDAI <-> Mainnet)

## Test 5
xDAI DAO and Multisig/Minion on Main

All funds held in the Minion on Mainnet
Needs Shares mirrored from xDAI
Needs Token balances mirrored from Main

### Tribute
Member submits prop on xDAI
If passes, the member needs to send tribute to the Minion to claim Shares or smth

### Ragequit
Minion watches for Ragequit/Withdraw, sends proportionate share of tokens to addr on Mainnet and updates Members/Shares/Loot state.

### Funding Proposal
Submit proposal to send 10000 dai to addr
Voting on xDAI and if passes
Minion sends 10000 to addr

Submit Proposal to send 5000 pToken
Voting on xDAI and if passes
Minion sends 5000 to addr

Pros/Cons:
No need to bridge any real mainnet value, but might require a new contract for state mgmt as well as other UX problems like having to send funds to the Minion for tribute

**Miro** => https://miro.com/app/board/o9J_kn5T6YY=/

## UX screenshots

**Tribute**

![](https://i.imgur.com/JIGYlWr.png)

**Ragequit**

![](https://i.imgur.com/HaSmIEn.png)



---

## Migration of hausDAO

![](https://i.imgur.com/NW80j4f.png)

## clone dao and deploy on xdai
summoner #1
* add summoners (2hr voting periods, 10 summoners, may not be needed) 
* around 60 proposals total (60*2 = 120hrs = 5days)
* add loot and core share values

if others help would take 5 days to first get helpers in

deposit price = 20 * 60 = 1200
no processor bots so should get full refund

* make proposal to withdraw all funds
* bridge to xdai
* wrap with wxdai
* send to bank

may have to do 100k a day because of bridge limit

deploy transmutation/trust contract

### notes
could speed up voting period for xdai, shorter period would mean faster migration

if initial summoner does not do all the proposals we would have to wait at least 5 days

### gas cost 
~5xdai proposal/member management and contract deploys vs $3-5k on mainnet
still needed on mainnet gas fees - $500 to process outstanding props
bridge $10-$50



## timeline
min 5days to clone dao
3-5 days to migrate funds across bridge depending on bridge limits


# xdai current dao migration

withdraw all funds to a xdai bridge relay. 
then relay deploys a v2x dao on xdai with all members and share values
drops in the funds.
Could even give every member 1xdai to get started.










---

Archive of initial setup

### Potential Deliverables
Product Purpose and Goals for the duration of Round 1
Refined Roadmap (30,60,90) Try to package up starter initiatives
Some Contributor Experience and Product Management process
Methodology and process for User/Market/DAO Feedback/Testing 
=> Afterword diverge to UX and Tech Architecture buidl


### Sprint Schedule
Tues - 1. Understand (1p-3p PST)
Wed - 2. Diverge (async)
Thurs - 3. Converge (1p-3p PST)
Fri - 4. Refine (async)
Mon - 5. Present (war camp 1p PST)

### Figma 
https://www.figma.com/file/27yvRX8MyimcqkgxlE515S/Product-Sprint-1?node-id=1%3A32

### Participants (8)
~Sam (dev)
~Spencer (pm)
~Dekan (dev)
~James Y (dev)
~Scott (dev/design)
~Bill W (design)
~Darren (design)
~Ven (design)

### TODOs
~~Set up Figma (VG)~~
~~Send invites~~

---

## Notes

Getting a good product base setup helps lower coordination costs for contributors. i.e. we can spec/design things and pass to RG.

- Innovation/Agility
- Composability
- Usability
- Focus on value for current use-cases

Questions for DAOs
- As a DAO what parts of Ethereum do you want to interact with most frequently?

### List of priorities
1. transaction costs
2. quick win -- e.g. public-facing progress
3. DX / tech debt reduction
4. Further usability enhancements


## Start
Credible announcement of where we are, where we're headed, and how we look to get there.
- Existential threats = TX costs
- DX/UX enhancements

### 30
Quick Win = Something that pleases all stakeholders.
User research and document direction forward
Clear Tech debt and squash some bugs
Getting daohaus/pokemol aligned
Basic style/brand guide
? Audits (Minion, ENS, Transmutation, Trust)
xdai research

### 60
First Boost and Boost Pack (DAO theme, notifications)
Side chain focus
Start on IDO Boost

### 90


### Design Studies / UX Research:
* 	Error Analysis
* 	Extreme User Interviews (Extreme familiar/unfamiliar)
* 	Five Whys
* 	Flow Analysis	
* 	Fly on the Wall
* 	Long Range Forecasting / Long Term Roadmap
* 	Character Scenarios / Personas*
* 	Scenario Testing
* 	Shadowing
* 	Card Sort
* 	Character Profiles*
* 	Competitive Product Survey*



### longer term / out of scope
- expanding to compete head to head with Aragon