---
###### tags: `Haus Party Live`
---

# HAUS Party LIVE! Notes (2/24/2022)

Join us for 🎉 Haus Party Live 🎉 every Thursday at 2pm EST on the [DAOhaus Discord](https://discord.gg/daohaus)

## Guests and Topics
- No specific topic for today -- audience members can join and chat

## General Discussion
- New name for Warcamp?
- Move away from identifying with *war*
- Potential names:
- Basecamp
- LightHaus

## Moloch v3.0 & v3.1 (Baal)
- What is Moloch v3.0 (Baal)?
- Several big changes from current versions: https://decrypt.co/93196/dao-framework-builder-moloch-launches-v3-at-ethdenver
- In Baal, DAOs will have options (via passing a proposal) to turn on transferability for shares and loot
- Shares will be an ERC20 token and loot is a *pseudo* ERC-20
- DAOs can turn this on and off (via proposal) for this
- Likely that DAOs will start with transferability off, but this adds flexibility for DAOs to grow and evolve
- Allows for changing parameters without needing to start a new DAO
- Baal DAOs can update parameters (quorum, grace period, etc.) via proposals
- Instead of needing a minion to interact with other protocols/apps, Baal allows for execution of arbitrary function calls
- DAOs can interact with a DeFi protocol without needing to interact within a minion (keeps original assets Ragequittable)
- Shamans: essentially Moloch DAO extensions
- Contracts that the DAO approves that will have special privileges within the DAO itself
- Example: Shaman contract has ability to modify shares and loot (mint or burn) without having to go through proposal process. Meaning that any logic can be used to programmatically manage shares and loot
- Yeeter is a shaman platform: send ETH -> receive certain amount of loot
- "Sword of Damocles"
- Make DAO have a commitment on a certain day: "Burn all shares and loot *unless* all conditions have been met one year from now."
- Coordinate and accomplish goal with added pressure to the DAO
- Generally, opens up a huge design space
- What is Moloch v3.1 (Baal)?
- New smart contract that opens up additional, composable options
- Can use a Gnosis Safe with a multi-sig and then add Baal as a governance module *on* the safe
- Start with a safe and multi-sig and then extend into more governance as needed/as the DAO evolves
- Flexibility, composability, and upgradeability are core aspects of Baal
- From a DAOhaus perpspective, this allows us to provide options for DAOs built on DAOhaus platform to *not be locked in*

## Baal Shamans
- How are people that are in a DAO that will be using Shamans and other extensions aware that these are active in their DAO? Does it require a lot of technical verification from folks within the DAO? How does this impact users, particularly non-technical ones?
- Not necessarily a single answer for this. Starts in the *approval process* for a Shaman
- Any ETH address on the network DAO is on can become a Shaman, so will be critical within the DAOhaus app for the DAO to increase clarity about what a Shaman can do
- Create a culture where folks *reject proposals* if it's unclear what a Shaman can/will do
- Folks in DAO will want to be skeptical about what Shamans are activated
- Potentially create a registry/marketplace of approved Shamans for the commumity to pick from
- Curated by the community -> distribute this signal through the app
- Being aware that the flexibility can introduce information assymetry and incoherent UX
- Thinking about Shamans as a subset of the *Boosts Marketplace* -- Boosts are DAO add-ons
- $HAUS token used for mechanism for curation of Boosts/Shamans
- Representation of our collective abililty to represent this
- What limitations are there?
- Any address provided that the address is able to call certain functions with the Moloch contract (DAO would need to grant permission)
- Has to confirm to the Moloch Shaman interface
- No one should set an EOA for the Shaman address as this gives lots of power
- As this is powerful, default vote should be *no*

## Transferability of Shares/Loot and Quorum
- Introduces new mechanisms and considerations
- How to avoid plutocratic systems? Quorum is a preventative mechanism
- Leads to a critical question: How does turning on transferability change governance?
- Interesting that Baal DAOs are able to *ask this* as opposed to it being decided from the start (currently, shares and loot are *non-transferable*)

## Delegations
- Since shares are now ERC20s this unlocks the delegation system used by Compound Governor
- Delegate Moloch shares to *any address*

## Developer Experience and Process
- Testnet -> Sidechain -> Mainnet workflow
- No economic incentive -> some econmomic incentive -> lots of ecomomic incentive
-