daostar icon indicating copy to clipboard operation
daostar copied to clipboard

Updated version of contractsURI

Open thelastjosh opened this issue 9 months ago • 9 comments

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:

  1. On-chain contracts
  2. Associated treasuries, e.g. Safes
  3. Official Telegram
  4. 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

  1. Aggregator
  2. Trustless / permissionless integrations (i.e. more interop)
  3. 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.

thelastjosh avatar May 29 '24 13:05 thelastjosh