 Thank you for the introduction where was it introduction sorry for the talk before because it was really great Introduction for my talk. I want to build on top of that So I'm Friedka Möfke, I'm the maintainer of the Android SDK of block stack and I want to talk a bit how you can use decentralized identity in a way That's well, I'm really excited about It's kind of new technology decentralized and everything society might not be ready. And if there's blockchain involved This is not financial advice. So just disclaimer I'm Android developer for many years and the concept that really excites me is the Android content providers the idea is that many apps can access the same data This happens on Android device Through this type component is content provider and it's backed by Files or also maybe by the cloud But really the interesting idea is that your contacts your images your calendar Sits at one place and many Applications can make use of them. You do not have to type them again and again again And now the question is how can we get this to the web? And This is possible because we have now Identities that are decentralized identities that you can use to make to well to associate your data with So we heard decentralized identity we have a w3 working group It is self-soverened other people can verify it. We had a demo really here five minutes ago great So it's really about cryptographic keys once we have a cryptographic key then we can make work with the with the data and There we have this Authenticator that owns the private key that managed your private keys and application can ask this authenticator to Give you some information some piece that you can prove to That you are the owner of the key So I skip this we had the introduction how this the ID looks like so you do not have to have a password anymore You have 45 different ways how you can create your decentralized identity and Block stack is one of them. We saw is a real version of in the talk before so the idea is When you log in when you out you can authenticate to your device You are creating with your cryptographic keys some kind of a proof that you own this key and Yeah, so for Ethereum there's for example three boxes wall they really have a nice Concept where you associate away your identity is represented with a profile and this is the ethereum address and you get some information about the user and Block stack using more human readable way to represent your identity, but it's really about that you Can have a proof that you own this private key in the end and the app wants to have this proof so that they can act in Act on behalf of the user interact with other users exchange encrypted messages Talk to other services or other users So once we have this proof We might want to store our data at a place that where they know I am the owner of this data and That's where we come back to the under a content provider. So we want to have a concept where The user can access or give applications authority to access these data and decentralized storage, there are different possibilities The idea is that we don't want to have this honeypots anymore. We had to talk yesterday web 3 why this is really bad and There are different possibilities, but the applications in the end they don't want to Don't want to manage all the data of all users, but the idea is that The user is managing their own data so we want to get get away from the state where we now that applications databases manage all the users several times for different application abcd Facebook Google and so on We want to move to a place where one user can manage their own data so For the content provider. What does it mean on the device? so we have the authenticator and the user can now give proof to the Application that they can act on behalf of the user and access for example the images So there's one particular key that allows you to access your images somewhere in the cloud probably There's a concept of identity hub, but that's this standard iteration details I just want to make sure that the idea is clear you can give another key only to one application and then this application is allowed to access your contact data and So these are these are web applications. So they are served from the web but they are sitting on your device and they're working locally and So the yeah, it's it's about Let's see. We have the two examples to compare a bit the authenticator Blockstack we have a web app where you authenticate yourself. So they manage your keys and a web app running on your device Three box has this web three authenticators So there you have different browser extensions also on to manage your private keys And then for the storage there you have in three box orbit DB that is based on IPFS and You have its key value based and in block stack you have Gaia protocol that is based on Existing cloud storage. So really fast and performance and cheap it's five based and What is kind of missing for them that you have the Data schema and I'm gone. Thank you