Project Management
Project managers: Josh
Table
Projects
Name
Dec. 1
Related to Working Groups (Projects)
Project lead
Comments
Related to People (1) (Related to Projects (Project lead))
Update Oct. 12
Update 2022-08-18
Project doc
Update 2022-10-27
Priority
Nov 17
Jan 19 2023
Update Sep 15
Update May 19
Last update (Apr. 14)
Update 2022-11-03
Action Items
Isaac just built the Gnosis Safe reference implementation, that’s now in the DAOstar repo, need to build a few docs for it.
Deployed contracts everything but Arbitrum and BSE and Avalanche [need to send tokens from these things to Isaac so he can deploy]
dOrg SoW making progress, basically go in and make the current safe implementation better.
TODO: api.daostar.org (share AWS deploy keys with Isaac)
[Be in a state ready to onboard a ton of DAOs in person.]
1. [JOSH] get ball rolling, reference implementation for the compound stack
2. [JOSH] pester Isaac to continue to register more DAOs into the EIP-4824
3. JOSH talk to Spencer about getting v3 integration up when it launches. (v2 would need minion auto-deployment too, not worth it).
4. Follow-up SuperDAO about automatic integration.
Moloch v2 in production. v3 is ready for production but waiting for v3 audit to be finalized! <3
hard part was membersURI and proposalsURI
Milestone
2 - Demonstrate Adoption & Deploy an easily forkable reference
implementation
Simple Summary
Implement, document, and share a documented and easily forkable reference implementation
of the data service. Extend functionality to another DAO framework. Support dOrg or other
external service to build a Gnosis safe reference implementation + integration
spec
Acceptance Criteria
* Another DAO framework besides Moloch is supported on the API service (ex. DXDAO)
* API service is deployed to the DAOstar domain
* 5 small DAOs & 1 major protocol DAO registered (or in governance to be registered)
* Subgraph deployed that supports all EVM chains
* Smart contracts are deployed to all major EVM chains
still need arbitrum, bsc
* Smart contracts are updated to support manager administration of URIs
* Spec is updated to support contract registry
Josh is writing a SOW with dOrg to define the Gnosis Safe reference implementation + an app to make it even easier to onboard existing safes to DAO* + an integration or some sort of progress toward making all new safes 4824-compliant.
- Taking Tucker’s UI and baking it into a safe app?
- Ping Isaac to make sure he reviews the SOW once draft is out
Isaac: spec update (to EIP-4824) to support contract registration of multiple contracts. This extends governanceURI to include mapping + tags of other relevant smart contracts. There’s a PR open to update that.
Also updated the smart contract to use OZ roles. New contract deployed to Goerli.
New Milestone:
* Get DAOstart member DAOs registered
1. Josh is talking to Phil at dOrg, who will be leading the Gnosis Safe reference implementation. (Also possibly a Safesnap reference implementation?)
2. Moloch ref is done, now focusing on getting it integrated into DAOhaus.
3. No word yet on Aragon ref implementation, is Alex working on that?
BLOCKED: still need to figure out where the data transformation takes place; we have the subgraph working for moloch v3 + the architecture for registration, but where is the actual transformation to JSON-LD taking place???
One way: client-side SDK queries the graph, concatenates it and produces the JSON-LD client side. Basically it’s just adding the context field and the DAO name.
Or: ping an API that integrates the SDK.
User: DeepDAO and Etherscan will not be a big deal, they’ll use this SDK.
Separately: we will be able to host the service as a service provider, but also if you don’t want to rely on DAOstar... you can just fork the repo and deploy their own service.
Meeting with Keating next week in Amsterdam
- deploy contracts to rest of EVM networks,
- comments + merge open PR
- extending API service
Do we have a subgraph for indexing the registration contracts?
MILESTONE 2
Additionally:
[medium priority] Getting implemented in DAOhaus UI
[high priority] Instruction set for Moloch v2s
[high priority] Isaac just goes through every Moloch DAO he’s in and submits an upgrade proposal
[high priority] Making AWS lambda easier to use for other references implementations; we have a lambda that translates from a subgraph to a DAOstar format (incl. Snapshot translation)
5. research into PKPs from Lit Protocol are live on Celo— possible replacement of Lambda (?) [delegate to the guys at Lit? Jason & David Sneider; Isaac will ping in main chat]
5. [high priority] Josh get Gnosis (dOrg) and Aragon and DAOstack ref implementations rolling
6. Get DXDAO registration instructions
7. Send Cosmos integration to DAODAO / Case+Jake?
8. dOrg has been non-responsive; instead, find an existing Gnosis Safe members and/or proposals subgraph and just use that—see how Utopia does it?
1. Josh needs to talk to Messari and Etherscan.
2. We REALLY need to hire a marketing / community person.
Still trying to find a marketing / community lead to head up DAO-facing stuff. Matt Wright at Consensys could be a good fit? Or he’s training people to take this kind of role.
Experiments ongoing with Avenue, Govern, and Charmverse (for the attestations framework)
Zargham: some of the most important things we need to produce for adoption is a blog post: enable more do-ocratic implementation!
Josh: meeting with Ivan, next step is Compound support + setting up Aave, to get them to ratify (invite harry to this call next week to do a pairing session?)
Isaac: will do this after new contract is up.
1. Josh needs to talk to Messari and Etherscan.
2. We REALLY need to hire a marketing / community person.
No additional updates from Etherscan, Messari, DeepDAO. Experiments with Disco, Dework, Avenue, Consensys Mesh from other WG.
Josh had call with Etherscan; need to hire some people; are we internally mature enough to support the EIP + project; PM person? medium articles + syndication? NEED TO FINALIZE EIP!!! Need easy API deployment (could this be automated directly in the manager factory contract?). Host an in-person workshop?
No update.
TO DO: set up a pairing session in place of the strike team call with Aave (Harry) to get them onboarded / set up the endpoint.
[high priority] Blog post with Z, Isaac on “what does it mean for a DAO to own a DAO registration contract?” Access control patterns for DAOs, ref. Dennison’s question on roles in the Ethereum Magicians post, so we can have a quick linked answer to that kind of question. Send to Josh to edit.
[high priority] Isaac just goes through every Moloch DAO he’s in and submits an upgrade proposal
[JOSH] follow up with Messari, Etherscan, and DeepDAO
We got 120k! hooray!
Got a $5k grant from The Graph. No word yet from ONTOCHAIN.
No update.
STILL finishing the grant agreement
Gnosis GIP posted; GitHub still in progress
Finishing up grant agreement plus work plan for EU NGI grant.
[JOSH] Check that the Moloch DAO payment has come in.
Send out more 4 grants.
Find an owner for this task! Who can reach out to stewards of DAOs, doing comms work. Who could do this? Intern/trainee at Fire Eyes? Andrej Berlin at Deep Works?
Hire Hazel or Fotis (recently gone from SCRF) or someone to do some of this? Billy Rennekamp, potentially Auryn, potentially Nader, etc. for a “solutions architects / technical community manager / developer relations.”
We’re bringing on Hazel, who will own this branch. We probably still need to bring on someone with more capacity and regular availability to do this though, since Hazel is a full-time student.
Hazel is taking this, working on tweet threads. We have a draft tweet thread that will be posted soon in the TG
No update: Isaac will get in touch with james.eth and ask if Wildfire would be interested in
We should hire/bring on someone full-time or part-time evangelist who can take point on this + draft a plan.
Need to find someone to take this up.
James is handling the substack & roundtable writeups.
Go to daostar.org/gnosis and see all the 4824-compliant Gnosis Safes (or Moloch DAOs, or Aragon DAOs, etc.) along with all their data.
Josh needs to clean this up and do some project management because the indexer is effectively going to get wrapped into the reference implementation development / the JSON Schema development.
Tucker has started on the subgraph on the Graph, have set up a subgraph for the Goerli contracts. For the others we will set up new subgraphs. For the explorer we will need to multiple queries to all the EVMs to get all the registrations.
Brainstormed this idea.
Could we partner with Messari and DeepDAO and Etherscan on producing such indices?
started WG chat
No update.
Isaac has already built an MVP of a DAO vulnerability scanning tool that he might release a product.
Josh is writing that right now.
[JOSH] Send one-pager to Isaac and Michael at Oz.
We have a bunch of RAs supporting, building out the data set, have a bunch of proposal types.
Almost complete!
RELEASED!
George is posting this TODAY!
[JOSH] Send back to George.
Need to connect current frontend with testnet contracts, create some registrations to populate.
Tucker:
Josh: a lot of working with Jenny to revamp the design of the new front page
Josh: need to move standards docs to a repo.
FE is coming together, see Figma files. Need to discuss “Explore” component.
Jenny doing a broad UX redesign, will be revising the daostar.org site to incldue more interactive elements + more persuasion to get people to upgrade
Member concept for the roundtable / foundation — what does it mean to be a member, what’s the purpose of the organization. It’s more of a community hub experience.
We’re going to move more of these updates into GitHub repo.
Who would be a good candidate for an executive director for the DAO* Foundation, where the foundation has a mandate around events, education, and using of tools? Right now there’s a fracture of different organizations doing this. So you would need to talk to a bunch of them to get them to work together. Consortium-izing this activity—how would that look though?
Ido is still out of commission
No update.
Ido is back!
Next step: generate a daostar.rdf file and start using it as the canonical source of truth for the ontology
Ido has been in the desert; schema not uploaded
No update.
Come up with a project plan for this, starting by identifying how daostar.org/schema will actually be used. E.g., it’s clearly referenced in the actual EIP, so there needs to be SOMETHING HUMAN READABLE there. But when a computer goes to daostar.org/schema and tries to parse it (e.g. because they want to display it in their UX), what should it expect—an RDF file? A JSON-LD file?
Also, we need a JSON Schema implementation.
2. Parsers + data science to illustrate the use of this data
3. Standardized docs for every DAO reference implementation
4. Generate standardized docs for every actual 4824 endpoint.
3. Plan for daostar.org/schema, what is it actually being used for?
4. links to all the nice files .owl, .rdf files at daostar.org/schema
5. clean up daostar.org/schema
6. add link to daostar.org/schema from daostar.org
7. and some sort of schema.org integration TBD
Host a workshop at CMU? Or possibly DAO Palace v2? Feb/March
No update.
We need to follow-up the discussion from DAOstar conversations with Z, what is the future, is the model ENS, or Ethereum Foundation, or W3C, or an incubator, or a traditional development company related to a token/OSS protocol? What is the business model for each of these entities?
Josh gave a preview of the plans for DAOstar One. ALSO: DAOstar Two.
- maybe we can make progress on this in an DAOstar in-person workshop, potentially at CMU in the winter/early spring as part of a larger gathering of governance people?
Ask George, Will, Opolis Josh, or Ivan to take the lead here? [Cozy Room M&A chat]
No major change since update last week; still need to sort out the Web3 connection for the auth flow. Have a broader talk about that flow as part of the UX design.
Blocked by lack of “manager” address in current registration contract.
Need to hire a top notch API devops backend engineer.
Building Web3 auth flow for a “manager” address, but we need to figure that out!!!
Go through UX design.
First step: post DAOIP-1 API standard (+ DAOIP-0 for process)
Biggest need: ability to list all Cosmos / Solana / etc. DAOs alongside all the Ethereum DAOs
Isaac connected us with Dennison for DAO NYC; let’s do something there! June 22
Andros is not around these days.
Posting to Hack Money (?)
Find someone to take charge of the bounty program.
Ask James to host a “register your DAO” table at MCON
Minimal data analysis, to ensure data we’re making available is actually useful and is not just crap. Basically, a set of services related to the externally-facing APIs. +
Developer support resource, outward-facing and helping DAOs produce good data.
Need to source a data scientist.
Need to source a developer support person who can help DAOs produce good data.
Need to source a data scientist.
Need to source a developer support person who can help DAOs produce good data.
survey on one of the calls on what to discuss; consistent weekly call with a more regular cadence; identifying a particular question that is to be discussed; lightly facilitated with some context setting; ask why are they there and put into the chat; preparing questions; for certain conversations cross-pollinate
Going well, David’s running this.
Working paper is done and finalized.
https://daostar.one/attestations
Lots of updates.
Avenue, Govrn, Disco, and possibly Mainstream + CharmVerse are working on a shared implementation now.
Officially: it has been approved. But we have been waiting for a week for someone to manually merge it.
Josh has been responding to the GitHub repo. What is the blocker exactly?! Responding to suggestions. Z thinks they just want to see more implementations
Ethereum Magicians post drafted; manager contract specced; need actual contract / feedback from Solidity devs
Add manager address + functionality to the registration factory contract.
Table
Working Groups
Name
Related to People (1) (Related to Working Groups (Property))
Description (pinned on TG)
Projects
Chair's Telegram handle
Telegram group
Type
Chair
Subject
People
EIP-4824 Reference Implementations
EIP-4824 Documentation, Schema Files, Ontology
EIP-4824 Endpoint Service; DAOstar historical record feature
EIP-4824 Schema Extension Tool
DAOstar One Token
Finalize EIP-4824 on EIP
DAOstar DAO Data Quality Assurance
DAOstar Workshop
DAO indexer
DAOstar front end / website revamp
Project management
@IsaacPatkaCore engineering; EIP-4824
@thelastjoshCommunity management and onboarding to DAOstar and DAOstar One
@thelastjoshHow DAOstar and DAOstar One should be governed
Promoting and supporting adoption of DAOstar standards, along with other partnerships