🛠️

Strike Team #26

Last Edited Time
Jun 13, 2022
Created time
May 26, 2022
Participants
Created By
Type
Strike Team
Created
May 26, 2022
Property
Property 1
Attendees: Josh, Z, Isaac, Ido, Luke, James Brennan, Keating
Minutes
Isaac: API is almost live!
We need a basic policy for dealing with grant tokens, e.g. keeping modest stakes in a variety of projects.
 
Feedback
  • Ido: I expect daoURI (unlike membersURI) to point at IPFS or a CID. Or… do we expect daoURI to change quite often?
    • Zargham: daoURI itself should require a governance action to change, but the CONTENT of daoURI (i.e. the JSON with name, description, membersURI, etc.) can change.
    • Feature request: if a DAO wants to host daoURI as a IPFS file, we can pay to host that file on IPFS and provide access to that IPFS file via the same UI
    • Feature request: URI should be content addressed not location addressed
    • Isaac: as long as there is auth, I’m okay with location addressing / daostar hosting this to lower the difficulty
  • Josh: I was just thinking, I wonder if it would make sense to use an existing API gateway service like Kong Gateway to manage all these APIs? I.e. we could be just a branded + managed version of Kong Gateway.
  • Isaac: what if we eventually did a thin client / integration of ENS, Lit Protocol, Ceramic, so that people can choose how they want to authorize.
  • Z: I think the content addressing allows us to use daoURI much more as a unique ID of the DAO; location addressing is harder
 
🛠️

Strike Team #26

Last Edited Time
Jun 13, 2022
Created time
May 26, 2022
Participants
Created By
Type
Strike Team
Created
May 26, 2022
Property
Property 1
Attendees: Josh, Z, Isaac, Ido, Luke, James Brennan, Keating
Minutes
Isaac: API is almost live!
We need a basic policy for dealing with grant tokens, e.g. keeping modest stakes in a variety of projects.
 
Feedback
  • Ido: I expect daoURI (unlike membersURI) to point at IPFS or a CID. Or… do we expect daoURI to change quite often?
    • Zargham: daoURI itself should require a governance action to change, but the CONTENT of daoURI (i.e. the JSON with name, description, membersURI, etc.) can change.
    • Feature request: if a DAO wants to host daoURI as a IPFS file, we can pay to host that file on IPFS and provide access to that IPFS file via the same UI
    • Feature request: URI should be content addressed not location addressed
    • Isaac: as long as there is auth, I’m okay with location addressing / daostar hosting this to lower the difficulty
  • Josh: I was just thinking, I wonder if it would make sense to use an existing API gateway service like Kong Gateway to manage all these APIs? I.e. we could be just a branded + managed version of Kong Gateway.
  • Isaac: what if we eventually did a thin client / integration of ENS, Lit Protocol, Ceramic, so that people can choose how they want to authorize.
  • Z: I think the content addressing allows us to use daoURI much more as a unique ID of the DAO; location addressing is harder