# Moloch v3 x DAOhaus, Twitter Spaces on Fri, 23-Sep

## People of the Hour

Matt Wright, DAO coordination at Consensys.

Ameen, worked at Consensys, started out thinking of how to bring this on-chain. Led to Moloch and v3 is the latest iteration.

Ven, Product Designer at DAOhaus among other places, now a Coordination Designer.

Dekan, full-time DAO contributor (RaidGuild, DAOhaus, etc.)

## Memes as a means of coordination.

"Yell at Moloch, not at your colleagues!"

The meme of Moloch -- @ameensol used the word "Moloch" to get people to read the @SlateStarCodex blog post on Moloch. (Link below). Scenarios where people want to work together but they can't, for ex. nuclear disarmament.

More about "upgrading ability to coordinate to move beyond zero-sum situations", and less about "policing each other".

Increasing coordination is often at the cost of growing overheads. Ethereum let us do the former without the latter!

Slaying Moloch catches people off-guard! We're not devil worshippers lmao.

web2: what's your why
web3: what's your meme

Mission > Tools / Frameworks / GTMs, etc.

300 communities embracing it right now, with people who are optimistic, pro-social and collaborative.

Moloch meme on CNBC -- wouldn't that be hilarious!

## The Technical Framework

How did the technical framework of Moloch came about? All three versions are from separate groups of core contributors, so what teams were behind which versions?

@ameensol: v1 is Spankchain and Connext, Arjun, Rahul from Connext, James Young from Spankchain.
Got audit report one day before ETHDenver, '19.
Dekan joined a bit later, and v2 was done mostly by DAOhaus, @ameensol did a little, managed auditors.

@dekan: v3 had newer people, @ross from LexDAO, @isaac from Logos, the idea was to bring all the people working in this DAO structure together and discuss where to go ahead. Codenamed BAL (like a nickname for Moloch) and that's also the name of the contract.

Multiple groups working together but also independent from DAOhaus.

@vengist: People just hanging out in the Los Moloches channel in the MetaCartel Discord, really.

Fun fact: Los Moloches is how the sub-graph pluralised.

@ameensol: DAOhaus had helper contracts (re: shamans), Ross did a lot of the coordination heavy-lifting. We have a wishlist for v4 already!

The stuff is guild technology, people will want more guilds! More about creating smaller guilds.

Small groups working closely together > large groups *trying* to work.

First Moloch v3 in the wild: the wgmi community!

Solving analysis-paralysis: go one at a time, just focus on what DAO will look int he near future, don't worry about what it'll look like in 10 years!

Funding proposals and member proposals on-chain instead of a wall of words on Discord.

"If Discord's down and your DAO is down then you're not a DAO."

## v3!

Extensibility and composability to say, "what problems do we have? what do we wanna do?", and just plug in things to get that done.

v1 and v2 were made for specific use-cases.

v1: Hold a single token, and submit proposal to spend that token. Only give out grants.
(The kickback DAOs used it to throw parties and the rage quit with whatever was left lol)

v2: We have tokens! And also, you can now kick people out. And it allowed the DAO to hold a portfolio of tokens.
So this formed the basis of the LAO and MetaCartel ventures.

v3: Better than v2 (more powerful). v1 / v2 built with security in mind (collectivelvy recoverign from PTSDAO). v3 powerful but riskier. Shares and tokens are tokenised, that are stored in Gnosis. v3 sits on top of a Gnosis safe basically.

Different permission levels can do different things now. So shamans let you freeze the shares and loot with one permission level, one set the ---

Since things are tokenised, can be traded, so a quorum % for submitting proposals, % to sponsor one, % to pass a proposal, etc.

Membership is more fluid -- tokenised -- you can buy in!

Also, proposal cancellation, can cancel the proposal in case you wanna pull it back or something.

Dekan: how can we add composability and make things more dynamic!

Gnosis Safe modules : Shamans

Now, communities have the ability to *extend* the technology, instead of being limited by it.

@infi's take: this is where DAOs truly start to take off.

Front-end framework, data libraries, npm utilities around SDKs and the contract let's people evolve in a whole new direction.
For example, any project can become a protocol by layering on top of this framework. The path to community ownership is much clearer now!

@ameensol: Cool thing about Gnosis Safe is how you can add modules. So you can add BAL as a module, and then remove the Gnosis Safe signers or admins. Become a DAO in 3 steps!

DAO modules around CDPs. Moloch v4 will lean more towards the Gnosis ecosystem.

@ameensol: "Funny thing is, Aragon was good enough, but they just didn't have rage quit. So that's how we started out and now we're here."

@Dekan: "The possibilities are endless when you start combining all these legos."

## Certain Use-Cases

@ameensol: "One DAO control multiple safes, multiple DAOs control one safe, multiple Moloch DAOs with shared governance, one could be fast governance, one could be slow governance."
One BAL has 10 shares (effectively, a flexible multi-sig) and another one with tokens (setup a bicameral system).

@Dekan: Moloch v3 you have a safe. Now you have more people join in, so now you have a governance layer. Or even the other way -- basically Moloch let's you switch from the token-based governance to the non-transferrable stuff too!

@vengeist -- Enables coordination that wouldn't otherwise happen. For example, if I have the option to take out my money anytime, I would be more willing to give them the money.

@ameensol: Loot shares as governance.
Two types of governance power, voice and exit. Now exit, is what really changes, because I don't want to have a propsal where people leave, because if people leave then it's more expensive per person (lesser epople) thus more expensive for me.

Two major frameworks: tokenised communities using goverannce contracts (NFT contracts), and then there's the Moloch framework. What are your opinions on the two sides of the ecosystem?

@ven: There is a duality between transferability and non-transferability. Large DAOs had transferable power, and small DAOs in the opposite way. With Moloch v3 we have a non-dualist situation -- we can do both here! Applicable to protocol gov., non-profits and treasuries.

@ameensol: Consensys is a venture production studio. First pass of design for Moloch looked more like v3 instead of v1! But because of PTSDAO we stripped everything. But now, arbitrary transactions, transferrable shares, hold multiple tokens!

@dekan: We really wanna create tools for people to build what they though the solutions will be.