---
tags: v3
---

# Daohaus v3 Roadmap Working Session

## Destination

- Re-designed/engineered platform
- Core component and data delivery libraries
- Enable micro app structure/bolt-ons

### Roadmap
- What is the first deliverable?
- Last roadmapping session we descided to start with the core dao ui/moloch v2 contracts/component+data libraries
- would pan v3 integrated next
- Should we support v2 in a new platform?
- We are going to be allocating a ton of resources to this does it make sense if v2 daos are upgraded to v3?
- How does Daohaus as a governance platform infro this?
- How should we prioritize apps? what to push to community
- Core dao ui
- Summon
- v2 -> v3 upgrader
- Hub
- Marketplaces
- Explore/allies/social


#### Moloch version options

##### v2 contract (reskin + dao core ui)

| Pros | Cons |
| -------- | -------- |
| Fastest to market - few unknowns/infra in place | Does a reskinned v2 add a ton of value if it's just the core dao platform? |
| Path to most reliable codebase - learning directly applied | v3 is several months out |
| Gives rage time to fully explore v3 and prep for integration | How do we make it clear to users how to distinguish between v2 and v3 moloch DAOs once both in place? |
| Supporting both versions forces us to design in a way that can support future versions| Supporting both versions adds complexity upfront |

##### v3 contract (dao core ui)

| Pros | Cons |
| -------- | -------- |
| v3 gets to market quicker | Lots of unknowns - contract just finished / lots of UI changes / Unaudited contract |
| Building out the new UI take a while and will likely line up with moloch v3 audit timeline | More infra to build upfront |
| Addresses a lot of current user issues | Learning about v3 ux/use cases as we go |