...on-chain proofing without disclosing any personally identifying information...
...using soulbound nfts...
...may use zk proofs...
Nelson
...should we focus on on or off chain?...
Balaz
...make a decision based off alignment of work interests...
David
...on chain data is the credential...
...the softer broader information is offchain...
...how we are working on this at Lit Protocol:
...we are using credentials to provide encryption and decryption mechanisms...
Stepan
...aggregating reputation system to enable clear contribution credentialing...
...identity is a set of attributes around a core attribute
...that could be a list of on or offchain contributions you have made...
...one metric for valuing identity system is how much time or money it saves for the validators...
...standards should be targeted to this metric...
...the supply of data is primary...
...standards emerge naturally when we are able to create an abundance of data supply...
...as an idea: potentially we could start with not just a standard spec, but we could create a way of standardizing how people submit information rather than working on a spec...
...as a proposal: one common problem is DAOs have unique HR problems. Their problem is not recruiting people, but filtering people. there is no scalable way of verifying experience/reputation...
...reputation is the end goal (possibly vibe scores), but before we get there it would be individual credentials and attestations since they are more discrete data point...
Josh
...a lot of us are producing reputation...
...saying that reputation is the use case is not as informative...
...likes the idea of filtering...
Stepan
...one thing the protocol does is aggregate data from different applications like coordinape etc. ..
...when you use any DAO tooling, there is data produced...
...this data can be used by the DAO...
...the biggest value of the standard is making sure that whatever data is produced by DAOs and DAO tooling is ready to be used and enforced, and compounded by everybody else...
Andros
...Wonderverse is interested in Identity less in one reputation score, but more interested in how we publish work on a chain in a way that people agree upon, and being able to filter by trust based on work done...
...coming from a project management system background and having people able to make resumes based on what happens onchain...
...how do you show that something published on chain is verified by a DAO...
...possibly connected to a DAO URI?...
...what is the structure of the data, and what is inside the piece of data?...
Josh
...is it fair to say that since wonderverse is more focused on PM, they are expecting this standard rather than delivering it?...
Andros
...we would rather work from an agreed upon standard than making their own using something like Ceramic...
Nelson
...we will be both generating the data (platform for daos to rival discord), but will also be interpreting data from multiple sources...
...we’ll probably need to use one or multiple of their solutsions to interpret external data...
...we want to make sure the data we are creating is legible and portable to the ecosystem...
...on both side of using and implementing data structures...
...people will have profiles on Closer linked to individual users...
...all individuals will be pseudonymous...
...”consideration” will become more complex...
...interested in how to reveal different parts of your identity in different contexts...
Gregory (Spruce)
...the work we have done: we have found identity to be a very wide problem...
...many different interpretations of ID...
...focused on credential sides (CELO)...
...focused on different things in different contexts...
...more focus on identification and authentication side...
...dumbest form of identity: how do you use an identifier that you use to authenticate with a server?...
...with additional context: you get more complexity...
...at the core are identifiers...
...working on data vaults, and are less opinionated about reputation or more complex forms of identity...
...very focused on primitives side...
Stepan
...there are many different focuses in this area...
...people who create end-user applications don’t need to work on standards...
...we still need to build systems for managing data structures and schemas...
...if you want to build a profile for dao contributors, you still need to go down the stack and build this up from scratch...
...it is valuable to go through this process, but there is also a lot of redundancy in this work happening today...
Josh
...there is redundancy , but this is also important to go through this process?...
Stepna
...it is important because we need to go through this process to make things work, but everyone is building for themselves...
...not built for others, built for speed, and not good documentation for easy development entry...
...right now you either build the full stack or it doesn’t work in the identity space...
Reviewing the Table
Josh
...some type of schema would be helpful...
...this might be the easiest thing we could produce...
...what exactly is that and what needs to go into that without over formalizing...
Stepan
...sharing schema manager for verifiable credentials...
...a visual tool might help...
..showing Affinidi...
...mostly for offchain se cases
...allows reusability across industry for data models...
Partial example
...this can be forked and you are able to add additional data types...
...not specific to identity storage system...
...public exploration...
...way of getting convergence around common schemas...
...basic functionality of creating JSON schemas...
...important to do research with DAOs to better understand what data (not in terms of data structure but valuable data) DAOs are prioritizing...
Josh
...while thinking about what data to standardize in these schemas, we should think less about what we need, but what DAOs need...
...this group is oriented towards serving DAOs...
Nelson
...have done some user research interviews around this...
...within the DAO already: trust needed between people in the DAO, and needing to know if they are in the DAO, or how long they have been in the DAO, etc. ...
...dao2dao needs: i.e. applying to certain bounties...
...also important to know where else they have been in other DAOs...
...this is the web3 CV coming to bare...
...also where the pseudonymous element comes in...
...you don’t want to have someone ask themselves to dox themselves to show where they have been...
Stepan
...also: a lot of people, this will be their first time in DAOs...
...in terms of L1: they want to focus on getting people onboarded to DAOs who have never been on them...
...linkedin is not highly valued...
Nelson
...not asking for linkedIn information...
Josh
...two different needs: onboarding for first time vs having an on-chain record...
Stepan
...corelation attack reduction yet still getting verifiable data from platforms: working with_____...
...algorithms for building reputation scores from github, using both public and private repos...
...issuing an nft that doesn’t reveal any proprietary code, but does reveal metrics of engineering skills...
...same use cases for twitter where you don’t need to know the account, but have access to the graph’s implications...
...these systems are developed, attacked, improved, and evolve over time...
Andros
....difficult to determine how effect a contributor will be...
...onboarding tasks specific to a DAO which is sort of like the training process...
...with DAOs, the permissionless way of onboarding people is important...
...though this is tangential to the need to show previous work you have done...
Nelson
...the onboarding tasks are still necessary to determine if they will be effective...
...also happening at the moment because there is a lack of clarification of quality for this type of verification work...
...not needing to go through the whole building up process every time they want to submit to a DAO or protocol...
...want to get to a state where people can skip these training steps because they have already proven themselves...
Stepna
...useful way of thinking about this from an economic perspective...
...different ways of going through this process...
...mentorship as an alternative to the training process, yet still feeding into history of credentials...
Zoom chat
11:04:00 From Joshua Tan to Everyone:
https://daostar.notion.site/How-does-identity-work-within-DAOs-3842497b4eaa45668fb99c308d86c552
11:08:23 From Balazs to Everyone:
Standard of standards!! Always the best idea
11:09:49 From Joshua Tan to Everyone:
https://daostar.notion.site/How-does-identity-work-within-DAOs-3842497b4eaa45668fb99c308d86c552
11:15:03 From Joshua Tan to Everyone:
Live notes being taken here, 🙏 thanks Cent! https://www.notion.so/daostar/Voyager-Identity-2-0557ae8f371b498685900c7399d63326
11:18:19 From Balazs to Everyone:
Lit looks really lit!
11:18:36 From Balazs to Everyone:
What’s your storage mechanism to manage the auth flows coming from decrypted keys?
11:18:39 From David Sneider to Everyone:
Thx @balazs! Docs are here: https://developer.litprotocol.com/docs/intro
11:18:56 From David Sneider to Everyone:
“What’s your storage mechanism to manage the auth flows coming from decrypted keys?”
11:19:43 From David Sneider to Everyone:
“What’s your storage mechanism to manage the auth flows coming from decrypted keys?” - in terms of where the data is stored? Lit doesn’t have an take on this. In terms of where the key to the data is stored? It’s encrypted with the network key and hashed and stored to a statemachine
11:20:22 From Balazs to Everyone:
Ty!
11:25:11 From Joshua Tan to Everyone:
Can we start a DAO here where voting power is based on our respective Tinder "scores
11:27:36 From David Sneider to Everyone:
Got to run - looking fwd to tuning into the recording + notes! Thx all 🙂
11:30:07 From Balazs to Everyone:
“Publish on chain” is a question that we might need to find clarity.
11:30:12 From Gregory Rocco to Everyone:
+1
11:35:05 From Andros Wong to Everyone:
https://daostar.one/EIP If you look at the Proposals section this is the kind of data structure we’d love to agree on, but for work completed.
11:38:52 From Balazs to Everyone:
Yes, agree
11:54:43 From Cent to Everyone:
what other information is actively not being collected or not positively valorized in web3?
11:54:59 From Stepan Gershuni to Everyone:
Good question!
11:55:05 From Stepan Gershuni to Everyone:
P2p attestations
11:55:15 From Stepan Gershuni to Everyone:
Offchain data from web2 platforms
11:59:43 From Gregory Rocco to Everyone:
Sorry y’all have to run! Enjoy your weekends!!!!
11:59:58 From Balazs to Everyone:
I will have to hard drop. Was a super session!
12:02:27 From Andros Wong to Everyone:
I also have to drop! Thanks for the great session :)
12:02:37 From Joshua Tan to Everyone:
Thanks Andros!
12:02:48 From Conor O'Meara (he/him) to Everyone:
Super great to meet you all, and hear the discussion. Look forward to keeping track on the Notion and speaking to you all very soon! Appreciate it!
...on-chain proofing without disclosing any personally identifying information...
...using soulbound nfts...
...may use zk proofs...
Nelson
...should we focus on on or off chain?...
Balaz
...make a decision based off alignment of work interests...
David
...on chain data is the credential...
...the softer broader information is offchain...
...how we are working on this at Lit Protocol:
...we are using credentials to provide encryption and decryption mechanisms...
Stepan
...aggregating reputation system to enable clear contribution credentialing...
...identity is a set of attributes around a core attribute
...that could be a list of on or offchain contributions you have made...
...one metric for valuing identity system is how much time or money it saves for the validators...
...standards should be targeted to this metric...
...the supply of data is primary...
...standards emerge naturally when we are able to create an abundance of data supply...
...as an idea: potentially we could start with not just a standard spec, but we could create a way of standardizing how people submit information rather than working on a spec...
...as a proposal: one common problem is DAOs have unique HR problems. Their problem is not recruiting people, but filtering people. there is no scalable way of verifying experience/reputation...
...reputation is the end goal (possibly vibe scores), but before we get there it would be individual credentials and attestations since they are more discrete data point...
Josh
...a lot of us are producing reputation...
...saying that reputation is the use case is not as informative...
...likes the idea of filtering...
Stepan
...one thing the protocol does is aggregate data from different applications like coordinape etc. ..
...when you use any DAO tooling, there is data produced...
...this data can be used by the DAO...
...the biggest value of the standard is making sure that whatever data is produced by DAOs and DAO tooling is ready to be used and enforced, and compounded by everybody else...
Andros
...Wonderverse is interested in Identity less in one reputation score, but more interested in how we publish work on a chain in a way that people agree upon, and being able to filter by trust based on work done...
...coming from a project management system background and having people able to make resumes based on what happens onchain...
...how do you show that something published on chain is verified by a DAO...
...possibly connected to a DAO URI?...
...what is the structure of the data, and what is inside the piece of data?...
Josh
...is it fair to say that since wonderverse is more focused on PM, they are expecting this standard rather than delivering it?...
Andros
...we would rather work from an agreed upon standard than making their own using something like Ceramic...
Nelson
...we will be both generating the data (platform for daos to rival discord), but will also be interpreting data from multiple sources...
...we’ll probably need to use one or multiple of their solutsions to interpret external data...
...we want to make sure the data we are creating is legible and portable to the ecosystem...
...on both side of using and implementing data structures...
...people will have profiles on Closer linked to individual users...
...all individuals will be pseudonymous...
...”consideration” will become more complex...
...interested in how to reveal different parts of your identity in different contexts...
Gregory (Spruce)
...the work we have done: we have found identity to be a very wide problem...
...many different interpretations of ID...
...focused on credential sides (CELO)...
...focused on different things in different contexts...
...more focus on identification and authentication side...
...dumbest form of identity: how do you use an identifier that you use to authenticate with a server?...
...with additional context: you get more complexity...
...at the core are identifiers...
...working on data vaults, and are less opinionated about reputation or more complex forms of identity...
...very focused on primitives side...
Stepan
...there are many different focuses in this area...
...people who create end-user applications don’t need to work on standards...
...we still need to build systems for managing data structures and schemas...
...if you want to build a profile for dao contributors, you still need to go down the stack and build this up from scratch...
...it is valuable to go through this process, but there is also a lot of redundancy in this work happening today...
Josh
...there is redundancy , but this is also important to go through this process?...
Stepna
...it is important because we need to go through this process to make things work, but everyone is building for themselves...
...not built for others, built for speed, and not good documentation for easy development entry...
...right now you either build the full stack or it doesn’t work in the identity space...
Reviewing the Table
Josh
...some type of schema would be helpful...
...this might be the easiest thing we could produce...
...what exactly is that and what needs to go into that without over formalizing...
Stepan
...sharing schema manager for verifiable credentials...
...a visual tool might help...
..showing Affinidi...
...mostly for offchain se cases
...allows reusability across industry for data models...
Partial example
...this can be forked and you are able to add additional data types...
...not specific to identity storage system...
...public exploration...
...way of getting convergence around common schemas...
...basic functionality of creating JSON schemas...
...important to do research with DAOs to better understand what data (not in terms of data structure but valuable data) DAOs are prioritizing...
Josh
...while thinking about what data to standardize in these schemas, we should think less about what we need, but what DAOs need...
...this group is oriented towards serving DAOs...
Nelson
...have done some user research interviews around this...
...within the DAO already: trust needed between people in the DAO, and needing to know if they are in the DAO, or how long they have been in the DAO, etc. ...
...dao2dao needs: i.e. applying to certain bounties...
...also important to know where else they have been in other DAOs...
...this is the web3 CV coming to bare...
...also where the pseudonymous element comes in...
...you don’t want to have someone ask themselves to dox themselves to show where they have been...
Stepan
...also: a lot of people, this will be their first time in DAOs...
...in terms of L1: they want to focus on getting people onboarded to DAOs who have never been on them...
...linkedin is not highly valued...
Nelson
...not asking for linkedIn information...
Josh
...two different needs: onboarding for first time vs having an on-chain record...
Stepan
...corelation attack reduction yet still getting verifiable data from platforms: working with_____...
...algorithms for building reputation scores from github, using both public and private repos...
...issuing an nft that doesn’t reveal any proprietary code, but does reveal metrics of engineering skills...
...same use cases for twitter where you don’t need to know the account, but have access to the graph’s implications...
...these systems are developed, attacked, improved, and evolve over time...
Andros
....difficult to determine how effect a contributor will be...
...onboarding tasks specific to a DAO which is sort of like the training process...
...with DAOs, the permissionless way of onboarding people is important...
...though this is tangential to the need to show previous work you have done...
Nelson
...the onboarding tasks are still necessary to determine if they will be effective...
...also happening at the moment because there is a lack of clarification of quality for this type of verification work...
...not needing to go through the whole building up process every time they want to submit to a DAO or protocol...
...want to get to a state where people can skip these training steps because they have already proven themselves...
Stepna
...useful way of thinking about this from an economic perspective...
...different ways of going through this process...
...mentorship as an alternative to the training process, yet still feeding into history of credentials...
Zoom chat
11:04:00 From Joshua Tan to Everyone:
https://daostar.notion.site/How-does-identity-work-within-DAOs-3842497b4eaa45668fb99c308d86c552
11:08:23 From Balazs to Everyone:
Standard of standards!! Always the best idea
11:09:49 From Joshua Tan to Everyone:
https://daostar.notion.site/How-does-identity-work-within-DAOs-3842497b4eaa45668fb99c308d86c552
11:15:03 From Joshua Tan to Everyone:
Live notes being taken here, 🙏 thanks Cent! https://www.notion.so/daostar/Voyager-Identity-2-0557ae8f371b498685900c7399d63326
11:18:19 From Balazs to Everyone:
Lit looks really lit!
11:18:36 From Balazs to Everyone:
What’s your storage mechanism to manage the auth flows coming from decrypted keys?
11:18:39 From David Sneider to Everyone:
Thx @balazs! Docs are here: https://developer.litprotocol.com/docs/intro
11:18:56 From David Sneider to Everyone:
“What’s your storage mechanism to manage the auth flows coming from decrypted keys?”
11:19:43 From David Sneider to Everyone:
“What’s your storage mechanism to manage the auth flows coming from decrypted keys?” - in terms of where the data is stored? Lit doesn’t have an take on this. In terms of where the key to the data is stored? It’s encrypted with the network key and hashed and stored to a statemachine
11:20:22 From Balazs to Everyone:
Ty!
11:25:11 From Joshua Tan to Everyone:
Can we start a DAO here where voting power is based on our respective Tinder "scores
11:27:36 From David Sneider to Everyone:
Got to run - looking fwd to tuning into the recording + notes! Thx all 🙂
11:30:07 From Balazs to Everyone:
“Publish on chain” is a question that we might need to find clarity.
11:30:12 From Gregory Rocco to Everyone:
+1
11:35:05 From Andros Wong to Everyone:
https://daostar.one/EIP If you look at the Proposals section this is the kind of data structure we’d love to agree on, but for work completed.
11:38:52 From Balazs to Everyone:
Yes, agree
11:54:43 From Cent to Everyone:
what other information is actively not being collected or not positively valorized in web3?
11:54:59 From Stepan Gershuni to Everyone:
Good question!
11:55:05 From Stepan Gershuni to Everyone:
P2p attestations
11:55:15 From Stepan Gershuni to Everyone:
Offchain data from web2 platforms
11:59:43 From Gregory Rocco to Everyone:
Sorry y’all have to run! Enjoy your weekends!!!!
11:59:58 From Balazs to Everyone:
I will have to hard drop. Was a super session!
12:02:27 From Andros Wong to Everyone:
I also have to drop! Thanks for the great session :)
12:02:37 From Joshua Tan to Everyone:
Thanks Andros!
12:02:48 From Conor O'Meara (he/him) to Everyone:
Super great to meet you all, and hear the discussion. Look forward to keeping track on the Notion and speaking to you all very soon! Appreciate it!
