DAOstar One (Internal)
DAOstar One (Internal)
/
🚀
Voyager Identity #5
/
Meeting Primer

Meeting Primer

Recap
Attestation framework
Previous framework on data sources from Voyager #3:
  • data from self
  • data from DAO
  • data from DAO peers
  • data from services
    • oracles? collab.land
Content framework
Previous framework on data content from Voyager #4:
  1. Group Membership: “I am a part of this group”
  1. Proof of Action: “I did this thing”
  1. Metrics: “I did/have/own X things”
 
🔑
From here, we found alignment on focusing on one type of content: the top-level membership in an organization.
Attestation Investigation
Via Lucidchart, we attempted to model how to create Attestations that a particular user (identified by Ethereum address) is a member within an organization. The diagrams involve 3 key stakeholders: DAOs, members, and issuers of these attestations.
 
🔑
From here, we recognized that our efforts were going down into architecture patterns explicitly adopting DIDs/VCs. Although we have general agreement that this infrastructure will be useful for this class of problems, designing a standard around infrastructure none of us have taken to production is unlikely to be adopted in the near or midterm. Our goal is to make a standard that will be adopted, so we should focus on enabling current platforms to easily conform to our proposal.
 
In Voyager #5, we should:
  1. Design the basic schema, focusing on ways of extending EIP-4824.
  1. Spec out a basic experiment where we (platforms implementing some form of web3 profile or cv) share interfaces and reach each other’s top-level membership data.
    1. In doing so, make progress on answering the question that Conner posed in Voyager #3: If we have the basis of defining organization membership, how can we guide ourselves to reuse each others data? How can we work towards a world where I define I contributed to DAOStar in platform X and it automatically shows when I go to platform Y? How do different infrastructure choices impact this ability to import each others’ data?
 
🔑
With this tighter scope alignment, we are now working on an initial proposal draft here:
🚀
Attestations for DAOs [DEPRECATED]
 
 
DAOstar One (Internal)
DAOstar One (Internal)
/
🚀
Voyager Identity #5
/
Meeting Primer

Meeting Primer

Recap
Attestation framework
Previous framework on data sources from Voyager #3:
  • data from self
  • data from DAO
  • data from DAO peers
  • data from services
    • oracles? collab.land
Content framework
Previous framework on data content from Voyager #4:
  1. Group Membership: “I am a part of this group”
  1. Proof of Action: “I did this thing”
  1. Metrics: “I did/have/own X things”
 
🔑
From here, we found alignment on focusing on one type of content: the top-level membership in an organization.
Attestation Investigation
Via Lucidchart, we attempted to model how to create Attestations that a particular user (identified by Ethereum address) is a member within an organization. The diagrams involve 3 key stakeholders: DAOs, members, and issuers of these attestations.
 
🔑
From here, we recognized that our efforts were going down into architecture patterns explicitly adopting DIDs/VCs. Although we have general agreement that this infrastructure will be useful for this class of problems, designing a standard around infrastructure none of us have taken to production is unlikely to be adopted in the near or midterm. Our goal is to make a standard that will be adopted, so we should focus on enabling current platforms to easily conform to our proposal.
 
In Voyager #5, we should:
  1. Design the basic schema, focusing on ways of extending EIP-4824.
  1. Spec out a basic experiment where we (platforms implementing some form of web3 profile or cv) share interfaces and reach each other’s top-level membership data.
    1. In doing so, make progress on answering the question that Conner posed in Voyager #3: If we have the basis of defining organization membership, how can we guide ourselves to reuse each others data? How can we work towards a world where I define I contributed to DAOStar in platform X and it automatically shows when I go to platform Y? How do different infrastructure choices impact this ability to import each others’ data?
 
🔑
With this tighter scope alignment, we are now working on an initial proposal draft here:
🚀
Attestations for DAOs [DEPRECATED]
 
Â