J1 AG 08 JAAK INTRODUCTION TO THE KORD DAPP

what do now it's just follow on from the concepts that the think was talking about and hopefully show you a little prototype of the first product that's been power under the cord banner which is the chord app so as we've said the chord app is essentially an interface to the underlying mechanics in the chord Network today has kind of three main points of functionality the ability to create a graph in a network the Billy to make claims and attach those to that graph and the ability to query those graphs okay cool so now we're gonna seamlessly switch over to the video so just while we're setting up what we've done is we've placed the concept of identity at the core of of the chord network and the reason we do this is so that we can really just verify that agents in the network are who they say they are and the statements they're making are actually true and we can infer trust from those statements an identity can be thought of as an aggregation of all your existing identifies and by identifiers we mean anything from a PGP key to a social media account and the idea of an identity and cord is to aggregate all of those things and so essentially an identity in encored is a graph which is made up of cryptographically verified claims so what do you now is just show you that how that looks in that so what we've done here is this is just this is a prototype at this stage we've just simplified it for purposes of demonstration so take you through that now so what we look at first is the okay yeah so what we look at first it's the journey of creating a new graph so we call that registering an identity and at the core of an ID is essentially a theory and public key you can either use a existing key store or we will softly ability to create a new key store for those who don't have one so to register and what we essentially do here is is send a signed transaction to the network and add a new entry to the court registry under that public king and now that public key becomes your cord ID so the timing's might be slightly out on this video yeah go magic so there's a brief cell section just after you've registered your chord ID and here we're just attaching some superficial profile data to an identity and as you can see here a new a new identities been created we've got a little avatar there and the name so profile data in a network is essentially just another claim a statement that you've made about your identity and this is a self side self signed claim that you place into your graph but other agents can come along and and countersign that and say yeah that looks like you as Vic mentioned we have the the concept of of guardians in network and guardians essentially provide authority services by running guardian nodes and here we're going to talk about just one example of a guardian which would be could be key base and key base would provide this authority service underneath the wider umbrella of identity so to make a claim you say you basically send the request to the cord guardian usually attaching some sort of proof along with that that the Guardian can use to verify that that claim is actually genuine so we've sent that claim got verified luckily and there you go you can see that that claims been added to your graph you can view it and it's visible in the network father's to explore as well and so on the flipside we can search for other chord IDs just by inputting their public address a very short public address and there we go we've we've search for mr. Fred Tibbles and he's actually got two claims he's got key based claim and he's also cannily connected his you port account as well and that concludes the prototype cool so what we're just going to do now is quickly take a look at some of the architecture that underlies that that that that we just saw so we're just going to take a look at all the different points in in the architecture and the tools that we've used to make up that stack and we're just going to look at the data flow and that goes along with that on the right-hand side there so they first and foremost adapt can exchange data with nodes running in the cord network and each of those nodes exposes a graph QL API this allows the client to decoratively define that they requests whilst allowing the know to maintain a nice lightweight Universal API for all you old-school web to Devers developers out there we use some react Redux and a little bit style components for the flourishes there and then on the test net as a said graph QL and go so yeah it's just simple or graph queries you can see there all that's doing is saying please give me some claims all the claims related to this chord ID okay so as well as queries that graph QL API also exposes some mutation operations so in in this case a mutation would be create a new graph so here we have the dap sending the sending a mutation to the node the node verifies the signature that's come along with that transaction and if at all if all is ok then the court ideas is sent to the court registry which is a smart contract running on etherium which essentially just maps public addresses to the graph hash so as I mentioned in the walk through profile data essentially am self son claims and the the raw data itself so the the image or a piece of text that's stored on swarm and the the hash that we get back from swarm makes up the claim value and that's what's actually stored in the users graph and then at that can just fetch that data from swarm and render it that's per usual the other point in that stack are these court guardians at the moment they are simply Micra services running on the cord guardian node and from a DAP a user can send a statement about their about their identity and then the cord guardian will run some verification checks primarily they'll check that the that the transaction has a valid signature and they also run any additional verification sex and and that's entirely up to the implementer right so that could be our war that could be multi-factor or it could be JWT or TLS node tree for example so the guardian would run those verification checks and providing they were all successful and it would return a verified claim and that's an example of a verified claim there and this verified claim is actually what ends up in in your court graph and it's distributed throughout the network there so as I mentioned we're currently developing the DAP and plan is to release this at the end of March our dev meetup in London which you're all invited to if you're gonna be in London obviously I was on March March the 29th our websites their court network so hit that up for all your additional links including our github and we've got all the open source code on there and yeah I think that's it opens questions Q&A any questions out there for myself Victor sweet okay hoodies so yeah come and find us and we'd love to have a chat about anything we've presented any of the concepts especially the tech stack would love to have a chat by that as well alright thanks very much