 Let me do recording. Awesome. So just to quickly kind of get started, we have a couple announcements for some upcoming events. The first one is the Hyperledric Global Forum that will take place between June 8th and June 10th. There's quite a lineup of various speakers, panels. So I highly encourage you guys to take a look. Here's the link to that, and you can register. This will be a virtual event because of the pandemic. So feel free to join and call in from wherever you may be across the globe. The second thing is the Hyperledric Social Impact SIG blog post. So this was released back in March. Actually, this is going to be the first part of a four-part series on the barriers to the circular economy. At this point, we're really looking forward to any comments, suggestions for the next release, as well as interest from the overall community. So if you guys are interested in publishing a blog post, as it pertains to social impact, please feel free to reach out to us via our mailing list, and we'd be happy to look into those opportunities. Another thing is the Hyperledric Social Impact new LinkedIn page. So we are officially a LinkedIn company page. So please add us on LinkedIn and follow us. And if you have any announcements that you would like to make, any different activities that are going on in this community, please do let us know so that we can highlight those via LinkedIn. The final thing is the Hyperledric Mentorship Program. So the Mentorship Program has been kicked off. There is quite a list of 2021 projects across the board for the various Hyperledric products, as well as different use case developments. So if you have any recommendations or know of any folks that might be interested in participating, these are paid opportunities, especially for students that are looking for summer internships. The application for this closes May 7, so please keep that in mind and feel free to pass along this information to students that might be interested in participating. So to quickly get started, so we actually have a really exciting community presentation planned and stored for today. So Shashank, I see that you're here on the link. So if you can, I'm going to pass over the screen sharing. Is it OK if are you able to screen share? Can you see if you have the ability to do that on your end? Oh, I don't think we can hear you. No, sorry, my bad. No, I can't screen share right now. OK, so let me stop my share. And I'll make you a co-host. And then hopefully that will resolve that issue. It's always positive. These are the rituals of the meetings are always nice. I think the meeting will go otherwise nicely. Can you hear me? You're on mute. Can you share? It's part of the pandemic. Yes. So then let me ask the next mandatory question. Can you see the screen? Yes, we can. Lovely. So whenever you're ready, Nancy, I'm happy to kick off. Yes. Feel free to start. Lovely. Well, Nancy and everyone, thank you for having me and giving the opportunity to really share some of the work we are doing here, which is what we call the UN Digital ID project. And just walk through this. But please, let's try and keep it as interactive as possible. Do us questions. I'll try and answer most of them to the best of my ability. I do have some people from my team also here. I can see Pablo is here. And then it gets too deep technical that I'm sure Pablo will be able to handle it for me. Right, so a quick introduction about who we are. What's United Nations International Computing Center? So we were established 50 years ago, actually. And if you see my video feed, my background says our Golden Jubilees being celebrated by a resolution of the UN General Assembly, that big tall building in New York. The idea and the intent then was to have an international computing center because three organizations, the World Health Organization, United Nations Development Program, and the main UN itself, were looking to buy a mainframe to process payroll. So rather than sort of buying three mainframes because it was expensive, they bought one and they set up ICC to actually manage and run it. As part of UN, obviously we are a not-for-profit entity. We, officially, we are administratively hosted by the World Health Organization. So what that means is really our WHO staff. And while from outside, UN might look like a single world. It is not within UN itself. We have a lot many agencies. You see some of the names here. These are some of the organizations we work with. From UNICEF, UNESCO, the ones that you may know of, UNHCR, or the World Food Program. Those might be some obscure ones like UNCTA, UNCTAD, or UNECE, et cetera. We do work with other international organizations as well like the World Bank, Asian Development Bank, et cetera. So, and sort of, let me just very quickly introduce myself. So I run what is called the Solution Architecture section here at ICC and I'm the Chief Technology Officer. And really blessed to have an amazing team to work with and try out some really cutting-edge projects, kind of what we are doing. By way of our association with Hyperledger, we are an associate member and the two sort of highlighted pieces of technology that you see, we are already using it. They're actually in production deployment. And as I walk through this digital ID use case that we are implementing, I will highlight a particular point where we do have an in-production system now using Hyperledger and DNAries to be used in a specific use case. Right, so what is digital ID? And I do apologize to the group here if they already sort of know this, but generally, depending upon the nature of the audience I'm interacting with, I find it quite useful to set the context. Slightly philosophical, when we talk about identity, I think we all will agree that identity is not just my first name, my last name or an email address. Identity is far more than that. It depends on my social status, my economic status. So the fact that I'm married or I have a family and I have a kid form a part of my identity, I have a certain ethnicity forms a part of my identity. So all these aspects that come together is what really makes my identity. And for anyone across the world to really agree to some of the facts that I'm claiming about myself, we generally have a third party between us, a trusted third party, who would attest these facts for me. So for example, I might get a birth certificate from a municipality or a borough or a state which you may trust and say, yes, okay, this birth certificate says your name is Shashankarai so we trust that as a fact. So we have a mutually trusted third party who is attesting certain facts about me which then you can consume. And but it's not just one mutually trusted third party, they are multiple mutually trusted third parties and they attest certain facts about me to make up my identity. So when we talk about identity, I think what at least I have seen as we were socializing this particular project across the UN itself was this misdomer that if you have an active directory account, that's my identity. I believe that's just an account. It's a set of user name and password. Yes, over a period of time, given the challenges that these accounts had, we have added layers of security on top of it. And in a way, one can say biometric two factor authentication or multi-factor authentication based on biometric might be attesting to the fact that a set of user name and passwords that I'm supplying are uniquely owned by me. But that still sort of just talks about one piece of information that is here, Shashank has this user name and password because as a multi-factor authentication he's biometrically proved it. It does not bring with me all other attributes of my identity together. So when we talk about identity in the digital world, I think all of us know this very famous cartoon from Peter Steiner which was published in the New Yorker, which primarily says that on the internet, nobody knows you're a dog. So what does that mean for digital identity? For digital identity, what this means is a set of accredited social, physical, or personal attributes that are digitally accessible by anybody who wants to consume them about me, however, by my consent. So I am sort of playing a central role in saying who can consume certain attributes about Shashank and yet trust them when I provide those attributes about myself. So this is what is the classical or the current model for identity on internet or digital identity, if one may call it so. Again, I will not claim of having done, made this diagram. There's a link over there. It's a very interesting write up on the state of identity on the web today, but I'm assuming most of us are familiar with what this is. This is really us as an end user who have a shared secret with an identity provider. No, this could be Microsoft, this could be Google, this could be Facebook, LinkedIn, or organizations. For example, in my case, my username and password with UNICC. And then we have the relying parties who are trusting the fact that this identity provider has validated my credentials. Thus, when I'm accessing these relying parties, I am who I am claiming to be. And then I can obviously log into these systems, the relying party systems, and I can start feeding it any kind of information. So I can, I can create an account and then I can choose any date of birth I so wish on the relying party. So this is the current state of OpenID Connect and how identities proven on internet. Now, and the reason I call this slide, the hammer in the nail is because when again, while socializing this project across the UN, the idea was, okay, fine. We think decentralized identity is the hammer. So what is that nail we are trying to hit? What is that problem we are trying to solve? And thus does the title of the slide. So the shift in identity and the concept behind decentralized identity is now really that we still have the three same players. There is an issuer and there is a holder of identity and then there is a verifier of identity. If you have to sort of think of this in the physical world, and the reason I have sort of her majesty on the left is because I have a driving license issued to me by the Department of Motor Vehicles here in UK and if and when I'm stopped on the road by police and I have to prove the fact that one I'm over the age of 18 I'm eligible to drive, what my name is, et cetera. I take out this piece of plastic, I hand it over to the policeman and he looks at it. He trusts that piece of plastic because of certain physical characteristics to sort of indicate that it has not been tampered with. It's not a fake counterfeit copy. And he looks at the details that are there and accepts those details as facts or he may also do a verification with some backend system and then sort of allows me to move on, et cetera. So that three-party trust system that we see in the physical world is what we are trying to now replicate in the digital world. So in the digital world, the equivalent would be that an issuer which is what is called an identity provider in OIDC has issued me a credential. And when I need to access some digital system I'm actually going to the verifier and saying, hey, here is a sort of credentials I have. And I'm sure technically I'll be corrected the fact that actually it's the verifier who challenges me for the credentials and then my system responds back with appropriate credentials. But I present the credentials to the verifier and because the verifier is trusting the issuer they will take those credentials as empirically true and allow me or process the information that I have presented to them. So that broadly is the concept behind a decentralized identity. And from a technology point of view, I'm assuming that since we are in the Hyperledger Forum people here are aware of the different roles that different technology components such as Indy and Ares and also, et cetera, play in this whole ecosystem of identity. But I'll get into some of the details later on after sort of talking about the use cases for us in UN. Yeah, some other terms people might be familiar with self-sovereign identity, decentralized identity, verifiable credentials, KP's. I believe fundamentally self-sovereign identity is a slight misnomer. I mean, whenever it was conceived I think it has led to a lot of wrong perceptions. I'll be honest with you, when I started sort of looking into this when a use case came up for ICC to build a solution using decentralized identity. And I started reading about it. My first impression when I read self-sovereign identity was, well, this seems to be, you know, long live the revolution, power to the people and we don't need a state. Obviously as I went into the details of technology I realized it's a different concept. But I think that still hangs quite a lot when the discussions around decentralized identity start about what self-sovereign identity means. And that is another reason you see the sovereign head of the state on the top left in the slide. Right, so what's UN Digital ID? And this is actually a YouTube video. So if the slides are shared and if you can also go on YouTube, you can look it up. It's called the UN Digital ID solution. There are quite a few funny odd videos that have been made out of it. And just to clarify, no, we're not, and UN, we're not trying to track everybody by injecting them with microchips and using 5G technology. But you might come across some of those videos that were built around the UN Digital ID video that we had released. Okay, so what is that UN Digital ID solution that we are trying to build within the UN ecosystem? And to set the context, this is a slightly inward-facing solution we are working now. In the sense, it's meant for UN staff and consultants. So UN across the multiple agencies, UN agencies that are out there on the globe, there are roughly about 220,000 people who work for different UN agencies. And this is really trying to build a solution so that there is a lot more, I'll talk about the use cases later on, interoperability between different UN agencies. So the problems that we're trying to solve. Today, within the UN ecosystem, if you look at an agency like UNHCR, which is the United Nations High Commission for Refugees, they are responsible for helping the refugees across the globe, or the World Food Program, or United Nations Development Program. Multiple of these agencies that operate across the globe, each of them are huge. These agencies have 10,000, 12,000 people strong. And there's hardly any interoperability of IT systems between these agencies. The result of that is that, let us say there is a crisis happening somewhere in Central Africa, and WFP has a bit of a presence there. But HCR needs to mobilize a workforce to get a set up refugee camps. The inter-UN processes are so complex that it might actually take HCR if it wants to use the WFP workforce. It might take HCR about two to three weeks before it is able to onboard some of those WFP staff and consultants and say, hey, can you go and work on behalf of HCR into the field? And that's one example where humanitarian aid gets stifled by just the processes that we are all slaves of. So the idea, and that was one of the main use cases we were trying to tackle. And there are other use cases I'll go into details of, which we're trying to solve with this digital ID project. The idea was fairly simple, is if we can have a simple mobile app, the mobile app allows each UN staff and consultant to have a set of identities defined by the organization they work for, or other identities issued by the UN organizations in their mobile wallet. And as and when they need to be mobilized, and these identities need to be consumed by different organizations, they can be picked up from the wallet by user consent, and the organization can consume those details. Fairly straightforward, simple implementation of decentralized identity. So some of the use cases that we looked at and realized the sort of the value, business value of such building such a solution, sort of the return on investment, as I mentioned onboarding the first one. So the estimation is that if we have to do inter-agency employee transfer, which in the best case takes about five days, it can be cut short down to about four hours. Pension eligibility, and that's one of our in-production use cases, I'll go into a bit more detail when the slide comes up, which historically used to take about two months has now been cut down to two minutes now. And security clearance, and that's the MVP that we have built for this particular project. So typically when any of the UN staff have to travel in the field, there is a particular department of safety and security, and we need to take the clearance from them before we go into the field. Especially if the UN staff is really traveling into troubled areas. So for example, if somebody has to go on a mission to UN, sorry, Yemen, they would need the DSS clearance, and that is important because as UN, we want to ensure that, and especially the department of safety and security wants to ensure that they know where each staff member is and in case of emergency, the required help can be provided. So obviously very important, and there are about three million such a request per year over here to travel. And it's a very complex process for all of us because we have to go into the system, provide the itinerary details, depending upon where you're traveling, provide medical information, and also at times we travel to areas where there is no public transport available. So for example, in South Sudan, if you have to go from Juba, which is the capital of South Sudan to what is called Deep Field in UN, a town called Bintu, there is one flight that World Food Program operates. There's a WFP flight, which flies once per week from Juba to Bintu. And imagine if a HCR staff has to not travel there, the amount of logistics and the administrative overheads are really complicated. So those are the kind of use cases we were looking to solve, those business problems we were looking to solve with this solution we're building. Right, so different user stories, I have sort of spoken about a few of them, so rather than reading off the slide, I'll try and talk through some of these pieces. The idea that we can see was that the inception of a person's identity within the UN really starts when they are about to join any UN organization for the first time. So it's really the organization's ERP, their chart system where the life starts. So how about we build a solution where when a user is being onboarded in a UN organization for there, they are the systems start issuing a set of credentials to this user. The credentials are getting stored in user's mobile wallet in their mobile app. That the user experience is really that the HR person is onboarding the person. So let's say I'm joining UNHCR, I, the UNHCR HR staff will know my personal email address. They will enter that into the system. It will trigger something where I'll receive an email to say, Shashank, why don't you go and download this UNDigital ID app and click on this link to receive a set of credentials from UNHCR. I will do that. My app will connect to the UNHCR systems. It will pull the credentials which I'll store in my mobile app. And now that's a set of credentials that I have from HCR. Now I need to get some medical checkups done and I need some medical clearance and I go to WHO, the World Health Organization. And they typically today, we carry this little yellow book where we carry our vaccinations, especially for field missions. I, WHO issues me a new sort of credential saying Shashank is vaccinated against A, B, C, D, E and I sort of store that information in my mobile wallet. So that's the general idea that which we started building the system. Use it as a set to travel overseas or deploy to a mission. Mission, sorry, before you all start thinking of Tom Cruise and Mission Impossible, mission in UN context means when you have to travel for work. So business travel is a mission for us. Nothing very fancy and I can tell you we don't go to very fancy places. So if you have to deploy on a mission we can use this to exchange information. The example I gave, so if I'm working for UNHCR but I want to take that flight from Juba to Bento which is operated by WFP, WFP obviously needs to know my details and needs to make sure that one, I've been cleared by the UNDSS systems to take that flight. I am really a UNHCR staff and I am approved for the mission, the work that I'm going to do in Juba or sorry, in Bento. And today, as I said, the administrative paperwork is quite overwhelming but what if all that information was actually stored as credentials in my mobile app? So I could present that to the WFP officer in Juba and say here's all the information. He can scan it off another mobile app and allow me to board that flight to Bento. So those were the kind of use cases we were exploring for Digital ID. Authentication, I think that's the no-brainer part which is rather than sort of using then your active directory accounts or local accounts, et cetera, really use the credentials stored in the wallet to log into systems. And what this would allow is if I'm working for agency A and there's a system that I want to log into for agency B, I can actually use my wallet and the credentials stored in my wallet to log into agency B system. And agency B would know that yes, this is Shashank because they trust the issuer of the credentials, which is agency A which again is the magic that comes through the decentralized ID solution. Vaccination records because today, as I said, we carry this little yellow book from WHO so we can store those records in the mobile wallet. This is an interesting one. Again, a big challenge for UN. So when we get deployed to field missions and I sort of walk up to an office and let's say Nairobi, so there's a big presence of UN and other nations in Nairobi. Today, my ID card, which has been issued by WHO is not honored on the Nairobi gates. I will have to present either my national passport or the UN passport, the blue booklet to prove my identity to the guards who then would issue me a new card to let me enter into UN in office in Nairobi. And the use cases we are exploring is that if I can just use my mobile phone, scan at your code and then the gates or the guards know that, yes, this is Shashank because I have got my credentials stored in my wallet and allow me access into the building as opposed to going through and hold approval process even as a UN staff. So again, a use case that we're exploring for physical access. This is the one which we already have in production in an odd way actually was the inception for ICC to start using the Hyperledger Indian Aries set of products. Yeah, in a way, if you think of it, it's quite funny. We started with a retirement use case and we are working ourselves backwards. But the way this came about is that we have a United Nations Joint Staff Pension Fund. The fund provides post-retirement services to roughly about 80,000 beneficiaries spread across the globe, about 198 countries. So the fund approached us about a couple of years back and they said, look, we have a problem. There was a new CIO and he was quite looking to bring in some changes into the way IT operates in the fund. So he approached us at ICC saying, I have a problem. We have a 70-year-old process which the business need is that they need to determine if a particular person is still alive or not. So whether the pension should be disembursed or not, are they eligible for pension? And if they are alive, are they living at the address they promised to live at at the time of retirement? Now, the address or the location is important because our UN pensions get adjusted to cost-of-living indexes of different countries. So if I say that I'm going to retire in Switzerland, obviously my pension might be a tad bit higher than somebody who says, let's say I'm going to retire in South of Spain. Contextually just for people who are not from this geography, South of Spain is a lot more economical and well, personally, I would love to go there. Beautiful beaches, et cetera. So, but the way they do this, this verification process which they have been doing for the last 70 years is every year they would send by post a form to the address with which the beneficiary was registered. And then they would sort of wait for the beneficiary to sign on the piece of paper and send it back. And that was the verification process for location and also the fact whether somebody's alive or not. And based on that, the pension would continue. Obviously they would try to control it as much as possible. So if somebody's living for 120 years, that's sort of an immediate red flag to say, well, looks like somebody else is signing the paper on the behalf of this person. But within a reasonable range, it was difficult for them to determine what is working, what is not working. And it was also quite frustrating for the beneficiaries because the postal mail, you try and imagine postal services in around 198 countries. It may be fast and efficient somewhere, it might not be efficient in other places. So mail is quite under liable. So there was risk at times when people would post the form back, yet won't arrive and their pensions might stop because the fund sort of didn't get the signed form. So they were looking for a solution to solve the problem and what we did for them. And in the truest sense, really we did not need a decentralized, well, we needed a decentralized ID, we did not really need a blockchain or Hyperledger indeed at the back end. We could have in theory done with immutable database because one of the requirements the fund had placed upon us was that any digital solution system we build really needs to have immutable records because this is a 70 year old process that's changing. The fund is quite sensitive, they're quite heavily audited and they really want any new system to have clear track of what is being done and thus they wanted an immutable database behind it. So the solution that we've built for them is a mobile app which the beneficiary is using the field. What it does is it creates a biometric profile of their face. Then they undergo an onboarding process with the pension fund call center using the mobile app. So this can and upload a government issued photo ID. They get on a call with the call center operator who looks at the government issued photo ID, looks at the video call that's going on and looks at the profile picture, the biometric profile picture they have taken and says, yeah, it's the same person. And then this person at the required time is prompted to open the mobile app. Again, the biometric features are matched and they are expected to perform certain random actions such as smiling or closing and opening eyes, et cetera just to ensure that their loved ones are not holding a photograph in front of the mobile phone and it's actually a live person we are dealing with. Obviously, we can track their location and all this information is then packaged as a transaction and sent to the backend where it is recorded in Hyperledger indeed. In this particular use case, the mobile wallets, the Aries wallets are actually sitting in our data center. So they are what one would call cloud wallet. So sitting in our data center. Now, the reason I went into so much detail on this particular solution is as I said, we started with this, this is non-production. So we've got a production instance of Indie and Aries and whatnot, you have it. Since it's been about three months now, the solution was launched. And from this, the idea of actually trying to extend that whole Indie Aries solution across to a proper decentralized ID was born. And the bulk of the discussion I had earlier on the speech I made was really based on this idea then, hey, let's take this now. We know how to operate Indie. We know how to play with Aries. Let's move it forward. Let's try and build a UN-digital ID and solve the problem. Right. What did we do for MVP very quickly and the tech and that's sort of the last two slides and then happy to take field the questions. What we have for the MVP to demonstrate the fact that how this all will work is we've got three, the ledger itself, Indie, et cetera, notes running in three different agencies. The World Food Program, the United Nations High Commission for Refugees and ourselves. We have got our line of business ERP HR systems, which interact with the middleware that we have built. And I'll go into more details of it in the next slide. What is that middleware? What is the intention here? And then it sort of interacts with the whole, and this is, I admit it's very, very abstract. This was meant for HR directors and further senior management in different UN organizations. So I didn't want to go into too much detail of ACAPI agents and wallets and nodes and stewards, et cetera, but happy to go into those details in this call here. So we've got, for them, it was just, hey, you've got a blockchain, you've got different nodes running, they're talking to each other, we've got the API layer, the ERPs are communicating with the API. We have a mobile wallet in a mobile app. The user information at the time of onboarding is pumped from the ERP via the API. And then the issuing agents or the issuing wallets for different agencies will issue a credential to the user here. This is the journey, as I described, that the user receives an email, which is what our API layer does. It sends an email to the user. And it's got a link, which is deep linking. So if you tap on it, it just opens up the app. The app then automatically connects to the issuing wallet here, gets the credential, displays it to the user, and the user accepts the credential. Then what we have is this, I kept mentioning this DSS, the Department of Safety and Security System. What we have is the UNDSS Strip System, which has been modified to accept another identity provider. And let's say when this user tries to access this UNDSS Strip System, what this UNDSS Strip System does is we have built another piece of port, the open ID connect to a DID bridge. And so for the DSS Strip System, it's just looking at an identity provider, an open ID identity provider. The reason we did this bit, and the reason we did this bit is again, just to ease the integration with existing systems. So we sort of made an explicit decision, we'll not top native DID. I know there is an extension to open IDC protocol to actually allow it to communicate again with verifiable credentials. We explicitly made a decision not to go that route so that these integrations become easier. Again, because we're dealing with multiple UN entities, the smoother we can make the whole black magic for them. It's a sort of, hey, just this simple change and you can use this, the better it is for adoption of the system. So this is what we decided to be the minimum viable product to really demonstrate the concept to within the UN ecosystem and the UN management. This has been built and completed now, and now we are really looking to start moving and enhancing the system with different use cases. So bring in some HR use cases, bring in some physical access security use cases and start building on top of this middle, the block of the work we have done. The stack breakdown, as I said, we have Indy with the trustees keywords and the validator nodes running in different organizations. In terms of agent, we are using cloud, sorry, ECAPI as the cloud agent. We today have the ECAPI as a mediator agent as well to talk to the mobile wallets. And that's because we were using the React Native framework, actually working within VCO on that one. I think I saw James is in the call here. So we're working with that, but then we all jointly made the decision to switch over to the new JavaScript framework, the one which the group collectively set to use. So Pablo, who's from my team on the call here, he's helping use that, consume that and also, to whatever extent possible, contribute back to the community. And obviously, once we switch over to this framework, we will not need the mediator agents. Our ID manager and OIDC bridge, the two pieces of work we have explicitly done separately, they are available on our GitHub pages. The idea of the ID manager, which is a Django app, is really to decouple and allow the ERP integration. So today, it just takes us, it's just sort of single API endpoint, which consumes, which takes in a bunch of attributes and splits them across into three different credentials, core credential, personal credential and duty credentials. Our roadmap, the next set of features we are adding to it is a full schema lifecycle management, because the idea is that each of these agencies can then publish their own schema and start issuing credentials against those schema. So they can then actually retire existing schemas, update them and add new schemas as they so want. And also the whole credential lifecycle part to be introduced in the ID manager. So you can sort of revoke the credential. So if somebody leaves the organization, they are, the exit procedure takes place in the HR system. We don't want somebody coming in and making changes on this end. All that does is automatically, the HR system automatically triggers the right APIs and the credentials are revoked. So all those pieces would really be sitting at this API level. And that's what you're calling the ID manager piece. The OIDC bridge is really the, as I mentioned, it is an identity provider. The intention is that it will ease integration with existing systems. And we are passing quite a, we're doing some silly things actually as well. For example, in this DSS strip system, if this particular user doesn't exist, they're trying to access this system for the first time. We are actually, the silly bit we are doing is we are basically passing some attributes, claims in the JWT token, which then the system uses to create the account. But the system can implicitly trust the fact that it can take the attributes that are coming in in the JWT token and create a new user in itself is because it's actually trusting the whole token itself coming from the bridge and the DID. And to acknowledge and shout out, this was really inspired by the work that was done by the government of British Columbia. They do have a page on GitHub. Their implementation was in .NET. The team, I have the pleasure of working. We are all mostly Python and React native, et cetera people. So we just said it's easier and faster for us to port it into Python and start using it. So that's the reason it's been done in Python. And yep, that's pretty much it from my side Nancy. So back to you and if you go on the floor have questions. Thank you so much for the presentation. I think it was extremely informative, but I believe that the community probably has a lot of questions for you. So we'll open up the floor for folks that might have questions. I have one. This is Brian Bellender. Nice to see you Shashank. Thanks for presenting on this. This is fascinating. What's the current state of rollout? What do you expect to have in production this year with how many users? So today, as I said, Brian, we finished MVP. So that's broadly three agencies, the one you saw on the screen connected. So the way I like to sort of say in UN, we like to form committees and we move with slightly glacial pace. So we are beginning to form two sets of committees, one HR committee and one we have a working group on physical security. These two committees are being formed. The intention of these two committees is to then look and come up with what are the two or three or four major use cases they would like to see covered. And hopefully with the course of summer once these committees have been formed, intention is to start rolling those use cases that they have identified by tail end of this year. We do anticipate at least two other UN agencies to join this. And again, though, they're quite large UN agencies. So in a sense, we will have five UN agencies, the current three and sorry, the current four actually, because we are working with UN secretariat as well plus the two new ones. And hopefully by the end of this year, we are able to produce at least one or two HR use cases and put it into production. Having said that, the pension fund which was obviously didn't require multiple agency cooperation, that is already in production. So there we are running in DNA reason, what not you have it. And that's already in production. I think last I checked, we've got roughly 6,000 beneficiaries who have downloaded and installed the app and have, you know, registered themselves through the app. So we've really got 6,000 cloud wallets if I put it this way in the JSPF solution in production. Hopefully that answers the question, Brian. Yeah, I mean, understandably, organizations like yours move at a certain pace. And I think we're all grateful for the consideration and care that is put into such moves. But that's actually really remarkable progress. That's cool to hear. And I was intrigued by seeing world food program there who've done a lot of other kind of blockchain related kind of payments projects and the like. You know, are they looking at this or are other UN agencies looking at this as a way to extend what you're doing for kind of internal, you know, employee and HR kinds of uses out into programs out in the world, you know, on the ground? Yeah, so again, as we are sort of Hydra multi-headed beast, yes, the one district knowledge WFP program which was based on a medium for payments and has been quite successful actually. So Homan Haddad who's been one of the key persons behind that program is also broadly working with us on the digital ID on this particular program from World Food Program site. Also, in terms of taking it down to substantive programs of UN, there are a number of discussions that are happening. One of the challenges that we always run into and the questions that are rising, I think that two or three different challenges. One obviously is the comfort factor with such complex technology. The second one is the last mile. Obviously today what we have been able to demonstrate as part of the technology feasibility or the MVP to the community at large is that with a smartphone, a lot of these things are possible. But when we really start talking about infield implementations, the first question that's asked is a lot of the persons of concerns that UN deals with may not have a smartphone. So that last mile is this being a bit of a challenge and really again, a little open question with the whole committee here, which is that if there are smart solutions on that, we would really love to show that working, that the last mile can be handled without smartphones so that it builds confidence in the people who run the programs to be able to sort of be open to adopting these solutions. In fact, there's a lot of work going on in that over on the vaccine credential side. There was another sister organization, the Linux Foundation Public Health recently hosted a summit covering paper-based credentials and how you might squeeze a VC issued by, or tracked using areas in Indy, at least one that can contain enough metadata to track vaccination status. Encoding that into something that can fit in a QR code and then can be printed. And there's some open questions about privacy when it comes to exchange and that sort of thing because that's one code that you use everywhere and thus can become a tracking device potentially. But certainly scaling down to those who don't have such funds is a priority for folks on that side. So there's, I'll try to drop a link from the outcome of that summit in the chat if I can find it within the hour. I wanna create room for other questions. Otherwise I could ask questions for the rest of the hour if you wanted. But yeah, let me leave room for that for others to ask a question right now. Thanks, Brian. Yeah, and sort of, I do sort of collaborate a bit quite a lot actually with ID2020 team who again are quite focused on the substantive problems. And again, with IndyCO, I know James and Ken have been working on the paper side of it. But yeah, and certainly if you can share the information so we can then really take that as a demonstrable model and show it to the substantive programs because I think that what we need to build is their degree of confidence in them that this will really work forward. Cool. I dropped the link that I found in the summary report. Wasn't, I'm not sure this is something you can show to others yet because it's still kind of work in progress being hard to do this for vaccination credentials. But certainly there's lots of POCs kind of showing that it's possible. But you only get like 800 bytes to play with or something like that in a typical QR code. So it's really, I might even be wrong, might be 800 bits or something. It's super tiny, but very cool to hear. Thank you so much for the engaging question and conversation. Any other questions for Shashank since we have them on the call? Really appreciate your time. I do have one more and please if anyone else does, I want to, you know, make great the space for others to ask. But, you know, one of the challenges in this domain is right now there are plenty of startups offering commercial support for Indian Aries. But it hasn't yet been picked up by the major companies, major IT companies. Although I think Accenture has started to do Indian Aries related projects out there. But by and large, you know, if one were to go look for, you know, headline commercial support from a Microsoft or an IBM or an Amazon, it's not quite there. How much of that is a barrier to adoption by organizations like the UN? So I don't know, sort of call us stupid, call us smart, call us to adventure us. So when we started the JSPF, the pension fund project, again, a lot of this was quite infancy and it was really a leap of faith. In fact, at that point in time, Aries did not even exist as a project. So we, within the pension fund and ourselves, we knew we are making a leap of faith. And this is where I like always like to say standing on the shoulders of giants. So the team that I worked with at ICC, I was quite confident that if we run into some sort of trouble, we'll be able to handle most of it ourselves or seek community support and go along with it. So yeah, at that stage, the idea of having some sort of potential commercial support, while I did ponder over it, I was sort of quite confident we'll be able to get over it. I obviously, as we grow and as this gets more complex, we would like to have some sort of that question and quote for some degree of commercial support. But this is this, if it takes the shape that we are trying to give it, it is getting quite strategic for ICC. And then we'll start investing in our own people and building up that team to have that cushion ourselves to be able to absorb some of the support needs. But yeah, I can see in number of other places, especially if you are not, because we are an IT shop eventually, 650 or techies playing with all sorts of technology. So we can handle that. But I can see certainly somebody, if it was a World Food Program, doing it themselves or as UNHCR doing it themselves, they would have really looked to have strong, substantive support available. And they do realize it's a big challenge because typically the procurement teams would go out and look at Dunn and Bradstreet ratings and other ratings for different organizations. So it would not just even be the case of, here's a startup of 10 people and they'll be able to support you. They would really look for institutionalized companies to make that support. So there I would seem to both become a barrier. I think for us, I was quite comfortable that we will be able to manage it. So sort of took that leap of faith. So far, it's all holding together. Cool, well, we're certainly hoping to see more and more top line commercial support. I think especially with some of the vaccine credential work we're gonna see some of the other companies step into this space. I mean, IBM stepped into it with a health pass, although that's not Indian area space. It is using verifiable credentials kind of under the covers. So they're warming up to the technology for sure. Actually, have you seen the pandemic increase in interest at the UN layer in trying to address digital identity and do that? And do that in a way that, I mean, I know ID4D has been out there for a long time, talking about the relevancy and there's STG16.9 talking about the importance of providing documentation for every citizen on the planet. But do you think the vaccine question has raised the issue of privacy in this individual identity or is that still kind of thought of as a very separate topic? Yeah, if I may, Brian. So if you sort of take that UN beast and slightly dissect it, it becomes quite interesting. So as I said, internally focused pieces still a lot of hesitation, right? Then there is the normative side of it. So for example, WHO has a working group and I think concluding their work as well on the digital yellow pass and that normative working group in WHO which has small, big, multiple players trying to come up with a standard for this is one part. The smart vaccination record group or something like that. Yeah, I'll have to dig out the name I sort of don't remember it from top of my head. But then if you see the role of WHO per se there is the secretariat role. So the working group is formed and they just act as the secretariat. In a way, the way hyperlegia foundation, for example, is working as you sort of just supporting the community to come together. They are really just allowing the community to come together and come to a standard. But what happens as I think we all are seeing, for example, in case of vaccination passports is at times member states start running off on their own. So EU has announced that they would within the next couple of months have something rolled out. The IBM bit that you mentioned is I think with Germany which I guess then becomes the EU standard in a way. The Brits are talking about it. So I don't know what they will go with, highly likely they just follow what EU would do. So those conversations then and as that adoption occurs I think that will then start inferencing the standards as well. I think we've all seen that happen over years. But when we come to the operative agencies of UN, when we look, and what do we mean by operative agencies? When I look at a WFP or a UNHCR or what other UNFPA population fund, the adoption and implementation in field will take time. And this is where I, when I was sort of talking about the last mile problem and being able to demonstrate to the program owners in these different agencies that they can take it to a refugee camp in Myanmar or a refugee camp in Syria or Yemen or somewhere. They know the pain point, but we'll really need a break to be able to convince them and then implement the solution. It's not probably as conclusive as you wanted, but I just sort of putting the dots out there to see what the picture is for you. Yeah, I'm asking you to speculate on a lot of things. So not a problem at all. Yeah, no, this is obviously a space, a lot of us are dedicating a lot of time in. Actually, are you familiar with a project in India called Divak, D-I-V-O-C? It is, sorry, a project to provide verifiable credentials for proof of vaccination as a compliment to the Aadhar system, but to do it in a more decentralized way. I can pull up the link for that, but in a country, obviously with a particular focus on the full spectrum of use cases, and I don't want to call them a developing nation because I hate that term, because India has been an older civilization than most of the other countries in the world, but let me see if I can pull up the link to that because it's a fascinating project. I think what I haven't gone into details of it, but just talking about India, I know they have recently been speaking about actually doing voting over blockchain as well. Again, I don't know the details, what is the underlying platform, et cetera, but there was sort of something that came around and just sort of had a quick glance at it. And honestly, speaking about India, I would love to see that Aadhar card move into decentralized entity. I think it's right not too much centralized in my humble opinion. Yeah, no, it's hard to shift from a centralized world view to a decentralized one. It's kind of like expecting Facebook to suddenly wake up one day and decide to be a decentralized social network. It's very hard when all of your metrics and incentives and technology infrastructure is built around a centralized concept. That's why Divak is interesting because I believe it bootstraps off your Aadhar ID, but then issues you decentralized credentials that are centrally stored. There is a central record of who those credentials have been issued to, but it's otherwise follows the pattern of the holder having all the power in that setting. So yeah, it's all really good to see. Sorry, I don't have any other questions. I know we're right at time. So I'd appreciate this. Thank you everyone else for letting me hog all the Q&A time. I sincerely apologize for that if anyone else had questions and didn't want to get them in. So I should just shut up and see if anyone else has any last questions. Nancy as well, go ahead and put the most along me, Nancy. I'm sorry. No, I really appreciate the question, Brian. I think a lot of those were in mind with some of the questions. I think the community would also be curious about Shashank. Would it be possible if I could share your email address, just in case folks on the call had some questions? Just my audience. That sounds great. Thank you so much. And I will definitely be releasing the recording once this is done and make sure that we all have the link for folks that were unable to join the call today. Lovely, Nancy. Thank you ever so much for everyone part. For being patient listeners and allowing us to present the work. Thank you so much for leading the way for the innovative work so that we can actually highlight some of the great use cases. So really appreciate it. Thanks a lot, everyone. Have a wonderful day. Thanks, bye. All right, thank you, everyone. Have a good day. Bye. Bye. Thanks, everyone. Thanks, Shashank.