owned this note changed 3 years ago
Published Linked with GitHub

DAOhaus Community Track

Target Audience:

Community Managers, Leaders and Developers who understand basic blockchain fundamentals (ex. what a smart contract is, how it works), what a DAO is (high level understanding) and are interested in diving deep into what DAOs are all about.

Output

This course would start with the basics of DAOs and governance. It would make the case for Moloch DAOs and how they are not only a great tool for keeping the community safe from attacks, but how it is uniquely positioned to foster groups of motivated individuals who accomplish more.

Then we teach the practical knowledge. Students learn the interface inside-out, but more than that, they dive through a taxonomy of successful community models and learn how to manifest those models in reality.

Finally, they'll be given projects and practical examinations to test their knowledge, and once they've demonstrated their proficiency, they'll recieve an on-chain certification. By the end, community leaders will feel comfortable translating the needs of their community into real, onchain governance models.

Curriculum

#0 Intro to Human Coordination Games(Who is Moloch?)

Questions Answered:

  • What is a Coordination Game?
  • What's the difference between a System and a Game?
  • How can a Moloch DAO enable my Coordination Game?

Lesson Plan (UI369)

Unit #1 Intro to Moloch DAOs (Beginner)

2 sessions

Day 1: Why Moloch/DAOhaus

  • Intro and history of DAOs & Moloch
  • Intro and history of DAOhaus
  • What's new in DAOhaus V3?
  • Safe as vault
  • Governance layer
  • When to use it? Trust-mitigation

Day 2: Practicality:

  • Begin experiment of creating a honeypot.
  • Summon a DAO
  • 100 HAUS in treasury
  • Students as members

Unit #2 How to Moloch (intermediate)

2 sessions

Day 1: How to Moloch

  • Governance OffChain -> OnChain
  • Proposal Process (submission -> sponsor -> vote)
  • Adding/Removing new members
  • Funding Proposals
  • Signal Proposals
  • capabilities

Day 2: Practicality:

  • Full process of mock governance in a Moloch.
  • Participate in a DAO.
  • Defend against malicious proposal.
  • Vote for the right proposal

Unit #3 Coordination Game Design

2 sessions

Day 1: Building a DAO

  • How to build daos as coordination games to slay moloch. Learn how to fine-tune your usage of Moloch and combine with other tools for unlimited power.
  • Advanced proposal submission
  • Shamans for automated power
  • Advanced Coordination: Federations and Partnerships

Day2: Coordinate with others

  • DAO coordinape honeypot distro

Unit #4 Theoretical Moloch (Future Tease)

Practicality

Applied Theory of Moloch Slaying

Opportunities

  • Could take on sponsors to provide bounties for this phase. Perhaps a popular protocol is looking to build an app that wants integrate DAOs, they could offer an award for an MVP.
  • Could get a bounty from an existing DAO to build a custom DAO interface
  • Could offer bounties for Celo infrastructure. As an example, we know that we can easily upgrade existing multisigs to MolochDAOs. What if we made an app to do that on Celo?

Extra Offerings

  • Priority DAO design seshes for Celo users for a given amount of time (private channel + discord server for graduated Celo attendees, guarnanteed response time.)
  • Summon a verification and credentials DAO. Award an SBT (Non-transferable NFT) to those who complete the course. We, of course, could build this while teaching.

**References: **

DAOhaus "How to DAO" curriculum
"How to DAO" participant feedback


Boiler's Adds

boilerrat
Wasn't sure how to add this into curriculum format but just adding some points that could be covered in DAO building course. What I have been spending a lot of time pondering lately is DAO communication and how important it is.

Discord and Telegram

  • server setup
    • site security
      • choosing the correct bots
      • role management
      • using templates
      • spam controls
  • role management
    • creating roles and why they are important
    • web2 and web3 enabled bots to aide
      • mee6
      • Dyno
      • collabland
      • Guildxyz
  • server organization
    • keeping it simple enough to help people onboard easily
    • keeping it detailed enough so coms arent a jumbled mess
  • using discord as the primary means of DAO project Management
    • Scheduling in international environments
      • lettucemeet (web2)
      • Sesh (web2)
    • Meeting On Discord
    • Community Events
    • Making the server engaging

Considerations

  • scaling a DAO

    • how to start a DAO small and scale using v3 (turning on or off token transerability)
  • Defining a DAOs purpose

    • mission statements
    • manifesto design
  • Spreading the Word
    web3 does not advertise in a traditional sense, insread rely's on social media, podcasts, spaces, articles, video, blogging etc

  • social media

    • Web2
      • twitter
      • spaces
      • substack
      • Medium
    • web3 alternatives
      • lens
      • mirror
  • Documents Management

    • web2:
      • Hackmd
      • Google
      • Airtable
      • Notion
    • web3:
      • Charmverse
  • Github

    • Why would community managers need to learn github?
      • source control
      • pull requests
      • project management
  • Advertising (generally not done with DAOs)

    • Public Relations
      • In house
      • service DAOs
    • spreading memes

Service DAOs

often times a DAO may not have all the skills required to do all the things a DAO has to do.

  • when and how to use a service dao
  • where to find them
  • D2D
Select a repo