Strike Team #29 / Community Call #9
Last Edited Time
Jun 17, 2022
Created time
Jun 16, 2022
Participants
Created By
Type
Created
Jun 16, 2022
Zoom Recording
Property
Property 1
Attendees:
Hugo Masclet
Jordi
Luke Miller
Marcus
Cent
James Brennan
Keating
Quadri Oguntade
Joshua Tan
Ido Gershtein
Azfar A
Isaac P
Zargham
Minutes
Marcus - Guatemala: Background in creative production industries. Contributor citydao. Organizer for eth barcalona. Motivated by decentralized societies. In particular in Barcalona.
Hugo - Berlin. LUKSO. Work with Fabian NFT identity systems. Working on npm packages. Found via research. Happy to contribute in terms of packaging and tooling. Service that generates API, or packages. Connecting with Isaac, and connecting with VI TG.
Jordi - Tech lead at Aaragon. Interested to come. Some thoughts to ask for feedback about.
Updates
Issac: Live data for DAO*1 data. In another call about how to decentralize storage instead of hosting on AWS.
Z: More general scripting of rule that defines membership is made hard through the lamda, but lamda is flexible. Not content addressing the JSON-LD file, but the policy itself.
Jordi: This is not just about WASM. Imagine you could compile a CLI into web assymbeling that will give full access. Imagine compiling mysecure to WASM. CAn then put these at the edge.
Z: By content addressing things that already exist you are creating a reproducible environment and pure function. Emphasis is on taking things that already exist in web2 and making them executable in a web3 way. Anyone that has the content address can provably pr
Josh: Reference implementations are not meant to be standards that other's have to adapt.
Isaac: Demo of the getMembers code.
Have a first reference implementation live and running. Can start running experiements.
Josh: Next step for Voyager Identity is to build a test case of this. Comsuming and integrating attestations from example DAOs.
Keating: The tech lead at Govrn. Have been working on the engineering side.
Josh: The final paper for the attestation framework is aiming to be done by before NY.
Luke: Have a prototype to share. Working on service for DAOs to connecte to the DAOstar endpoint.
Can fillout a form to geenrate a DAO schema. In the background is an IPFS node connected to the Piñata API where it is pinned.
The API is a simple implementation for allowing DAOs to generate -- Luke is working on an interface that allows you to spin up and manage a hosted DAO* API. Should be quick and functional. A front-end version that plugs into the implementation that Isaac is building. If a platform like DAOHaus uses this, they would automatically spin up an API manager.
Mutable Schemas:
josh: This is in the context of DAO URI. This is like a RUI spliter that names all the api endpoints that a dao would want to ppublish. We don't epect this to change very often. It they want to change it they should go on-chain to the contact manager and change it there. My sense is that this is not the right approach. DAO URI names all the data that a DAO is publishing. UseCase: Every time we create a standard, like the Voyager Identity standard, they might want to adopt this toold. A more sustainable model, rather than going through on-chain proposal, when you put in a link to the API manager, that should be a signal that
Ido: Maybe a middle ground could be: It is hard is you have to on-chain update the DAO URI. Having EOA admins can make changes.
Luke: We could support both mutable and immutable versions of the api.
Jordi: discussion on eth magine forum. Facing similar problems four years ago. Issue was having data not related to daos but decentralized decision making. Needed to be static content, but also needed to have some centralized end point for censorship. Used extension of url schema, by having multiple endpoints separated by comma in url. Can pivot between different centralized and decentralized.
Link: https://docs.vocdoni.io/architecture/protocol/data-origins.html#content-uri
Link: https://ethereum-magicians.org/t/erc-4824-decentralized-autonomous-organizations/8362/29#standardised-multi-endpoint-urls-1
This is a transparent schema that could be potentially standardizes.
Josh: Use case is similar to what we are facing too.
Josh: Start moving some more of this conversation to ethereum magicians to make work more public and get more engagement with core developers.
Ido: It might be interesting now that we have reference implementtation we should think about interesting showcases. One idea: Have a side .eth. Could have : ens name or dao address like daostar. -- would go to daostart api and fetch information and an automatic dao site.
Josh: ENS -> DAO address -> webpage / endpoints -> display
Josh: Could mock up what this looks like in etherscan.
James: Have a writeup with some highlights from roundtable.
Josh: Will be sending out more grants (also EU horizons project working on ontologies)
Targeting 200k goal.
Josh: Will be participating in DAO NYC.
Adoption
Josh: Have been talking with DAO data publishers and DAO needs. Hope to discuss during a Roundtable.