daostar
daostar copied to clipboard
Updated version of contractsURI
Re: discussion with Arnold of Lighthouse (DAO aggregator) on May 29, 2024.
This is a stub for a new standard that develops out what we would like to see in contractsURI (currently an optional subfield of daoURI) and how we should go about verifying self-reported information in contractsURI.
We want ideally on-chain verification of the following list of data:
- On-chain contracts
- Associated treasuries, e.g. Safes
- Official Telegram
- Official Discord
All this information stems from deployer contract? Could we talk to Hats about integrating some of their on-chain information into daoURI?
Motivation
- Aggregator
- Trustless / permissionless integrations (i.e. more interop)
- Audits
Also see discussion of DAO ID: #213 .
Other ideas:
- Could this combine with Uma Protocol, to check if someone reports a false contract address? A true trustless version would require an oracle of some sort.