[TEMP CHECK] Extend Aave DAO with EIP-4824

Title: [TEMP CHECK] Extend Aave DAO with EIP-4824

Author: Aman & @thelastjosh

Date: 07-11-2023


An opportunity to publish an EIP-4824 compliant daoURI for Aave DAO and join the ranks of Optimism Collective, Arbitrum Foundation, ShapeShift, Snapshot, Aragon, etc. in advancing the interoperability of the DAO ecosystem.

EIP-4824 defines a standard json schema for publishing essential DAO metadata onchain. It does so by deploying a new smart contract to store the daoURI. This proposal was posted earlier in March and did pass the Snapshot vote unanimously. We are resposting it to meet the quorum requirements required to proceed further.

This proposal does not involve any transfer of funds or changes to Aave’s smart contracts.


Consider today’s DAO ecosystem. There are over 20,000 DAOs (from DeepDAO) deployed using different governance frameworks, many with token holders and treasuries on multiple chains. This number is set to increase by orders of magnitude in the next few years. Additionally, with the launch of new layer-2s and cross-chain solutions, the number of DAO-controlled parameters are increasing day by day.

Even so, we lack a robust framework to collect essential DAO data. While aggregators are doing the best job they can, it has become almost impossible to keep up with the DAO ecosystem given sheer number modifications and new launches happening in governance. This imposes several limits on DAOs. For one, new DAOs and DAO frameworks fail to be discovered and indexed by aggregators and policymakers. Secondly, from a tooling point of view, it is harder to build a protocol that interoperates with most DAOs and governance frameworks.

To address these shortcomings, we authored EIP-4824. The standard has gained significant momentum in the last year in terms of adoption:

  • Snapshot adopted EIP-4824 on their onchain governance framework, Snapshot X. Going forward, 100s and possibly 1000s of DAOs created using Snapshot X will automatically be EIP-4824 compliant.

  • ShapeShift DAO, Unlock Protocol and LXDAO recently adopted EIP-4824

  • Optimism Collective awarded DAOstar a Mission Proposal to ensure EIP-4824 compliance within the Optimism ecosystem. We are currently developing an alternate route to publishing daoURI’s, using Ethereum Attestation Station (EAS).

  • The Arbitrum Foundation awarded DAOstar a grant to streamline the adoption of EIP-4824 and infrastructure being built on top of it. This grant will support an ambitious regulatory interoperability project that leverages EIP-4824 to build a regulatory interface for DAOs.

On top of this, DAO frameworks including Aragon V3, DAODAO (Cosmos), Moloch v2 / DAOHaus, Moloch v3 / DAOHaus, Gnosis Safe, DAOstack, KALI, Q.org, Power Protocol and XDAO have either already adopted or have committed to adopting EIP-4824 in the short term.

EIP-4824 has also proved to be a good foundation for all the other standards. The Grants Management standard piloted by Gitcoin, Attestations standard built by Avenue, Govern, EAS & funded by Optimism, much of the regulatory interface work the Regulatory Interop WG did were composed on top of it. This proves the importance of having a DAO metadata standard.

EIP-4824 was authored by Joshua Tan (DAOstar/Metagov, Oxford), Isaac Patka (SEAL 911, Moloch), Ido Gershtein (DAOstack), Eyal Eithcowich (DeepDAO), Michael Zargham (BlockScience, UPenn), Sam Furter (Polygon) with contributions from Auryn Macmillan (Gnosis Guild), Fabien (Snapshot), Selim Imoberdorf (Aragon), Lucia Korpas, and Mehdi Salehi (Offchain Labs).


EIP-4824 defines a standard JSON-LD schema to publish DAO metadata onchain:

    "@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>"

We make the following suggestions for the subfields:

  1. name: Aave DAO

  2. for description, using the following lines from the documentation: The Aave Protocol is decentralised non-custodial liquidity protocol where users can participate as suppliers, borrowers or liquidators. AAVE is used as the centre of gravity of Aave Protocol governance. AAVE is used to vote and decide on the outcome of Aave Improvement Proposals (AIPs). Apart from this, AAVE can be staked within the protocol Safety Module to provide security/insurance to the protocol/suppliers. Stakers earn staking rewards and fees from the protocol.

  3. for membersURI, we using the Boardroon API to get a list of voters: https://services.daostar.org/api/v1/boardroom/members/1/aave

  4. For proposalsURI, we using the Snapshot API to get a list of proposals: https://services.daostar.org/api/v1/snapshot/proposals/aave.eth

  5. For governanceURI, pointing to the governance docs: Governance - Governance

  6. For contractsRegistryURI, pointing to the developer docs: Deployed Contracts - Developers

  7. governanceURI will point to: Governance - Governance

The DAOstar register page (DAOstar) provides a simple interface to generate a daoURI once the subURI’s are ready:

generating a daoURI for Aave DAO

daoURI’s generated through the register service above are automatically stored on IPFS.


If passed, Aave DAO will execute the following call to 0x2Dac5DBbF1D024c1E0D9c92D3AeDa7618e15aDd7 on Ethereum Mainnet to complete the registration, setting the timelock contract as its admin:

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.

The manager address can be left blank or delagted to a multisig. If a DAO-owned multisig is willing to volunteer, we propose setting a manager while registering. Otherwise, this can be left blank (set to 0x000) and changed later, as needed. From the previous forum discussion, @bgdlabs, pointed out that:

We would like to point out that it is probably better to avoid delegation to a multi-sig, just boiling down to make governance proposals whenever any “metadata” needs to be modified for the DAO. The best solution is to have the Level 1 governance Executor (Short Executor) with all the roles required, especially because doesn’t seem like a really frequent action.

Having had no counters to this suggestion, we suggest setting 0x0000000000000000000000000000000000000000 as the manager as that column cannot be left blank while registration. Additional managers can be added later as needed. We forsee daoURI updates to be infrequent.

Simulation Results

Given a salt of 0x42 and a msg.sender of the Aave Short Executor Timelock (0xEE56e2B3D491590B5b31738cC34d5232F378a8D5), the registration contract is deployed to

EIP-4824 registration simulation

As an extended example, here is Unlock Protocol’s successful EIP-4824 proposal & execution: Tally | Unlock Proposal


In summary, this is an extremely low risk proposal that’ll take us one step closer to true interoperability within the DAO ecosystem. This proposal does not involve any transfer of funds or changes to Aave’s smart contracts.

Given the importance of standards and how much they’ll improve the web3 ecosystem, we urge everyone to provide their feedback and support for this proposal.

Next Steps

  • Get community feedback on TEMP CHECK
  • Snapshot vote
  • If Snapshot is successful then move to AIP


Copyright and related rights waived via CC0.

thank you for the TEMP Check.
A few questions:

  • Whats the main benefit for the AAVE DAO integrating this EIP?
  • What are potential drawdowns?
  • What costs are involved in implementing this EIP?

I would also like to hear some feedback from other delegates that may be active in other DAOs already having this EIP. And also hear some feedback from @bgdlabs about the technical implications also regarding governance v3.

Overall i am not against this, but for now i don’t see the main benefit for the DAO.

1 Like

tbh, the ACI fails to recognize the big benefits of the adoption of this new standard.

It’s solving a problem we are not sure we have in the first place and benefits seem theoretical at best.

we will not fight against it, but not particularly supportive of this initiative.

We intent to cast an abstain vote on snapshot.


Thank you for the questions @MarcZeller and @EzR3aL. Let me provide some very practical examples of how this might be beneficial for the DAO:

Consider Aave DAO’s profile on DeepDAO. You can clearly see that they have been unable to index onchain governance and now displays just the Snapshot votes. While Messari has this covered, along with information about key delegates and contracts, all of this is behind a paywall, mainly because of the amount of resource it takes to collect maintain this data.

As another example, this is AaveGovernanceV2 contract on Etherscan. But can you find any additional info about Aave DAO, the owner of the contract, on that page? There isn’t a description of how Governance v2 works or any easily consumable context about it.

All 3 organizations I mentioned above, along with 80+ others are members of the DAOstar Roundtable. And all of them will attest to the fact that aggregating and keeping track of DAO metadata is a huge painpoint. While it can be done for a few DAOs, it is extremely hard to do across 1000 DAOs, many of which have different governance processes and treasuries & contracts on multiple chains. We’ve spoken to a majority of them and they would 100% love to improve this process.

EIP-4824 was created to solve this. Think of it as a one-pager that Aave DAO publishes on its behalf for everyone else to see. The daoURI can provide all essential information on the DAO- from members, to governance proposals to contracts owned to documents to refer for further clarity(and more details if you choose so). Afterall, it is the DAO’s responsibility to ensure that it is as transparent and approachable as possible. While the daoURI suggested above is a very basic version, DAOstar, with the funding provided by the Ethereum Foundation, Optimism Collective, Arbitrum Foundation and many others, is happy to customize it to Aave DAO’s liking.

So for no extra cost and by spending no additional resources, this is a chance for Aave DAO to increase its trasparency as well as interoperability with tooling providers. With almost all DAO governance frameworks committed to implementing/having already implememted EIP-4824, we would be seeing some significant improvements to how DAO data is supplied and displayed in the ecosystem. I urge Aave DAO too to be a part of this movement.

@MarcZeller, @EzR3aL, I’m happy to provide more clarity should you have any questions. As your support is key, kindly let me know if you have more questions.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.