Extend dHedge DAO to EIP-4824

[amanwithwings]

Abstract

The EIP-4824 standard defines common interfaces for DAOs via daoURI, akin to tokenURI for NFTs. This proposal will extend dHEDGE DAO to EIP-4824 by deploying a new registration contract through a contract interaction with the EIP-4824 factory maintained by DAOstar.

This proposal does not involve any transfer of funds or changes to dHEDGE’s contracts. DAOstar, with the help of a recent grant from Optimism, will help generate a daoURI to help dHEDGE adopt EIP-4824.

Motivation

EIP-4824 defines global interfaces for consuming and reporting DAO data. The absence of such infrastructure has been holding back the DAO ecosystem - many new DAOs/ DAO frameworks have zero visibility on aggregators, most tooling providers have a hard time ensuring compatibility for different types of DAOs, there is no comprehensive, self-maintaining registry that stores DAO-information, etc. By defining a simple JSON schema, EIP-4824 provides a method for DAOs to self-publish information irrespective of their architecture or the chain they exist on.

Adopting the EIP-4824 standard will enrich the on-chain information availability of dHEDGE DAO’s governance contracts, making it easier for existing and future DAO tools to seamlessly interact with the contracts. A specific example is enabling members to interact with the dHEDGE governance contracts through different front-end interfaces, potentially across multiple chains. Some of the tools that are digesting or committed to digesting this enriched information include Snapshot, Tally, Etherscan, DeepDAO, and other members of DAOstar One.

Recent EIP-4824 Updates:

1. Snapshot X, Aragon V3, Moloch V3 and multiple other governance frameworks have integrated EIP-4824.
2. Optimism awarded DAOstar a $100k grant to help DAOs on Optimism adopt EIP-4824.

Note that adopting EIP-4824 does not require any parameter changes to dHEDGE’s existing DAO contracts, nor is there any cost besides gas to call the factory contract. The proposal does not in any way change the way that dHEDGE’s governance works.

Specification

If passed, the dHEDGE DAO will upgrade to EIP-4824 by calling the EIP-4824 registration contract located at 0x37df3fc47c1c3a2acafd2dad9c1c00090a8655bc, setting the DAO Treasury multi-sig as its admin and Joshua Tan (thelastjosh.eth) of DAOstar as its manager. No funds will be transferred.

The registration contract exposes a daoURI view function which returns the URI containing the EIP4824 compliant registration JSON document.

This executable proposal will execute the following calls to complete the contract upgrades:

1. Call EIP4824RegistrationSummoner.summonRegistration(salt, daoURI,manager, contracts, data)

New clones are deployed to predictable addresses using the message sender and a bytes32 value combined as a salt.

Roles and Access Control

There are only two actions possible in the registration contract: (1) changing daoURI and (2) changing the role structure.

A manager can modify the daoURI but not the roles while an admin can modify both the daoURI & the role structure.

During registration, admin roles are granted to the treasury multi-sig. A manager role is granted to Joshua Tan (thelastjosh.eth) of DAOstar.

Deployment Details

The registration factory contract is deployed to nearly all EVM chains. The mainnet address is 0x37dF3fC47C1c3A2acaFd2Dad9c1C00090a8655Bc.

[patet]

Its an interesting idea. Can you share more implementation information? What if some of the schemas change. Then what?

[amanwithwings]

for sure, @patet. Here is a transaction simulation (I used this dHEDGE DAO wallet: 0x352fb838a3ae9b0ef2f0ebf24191acaf4ab9ecec).

You can see that the transaction is successful, with the registration contract getting deployed to 0xcc27e02108f32f9e09c2e4c69d3c4e790d43a243.

Since dHEDGE DAO has presence on multiple chains, you could consider deploying registration contracts of different chains, all pointing to the same daoURI. For the simulation purpose, I used this daoURI for dHEDGE: https://api.daostar.org/immutable/QmTRUaZhTRN7CNXNGuZbduD1E9ec4GXxZX26Ev7kQFkjDe. It does not contain much data at present, but we will work with you on building an enriched daoURI for registering.

What if some of the schemas change. Then what?

If the schema changes/you want to publish a different set of information, you can do so by a simple contract call to the contract deployed in the previous step. This would let you update the daoURI.

[patet]

So this is specifically for a DAO URI regarding proposals, voting, and DAO memebership tracking. Nothing else?

I’m trying to full grasp what this is exactly and how it is beneficial exactly. Can you simply explain this?

[amanwithwings]

A daoURI, in its MVP form, includes proposals, members, an activity log, a governance URI (can be linked to a constitution or a governance doc) and a contract registry. However, if the DAO would like to publish more information, it can definitely do so by extending the schema.

Although the schema looks quite basic in its present form, you will be amazed at how difficult it has been for aggregators and tools to collect even this much information from DAOs. And things get increasingly tricky if there exists multiple governances, treasuries on different chains or if the DAO is on a non-EVM chain. For example, look at what DeepDAO, the leading analytics engine for DAOs, displays as dHEDGE DAO’s treasury value. The only way to ensure correctness of this information is for DAOs to self-publish basic info and for aggregators to consume this.

I’m trying to full grasp what this is exactly and how it is beneficial exactly. Can you simply explain this?

Ofcourse, @patet, thanks for asking this. EIP-4824 greatly improves the discoverability and interoperability of DAOs. For example, consider the dHEDGE DAO multisig I used for simulating the transaction earlier. When we look it up on Etherscan, it does not show any info about the dHEDGE DAO, which owns the contract. Through EIP-4824, an indexer like Etherscan, will be able to say “hey this multisig belongs to dHEDGE DAO, here is some more relevant information about them…”. The same goes for aggregators like DeepDAO, Messari, etc. who often times struggle to find information on DAOs with presence on multiple chains.

While the advantages start with interoperability/discoverability enhancements, a lot of infrastructure is also being built on top EIP-4824. For example, Gitcoin is building a grant management standard. Karma, Tally, Uniswap, etc. are building an on-chain delegate registry utilizing it. So adopting the standard would also mean access to all these important pieces of infrastructure that are coming up.

[amanwithwings]

hey @patet , could you guide me through the governance process at dHEDGE? Like, does this proposal need to go through a vote? If yes, how do we move this to a vote?

[patet]

This proposal does not need a governance vote. It would need significant traction in the community first.

The product is also in its MVP form. I would certainly like to see more adoption before voting.

If all a manager can do is modify the URI, why does a person at DAOstar need this role? Couldn’t dHEDGE self integrate once key members in the community request this feature?

dHEDGE self-reports its treasury at https://zapper.xyz/daos/d-hedge-dao

[amanwithwings]

Got it, @patet. We are speaking to a bunch of DAOs at the moment, I’ll hopefully be able to share more info regarding adoption soon.

The suggestion to add someone from DAOstar as a manager is primarily to streamline the process of updating the daoURI. With the recent grant, we now have the capacity to collaborate with DAOs in building or adjusting their daoURIs. Having a manager in place alleviates the need to navigate the full governance process for every modification. However, if a working group or a steward from dHEDGE is willing and able to assume this responsibility, that’s even better!

[edson]

A large concern we have is adopting an EIP that’s still in Draft phase.