Building Applications on Privacy Preserving Identities | Sushaan Shetty - Humanity Protocol

[Music] hello everybody I'm Susan deril at Humanity protocol and today I'm going to be going through how we can build privacy preserving U build applications on privacy preserving identities and how we at Humanity protocol are making this a reality just to begin with let's just kind of understand the identity crisis that exists uh not just in the web3 world but also in general I'm pretty sure all of us here are aware of the kind of uh control and the amount of centralization that exists uh in the current world uh with large organizations and governments having complete control of our personal data and IDs and with data being the new oil every single day we hear news of all kinds of data breaches and leaks sometimes it's large organizations kind of trying to monetize on our data or it's just because of the central point of failure uh of these large organizations and also in web 3 we have a huge lack of robust identity mechanisms to really filter out the uh cils that are kind of interacting with our uh chains or platforms every single day and uh to really uh solve this problem we need to figure out a way to incentivize and reward the right uh users who are real human beings and that's where we come in uh at Humanity protocol at the most basic layer we have the humanity layer uh which utilizing proof of humanity uh our goal is to begin with ensuring that the decentralized ID or the wallet address that's interacting is an actual human being and beyond that once we know that it's a real human being behind the Walt address or the did we can further associate that wal address or did with all kinds of uh verifiable credentials uh for interacting with different ecosystems and how do we really uh figure out if it's a real human being uh associated with that did or wallet address I mean we could go with multiple approaches to I mean there's the software and Hardware approach where if you want to go with the software path uh we can use AI machine learning algorithms and uh other ways like you know social uh uh reputation scores Etc but eventually uh as Ai and Technology progresses I mean even at this point uh we can see how difficult it is to really filter out cils and you know uh cils and attackers and whoever intend to U you know attack the system can figure out multiple workarounds for all these safeguards that we try to put with just software mechanisms and that's where that's why we chose to go with a a hardware approach and coming for the hardware approach Biometrics Biometrics of course is uh the best approach and for that we had to keep few goals in mind the first would be that of course it's sufficiently accurate in terms of identifying that it's a unique human being and there's no overlap with multiple human beings and also keeping in mind that it shouldn't be uh invasive in terms of the Privacy for the user themselves so that's why we chose uh Palm signatures where the the Palm signature or the pal print or the ve veins of the user is like utilized uh to scan through and generate an encryp encrypted biometric and Associate that with a specific di of the user and keep in mind that this encrypted uh biometric signature doesn't reveal any of personally identifiable information of that specific human being that's just verifying that it's a real human being that they are a real human being utilizing the did and once we know that it's a real human being of course U we can utilize the fact that it's a did that's interacting with your platform with one to one matching for you know it's a human being that's interacting or one to1 matching with by attaching multiple credentials uh so associated with that did uh for various use cases uh across the ecosystem and this also leads to this whole concept of uh self- Sovereign identities where we have these self- Sovereign dids or identities of users who are real human beings and you know they have complete control over their identity and also uh they have multiple weab credentials that are uh kind of you know independently issued by trusted parties and they can all these credentials associated with real human beings or the did can be verified independently either through decentralized nodes or uh specific applications that are verifiers and of course it's uh privacy preserving with encryption uh in mind for the signatures of the Biometrics and decentralized storage uh and cryptographic proofs uh for proving certain parts of your did or verifiable credentials and to really build on top of it and understand uh the whole concept of uh kind of like attesting and attaching weab credentials uh to your did uh we need to understand the concept of verifiable credentials itself and what are uh verifiable credentials uh at the most basic level there just certain claims related to that specific did or unique user U or just you know in this case the credential subject which is the human user that's interacting or possesses that did now these claims can be customized and this is where uh we all developers come in and you guys can get creative and come up with all kinds of use cases uh to attach different kinds of uh verifiable credentials uh to that specific did of that unique uh human being and this is uh tamper resistant cuz uh it is signed using the keys of the user and U that specific signature of that uh of the rare credentials cannot be tampered because if there's any small modification carried out the whole signature is going to change and we're going to be able to prove that it's not a valid verifiable credential and uh most importantly this ades to the uh what w3c standards which is the worldwide Web Consortium standards of verifiable credentials and dids hence it's interoperable ac across uh not just web3 ecosystems but also web2 ecosystems and of course we you got to keep in mind that we don't reveal any personally anable uh information associated with the user but rather it's just certain verifiable credentials associated with a did knowing that it's a human being and they can selectively uh choose to reveal parts of the details to whatever uh applications or entities that they trust uh for an example it could be like a driver's license weable credential associated with a user maybe they just want to reveal the age uh DET age uh parameter they can just go ahead and reveal that uh selectively or they just want to reveal their whole weareable credential that they have this license that they process this ID they can just go ahead and uh Pro it and coming to the uh wide variety of applications that can be built uh leveraging uh you know our base layer of knowing that it's a human did and of course uh using our SDK to build on top of it the the key aspect that You' have got to keep in mind is the use cases are really Broad and you can get really creative and utilize the concept of verifiable credentials uh for multiple use cases for uh to mention few like Universal uh basic income like Ubi you know that it's a human being and they might have certain verifiable credentials associated with them you can go ahead and give periodic incentives to uh a verified human being or Enterprise defi where maybe certain dii protocols uh want want to comply with certain AML or uh policies or regulations of specific countries they can just selectively know that it's a user from that country and they have these specific uh you know uh verifiable credentials uh issued by certain trusted parties or issuers uh and go ahead and let them carry out the trades and onchain games where you know or also just games in general where uh the the game developer just wants to make sure that it's real human beings that's playing their game or competing they can go ahead and utilize the dids uh provided by humanity and decentralized signs where uh verified reviewers can contribute uh to it to the uh progress knowing that is real contributors and reviewers uh and further uh really interesting use case that I'm excited about which is the network States uh where you know we have like uh self-governed States and we have these dids and just with a palm scan people can navigate through the whole NK State buy uh buy whatever they want to buy or access certain events or the possibilities are basically endless and as I'm kind of running out of time yeah I'm just going to quickly Breeze through the uh the use cases where we have Dows where we know that we can give certain amount of weightage for specific uh human beings knowing that you know to prevent kind of like Dow attacks just to uh token holders of or multiple few entities having a large control we can just know that they are real human beings voting and there's a majority kind of like populous kind of uh approval for specific uh uh proposals and then there's RW for linking specific weable credentials assed with real world assets and of course the education certificates uh issued by authorities I mean universities or employment proof Etc can all be attached to the did of that human being uh as bare Fab credentials now in terms of uh what we can at this point uh how developers can build on top of our SDK or API so at the moment we're on testnet and we have rolled out few basic uh very simple apis to leverage the concept of verifiable credentials and issue uh verify revoke using the w3c standards uh so as I as I mentioned the use cases it can be broad uh you can just consider one of the multiple use cases or just get creative and think of some cool onchain use cases uh so in terms of the bounties we have got two tracks uh the first one would be focused on mobile apps with really good ux and uh you know easy onboarding for the users with their dids on uh testnet and uh think of some cool use cases that where you know they can just show that they own this specific rare credential on their mobile application or the other track if you want to just build like a web app and utilize our apis you can just go ahead and again get creative and build some cool use case uh where you utilize the Weare fiable credentials and the users uh can you know uh do whatever you want to do based on whatever kind of dap you're building and coming to the judging criteria yeah these are like the key criterias but to summarize the functionality in terms of it's got to make sense and it's got to be functional it's got to work end to endend not just a Half Bake project and it's got to be a novel use case and we are really interested in defi use cases uh cuz we believe that human dids uh along with veriable credentials can unlock a lot of D5 possibilities and uh of course the best practices for technical implementation and ux uh in terms of ux I think you you got to make sure that it's like super easy for the users to get onboarded onto your application so let me just quickly walk through the apis that we have got so sure yeah so this uh we've got a so uh if you go to our docs at docs. my.org uh you can look at the key apis and also a few other details but these four apis are going to be crucial uh for you know uh let me just show the issue part where it's very simple we are abstracting a lot of things for you all so the key goal for you is to get creative with creative with the digital claims part for the rare credential where you can uh customize this with whatever custom claim and uh the subject of the uh address out here is going to be uh the user um sorry I think yeah it's going to look like this and this is going to be the address on so make sure that whatever address you're trying to verify is signed uh sign has signed up on uh tet. humanity. .

org and it's just got to be the Walt address in this case of the uh user or the ID that you're trying to verify uh attach the credential to and you can just go ahead and and yeah this is where you get creative and you can add any kind of Uh custom claim associated with your use case and assign or issue the uh credential for that user yeah once it goes through and gets issued uh you're going to see the credential itself and a message saying that it's been issued successfully uh so we have like a bunch of details out here but I would like to focus here on the ID so the ID of the public credential is pretty crucial and uh also here the claims come uh you know the claims that you attach to that so remember that this is one specific veriable credential associated with the did and the claims that you have associated with that are going to come uh you know are going to show up out here under this section uh so post that you can just go ahead uh copy this uh credential uh as such uh you can just copy this credential and uh you know go to verify credential section and this is the body of it where just provide the credential and uh once you send that it's going to show that if it's legit or not this is for the verification part uh to know that if it's a legitimate uh uh credential now so this is an example of if it's not legitimate because I just revoked it and for that there's a revoke end point where for some reason if you want to revoke it you can just go ahead and revoke it after a certain point by providing the credential ID and then uh the list credentials where uh so here uh you got to keep in mind that you the holder did uh parameter is optional you can either choose to provide that and limited with specific dids you know the credentials you have uh issued for that specific user or you can just get rid of it and get all the uh did sorry all the rare credentials you have generated for your application with that specific API key uh all right so yeah so let me quickly yeah so uh these are our dogs and if you've got any dos you can hop hop onto our Discord server or our telegram uh and we'll be around here you can just uh approach us and we'll we love to help you with any doubts or if you want to just brainstorm your idea uh so uh also uh please do scan this OR fill this form uh this uh this is going to lead to the form and we're going to reach out to you with the API key for your application and yeah that's pretty much it uh really excited and looking forward to all the interesting new cases that you all are planning to build on top of humanity protocol thanks you so much