---
###### tags: `Dungeon Master`
---

# Dungeon Master v2 Proposal: Phase 1

### Summary

This RIP is to build Dungeon Master v2 with an emphasis on features that enhance Dungeon Master as a Moloch Hunter’s tool. In addition to the actual buildout of v2 features, we’ll be creating processes for contribution and bounty management.

### Overview

Dungeon Master v1 focused on creating a functional share-gated tool that replaced our Airtable for Raid management. The current version is stable and working for the primary purpose of providing insight into Raid lifecycles. This enhancement adds new functionality providing additional visibility into Raids, allowing for more folks to identify Moloch sightings and intercept them before they grow into larger issues.

v2 updates for Dungeon Master will use a new tech stack and API leveraging Hasura and SIWE. This is an opportunity to switch the UI to utilize the [Raid Guild Design System](https://github.com/raid-guild/design-system).

We’ll be kicking off the project with a thorough *Discovery Phase* where we validate our initial assumptions and clarify that our user stories match the actual use cases from the guild. From there, we’ll validate that our proposed features match the discovery output through a comprehensive *Testing Phase.* *Analysis and Synthesis* of these learnings will result in a finite build strategy for optimizing DMv2.

---

- Add visualization/story from Cleric POV of the use case of the tool

---
### Problem / Solution / Hypothesis

[*Adapted from the v2 overview.*](https://www.notion.so/jonathanprozzi/Dungeon-Master-v2-Overview-1deae29afed84b66868c749e3bfcea9b)

### Success / OKRs
#### Development

- Migrated API to Hasura + Postgres
- Migrate data from Mongo to new backend
- Add additional quality-of-life and optimization features, [including but not limited to those outlined here.](https://hackmd.io/@raidguild/BJgndvpKK)

#### Research

- Provide coherent documentation for the existing product
- Elaborate our own learnings into workshop-style training sessions with Clerics
- Ideate a method of capturing feedback for informing future improvements


---

- Discovery MVP: Interviews > User stories > Simple Sitemap?
- Testing MVP: Stories script > Testing sessions > Friction map?
- Frame into milestones so funds can be released periodically
- In combination with a Yeeter
- Foundation funded by RG RIP: MVP research delivered
- Each milestone associated with a fundraising goal on the Yeeter
- Community votes with their dollar to guage dedication to research
- Time/value/importance rating of each section of the discovery/testing method
- We vote on the priorities
- Whatever emerges is how we scope the proposal

---

### Raid Party

scottrepreneur#8411
jonathanp#9885
earth2travis#6969
TravisWyche#2116

*booyah*

### Budget

$22k for the team

- 1.8k for jp for v1.5 bounties
- 4k for dev (50% RAID)
- 16k for research (30% RAID)

*14.8k Stable/ETH / 8k (in) RAID*

### Timeline

- Engagement runs until end of 2022

### Milestones

1. v1.5 bounties
2. API migration
3. [Research 1]
4. [Research 2]

### Roadmap Ideas

Proposal 2 to follow
- UI Design
- Build

Future Service Use Cases

- Web3 Authenticated ERP/CRM as a service
- MetaCartel/MGD
- Grants
- Mentor Matching
- Events Template/Manager
- Consult with MetaFactory