 All right, the next project is the project provided by our friends from MoSIP. So let's have a look on that. Present about ING. It's a digital wallet solution from MoSIP. We are excited to be one of the core contributors to the OpenWallet Foundation. I'm Sasi Kumar. You can call me Sasi. I'm head of engineering in MoSIP. Let's jump on to the presentation. What is MoSIP? MoSIP is an open source project. We established in 2018. We announced our first code in the open source somewhere around 2019 after one year of our work. And from then on, we have been building projects in the open for all the countries to use. Our predominant customers are countries who enable their citizens to have a national ID. Identity is a big problem in quite a lot of the countries. Some of the countries are stuck with the vendor log solutions. Some of the countries have attempted to build their own and have been successful in issuing those IDs but not being very successful in actually putting the ID to the use. So what MoSIP offers at this point in time is an ability to issue ID for quite a lot of citizens across the globe. So we today operate in Africa, Asia and Latin America. We have close to 11 odd countries who work with us today and we expect that number to grow. We impact approximately 400 million people's life using this identity platform. 100 million people have received already IDs with this particular platform and they've been using their IDs to avoid social services or social benefits from their respective governments. The project is hosted out of a university called Triple ITB. This project is a non-profit. We've been currently sponsored and funded by Bill and Melina Gates Foundation, NORAD and Pratek Shatrasht. So what does ING do with MoSIP? Some of you for whom ING is a relatively new world, it's a Korean language world. It essentially means recognize. How do I bring recognition to the individual and that is why we named our wallet as ING. ING is a reference implementation to enable countries to provide their citizens with a wallet where they could have the mobile ID which are in the mobile for them to use. The wallet has been under development with us for almost a year and a half now. We have been working on various trial and errors and POCs across our customer base testing the wallet in the market. So it comes with relatively a huge amount of experience in the field knowledge that we gained by using it in countries in Asia and Africa. The wallet also an other interesting feature. The wallet can also be used as an authenticator to prove one's identity within them. MoSIP being a national ID, quite a lot of our countries, not all of them but quite a lot of our countries, do use biometric as a way of verifying and assuring a possible existence in front of them. This is to eliminate ghost and eliminate duplicates. And to assure that there is an individual who is really involved in our viling government services. So it's quite a lot of times there is also a need to prove yourself, not just cryptographically, but prove yourself that you are a physical individual who exists. And it's not a simple password that somebody has used it to transfer. So in order to achieve that, ING also acts as an authenticator within our system. This ensures a presence-based verification and gives us and the countries a very high assurance for what these service deliveries are. Today there are a lot of standards in use but some of the predominant standards that we are going to speak about is OpenID for VC and OpenID for VPU over BLE. These are two important standards that we have been working on. In one case we have been more consumer, in other case we have been the creator. So OpenID for VC we consume a lot of information that's been already created by the OpenID for VP community and the VC community. For the OpenID for VP over BLE, we have been one of the largest contributor for that standard. We have put our code in the open source and soon I will explain you what exists and how we do it. Our story behind YBLE. And a quick, you are going to see a demo a little later and Torsten is going to be there demoing our application, whatever exists as of today. But in chart what does it do? It enables the citizens of multiple countries that we operate to download their ID in a verifiable credentials format onto the wallet onto the phone, secures them using multiple cryptographic technologies that we know of and we go to work extensively in that space for the next one and a half years to ensure there is quite a lot of privacy driven signature schemes that could be built in. But as of today it has a very simple signature schemes. So we call it as a resident app. The resident gets this application, downloads their card and from then on they could verify this card with their mobile wallet. And it enables the service providers to use this wallet and not rely on a central authentication server to verify the individual. So this allows two important aspect. Quite a lot of times our customers who are the citizens of multiple countries that we operate in do not have connectivity. The government officers who go in to verify this individual or the NGOs who work in spaces where there is not enough connectivity often face a very critical problem of using a physical card. The assurance level of a physical card becomes very difficult. Compliance and regulatory standards to prove that an individual existed when they actually serviced them becomes very difficult. So coming from and more offline side of the story the application provides very, very interesting options to provide offline mechanisms as well as online mechanisms. Online predominantly all of us are used to. Online is something that we have been predominantly advocating which could let people to avoid services even in spite of connectivity problems. There is a verifier app that we are working on. The verifier app is more like a library and a proof of concept. So we are working with multiple other open source companies. Either private companies which have open source on part of our work or nonprofits who are actually into the same space. So we are working with multiple of them to use our libraries. This is again as I said it's nothing to do with just most of it's to do with the standards. So use this verifier application and the verifier libraries and build the application so that they could actually verify the individual and service them on the field. So that's potentially what NG today offers to its users. What's in the roadmap? As I said you can't do quite a lot of aggressive implementation so far. One we have been able to use and adapt the open ID for VC specification. Second, we have done a year long exercise in adapting BLE for almost 50 odd phones. So the BLE layers that we have built so far we could guarantee you that across 50 models across from Android version 9 unable. It has a hundred percent compatibility and it ensures that it can work from the lowest phone to the highest phone that the end users have. And just to remind you all we operate in a space where country citizens are going to use this application. And the models of the phone and the variety is going to be humongous and in the next one year we expecting that we will learn quite a lot. So NG comes with pre-built telemetry protocols to ensure we can collect a lot of these information back to help the citizens better. Obviously privacy is a big game. We do not collect anything private about the user. There is no location. There is no information about who you are. It's purely about what error occurs on the phone and we collect those information so that we could fix our code. We can make better code at the implementation level. So one thing is to be guaranteed that after our launch and maybe one year, one and a half years down the launch. We would have something which could work predominantly in almost all the phones. So that has been what we have been hacking through so long. But what's up next? The next stories are going to be a lot more interesting. One of our work has been on analyzing the SDJWT standards. And we are excited that we are going to work on that standard. Obviously there is a final go ahead that we are expecting with our research community here. So once we have that threat maps built for the SDJWT, we would be at full swing to start implementing them. That's going to be one of our next big work in the coming year. We will also be continuing to improve on the BLE specification to make it easier and safer for people to use. And that's an ongoing exercise and our commitment to that continues from our side. Apart from this, OpenID for VP is also one of the important areas that we would be working. So you should see us being very aggressively working. The code is going to also change very aggressively to make sure multiple of the countries that we are working with can adapt. There's going to be some layers of biometrics that's going to come in while we're not going to build a biometric phase verification into the wallet. But it is going to offer a plug and play opportunity for biometric vendors to plug in their layers and provide this authenticator in the countries. Now coming back to the code contribution, the entire ING is going to be a code contribution. But what's the most exciting code contribution that we're going to make is the work that we did with the BLE. So how do you transfer a verifiable presentation over a BLE channel with completely offline mode to a verifier and have a 100% assurance that the individual is the same as he claims to be with all the trust built in? That's what the protocol is about. And I think we have like 80 to 90% compliance to that protocol. We have released our code out in the open and we will continue to make improvements in the protocol as well as in the implementation. And that's going to go hand in hand. And we would be happy for anybody who would like to contribute, anybody who would like to use this and evaluate and work with us. As of now it's going to be JSON-LD profile. Most of Framad's inception has been more of a JSON-LD advocate. But we're not limited by JSON-LD, but most of our first implementations has been over JSON-LD. Today our issuance layer works based on JSON-LD. So at the end of any registration process in most of our workflow systems, the end of it is a verifiable credentials with customized schema for the countries. A verifiable presentation comes out in the JSON-LD format. And we expect to continue that space. But as I said, we're also looking out to enhance it not just for JSON-LD, but to support AWT and other formats as well as we proceed into the space. So Project WALL-E is our library for OpenID for VP and BLE. So today it supports Android and iOS both. There are a lot of native code in place in order to achieve it. We have gone through quite a lot of learning exercise in this process. And quick note what does a TWALL-E stand for? TWALL-E is based out of a Tamil word where I come from. This essentially means it's a tunnel. So BLE is a tunnel that gets created between a verifier, a secure tunnel that gets created between a verifier and the person who wants to present or person who's in need of a service. So it enables you to transfer your data, your presentations in a more secure fashion to a verifier and with the assurance that the verifier could potentially have. Now, this is based on BLE 4.2 and supports all the way till BLE 5 and the latest versions. We have tried this to work around with multiple layers of rust in the past. We tried our best to hack through things but there were limitations with the way how Android works and how iOS works and how REST would be binding them. So we had to fall back and start a lot of native code. So now most of our code comprises of Kotlin for Android and Swift for iOS which handles most of the BLE complexities within itself. REST has showed the complexity of the BLEs and the different models. People who worked in the BLE space would know the complexity that's involved. Every phone is different. Every model gives you a different way of handling things. But I think we've done a pretty good job so far. We expect to do better as we go into the production and into the people's hand. We will learn more. We will make this better. So that's a big work that's coming into the Open Wallet Foundation from our side. Obviously, there are going to be a lot of cleanups and other things that's going to happen because it has a history of from where it originated and where it is moving towards. So the cleanup is going to be an ongoing activity. But once we are done with the basic cleanups, we should be able to contribute this back to the Open Wallet Foundation. One of the other work the NG module is going to contribute is also about collecting an issued verifiable credentials using OpenID for VCI. And this is based out of a product called eSignet that we have developed. eSignet is an OpenID compliant authentication. And as an end product of it, the VCI is built as one of the modules. The VCI is built as a plugin and it enables us to connect to any existing data source, not just verifiable credentials. But it could literally connect to any existing data source, convert them into verifiable credentials and then issue back to the wallet. So it's once again an interesting work. It's going to be put to use across 80 million people very soon. You should be hearing us. I mean, we are preparing ourselves for a beta testing. We did an alpha testing in one of our countries with 1000 plus people. Things work pretty brilliantly. We are trying to test this now in Asabeta into the countries. We are going to launch it, which has approximately 80 million user base. So that's an exciting work that's coming in. And that's going to be in the open source available for all of you to use. And there's going to be a lot of learning. Any help here is greatly appreciated from the community. And quick, that's pretty much all about what we're going to contribute for OpenWallet foundation at this point in time. And as I said, we are an open source community. We have pretty much everything in the open source, but it would be nice to have some of these code modules to be part of the OpenWallet foundation. And we could share knowledge and experiences together and make this a better code for a better implementation for the future. And here are all our links that could help you all to reach out to us, look at it and help us and work together as a community together. Thank you. Now, we should be able to see a small demo of how the IG actually works in real time. Thanks everyone. Bye-bye. So we're going to show now the demo of the Mossib Wallet. An application that facilitates storage of verifiable credentials in a single digital wallet and further facilitates sharing credentials with decentralized verification of identity in an offline mode through Bluetooth. In this demonstration, we will showcase how a resident can use the IG application to first download and then share his or her credential with a service provider to avail the required services. For this, the resident opens the app and opts to download the card, which is the national ID in our case. The resident provides the UIN or VID number as available. So let's enter the UIN and initiate the download process. Note that the initial download needs to happen in an online mode. And at this point, during registration, let it be configured to be used based on the nature of service being delivered and the level of assurance required to avail it. Let's first carry out a simple sharing of the card by clicking on the share option. Upon successful sharing of the card, the service provider receives it on his application. Further, the service provider can also view the card in the received card section. Let's now share the card with the selfie option. For this, the resident clicks on the scan option, scans the requesting QR code and clicks on share with selfie. The resident captures a selfie and submits it for face verification against the photo held in the card. Upon successful verification, as we see, the card will be shared with the service provider. In this manner, ING can be used by residents to securely download, store and share cards in the form of verifiable credentials with service providers to avail services. Find more information on how to set up and install ING at talks.mosec.io or reach out to the Mosec team through community.mosec.io to send us your comments and queries. Thank you. So thanks a lot and thanks for your attention. Goodbye.