---
# System prepended metadata

title: Moloch V2 to V3 upgrade Patterns

---

# Moloch V2 to V3 upgrade Patterns

There are a couple options to upgrade from Moloch v2 to Moloch v3.

### DAO proposals to transfer all funds

This requires a proposal for every asset in the treasury. So if you only have one assest it's not too big of an issue but if you have many assets this can be a lot of overhead and coordination.

Beforehand the new v3 DAO should be setup to clone the existing members loot and share holdings.

### Coordinated Ragequit and Restake

All members ragequit, withdraw their funds and then stake into the new dao.

This has very high coordination effort and there is no garuntee that all members will make the transition.

This keeps funds under control of the members at all times

### Single royal ragequit and transfer

**primary (maybe best option of all of them)**
Beforehand the new v3 DAO should be setup to clone the existing members loot and share holdings at a snapshot.

create a new member proposal (v3 target safe) on the v2 dao for 1000x more Loot then the current total supply of loot and shares. When they ragequit they will be able to withdraw all funds except for a very small amount of dust.

This new member should be the target safe of the new v3 DAO, it will require a single multi-call proposal to withdraw all funds from the v2 into the v3 'target' safe

funds remain ragequitable except for the short period during the proposal to withdraw funds, this could even be timed to limit that period to almost instant.

* ^ this is probably the version that makes the most sense to build an automation tool around.

**alternate** - A safe with a delegated trusted team of signers that will summon a new v3 module on the safe that ragequits

## Minion spool
Transfer all funds from the main treasury to a DAO controlled Minion Safe. 'Upgrade' that safe with v3 module

This might be especially good if the DAO already has most funds in a minion safe.

**notes**
- if the DAO has many minion Safes than only one can be the primary target of the v3 but the others can be side vaults where the v3 is a module but the safe is not marked as the 'target' in the v3 dao contract. 
- Some minion safe are not to be ragequitable, these should not be set as the primary 'target' of the new dao.
- Every transfer of a minion would require a proposal on the v2 DAO.


## Combo
Mature DAOs will have many tokens in the main treasury and many Minion Safes. It will probably require some mix of the above options to do a full upgrade. Timing and orchestration will be important