DAOHaus primary sources — 2026-05-09

What I reviewed

• Official docs / pages:
  • https://docs.daohaus.club/
  • https://docs.daohaus.club/contracts
  • https://docs.daohaus.club/contracts/moloch-v3
  • https://docs.daohaus.club/contracts/treasury
  • https://docs.daohaus.club/contracts/shamans
• Official repositories / technical docs:
  • https://github.com/HausDAO/Baal
  • https://raw.githubusercontent.com/Moloch-Mystics/Baal/main/README.md

Key takeaways from primary sources

• DAOHaus is best understood as a governance operating stack built around Moloch v3 (Baal) rather than as only a frontend for spinning up clubs.
• The core architectural move is to separate governance from the treasury by putting a Moloch-style governance layer on top of a Safe multisig through Zodiac-compatible modules.
• The most important reusable mechanism is the combination of tokenized membership, ragequit rights, Safe-based treasury execution, and shaman contracts with explicit permissions. That combination makes DAOHaus a strong comparison class for Safe-, Aragon-, Hats-, and Llama-style control-plane analysis.
• Shamans are the clearest practical-authority surface. The docs explicitly warn that shamans are powerful contracts that can make critical changes outside the proposal process, and they can hold admin, manager, or governor permissions.
• The treasury docs make clear that the system can pair one ragequittable main Safe with additional non-ragequittable sidecars, which means capital structure and exit rights can diverge inside one DAO deployment.
• The Baal README is valuable because it preserves the more mechanism-rich framing: arbitrary actions, flexible proposal periods, ERC-20 shares and loot, gasless approvals, and Moloch-style ordered proposal processing anchored by ragequit economics.

Specific source signals worth retaining

• DAOhaus docs homepage: describes the stack as protocol infrastructure made of contracts, subgraphs, and contribution workflows powering the DAOhaus ecosystem.
• Contracts overview: says Moloch v3 is a governance layer on top of a multisig treasury, highlights tokenized membership, shamans, arbitrary actions, adjustable governance parameters, and summoners.
• Moloch v3 docs page: explicitly says Baal sits on top of a multisig treasury and abstracts governance into its own layer.
• Treasury docs: define the main ragequittable treasury Safe versus non-ragequittable sidecar Safes and note that proposals execute through Safe multicall.
• Shamans docs: state that shamans are approved contracts with administrative permissions and can make critical changes outside the proposal process.
• Baal README: ties the system back to Moloch, Minion, Compound, Safe, and Zodiac lineage while documenting proposal types, ragequit behavior, arbitrary actions, and extension hooks.

Why this entry belongs in the corpus

• DAOHaus belongs in the corpus because it shows a specific and influential answer to the question “where does DAO authority really sit?” — not just in token votes, but in the seam between governance contracts, Safe modules, treasury structure, extension permissions, and ragequit economics.
• It improves comparisons across governance operating systems by making the Safe-plus-governance-layer pattern explicit rather than treating all DAO frameworks as monolithic governors.
• The reusable insight is that modular DAO systems often relocate power into extension permissions and treasury wiring, even when their user-facing story is still about member voting.