metagov / daostar Goto Github PK
View Code? Open in Web Editor NEWDAOstar (or DAO*) is a set of technical standards and tools for DAOs and DAO tooling
Home Page: https://daostar.org/
License: MIT License
DAOstar (or DAO*) is a set of technical standards and tools for DAOs and DAO tooling
Home Page: https://daostar.org/
License: MIT License
November 13 - 19
Two-week Zuzalu gathering also in Istanbul right before
What could we do?
Post suggestions below!
Definitely going
Create a series of readme files or a readthedocs or a gitbook or something linkable and hosted on this GitHub for docs.
What are we really trying to do with these docs? Enhance adoption on (1) DAO tooling companies (think members of DAOstar) and to a lesser extent (2) DAOs, especially more sophisticated DAOs who are building their own infrastructure. Normal DAOs will be interacting with the app frontend.
initial sections might be:
This should be super clean and simple, since our infra is very lightweight!
Following up on the original Snapshot integration (#65), can we improve it by adding a activityLogURI? Refer to EIP-4824 for the specification of activityLogURI.
Also, fix the URI design for all the URIs to deal with the fact that somewhere the records are getting capped (so we are only seeing like the top 15 proposals, the first 15 members, the most recent 15 votes, and stuff like that).
Also, potentially fix the membershipURI design (ref. the one that we built custom for ENS). I will update this part of the issue later.
tldr: we need to upgrade the registration factory contract at the canonical DAOstar address
The existing use-case for the registration factory is this:
We need to upgrade the registration factory contract to enable two additional use-cases:
2. Existing DAO with daoURI asks to get verified and added to the registry, [but how would we track further events emitted by the DAO? they need to have the same events]
3. A factory contract deploying DAOs with daoURI asks to get all additional DAOs tracked to the registry
This issue constitutes a specification of the upgraded registration factory.
The new Aragon OSx, DAODAO, Kali, Superdao, etc. all have daoURI embedded in the DAO contract, so they are technically 4824-compatible. But this presents an indexing problem.
Aragon, in conversations, would prefer something like an ENS for DAOs, i.e. a centralized and possibly on-chain registry, something that people can easily verify. We need to write a quick spec of what this "ENS for DAOs" would need to do.
Josh needs
Additional discussion elements to address later:
Right now, we can't even access the management flow for daoURI.
Before connecting wallet, I want to be able to:
After connecting my wallet, I want to be able to:
can we add a function for daoURI(address)
to the standard?
Basically, having a variant of daoURI()
with an address
that returns a string
.
This would allow a singleton registry for all daos rather than creating a registration contract for every single dao.
Add an "updates" section for daostar.org as well as a calendar of community calls similar to login.xyz, to give the site a more dynamic feel, and to give folks the sense that it is alive and being supported.
Let's incorporate the attestations explorer being built by @frm into the new frontend!
The main, consolidated list of all issues and improvements is at this Google doc.
This issue consolidates multiple issues and feature requests for the new daostar.org website, including: #75, #101, #90.
Luke and Josh need to add an institutional credit card on Pinata / IPFS to make sure the current api.daostar.org doesn't break when the free account runs out. Note, AWS instance has already been set up.
Build a backend caching database (and API) that Metagov/DAOstar would maintain, that would allow for queries against all the membersURI, proposalsURI, activityLogURI data, e.g. "list all DAOs by number of members".
Contact Josh or Ido to get more details here.
Original proposal: https://app.charmverse.io/op-grants/page-31849314357430236
These are the key components of the project:
An attestation-based architecture and data model for DAO membership, member contributions, and other data (a.k.a., Attestation Standard V2)
A web platform for attestations and contributions: This platform will be capable of displaying DAOIP-3 attestations and contributions for any given Ethereum address.
Accompanying Infrastructure: This infrastructure will allow a client to deploy a new platform instance for a given Ethereum RPC-compatible network.
But the critical milestones of the project are:
Ideally, we want to complete all things promised under the key components by Q4 2023 and also try to get some adoption for it.
The Snapshot integration would allow a DAO with an existing Snapshot instance to just copy the members definition there to populate a membersURI. It would also allow the proposals in Snapshot to populate a proposalsURI.
Effectively, the flow should be, a DAO selects "Snapshot" as the framework, they give us their Snapshot instance, and we just populate everything for them.
Display the (off-chain) attestations via the Attestations for DAOs standard being published by Govrn in the DAOstar frontend. On request of Aaron of Govrn.
Right now, continued development of DAOIPs means that daoURI is getting rapidly updated. There are new changes and additions to the schema all the time. What is the best way of pushing updates to the schema?
This issue will be considered resolved when we have a full update flow specified and implemented.
The successful implementation and deployment of the EIP-4824 standard in the Optimism ecosystem, confirmed by Optimism and at least three other large DAOs on Optimism publishing a daoURI.
Tasks:
Due date: end of September 2023
The grant will only be received once the aforementioned tasks have been completed.
Original proposal: https://gov.optimism.io/t/final-daostar-governance-standards-for-the-optimism-ecosystem/6181
We need to be able to recognize who has given grants to DAOstar.
The purpose of this issue is to explore and address the development of a robust Membership Management System for DAOstar. This feature requirement emerges from the need to streamline our current processes and offer better service to our members, and it should not hinder or delay the launching of our new membership/dues program.
The proposed system should seamlessly integrate the following components:
A major complicating factor (or opportunity) is the potential interaction between this membership management system and any eventual DAO or DAOs (it's hard to imagine a single contract, since participating DAOs will exist across many chains) that will govern DAOstar. I.e. one might expect that being an active member will give you certain governance rights in the DAO. To the degree possible, we should proceed with the design of this system in a way that does not constrain the future governance of DAOstar.
Previous discussions regarding this topic have included @ipatka and @mzargham, and older conversations have also involved Auryn, Kei, Zargham, Ivan, and others. Further input and involvement from all relevant parties will be invaluable to this project's successful execution.
Actions:
Looking forward to your thoughts and feedback on this matter.
Hi! This is a request to create a daoURI schema on Ethereum Attestation Service, so that DAOs can deploy daoURI by making a EAS attestation.
EAS is a public good for making attestations on or off-chain about any topic.
Here's an example daoURI attestation made on EAS.
Note - you can customize the schema however you'd like.
Quick links:
Let's clean up the Notion and webpage of defunct members. Currently, I notice at least that Bribe, ADAO are no longer functional. Not sure if there are others.
Also, let's rename Orca to Metropolis.
Extend "The standard" section with a live demo of the standard, plus icons going to DeepDAO, Messari, Etherscan, and other live integrations etc. to illustrate how DAOs benefit from the legibility + reporting features.
Ideally Asia-based, as we re-center toward Asia.
A section of the website where we can advertise current support for the standard, including (1) embeds of favorable Twitter coverage or articles, (2) commitments from partners such as Messari, DeepDAO, or Etherscan.
We have a new factory contract that makes it easy for existing DAOs to own and manage an API. We should reference that in the website.
One Pager Article on "Why do we need standards" completed by Hazel EOW.
Josh: would be useful to get a few quotes from people, DAOstar members
Ivan: Industry feels younger
Pre-make some endpoints for the Gitcoin DAO, prior to the proposal going onto their forums.
When you click "Register", the daoURI created is empty. It needs to have the subURIs filled
eg: for ens.eth, this is the daoURI being created: https://api.daostar.org/immutable/QmcnPsUNY5x49MX5weF6bBRJ8vx2H12GNxQPJt2NhMNWUH
Note that before "Registering", the subURIs are being generated.
@ipatka weren’t you talking about some kind of remix license? Could that be used here.
Background: no idea what we’re doing with DAO Creative Universe, it’s kind of a marketing draw to bootstrap the DAOIP system, but could be fun to experiment with some sort of open source approach to developing a “cinematic universe” of related stories and IP.
We need to diversify DAOstar's funding stream and establish a basic membership program.
Current DAOstar API is running a IPFS node and hosting files via Pinata free tier. The free tier is limited to 100 files, and the node is not designed for hosting a large amount of data, and won't propagate to multiple nodes. Once we have a larger release / more contracts hosted we will need to find a longer term solution for decentralized storage ie FileCoin, hosted Metagov IPFS nodes, spending money on Pinata or other pinning services, etc.
This is the context of a potential contract with dOrg. They are requesting additional detail, rather than have that sit in a contract I'm going to organize those specs into public issues.
Currently:
Not in scope but should be converted to issues:
Most of the activity & calls-to-action (as well as the working papers themselves) live on daostar.one, making daostar.org feel a bit dead and non-interactive. How can we improve that interaction?
This will require checking factory contracts, deploying a couple of OP testnet, etc. and is critical to supporting the OP tasks. @crazyyuan @Rashmi-278 please fill in additional plans & requirements here, and meet to discuss at some point this coming week / ASAP.
List of things to edit into the EIP:
GovernanceURI
"proposalsURI"
We should have a demo for this! Here's what you can do with that standard.
Member:
activityLogURI
Working Document Spreadsheet
This issue consolidates several tasks for documentation.
Stuff we need to add
The proposalsURI for MetagovDAO, generated automatically through the Safe reference implementation, has no data: https://daostar.org/registration/mainnet:0x48d1981a86bf62f3f005b03dd106789fd2d28104
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.