The second meeting
Last Edited Time
Jan 3, 2023
Created time
Nov 26, 2021
Participants
Created By
Type
Created
Nov 26, 2021
Zoom Recording
Property
Property 1
Slides: https://docs.google.com/presentation/d/1mxt_V6eC_NvcCDRh1OvEEt9CAZmjHQfCCr2uHW40TOA/edit#slide=id.p
Zoom recording: https://stanford.zoom.us/rec/share/SOb-KYW-gQwP5aDNmtQd2VzA0EDETGDcWsZWottdmz6pUOJP4tox2DaW18QZtwPe.uBoKGwlpKaeld2xO
Participants
- Aragon (Ivan Fartunov, Samuel Furter, Selim)
- Moloch (Isaac Patka)
- Colony (Daniel Kronovet, Jack du Rose)
- DAOstack (Ido)
- Tally (Dennison Bertram)
- Snapshot (Fabien M.)
- DeepDAO (Eyal)
- MetaCartel Ventures (Rolf Hoefer)
- Metagov (Primavera De Filippi, Michael Zargham, Joshua Tan [Chair])
- Orca Protocol (Julia Rosenberg)
- Coinbase (Jesse Pollak)
Observers: Andrew Hong, Will Nuelle, Shreyas from Llama
Agenda
- Welcome to new folks & introductions (15 minutes)
- Topic 1: Introducing the strike team (5 minutes)
- Topic 2: DAO membership (25 minutes)
- Topic 3: Let’s make a DAO (15 minutes)
Topic 1: Introducing the strike team
- Intended outcome: update the larger group, identify milestones, make the authoring process for transparent.
- Currently: analyzing specific topics. This week: membership. Next week: proposals.
- In the future: full parameter analysis + mapping for all major DAOs contracts.
- Still need: open to anyone, but we especially need developers with experience with Compound, Tribute, and Colony.
Proposed milestones:
- Nov. 26: present initial research to roundtable
- Dec. 30: draft EIP
- Jan. 7: present EIP draft to roundtable
- Jan. 20: sample implementations integration workflows for existing frameworks
- Jan. 27: minimal DAO contract live on testnet
- Jan. 28: present DAO contract to roundtable
- Thursday, Feb. 3: SUBMIT EIP DRAFT, new site launch
- ETH Denver: announcement
Topic 2: DAO membership
- Intended outcome: a list of comments & objections.
- Outcome: consensus toward option 1 (see slides) in how to standardize membership
Discussion notes:
- Decision 1: membership is a fundamental concept in DAOs
- Decision 2: we should not standardize what membership means in DAOs
- Decision 3: we should have a URI field in every DAO, pointing to a text file, that contextualizes what membership means in the DAO (e.g. a constitution)
- Decision 4 (in-progress): how to query membership data
- Two options: simple vs. loose
- Review membership in existing frameworks
- Daniel reviewed Colony DAO: reputation came first; anyone with reputation (continuous metric) is a member of the Colony DAO. Later on we introduced permissions, which are discrete. Colony doesn’t really have a notion of member that is really well-defined. For purposes of discussion: a member is anyone that has anything. As for querying: there’s a reputation oracle. For permissions: do something events based or query the contracts directly to see if an address has a permission.
- Eyal: we missed Snapshot, and there definitely is a kind of governance in a Snapshot space; the strategy of the space, which determines whether you can or cannot vote.
- Josh: while Snapshot is important, I also feel like we should rein in the scope.
- Zargham: let's get to Snapshot when we get to proposal discussion, and make sure Fabien is there.
- Julia: want to make sure Orca gets in on this conversation. We focus on this! We use ERC 1155 for membership. That said, "what does even membership mean" is a pretty fair question. Comes back to the coordination spectrum. Does token voting count as membership? But we’re seeing more granular + more focused groups within DAOs that have additional permissions. It’s worth noting that there’s a range of coordination + membership within DAOs.
- Dennison: we’ve been specializing on Compound governance, and have been pushing a new DAO implementation based on NFTs. Pretty strong diff between standard Compound vs NFT-based. That drives a totally different participation in DAOs, the sense of what it means to be a member is very different. So Compound governance is becoming a little more interesting!
Topic 3: Let's make a DAO
- Intended outcome: a list of ideas for what the DAOstar DAO should do
- Outcome: agreed: we should focus on aligning incentives across competing frameworks + tools in order to support joint initiatives (including standards adoption).
- Outcome: we decided to start a new working group to work on this DAO.
Zoom chat