DAOstar One (Internal)
DAOstar One (Internal)
/
🤝
Strike Team #27 / Community Call #8
🤝

Strike Team #27 / Community Call #8

Last Edited Time
Jun 13, 2022
Created time
Jun 2, 2022
Participants
Created By
Type
Strike Team
Created
Jun 2, 2022
Zoom Recording
https://stanford.zoom.us/rec/share/BJibLpba7nAatEK3JRWFbs2rPv9zy8GTL8Y49OYzR1L5ZE4Xu0Pv13SwzYRsEeGb.Xwi9MTli1d5qE4Qh
Property
Property 1
Atendees: Josh T., Issac P., A.Azfar, Ido, Luke,
Minutes
  • Isaac -
    • Updates on Data transformation
      • API will point to CAPs(?)
      • Sends webhook with result after
      Azfar -
    • Asks for results/example to bring back to team
      • Isaac -
    • Has budget implementation update for Keating
    • Lambda will be up shortly
      • Ido -
    • For now there will not be transformation to add context?
      • Correct
      Isaac -
    • Currently primary data storage is “centralized IPFS
      • Ido -
    • Is there any update on the EIP review?
      • Noted new comment on “name of EIP”
      • Seems blocked
      • James will reach out to Josh on this
      Ido -
    • Revist last week’s schema convo
      • Luke -
    • got info from Z on ipfs implementation
    • support both cloud storage, chain-agnostic, (schema current storage)
      • On our backend … chains could like to CID
      • Verify by checking on-chain data
      • Can also support temporary link
    • Action
      • Test implementation using CID
      • Generating schema using JSON-LD
      • Generate hash
      • Steps are to set up front-end UI
      Ido -
    • “Pinning” providers could be useful here
      • When endpoint is deployed, we could use pinata(?) to store to IPFS
      Luke -
    • Josh mentioned need for ability to host some things ourselves
      • Other services cost $$$
      Ido -
    • Data availability questions
      • Different circumstances for when hosting ourselves is preferable
      Luke -
    • Next week may be able to demonstrate some of the steps in action
      • Lucas -
    • Introduces himself and asks where he can help out
      • Isaac -
    • Schema help
    • Reference implementation help (e.g. with Moloch implementation)
    • Getting the word out to DAOs that these standards are coming
      • How do you organize X, Y, Z data/rules
      • Constitution documents markdowns
    • Perhaps add to airtable Lucas brought up with data
    • ** We ought to have an ecosystem wide Telegram/Discord**
      • “DAOstar Adoption”
      Lucas -
    • Made telegram group “DAOStart”
    • DAO planet event could be useful for this
    • How is DAOstar organized?
      • Isaac -
    • Metagov is parent group
    • Metagov handles wallets
      • Lucas -
    • General Metagov collaboration opportunities/seeking
        1. Index - Sharing
        1. Voting - Advisory
        1. Data dashboard - schema
        1. Education - Consensus
       
DAOstar One (Internal)
DAOstar One (Internal)
/
🤝
Strike Team #27 / Community Call #8
🤝

Strike Team #27 / Community Call #8

Last Edited Time
Jun 13, 2022
Created time
Jun 2, 2022
Participants
Created By
Type
Strike Team
Created
Jun 2, 2022
Zoom Recording
https://stanford.zoom.us/rec/share/BJibLpba7nAatEK3JRWFbs2rPv9zy8GTL8Y49OYzR1L5ZE4Xu0Pv13SwzYRsEeGb.Xwi9MTli1d5qE4Qh
Property
Property 1
Atendees: Josh T., Issac P., A.Azfar, Ido, Luke,
Minutes
  • Isaac -
    • Updates on Data transformation
      • API will point to CAPs(?)
      • Sends webhook with result after
      Azfar -
    • Asks for results/example to bring back to team
      • Isaac -
    • Has budget implementation update for Keating
    • Lambda will be up shortly
      • Ido -
    • For now there will not be transformation to add context?
      • Correct
      Isaac -
    • Currently primary data storage is “centralized IPFS
      • Ido -
    • Is there any update on the EIP review?
      • Noted new comment on “name of EIP”
      • Seems blocked
      • James will reach out to Josh on this
      Ido -
    • Revist last week’s schema convo
      • Luke -
    • got info from Z on ipfs implementation
    • support both cloud storage, chain-agnostic, (schema current storage)
      • On our backend … chains could like to CID
      • Verify by checking on-chain data
      • Can also support temporary link
    • Action
      • Test implementation using CID
      • Generating schema using JSON-LD
      • Generate hash
      • Steps are to set up front-end UI
      Ido -
    • “Pinning” providers could be useful here
      • When endpoint is deployed, we could use pinata(?) to store to IPFS
      Luke -
    • Josh mentioned need for ability to host some things ourselves
      • Other services cost $$$
      Ido -
    • Data availability questions
      • Different circumstances for when hosting ourselves is preferable
      Luke -
    • Next week may be able to demonstrate some of the steps in action
      • Lucas -
    • Introduces himself and asks where he can help out
      • Isaac -
    • Schema help
    • Reference implementation help (e.g. with Moloch implementation)
    • Getting the word out to DAOs that these standards are coming
      • How do you organize X, Y, Z data/rules
      • Constitution documents markdowns
    • Perhaps add to airtable Lucas brought up with data
    • ** We ought to have an ecosystem wide Telegram/Discord**
      • “DAOstar Adoption”
      Lucas -
    • Made telegram group “DAOStart”
    • DAO planet event could be useful for this
    • How is DAOstar organized?
      • Isaac -
    • Metagov is parent group
    • Metagov handles wallets
      • Lucas -
    • General Metagov collaboration opportunities/seeking
        1. Index - Sharing
        1. Voting - Advisory
        1. Data dashboard - schema
        1. Education - Consensus
      Â