📓

Specification

Participants
  • DAOs emitting daoURI
    • DAOstar Voyager Identity
    • DAOstar Strike Team
    • DAOstar One
    • Metagov with metagov.eth (Gnosis Safe), and 0x123afj (Metamask account)
  • Issuers
    • Disco, emitting membership attestations
    • Govrn, emitting contribution attestations
    • Dework (?), emitting membership attestations
  • Attestation consumer
    • Avenue, consuming from Disco and Govrn
  • Persons
    • Josh with thelastjosh.eth and blahjoshblah.eth [this is going to be an arbitrary address]
    • Fernando
v0.1 - minimal complete flow
  • As a member of DAOstar One, Voyager Identity, Strike Team, I can...
    • see my membership on Disco.
    • see a list of my contributions on Govrn.
    • see a list of my contributions on Dework.
  • DAOstar One, Voyager Identity, and Strike Team each...
    • emit a daoURI endpoint
    • emit a minimal membersURI, with only Ethereum addresses and ENS addresses
    • publish some information on Josh
    • DAOstar One and Strike Team publish member information on thelastjosh.eth
    • Voyager Identity publishes separate, non-contradictory member information blahjoshblah.eth
  • Disco, Govrn, and Dework each...
    • consuming information from daoURI for all the three DAOs above
    • maintain an attestation endpoint that returns a JSON blob following the Issuer JSON Schema standard
  • Avenue consumes each of the attestation endpoints by Disco, Govrn, and Dework
  • At this point, Josh has not yet created an account on Disco, Govrn, Dework, or Avenue
v0.2 - Josh creates an account on Disco and Govrn, Avenue consumes Disco’s identity merge attestation
  • Josh has created an account on Disco, Govrn, Dework, AND Avenue
    • Josh has linked thelastjosh.eth and blahjoshblah.eth on Disco
  • Avenue consumes Disco’s attestation, and links thelastjosh.eth and blahjoshblah.eth
  • Avenue consumes Govrn’s attestations, and uses it to populate BOTH thelastjosheth and blahjoshblah.eth
v0.3 - Govrn consumes Disco’s identity merge attestation INTERNALLY
  • Govrn consumes Disco’s attestation, and links thelastjosh.eth and blahjoshblah.eth INTERNALLY
  • Govrn does NOT publish contribution data with linked profiles
  • Govrn does NOT allow “transfer” of contributions across profiles (? this seems bad, we should allow transfer across contributions)
v0.4 - attestations as NFTs?
  • Govrn wants to publish all contribution attestations as NFTs
 
CUT
  • Going to service providers: their Ethereum address, Discord servers, and other third-party integrations / identities (via OAuth, social post / verification flow, and just self-attestation)
    • Note that the third-party integrations are NOT going to be shared? Or is exposing a third-party integration a “public” act?
  • To service providers: what information would you be willing to share / expose to other service providers? What information would you want to consume?
    • Closer: we want to consume any and all information being published by anyone! “Am I a good fit for this DAO?” +1 Govrn. Pull in any information on contributions or tasks done, actions taken.
    • Dework: we currently have public endpoints where you can put in an org ID and get a list of completed tasks + related wallet addresses assigned to those tasks (but only for public projects)
    • Govrn: we’re able to provide a list of contributions, the associated social attestations to that contribution. The only thing to consider is privacy, right now it’s up to the contributor on what types of contributions they choose to expose. That said in our model, if they plan on having it be recognized by a DAO, the contribution record becomes public even if the associated metadata about the contribution remains private.
    • Next step: get access to Dework’s endpoint or just get a quick sample JSON blob from that endpoint.
DAOstar Voyager:
requirement: owning a $VOYAGER token
issuerURI: $VOYAGER contract
Strike Team:
requirement: having earned $USDC from working in a client project
issuerURI: internal tool that checks if the user meets the requirement
 
DAOStar One:
requirement: having a claim issued by the DAO
issuerURI: - ? service that validates the claim?
To consider: cases like PolygonDAO with claims not bound to any address - since the verification is done by checking the claim itself, is there a need for a issuerURI?
APIs for the issuers
Revocation?
📓

Specification

Participants
  • DAOs emitting daoURI
    • DAOstar Voyager Identity
    • DAOstar Strike Team
    • DAOstar One
    • Metagov with metagov.eth (Gnosis Safe), and 0x123afj (Metamask account)
  • Issuers
    • Disco, emitting membership attestations
    • Govrn, emitting contribution attestations
    • Dework (?), emitting membership attestations
  • Attestation consumer
    • Avenue, consuming from Disco and Govrn
  • Persons
    • Josh with thelastjosh.eth and blahjoshblah.eth [this is going to be an arbitrary address]
    • Fernando
v0.1 - minimal complete flow
  • As a member of DAOstar One, Voyager Identity, Strike Team, I can...
    • see my membership on Disco.
    • see a list of my contributions on Govrn.
    • see a list of my contributions on Dework.
  • DAOstar One, Voyager Identity, and Strike Team each...
    • emit a daoURI endpoint
    • emit a minimal membersURI, with only Ethereum addresses and ENS addresses
    • publish some information on Josh
    • DAOstar One and Strike Team publish member information on thelastjosh.eth
    • Voyager Identity publishes separate, non-contradictory member information blahjoshblah.eth
  • Disco, Govrn, and Dework each...
    • consuming information from daoURI for all the three DAOs above
    • maintain an attestation endpoint that returns a JSON blob following the Issuer JSON Schema standard
  • Avenue consumes each of the attestation endpoints by Disco, Govrn, and Dework
  • At this point, Josh has not yet created an account on Disco, Govrn, Dework, or Avenue
v0.2 - Josh creates an account on Disco and Govrn, Avenue consumes Disco’s identity merge attestation
  • Josh has created an account on Disco, Govrn, Dework, AND Avenue
    • Josh has linked thelastjosh.eth and blahjoshblah.eth on Disco
  • Avenue consumes Disco’s attestation, and links thelastjosh.eth and blahjoshblah.eth
  • Avenue consumes Govrn’s attestations, and uses it to populate BOTH thelastjosheth and blahjoshblah.eth
v0.3 - Govrn consumes Disco’s identity merge attestation INTERNALLY
  • Govrn consumes Disco’s attestation, and links thelastjosh.eth and blahjoshblah.eth INTERNALLY
  • Govrn does NOT publish contribution data with linked profiles
  • Govrn does NOT allow “transfer” of contributions across profiles (? this seems bad, we should allow transfer across contributions)
v0.4 - attestations as NFTs?
  • Govrn wants to publish all contribution attestations as NFTs
 
CUT
  • Going to service providers: their Ethereum address, Discord servers, and other third-party integrations / identities (via OAuth, social post / verification flow, and just self-attestation)
    • Note that the third-party integrations are NOT going to be shared? Or is exposing a third-party integration a “public” act?
  • To service providers: what information would you be willing to share / expose to other service providers? What information would you want to consume?
    • Closer: we want to consume any and all information being published by anyone! “Am I a good fit for this DAO?” +1 Govrn. Pull in any information on contributions or tasks done, actions taken.
    • Dework: we currently have public endpoints where you can put in an org ID and get a list of completed tasks + related wallet addresses assigned to those tasks (but only for public projects)
    • Govrn: we’re able to provide a list of contributions, the associated social attestations to that contribution. The only thing to consider is privacy, right now it’s up to the contributor on what types of contributions they choose to expose. That said in our model, if they plan on having it be recognized by a DAO, the contribution record becomes public even if the associated metadata about the contribution remains private.
    • Next step: get access to Dework’s endpoint or just get a quick sample JSON blob from that endpoint.
DAOstar Voyager:
requirement: owning a $VOYAGER token
issuerURI: $VOYAGER contract
Strike Team:
requirement: having earned $USDC from working in a client project
issuerURI: internal tool that checks if the user meets the requirement
 
DAOStar One:
requirement: having a claim issued by the DAO
issuerURI: - ? service that validates the claim?
To consider: cases like PolygonDAO with claims not bound to any address - since the verification is done by checking the claim itself, is there a need for a issuerURI?
APIs for the issuers
Revocation?