 This is Gaurav Koth from Ping Identity. I am a principal architect responsible for the Ping One Neo product. Ping One Neo is a suite of products for decentralized identity which have been in development for over 8 years. Today I am going to talk about how we are helping developers accelerate the adoption of standards-based verifiable credentials We are our partnership with the OpenWallet Foundation. Let's take a look at some of the open source projects we are proposing to release in the near future. First project I would like to talk about is the Credential Format Support Project. We are building support for ISO 23220 MDOC style credentials, HDJWT credentials and JWT verifiable credentials. We are building a set of libraries that will enable developers to create, lead and verify credentials in multiple formats. This project is primarily focused on integrating into your wallets, but we have designed the projects in a way that will allow you to embed the Java libraries into your Java server applications as well. We will provide interfaces to provide key material, credentials subject and format specific parameters. We will also include support for creating redacted versions of the credentials for selected disclosure, format permitting. This project is in progress with the support for ISO 23220 format MDOC and JWT based verifiable credentials already baked and ready to be released as open source. We are expecting this project to be open searched by the end of Q4 2023. Next, I would like to talk about support for OpenID for verifiable presentation. OpenID for verifiable presentation has been in the works in development for quite a while and we have been actively participating in multiple profiles to support the presentation of verifiable credentials using OpenID for VP. We will provide Android and iOS libraries to read authorization requests from verifiers and post authorization responses. Support for multiple response types, support for multiple response modes, as well as multiple decentralized identifier methods as well will be a part of this project. We are supporting the implementation of two specific profiles, the ISO 1837 for presentation of MDLs over the internet using OpenID for VP and the JWT VC presentation profile. The project is implemented and ready to be shared with the WWF in the coming months. We think support for presentation exchange is critical for being able to communicate between wallets and verifiers and we are going to build support for presentation exchange 2.0 as Android and iOS libraries. This project will include wallet libraries to read presentation definitions and wallet libraries to create presentation submissions. On the flip side, we will also have server libraries to create the presentation definition when requesting for a presentation from a wallet and to process presentation submission returned by a wallet. We will have a reference verifier implementation as well provided as well. Project ETA is Q1 2024. While we have been actively working on supporting ISO 18 or 13.7 for presentation of MDL over the internet using OpenID for verifiable presentations, this project will provide the iOS libraries for presentation of MDL over the internet to enable support for the unattended use cases. We will support the device retrieval flows in wallet libraries to implement the C-BAR request response REST APIs for a presentation of MDL over the internet. This project is in progress and is expected to be shared with the OWF by Q1 2024. Next, I would like to talk about OpenID for verifiable credential issuance. We are committed to supporting OpenID for verifiable credential issuance, the latest draft, as we understand it. Support for OpenID for VCI is actively being put into the product. For this project, we are working on supporting the newly released OpenID for VCI profile with HDJWT VC format credential issuance. We have plans for supporting the entire OpenID for VCI spec and when we do that, we will be releasing that as open source via our partnership with the OWF. The project will be released as open source via OWF, latest by Q2 2024, hopefully earlier. While we recognize that support for credential formats and protocols for issuance and protocols for presentation are critical to the adoption of standards, adoption of wallets, adoption of decentralized identity, PingOne Neo has been in a product that has been in development for over eight years. Our Neo product supports full standard protocols and formats but also goes further allowing our customers to develop products that can be used in their own ecosystem for decentralized identity. So, PingOne Neo credential format for issuance presentation and verification of decentralized identity credentials will eventually be also released as open source. In the meanwhile, we will release sample iOS and Android apps. We will publish a public service for issuance of credentials into a PingOne Neo wallet using the PingOne Neo native format. Our service in the app will also use the open source libraries contributed by Ping2 OWF as discussed earlier. This project is implemented at the ETA of Q4 2023 to be shared via the OWF. Thank you very much. Thank you for all the questions on Ping's contribution. But I'm realizing there is a lot of drama. Yeah, it's up to the projects really. Yeah, okay. So, some of these, like particularly impact has a high diversity department. So, if it's a single company effort, they're not going to be able to meet the higher project status, regardless of the maturity of the code piece. I think we need to take a look on each of the code projects individually. The Ping contribution, for example, is composed of different projects. And some of them are pretty mature. Some of them they just started to work on. And with MossApp it's similar. So, the open ID for VCI implementation, for example, they have just started to implement, whereas the InGi itself exists for a longer time. So, I think we need to show, we need to see what they are proposing in the end and how the project split is. What I also noticed is there is a huge overlap between the different projects, which I personally think is a real opportunity. For example, Pings and Google's proposed contributions more or less are complementary. However, there are, for example, VCI implementations for Android or iOS in MossApp's contribution and Pings contribution and so on. I think we should sort it out and then discuss with the contributors and the maintainers how we would like to structure that going forward. I'm really looking forward to that. But let's first of all onboard them to OWF. Okay, so that concludes the presentation of the actual code projects.