Aragon DAO names

[daviddavo]

The current approach is too manual and should be somehow automatized

• Add the DAOs from poweredby.aragon.org
• Read the code and Investigate how dao-list-middleware works
• Investigate if its possible to do something with the templates
• Investigate Aragon ID repo
• Try to modify the subgraph to get the address
• Parse organization_scores.csv

[daviddavo]

It seems that it "knows" that the controller is blankdao.aragonid.eth because you accessed it before, and the app saves it as an alias.

But if you enter after removing the cache, that knowledge disappears.

You get that the controller is the domain [3c960f08825374c264d9a5e412ac6b878f1812a06870e2251c1ad3a279c776c4].[b50225e66585b05f85fa55923224991b0517e07903ac43c0e5258b4d48950a97].eth which doesn't give us much information...

So I still don't know how to get the dao name given the address

[daviddavo]

poweredby

We could also get some data for our json from their poweredby page

https://poweredby.aragon.org/

[daviddavo]

I also found this file

https://github.com/1Hive/apiary/blob/master/data/app_mining_cycle1/organisation_scores.csv with a lot of info about organizations. It's from an old 1hive project that listed all aragon DAOs...

Here is the script they used to get this data (in nodejs)

https://github.com/1Hive/apiary/blob/fd22f324428c00857c9a39afc62ad7dbacd7a29b/scripts/calcscore

https://github.com/1Hive/apiary/blob/fd22f324428c00857c9a39afc62ad7dbacd7a29b/scripts/calcscore#L34-L143

The problem?

It uses the following line:

  } = await got.post('https://daolist.1hive.org', {

But dailost.1hive.org is dead...

I think this is the repo with that service, but It needs further investigation

• https://github.com/1Hive/dao-list-middleware

In the meantime, I think we should add the "poweredby aragon" DAOs to our list manually.

---

dao-list middleware just processes the data from the repo 1hive/daolist

In this repo, we can find a json with info about some daos on xdai. More specifically, the info of the daos on xdai's gardens interface (gardens.1hive.org).

I think these are a kind of DAOs based on aragon, but with a new set of apps.

• Blog post about gardens

By the way, 1hive's aragonOS deployments are located here, but we still don't have enough info about mainnet

---

We can modify the subgraph so it includes names, using this source from the contract. Here is the JSON ABI: https://github.com/aragon/connect/blob/master/packages/connect-thegraph/subgraph/abis/ENS.json

[daviddavo]

The previous contract sets up the registry, but not the DAOs

But we found the contract that receives the name to be put for DAOs created using the company template

    * @param _id String with the name for org, will assign `[id].aragonid.eth`

https://github.com/aragon/dao-templates/blob/a575d3711a21a2f3a2048c77a7321883a606a571/templates/company/contracts/CompanyTemplate.sol#L26-L52

Nevertheless, every template at some point uses the _registerID(string _name, address _owner) function from BaseTemplate.sol, so we could try and scrape that somehow?

https://github.com/aragon/dao-templates/blob/a575d3711a21a2f3a2048c77a7321883a606a571/shared/contracts/BaseTemplate.sol#L387-L390

[daviddavo]

HOW TO GET THE NAME OF A DAO GIVEN AN ADDRESS (manually)

Let's say we have a random address like 0x67757a18eda83125270ef94dcec7658eb39bd8a5

On etherscan, we can click on Creator txn, and then decode the input data of the transaction and...

This could be automated with API calls to Etherscan, having the ABI of the contracts. Perhaps this could be put into the subgraph.

[daviddavo]

Not with every DAO is possible to follow this process. For example, with this address... 0x054086d40cf8fd5bf6200eda7f9c6877b0302dd1, the input data doesn't have an _id, because it uses a custom template.

And for DAOs created with DemocracyKit, instead of _id we have to use aragonID

[daviddavo]

I've created an Issue about the subgraph in aragon/dao-templates#221, in case someone who knows how to make subgraphs wants to do it

I'll snooze this issue until I want to learn how to make subgraphs