*a very poor representation of EIP-4824 registration flow. To be updated

EIP-4824 was authored with the single intention of making the lives of DAOs and DAO Tools easier.

At present, there are over 20,000 DAOs spread across multiple blockchains, governance frameworks, and operational structures. Due to an increase in their complexity and the number of DAO-controlled parameters, collecting essential DAO metadata has become a hard job. The extent of this problem is visible when we look at incomplete data sets in DAO-aggregators, tooling with limited support for different governance frameworks, and the monumental dev work required to integrate a new DAO/DAO framework into a tool. The EIP-4824 standard addresses these issues.

The Schema

EIP-4824 defines a simple JSON-LD schema for a daoURI that contains essential DAO metadata:

{
    "@context": "<http://www.daostar.org/schemas>",
    "type": "DAO",
    "name": "<name of the DAO>",
    "description": "<description>",
    "membersURI": "<URI>",
    "proposalsURI": "<URI>",
    "activityLogURI": "<URI>",
    "governanceURI": "<URI>",
		"contractsRegistryURI": "<URI>"
}

To create a daoURI for your DAO, you may use the DAOstar website.

Creating a daoURI for your DAO using DAOstar

Head over to DAOstar’s register page to locate the registration form.

Once you choose the blockchain and governance framework, and enter the DAO’s main contract address/ENS name (for example, Mainnet, Snapshot, ens.eth) some of the sub-URIs will automatically get populated. In this case, ENS DAO’s proposals are pulled using Snapshot’s API and members using Boardroom’s API. You may replace these fields with your own subURIs and add any extra info you wish to other fields (for eg, to the description, contracts Registry URI, etc.).

Once you finish customizing, you’ll receive a daoURI + some helpful metadata:

The daoURI hence created is automatically stored to IPFS. Here is the one from the example: ipfs://QmQPwwDDi2YCYsXxHwLqHECPPimynF8HRg9ae1Pxfdbgit

As you can see, this page also specifies a smart contract and a function call you may use to publish this daoURI onchain. As we’ll see below in greater detail, this is only one of the methods for adopting EIP-4824.