Simple summary

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

Rationale

Adopting the EIP-4824 standard will enrich the on-chain information availability of Aave 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 Aave 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, DAOhaus, Etherscan, DeepDAO, and other members of DAOstar One.

Note that adopting the standard does not require any parameter changes to Aave’s existing DAO contracts, nor is there any cost besides gas to call the factory contract. To make the process easier, we have already built and deployed 4824-compliant subgraphs for the component endpoints of daoURI, including membersURI, proposalsURI, and activityLogURI. What remains is for Aave to claim these off-chain endpoints via the on-chain process specified by EIP-4824. The proposal does not in any way change the way that Aave’s governance works.

DAOstar is a public goods project supported by the Ethereum Foundation, Gnosis, Aragon, Radicle, MolochDAO, MetaCartel Ventures, The Graph, and many other members of DAOstar One.

Governance action

By voting yes, you agree that Aave DAO will (1) upgrade to EIP-4824 by calling the EIP-4824 registration contract located at 0x37df3fc47c1c3a2acafd2dad9c1c00090a8655bc, with Joshua Tan of DAOstar/Metagov (thelastjosh.eth) as the temporary manager for the registration contract. No funds will be transferred.

By voting no, nothing happens.

Technical details

To simplify adoption, we have pre-built the subgraphs and endpoints for Aave DAO. The endpoints can be edited at will by the selected manager, or by another vote of the DAO itself. For example, here is a live endpoint serving 4824-compliant data for Aave.

Conclusion

This proposal will upgrade Aave DAO to EIP-4824 by deploying a new registration contract through a contract interaction with the EIP-4824 factory maintained by DAOstar. It is extremely low risk, benefits Aave DAO by upgrading it to the ecosystem standard, and also positions Aave as a leader on standards for the ecosystem.