Strike Team #15
Last Edited Time
Apr 27, 2022
Created time
Mar 3, 2022
Participants
Created By
Type
Created
Mar 3, 2022
Zoom Recording
Property
Property 1
Attendees: Josh Tan, Ido Gershtein, Rolf, Isaac, Lucia, Zargham
Observers:
Zoom video:
Â
Minutes for 2/24/2022
Introductions:
- Ido Gershtein: Developer at DAOStack.
- Denise Duncan: Unfinished Labs. Unfinished Labs is working on Project Liberty. Working on the Decentralized Social Networking Protocol. Investigating DAOs and approach to governance.
- Junhe Li: Work at Wonderverse. Project Management. Heard talk at Eth Denver.
- Sam: Worked at Aragon.
- Cent: Work with Metagov as Community Manager
- Andrew Poterala: Chain Vision, in Chicago. Liquid token engineering.
- Vaughn McKenzie-Landell: Been following Michael Zargham. Looking at IP rights, FlameDAO. A standard setting of DAOs would be a good way of getting a good angle on the space.
- Keating: Active in MolachDAO, DAOHaus. Working on kickstarting the MolachDAO implementation of the standard.
- Andros Wong: Working with Terry at Wonderverse. Interested in DAOstar to progress tooling in the ecosystem. Wonderverse is interested in creating a standard for workflows. Working with Radicle team.
- Lucia Korpas: Data scientists. Working on reference implementations for DAOstar.
Goals
Agenda for Thursday:
- 🥂🍾
- Review EIP
- URIs and Off-chain
- Most DAO information is off-chain data
- Off-chain is the focus at this moment
- Proposal Standards
- Uses CAIP (Chain Agnostic Improvement Proposal)
- “status”: there is no current consensus what the fields for proposal status are
- “calls”: basic call data and ability to simulate the prposal
- i.e. tinderly: a tool for simulating contract behavior
- sophisticated enough to simulate internal and external calls
- though may not be true for all contract cimulators
- Activity Log
- arrays of activity
- JSON-LD
- More flexible than JSON
- Allows more cross-chain flexability through extensibility
- Questions on the Standard
“status”
Andrew: Question on the “status” of a proposal. Has there been any discussion of having limited standards for this field?
Sam: The social field of decision making is perhaps too complicated to specify status
Josh: Zargham can speak to this well. There are ways of providing descriptions, but it would be too large to incorporate into this standard at this point.
sam: The discussion ended there that we somehow would start to define a lang for state transitions
Ido: The tools, and the JSON-LD extensibility, still allow DAOs to add this information
Member URI
Mayur: How are you constantly updating the Members URI since things are being constantly updated
Josh: Pointing to a dynamically generated end point that is updating member information continuously.
Sam: There are some cases where you can’t well index members. I.e. you need to have a token and be active in some organization. In those cases it would not be possible to create a Member URI for them, though they have the constitution .md to learn how membership is constituted
Josh: One of the goals is that this standard will spurn more clarity and legibility of what membership means in DAOs, up to what the DAO choses to communicate.
Mayur: Are DAOs supposed to make and submit this data? What about organizational impersenation?
Josh: Working with lots of DAO platforms to help automate this process.
- Present the API service at daostar.org, get feedback
- Walking through the input form for connecting a DAO with the DAOstar API
- Currently permissionless, but will be permissioned through a web3 login process.
- Ido: schemas update
- Ido: Spend time working on how to host schemas
- took inspiration from schema.org
- Josh: A JSON-LD schema is very similar to an RDF schema, or any other format for specifying a semantic web ontology.
- Josh: daostar.org will host these schemas, so there is a consistent definition of all the properties in the JSON objects we recommend.
- Ido: We will create an ontology for DAOs
- The question is how to present it prettily in the site
- Idea is to have a page similar to the Person page on schema,org/Person
- This would allow people to see all the fiels in the DAO schema
- Continuing to work on ontology creation
- Will create a turtle file and then someone will implement the turtle file in the DAOstar site
- Action: Connect with schema.org about how to help translate the turtle files into a format that looks like html
- Vaughn: I might have someone
- Josh: the MVP for the schema is a static representation
- Once we have DAOs submitting information, there will be scanners crawling this (i.e. etherscan)
- This is display which properties are being used the most
- Popular properties would float to the top
- Ido: Instead of people extending the ontology file, we will crawl all the URIs exposed and present those
- Josh: Once there is a canvas for displaying property selection it wil be easier to see how other DAOs are using the standard.
- Mayer: It might be interesting if one could see their contribution across multiple DAO which might useful for their unchain credibility score
- Junhe: ^hehe we are working on that! Love to work on a standard with people
- Junhe: Are we thinking of using the contract address as the unique identifier for daos? On the tooling side, to integrate with downstream services, it would be immensely helpful to have a way to do entity resolutions across protocols/platforms
- Review requirements + progress on reference implementations
- Josh: Out of ETH Denver: wouldn’t it be interesting to implement a DAO in a Github? Is the standard is as robust as we think it is, it might be able to accommodate organizations like Github and other web2 applications.
- Priority list for partner integrations (e.g. Etherscan, DeepDAO, Snapshot, Tally, etc.)
- Sam: will discuss again with the product team at Aragon
- Josh: posted the proposal to the Aragon forum with enthusiastic response
- Open community questions
- Junhe: Will contracts that implement the schema function as a unique identifier. Could this be similar to a Blue Checkmark?
- Josh: Unique Id for DAOs is complicated. A round table for this will be starting March 4th.
- A given DAO might contain multiple contracts
- They might also have multiple sub DAOs
- There are also DAOs that are basically just a Telegram or a Twitter and also ones that exist on multiple chains
- When you set DAO URI, you can map multiple contracts to the same URI.
- Making a data API end point that synthesizes the standard (a gateway for the organization) that displays all that information.
- Having this kind of URI is one steps towards Identity creation
- Marc: Sorry, I joined late. But would a service like Covalent be able to crawl DAO data, with what DAOstar is aiming for, and help people gain cross-DAO insights?
- Sam: Making something that is both machine and human ledgible is still a complicated question
- Mayur: Is there a research done on various DAO operational structure or DAO organizational hierarchy?
- Josh: There is a lot of research on this. This question is related to governance. The standard does not want to standardize governance, where there is a lot of ongoing inovatio. Instead wanted to standardize things that every DAO would have.
- There is an EIP, but it is still a WIP. If there are things not well reflected in the standard, please let us know so we can make revisions for this or future stnadards
- Andros: How would we be able to propose changes? Would be nice to brainstorm on task standardization.
- Josh: There is a round table on credential verification that you could join.
- Testing
- Josh: endpoints can be experimented with on the DAOstar site.
Zoom chat
Â