DAO URI doesn't accept managerAddress and contractRegistryURI

[Rashmi-278]

This was because the graphQL schema and API validation schema did not include these fields.
PR: #135

[Rashmi-278]

Adding this would conflict with the current DAO-IP2 Standard, perhaps more discussion is needed on which fields should be included in the DAO URI.

[Rashmi-278]

Should the standard include managerAddress?
https://eips.ethereum.org/EIPS/eip-4824

[thelastjosh]

It does already!

…

On Sat, Sep 16, 2023 at 4:16 PM Rashmi V Abbigeri ***@***.***> wrote: Should the standard include managerAddress? https://eips.ethereum.org/EIPS/eip-4824 — Reply to this email directly, view it on GitHub <#134 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHA5PBTXJT6IXMHYIHC7QDX2YJJDANCNFSM6AAAAAA4EBYYWE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- http://www.joshuatan.com/research/

[Rashmi-278]

Sorry! My bad, I meant in the DAO URI schema

[Rashmi-278]

The graph error on my end is resolved, build succeeds
Blockers

• DAO* API deployed on Digital Ocean Droplet needs to be reloaded to reflect the changes
• After the above step, we need to deploy the graph instances for all the networks once again

[Rashmi-278]

Demo: https://api.daostar.org/immutable/QmaZF9ffGG6qhPsNWpqHQGJLW2fNMFfb6MACb7c3gzGpG8