If passed, this proposal will extend ShapeShift DAO to EIP-4824 by deploying a new registration contract through a contract interaction with the EIP-4824 factory maintained by DAOstar.
The EIP-4824 standard defines common interfaces for DAOs via daoURI, akin to tokenURI for NFTs. In order to adopt EIP-4824, ShapeShift DAO will need to deploy a new smart contract that stores the DAO’s daoURI.
Note that adopting EIP-4824 does not require any parameter changes to ShapeShift’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 ShapeShift’s governance works. DAOstar, with the help of a recent grant from Optimism, will help generate a daoURI to help ShapeShift adopt EIP-4824.
The motivation of this proposal is to build a much needed piece of infrastructure for the DAO ecosysystem.
The absence of a DAO metadata standard has been holding back the ecosystem. Many new DAOs and 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 metadata, etc. EIP-4824 is an approach to solve all these problems and more.
When a DAO adopts EIP-4824, it deploys a registration smart contract that holds a daoURI. This daoURI contains information about the proposals, members, governance framework, contracts owned, etc. of the DAO. It is up to the DAO to decide what to publish via its daoURI. Even registering an empty daoURI is a significant step towards the much needed standardization in the ecosystem as it announces to every indexer that the owner of that registration contract is a DAO and it needs to be indexed.
Adopting the EIP-4824 standard will enrich the on-chain information availability of ShapeShift’s governance contracts, making it easier for existing and future DAO tools to seamlessly interact with the contracts. 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:
Snapshot X, Aragon V3, Moloch V3 and multiple other governance frameworks have integrated EIP-4824.
Optimism awarded DAOstar a mission worth $100k to help DAOs on Optimism adopt EIP-4824.
The EIP-4824 registration factory is located at 0x37df3fc47c1c3a2acafd2dad9c1c00090a8655bc. If this proposal passes, to upgrade to EIP-4824, execute the following call to this contract:
Call EIP4824RegistrationSummoner.summonRegistration(salt, daoURI, manager, contracts, data)
In the above contract call, the metadata needs to filled in. DAOstar will help ShapeShift build a daoURI. It can, for example, contain data from just ShapeShift’s Snapshot. It may also be partially empty, with the intent of updating later. A daoURI for ShapeShift is given below. More data can be added to the daoURI easily, including a link to ShapeShift, a link to the governance doc, a list of contracts owned by the DAO etc. We encourage the community to comment on this.
Demo daoURI for ShapeShift: https://api.daostar.org/immutable/QmT2bpbRtf2b3kpEoABY8iozSfk4N6fzczUR6EKDYyyHEK
New clones are deployed to predictable addresses using the message sender and a bytes32 value combined as a salt.
Transaction simulation: you can see that the above call successfully deploys ShapeShift’s registration contract to 0x58e593f2100fa06da34935c1b35fd78aaa32479a
Adopting EIP-4824 would greatly improve discoverability and interoperability for Shapeshift DAO. For example, consider the DAO’s multisig. Etherscan currently would not be displaying any info about the DAO which owns that multisig. Using EIP-4824, an indexor like Etherscan would be able to access ShapeShift DAO’s metadata and enrich its profile. After speaking with countless DAO tooling providers, many of whom are DAOstar members (there are 50+ DAO Tooling providers in the DAOstar Round Table), the existence of such a standard would greatly improve the ecosystem.
- Access to infrastructure that is 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, etc. Adopting the standard would mean access to all these important pieces of infrastructure and more that'll come up.
Gas costs required to call the registration factory.
For: adopt EIP-4824
Against: do not adopt EIP-4824