---
# System prepended metadata

title: 'RIP Proposal: DAO v2>v3 Migration'
tags: [Proposals]

---

---
###### tags: `Proposals`
---

# RIP Proposal: DAO v2>v3 Migration

### Project Submitted By

TW

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


## Summary

- We have been discussing the need to migrate the v2 DAO to the new v3 contracts.
- Due to the large amount of safes and dependencies, a thorough audit is required to clarify the best [migration path](https://docs.daohaus.club/v3Upgrade/migrate).


## Why should we build this?

- The Moloch contracts our DAO is built on have been improved to include [v3 feature updates](https://moloch.daohaus.fun/features/updates).
- DAOhaus is deprecating [v2 DAO features](https://docs.daohaus.club/v3Upgrade/featureImpact), limiting functionality and availability of support.
- There are a variety of nested social/community issues that deserve to be sussed out and collectively decided. We may consider a TCR signalling session (or similar) to quickly gather sentiment from across the guild. For example:
    - Is this an opportunity to weed out inactive members from our ranks? Certain migration strategies will accomodate this better than others.
    - Is this an opportunity to migrate chains? There are pros and cons to our decisions that will greatly impact future operations and alignments.
    - Is this an opportunity to incorporate custom features into the DAO that were not previously available? Clarifying these needs could lead to signficant future RIPs that iterate upon the DAOhaus SDK and Moloch v3 contracts.
    - How will this affect the ability of new members to onboard into cohort sub DAOs in preparation for joining the mother DAO?
- The actual migration will require careful attention to proposal details, requiring a high-trust delegation to execute and clear communication for the DAO to track.
- There will be numerous customization options to consider. They should be prioritized by utility, autonomy, and reducing bureaucratic frictions for future decentralized ops.
- A small team will be able to anaylze, research, and propose a strategy faster and with less distraction than the entire DAO dedicated to the effort.

## Deliverables / Output

- It remains unclear what is actually required for the migration. Therefore, we have broken up the work into two phases: evaluation and execution.

#### Phase 1: Evaluation

- **Survey** of existing v2 safes/minions, boosts, and other v2 DAO variables necessary for continued operations. Identification of what can be deprecated and suggestions for streamlining on-chain DAO ops.
- **Analysis** of migration options in relation to these identified needs.
- **Proposal** of any custom app development that RG might need, with options that segregate between minimally viable utility, nice to haves, and a "cadillac" DAO build.
- **TL;DR Report**, presented to the guild to consider, followed by any necessary polls to gather sentiment on options and an on-chain signal vote to ratify the process.

#### Phase 2: Execution

- **Execute** the proposed strategy (highly variable, TBD by results of phase 1). Could include:
    - Custom app design/development:
        - Summoner
        - Admin
        - Cohort-specific easy mode
        - Custom proposals
    - Social integrations:
        - DAO-side integrations of other RG legos
        - Dungeon Master
        - Discord/Charmverse updates
    - Submitting necessary proposals.
- **Documentation** that updates the RaidGuild handbook, policies, and other resources for the new v3 DAO structure (also highly variable, TBD by results of phase 1).

## Anything else you'd like to add?

Ξ2T, SK, and TW have been working together to deprecate v2 infra and produce documentation to help communities understand and execute their own migrations. We intend to thoroughly document this process as an important case study for the DAOhaus team to integrate into [docs](https://docs.daohaus.club/) and education efforts. They will oversee the research and community communications of the migration.

A portion of funds will be reserved for consultation with high-knowledge guild members and compensate them for their time. Dekan, plor, scottrepreneur, and others will lend commentary and guidance on the strategy.

## Raid Party

- SK
- Ξ2T
- TW

## Cost (in USD)

- Phase 1: 
    - 3 raiders x 3 weeks = $5400
    - Consultation budget: $600
    - Total: $6k
- Phase 2: 
    - TBD dependent on results of phase 1
    - Will be submitted as a separate RIP proposal