Extend Unlock DAO to EIP-4824

##TL;DR This proposal, if passed, will set Unlock DAO up for adopting EIP-4824, a metadata standard for DAOs. Adopting EIP-4824 involves deploying a registration contract to hold Unlock DAO's daoURI. No changes to Unlock protocol's governance/smart contracts, no trasfer of funds are involved with this proposal.

The EIP-4824 standard has already been embraced by the likes of Snapshot, Aragon, Optimism, etc. DAOstar, with the help of a recent grant from Optimism, will help build a daoURI for Unlock DAO.

##ABSTRACT

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

##MOTIVATION

The absence of a global DAO interface has been holding back the ecosystem for a long time. New DAOs, DAO frameworks have zero visibility on aggregators, most tooling providers have a hard time integrating with different DAO architectures, there is no comprehensive, self-maintaining registry for DAO data, etc. EIP-4824 aims to solve the above issues by providing 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 Unlock’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 Unlock DAO 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.

1. EIP-4824 has gained traction with industry leaders such as Snapshot (in Snapshot X), Aragon V3, Moloch V3, DAODAO, and Aave.
2. We are proud to announce that we recently secured a $100k grant from Optimism to promote EIP-4824 adoption among DAOs.
3. Importantly, adopting this standard does not necessitate any fund transfers from Unlock or alterations to its current smart contracts. It simply involves deploying a registration contract to store Unlock’s daoURI. With the support from the Optimism grant, DAOstar will assist in crafting the required daoURI for Unlock DAO.

DAOstar (https://daostar.org/) is a non-profit that builds standards and public infrastructure for DAOs. We are supported by the Ethereum Foundation, Gnosis, Optimism Collective, The Graph, Aragon and other members of DAOstar One (https://daostar.one/). Both Snapshot and Tally, that Unlock DAO uses in its governance, along with 80+ key organizations in the DAO ecosystem, are active members of the DAOstar One Roundtable.

##SPECIFICATION

If passed, Unlock DAO will upgrade to EIP-4824 by calling the EIP-4824 registration contract located at 0x37df3fc47c1c3a2acafd2dad9c1c00090a8655bc, setting a DAO owned contract as its admin. No funds will be transferred.

The registration contract exposes a daoURI view function which returns the URI containing the EIP-4824 compliant registration JSON document. During registration, the DAO may set a relevant multi-sig/working group as a manager, to more conveniently manage the daoURI.

This proposal will execute the following call to complete the registration:

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 role is granted to the DAO.

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

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

##SIMULATION RESULTS Given a salt of 0x42 and a msg.sender of the Unlock Timelock, the registration contract is successfully deployed to 0xec9d904e7ff0a70f0dd95e7e95c01e32544a0043.

##RISKS The proposal is extremely low risk. It involves calling a factory that will deploy a new, standalone registration contract on behalf of Unlock DAO. The sole purpose of that contract is to publish a daoURI field on behalf of the main Unlock contract(s).