 Recording and we're good to go. Sounds great. Thank you so much for setting that up. No worries. We're looking at ways to automate that process. So one of the challenges is we sometimes like a meeting doesn't happen, like it gets canceled and one person shows up and suddenly the recording starts. So we were Ryan and I are well rise done all the hard work. We're looking at how to automate this so that when you start the meeting, it just happens. Here we go. And we've got awesome. Oh, that's great. Oh, you can see my screen. It looks good. I can see your screen and I see Telegram Sam has joined us. Wonderful. Welcome, Sam. And set char to cohost. Thank you. Hi, Tim. Hey, Tim. Make cohost. All right, char, you're the cohost. Thank you. If there's ever anybody else you want to add as cohost, just let me know. OK, great. Good to know. I generally have a policy that we turn on cohost or have someone else's host because internet goes down. We don't want to end because one person is, you know, the point of failure. So yeah, yeah, that happened once before. Yes. Again, super fun. Thanks, Zoom. You're the best. Very fun. Although the alternatives are not even. Probably shouldn't say that on a recording like that. Well, let's see where our speaker today is Clacio of B.C. Gov. So let's wait until we see him on the call. Go ahead. Hi, Maria. Thanks for joining the call. Hi. We'll get started in just a few minutes. Perfect. Thank you. Hi, Clacio. Good morning. All right, let's see. We can probably go ahead and get started already recording. So that's great. Let's see. Welcome, everyone, to the Hyperledger Identity Special Interest Group call for May 4th, 2023. Thanks, everybody, for joining us today. My name is Char Haaland. I'm a co-chair of this group with Bipin Barathon and Tim Spring. So today we will talk about. We'll talk a bit about the change of this group from a working group to a special interest group and our merge with the identity working group, which we're really excited about. We'll also go over working group status updates. And we will hear a presentation from Clacio Varjo of B.C. Gov on Aries Beifold and the B.C. Wallet. So thanks so much for joining us today, Clacio. This is a Linux Foundation call. And so we are following the Linux Foundation antitrust policy, as well as the Hyperledger Code of Conduct, both of which are linked and written here. This call is, of course, being recorded and streamed on YouTube. I will post the recording on this meeting page later today. And I'll send out this page in the chat. Let's see if you want to write your name on the attendees list. That would be wonderful. Always fun to be able to see who's attending our calls. And I think we have some new faces on the call today. Would anybody like to take a moment to introduce themselves? Say whatever you want to say, a brief introduction of yourself, what has brought you to this space, what you're working on. So we'd love to hear from any new people on the call. Sure. Hi, everyone. My name is Chan Lu. And currently I'm a research manager at Blocher ABC, a Blocher Research Cluster at the University of British Columbia. And before I became the research manager, I was a post-doc research fellow at the research cluster. And I have a PhD in business focused on strategic management and organization. My research area is blockchain adoption and health care. I'm very excited to meet everyone and learn from everyone. Thank you. Yeah, thanks so much for joining the call, Chan. Thank you. Great to have you on. Sean, it looks like your hand is up. Yeah, hi. My name is Sean Bohan. I am a community architect at Hyperledger. I've been in and out of the Hyperledger community for the last six years. This week was the sixth anniversary of Indy being accepted into Hyperledger as a project, which is pretty weird to see pop up. And I am here. I'll be on a lot of these calls going forward now that we have an identity sig. We are live streaming this to YouTube. So folks want to watch it live or if they want to watch it later on, we have an identity sig playlist on Hyperledger YouTube. And if anybody needs to reach me, you can find me on Discord. Just pop a note in community architects. I've monitored that all day long, but also whether you're in the Indy or the areas of the Yonkreds community, welcome. And thank you for Char for leading on this. Absolutely. Thanks so much, Sean. Would anybody else like to introduce themselves? Let's see. A few announcements worth mentioning. There is an Yonkreds workshop on May 31st. Here's the link to register. That'll be great. So definitely encourage everybody to attend. Let's see. Another announcement, of course, is our merge with the identity working group and becoming a special interest group. I think it'd be nice to talk a bit about what that means, what that is going to look like, maybe reintroduce our co-chairs within Tim and myself. But before we jump into that, are there any other announcements that anybody has or any introductions that anybody would like to make? All right, wonderful. So Tim Spring and I have been co-chairing the Hyperledger identity implementers working group call for a while, and Bippin Barathon of DLT NYC has been leading the identity working group. So we're really excited to join forces and become a special interest group instead of a working group. This fits better what we do here, where it's a roundup of community news and working group progress updates, presentations and demos, rather than a technical project that we're developing together. So we're excited to consolidate the existing communities and resources of these working groups. It's really wanting it to be an entry point for newcomers, a place to ask questions, community news, there are so many calls, too many to attend all of them. So this gives the brief updates on what is going on. So those are some of the main goals, collaborating across Hyperledger identity projects and collaborating with other special interest groups that focus on identity as well, leading outreach to other Linux foundation identity communities. Of course, we track updates in the TOIP and the diff, which is great. Also bringing in speakers to talk about a deep dive of interesting topics or demos. And yeah, creating a forum for members to engage in the identity conversation within Hyperledger and have a place to host that conversation. So yeah, just wanting to open it up, if anyone has questions about this change, we're also always appreciating feedback. If anybody had suggestions on how we run these calls, format or content changes, would love to hear that as well. We could also probably do a brief introduction of reintroduction of our co-chairs, Tim and Bippin, if you're willing, I can start. My name is Shar and I work at IndyCO as a software engineer. I've mainly worked on projects related to Hyperledger Aries and Indy. I'm an active developer on the Aries, CloudAge and Python ecosystem, developing plugins and other purpose-built agents and protocols. And then I'm involved as a co-chair of the Hyperledger Indy contributors working group. And of course this one as well. But Tim and Bippin, would you like to jump in with a brief introduction of yourself? Tim, sure. Go ahead, Bippin. No, I said, you know, I'm waiting for you. All right. Hi, my name is Tim Spring. I'm a marketing director at IndyCO and I try to help line up speakers and do any help in promoting the groups. So that's kind of what I try to bring to the table. Hello, everyone. My name is Bippin Baratheon. I've been running the identity working group for quite a while. In fact, the identity working group started almost at the same time as the, you know, the Hyperledger itself in the first meeting, first hackathon, get together, we started the group. It was first chaired by one of the legends in the space. Then it got taken over. It got basically, it got orphaned and I jumped in to take it over. And we launched almost all the projects that are now flourishing. We were the mothership. Indy was launched inside the identity working group and also Aries and many others. And I'm so glad to see that it's all thriving. And we also did, we also differentiate, I mean, the identity implementers working group started as sort of a tactical group for reporting on the work in progress of all the work that is going on in the identity space. In terms of the differentiation between the two, it used to be that the identity working group proper was where strategic sort of vision was presented and specific project details were presented in the implementers working group. Identity working group as not as active as the implementers working group because obviously the projects are very alive. So I'm glad to see this new life being injected into the system. And we will take it to the next meeting and we will take it to the next meeting. And we will take it forward from there and hopefully we'll have some presentations that are focused more on a strategic vision, especially integration with other projects because identity by itself is not very exciting, at least for me because it is the foundational aspect of identity for all different projects, meaning healthcare, financial markets, anything you touch has an identity component. And that's where the identity working group used to focus, now identity sync will have these twin paths, but obviously not very divergent. Thanks for restarting, rebooting this whole concept to Sean who is now our new point of contact. And that would be all. I'm eager to hear what the presenter has to say. Likewise. Yeah, thanks Vipin for that. But if history, that's great to hear and really excited to join forces. All right, before we jump into the agenda, does anybody have any questions about the change in the working group? Any announcements or introductions? All right. So let's jump into the agenda for the working groups that we track. Did I see a hand up? Oh, okay. Well, feel free to jump in anytime. Let's see. Usually we spend the first part of the call going over working group updates and then we turn it over to the speaker to give their presentation or demo. So we will start with these working groups that we track. I'll send the wiki out in the chat again for those who have joined more recently. So in the Indie contributors call, we are making good progress on the sovereign node pipeline there. So there's been some branch switching happening. Main got switched to Ubuntu 16.04 and the Ubuntu 20.04 branch became main. This is a part of the upgrade to Ubuntu 20.04. And so there's testing happening. There's some branch comparison work yet to finish up but working towards an official release which is really exciting. Also scoping out the top priority tasks on the Indie roadmap that we have developed recently and especially repo cleanup is what we're starting with. So going through open PRs and figuring out what we want to do with them, retarget them to the right branch again or close them. So that is all going well. In the Aries working group, Sam, would you want to jump in with any updates there? Yes, sorry, I just took a bite of food. No worries. The discussion we had is pretty relevant. We're talking about transitioning the legacy use of unqualified DIDS and some Indie projects over to did peer method two. Also a did peer method three, which is an efficient synonym for did peer two. And then that will be leveraged into that conversion in anticipation of our continued work on defining AIP three. That's our quick summary. Very cool, thank you. All right, Aries bifold. Anybody attend that group who'd like to report? Claycio, you're probably pretty involved in that one. Yes, I do. I think the previous one, there hasn't been any major changes. And we're working on the component, creating more components, breaking down to more components that are reusable for different use cases and different applications. Wonderful, thanks for that update. Let's see, in the Aries collision Python user group, we had an update from the Indicator team on our basic code with us to upgrade ACAPI to use the hyperledger implementation of a non cred. So we've been working on revocation support, reassessing the existing revocation components to figure out what we can reuse there. So yeah, mainly working on revocation without some tails file issues we've had to solve. But next, we're looking at working on documentation, creating a non creds method plugin author guide so that there's enough documentation that people can create their own plugins and then unit integration tests as well. Another thing discussed on that call was talking about converting and ACAPI deployment to use Aries Ascar. So Wade Barnes talked about some lessons learned there, which was interesting to hear. All right, in the Aries framework JavaScript call, did anybody attend this one who'd like to report on their progress? So today's meeting's got canceled, so I don't think there has been any major change upgrades there. I know, as you had already mentioned in this, sorry, NMO is working on some of those in the VDR replacements as well and introductions to removing in the SDK, replacing with the in the VDR, shared RS and Ascar and all that. That's one of the major changes going on at that space. Great, thanks for that update. All right, in Hyperledger, Ursa, bit of a big announcement here. Ursa is being end of life. There has not been so much recent development or time from maintainers. There's some discussion on this PR linked here if you're interested in looking at that, but it looks like the pieces that other Hyperledger projects depend on with Ursa will be moved into those projects, which are Anon creds, Indy, Aries and Iroha. So the CL signatures part will go into Anon creds, BLS signatures going into Indy and BBS signatures going into Aries. So yeah, that's a big change that's happening. Does anybody want to provide any more information there or any questions on that? Char, I can pitch in just a little bit. So the Hyperledger staff had reached out to Ursa stakeholders over the last couple of weeks to talk about the status of Ursa, the progress of Ursa and where Ursa is going. The Ursa maintainers in a discussion that we have with them volunteered that there was a method by which they could help move the dependency components out of Ursa itself so that we're not abandoning the projects that leverage those components, but also end of life Ursa. As a follow on, we just had a conversation in the Hyperledger technical oversight committee about how we go about this in the future and making sure that we are not, even though the maintainers were the ones who volunteered the PR, we're not rushing these decisions and the possibility of going to a step before end of life so that there is some quiet period where folks can coordinate and make the decisions that they need to. So yeah, so we're gonna make some changes, not from a governance perspective but from an approach perspective where we have projects in the future that need to go to end of life. But at the same time, we also don't wanna have projects that are hanging out there and abandoned and other people are picking them up and using them as dependencies who we may not know about, it's open source. We don't know everyone who's using our code within the Hyperledger projects. So we wanna make sure that the projects that we have are being maintained and updated. And so this is a pretty national process. We end of life four or five projects last year. This is just the grooming of the projects that we have and making sure that we have active communities that are not just being built but ongoing. And so yeah, there's a lot of work going on right now in Aroha, Indi and Aries land to accommodate for this change and also going EOL. Yeah, thanks for that context, Sean. Can I say something here? Sure. Absolutely. When a project reaches a certain maturity, the contributions stay low. But if the project is being used actively and it is actually a library, I don't understand this whole concept of end of life for that project and then pairing it apart and putting it into different other projects. You know, there are many projects out in open source that reach a certain level of maturity and after which they are being used all over the place. Sometimes with the hidden bugs, as you know, like log4j, which has been around for 14 years or so. But the point is this whole end of life concept you know, it needs reexamining from that angle. Anyway, that's a different conversation somewhere else but as far as Ursa goes, is the library itself being archived in any state to be used or does it need further development? Could you repeat the question, Devin? The current library, which is Ursa, can it be used, you know, as a library for the foreseeable future or do we have to then now follow these different pieces that are in different projects to get, you know, future upgrades? If someone wants to use the current library, they can. We are making, we're putting a big disclaimer that it is an end of life archive project with no active maintainers and not being actively maintained. Use at your own risk. What we're working on as a community right now is making sure that the projects that we know that have a dependency on Ursa, specifically Indie Aries and Roja. Roja was using Ursa. They are able to transition the components within Ursa that they're using so they're not left high and dry. I still, we still have folks show up in like the Hyperledger Discord asking us about projects Avalon, which were deprecated a year ago. Or someone was using something in a project, they stopped that project, now they come back and they're like, hey, you know, how come no one's updated this? Well, we end up liked it over a year ago. Like that still happens and we want to be really considerate in how we approach this. And then plus one to Sam for not rushing, you're absolutely correct. We are looking from a process perspective how to make sure we're not rushing in the future. But also we don't wanna have ticking time bombs out there that we don't know about or a situation where the maintainers have moved on and we get a critical vulnerability report and there's a scramble to find someone to work on it. So this is, we're gonna find a balance between keeping things available and maturity and at the same time, being good stewards and being good stewards of the projects that we have. Yeah, absolutely. Let's take it up on a separate thread, Sean. Sure. Sounds good. All right, hyperlature and non-codes. Anybody attends this most recent working group meeting that would like to report? Looks like they are preparing for the non-codes workshop that I mentioned at the end of the month and getting updates from the non-codes, the two working group as well, talking about a non-codes in W3C, VC and JWT formats. So lots of good work happening there. See, those are the end of our hyperlature groups that we track, so onto the TOIP and I'll try to move somewhat quickly through this so we make sure to have plenty of time for Clasio's presentation. As far as I could tell, there haven't been recent meetings of the all members meeting during committee or communications committee, but feel free to jump in if I am missing information there. See, in the governance stack working group, they've been giving input on a third generation TOIP stack diagram. Looks like there are some other groups working on that as well that technology architecture task force under the technology stack working group is also collaborate on that as well as the TOIP glossary workspace which is name completion. Let's see. The trust registry task force has been focusing on EU comparison, so comparing with the EUDIARF, which is the European Union Digital Identity Architecture and Reference Framework and then TRAIN, which is Trust Management Infrastructure. So comparisons with what's going on over in Europe. See the trust spanning protocol task force as well has been having recent meetings and workshops which sounds like have been helpful towards making key decisions and they have another workshop planned today. No ACDC. I'm speaking at that one, by the way. Oh, great. Today. Today, yeah. Nice. What's the main topic for today? So I'm gonna propose a hybrid between the encryption and signing stuff that Sam Smith has been working on and proposing and the relevant pieces of the did come to one spec that allows us to gain both the advanced crypto that is desired, but also leverage the existing work but also in a way that allows for independent layers of the stack to be augmented or replaced later as we get smarter moving forward. So there's been lots of discussions in sort of various proposals all over the spectrum and this is my attempt to propose what I think is the cleanest way forward gaining the benefits that we want without taking any unnecessary time or having to reinvent the universe. Yeah, absolutely. Cool. I look forward to hearing about that workshop. The looks like in the AI and metaverse technology task force, Daniel Bachenheimer has been talking about biometrics. Let's see. The utility foundry group there on hiatus. They're working with the governance architecture task force and let's see. I don't believe the ecosystem foundry group has met more recently than us and the concepts and technology working group has been working on their terminology engine version two as well as that technology stack working group glossary workspace. We talked about, you know, I kind of breezed through these two IP updates. Does anybody have any more specific specifics or details to add from any of these working groups? Sandy, it looks like you came off mute. Did you want to add anything? All right. So moving on to the decentralized identity foundation. We've got the do come spec working group who I guess it was the first Monday of the month, this past Monday. Let's see. Sam, do you want to give any updates on the goings on there? Yep. And we talked a little bit about the possible work with the trespassing protocol and that we also are finalizing and actually like next hour and 30 minutes, I'll be seeking approval from the Diff Steering Committee turning that dot one release into a defratified specification that don't anticipate any issues there. The changes made and make it easier for ION to use did come. There was a accident of the timeline and that ION was finalized just prior to the spec and then did come and ended up going a different direction for it and chose the one thing that ION doesn't support for its endpoint definitions. And so a mild expansion of the spec allows for ION to use it easier. The did come was spec compliant before and after but expanding it a little bit makes it easier for that community. And so that's what the dot one releases. Wonderful. So that update. Taysha, I think I've been having a lot of issues the whole day long. Can you hear me now? Yes, yes. Thanks. So I was just going to add something on for the AI and Metaverse Task Force from PIP. So yeah, we'll meet biweekly over there and we're working on, yes, there were some conversations about biometrics from Dan and then also from Venging. We're specifically looking into something called something called authenticated content from say Adobe and other folks like I prove. And the focus over there has been that how do you really prove any given content like when you see some videos, something that's authentic and it's not being fabricated given the advanced AI technologies and that's pretty feasible these days. So that's one thing. And there's also a couple of white papers going on. In fact, one of the white papers I'm walking on is that Identity and Payments in Gaming and because I also had an approved mentorship project under Hyperledger Miesig, which is by the way getting a little free organized today. And that white paper is actually the topic of Identity and Payments, like essentially creating a mini game and then researching Identity and Payments in Gaming and how we can extend that. So like they essentially obviously focus on being decentralized Identity and Payments. Wonderful, thanks for those updates. Looking forward to hearing more about the white papers. Great, thank you. Absolutely, so on the white paper just to add one, 30 second thing on that is that as we're working on this mentorship project under the Hyperledger products, so I'm gonna be doing some joint work with Hyperledger and also under QIP to present the research contents and what comes out of that. Wonderful, that's great that you're using the mentorship program for that. Thank you. Awesome, thank you for those updates. All right, let's see. In the interoperability group, they've been having speakers join to talk about use cases, hearing about pain points that they're addressing and why their technical decisions addressed specific pain points and seeking to recognize patterns and information in interoperability decision-making. And they had a recent, I guess yesterday, they met and had a presentation on user adoption and interoperability from Dan Guresco. And let's see. In the IoT Special Interest Group, they've also been focusing specifically on use cases and sharing of interests and experiences for the direction of work in that group. Are there any other decentralized identity foundation updates that anybody would like to jump in with? All right, in the W3C, as far as I could tell, there haven't been more recent meetings of the did-working group, but let me know if I'm wrong. And in the Community Credentials Group, they've been having their education task force call and traceability call last week. And it looks like next week, they have a presentation on digital trust infrastructure for discovery and validation. So are there any other working group updates that anybody would like to give before we turn it over to Clacio for his presentation? You know, if I may, on the CCG thing, there was actually a bunch of presentations from Putan, from folks working in implementing DI, using SSI concepts in Putan. And so I'm not going to go into details, but I think you could probably share some of those things here, like if some have some links come over here, because they're actually going live on their official government level. So that sounds good. They're also trying to basically have the airlines work with the neighboring countries like, you know, NDI and other places to actually use the SSI for the actual IDing purposes. Yeah, absolutely. Thanks for bringing that up. It looks like the ecosystem foundry group in the two IP recently had a meeting related to that. But if you have any links related to the discussions in the CCG group that you could send my way, that would be wonderful. I can also look as well. So thank you for jumping in with that. All right. Let's see. I want to make sure we have enough time for Clacio. So I will turn it over to you and give the screen share up. Okay. Can you hear me well? Yes. My microphone, okay. Let me share my screen. It looks like my team. You should be good now if you want to try again. Okay. I think I will need to restart my zoom. Okay. Just give me one second. No worries. Does anybody have any thoughts from IAW that they'd want to share? Anybody in this group attend? Clacio is back. I was able to go to IAW two weeks ago. It was my first time, so it was really fun to go and connect with people in the community. There were lots of talks about AI and governance, lots of folks from the government as well joining and excited to collaborate. I gave a session on the Hyperledger Indie Roadmap, so that was fun to spread the word about the work happening there. And also talked about the launch of this group, the merge. So cool. That looks great, Clacio. I can't hear you, though, if you are talking. Let's see. Are others able to hear, Clacio? Oh, it's me. Okay. Okay, perfect. Okay. Can you hear me now and see me now? Yes. Yes. Everything looks great. All good. Can you just tell me that you can see a browser in the middle and have a phone on the right-hand side? Yeah. Okay. So I'm sharing the right screen. That's good. Okay. So hi, everyone. My name is Clacio Varjeu. I work for the government of British Columbia in Canada. So we have been working on an app called BC Wallet. But we have also been working on Aries by Fold, which is the upstream project for our app. We, both of them are open source. Of course, Hyperledger by Fold is open source, but also BC Wallet itself. We're also making that open source. I'd like to acknowledge and thank the community. Some of you are in this call as well. Some companies like NDCSR, Animal and DSR, there's a number of companies, organizations around the world who have contributed in one way or another to either by Fold, AFJ and a number of other projects that really enable this app to work. One of the things that I would like to highlight, I think, Shar, you mentioned in the Acapai call, there was conversations about moving to Ascar. We were struggling with the mediator particularly and how it was not scaling properly, it was not performing in a satisfactory way. So we have spent a lot of time investigating and doing some load testing, performance testing, and that's where we came to a conclusion that moving to Ascar would be our best direction other than come up with our new mediator service. So we do have a demo. I'm going to post a link that you can see. I'm going to run from a diving environment just because there is one feature that I want to highlight but I'll paste in chat the link if you want to follow along now or later, that is you're welcome to do so. This is a live demo, so hopefully things will work, fingers crossed. So in BC we do have this showcase where we provide a number of use cases that are represented by those two personas, one we have a student and a lawyer. The lawyer showcase is the one that we have been working, actually working, it's in production in a limited release. We started pretty small with about 20 lawyers participating in the pilot program and we now have reached over 200 lawyers who are participating now, and we expected that within the next two or three months to extend to the reminders of the lawyers, which is a total amount of about 14,000 lawyers would potentially be using the system. Also shout out to this demo, this demo is another working contribution from the open source community. We borrowed this from animals, so thank you very much. So if you go through this showcase, there's a bunch of screens explaining a little bit. I'm not going to go in details, but if you have the time, you can read and try it out yourself. It goes through the steps of installing BC Wallet, a little bit of background on why Law Society of BC is going digital, some explanation why it's important for court materials to go online. We talk about Law Society of BC is the organization that regulates the lawyer profession in BC. So they're the issuers and they have the authority to say who is an active, good standing lawyer authorized to practice law in BC. I'm going to start by getting a lawyer credential in the, I have my wallet right here, the same process I always scan a QR code. I will see if a credential offer with my lawyer membership card. In the real production, as it is right now, lawyers currently have access to a Law Society of BC member portal where they are able to enter their login, their username and password that they already have, and they are able to manage their own credentials. So they're able to issue a credential, revoke a credential or re-issue a credential. It's important to highlight as well that the issuer Law Society of BC have implemented a business rule that there can only be one active, non-revoked credential at the time. So they do apply a business rule where whenever a new credential is issued, any active credential, at least the previous one, is automatically revoked. So the next step is for going through this showcase, it's to get what we're calling to a person credential. The person credential, it's based on our BC services card program. So that information, we already have them. We integrate with that BC service card holder app. In a production environment, they use their BC service card app and we leverage the identity proving that it has already been done. It has been going around for quite a few years. We have recently reached a milestone where the BC service card app has been installed over two million users, two million devices are currently using BC service card app. And I'm going to show, explain a little bit why we needed the both credentials. So we have here in my wallet the Law Society of BC member card which tells someone that, yes, I'm an active, good-standing lawyer authorized to practice law in BC. If at any time this change, a credential can be revoked by the Law Society of BC and the user will be informed of that right away and verifiers would then have an option to request for approved number of vocation and that's where they would potentially lose access to some systems. I'll go through the use case of going through the card services branch. Card services branch is providing access to card materials online. Currently the service is only provided in person. So the biggest difference for lawyers is that they no longer have to drive to the courthouse and go in person to access those materials. They can do now from their own office, from their own computer anywhere they have access to the internet. This is the proof request that is going to be issued by the wallet. So once that proof request is satisfied they then have access to the system. You can see here on the proof request it's showing two credentials. One the Law Society of BC, the other one is the person credential. I'm going to notice that this proof request does not ask for all information but only what is the minimum information that is needed to access the system. One other thing that from BC we have very strong privacy laws in regards to tracking and identifiers. You notice that we have made a decision and decided to not provide any unique identifier in the person credential. The law member credential, they do have a made ID but from government right now we are not offering a unique identifier which might change over time but this is where we are right now. There wasn't identified a need for the services that we were enabling. I receive a proof request. I can then accept and share that information and the information is accepted on the outside of the system. Some validation process. There is some other business rules here. For instance, they check that the first name and the family names they match. There has been a few situations where lawyers haven't updated the records and their name, there is a mismatch either because they got married or they got divorced, their names hasn't been officially updated yet. There is also situations where lawyers prefer, we have noticed as well that potentially females they prefer to go by their maiden name when they are practicing law. That's a quick demo of our showcase using the lawyer credential and the person credential. I'm going to pause here for a brief second if there is any question and I would like to do a demo of another feature, the mobile verifier that has been one that has recently been put in production. I'll keep an eye for a hands up Shahr, can you let me know? Yeah, yeah, absolutely. I had a quick question too. So in order to access the court records you need to use the person credential in addition to the lawyer credential. Is that to match the names or why are both needed? Correct. That's an interesting question. So both credential mimics the currently kind of a manual in person process where in order to keep or the level of identity assurance the request to provide two pieces of ID. So that'll be the two pieces of ID. So one that is managed by the law society the other one managed by the government by a different party. So from a security and privacy perspective the likelihood of two identities from different issues being compromised at the same time is relatively low but also allow them to rely on the identity proofing process on BC service card app and the government issue credentials are much higher than the ones from loss of sight of BC. Okay. Cool. Thank you for clarifying. Okay. No problem. So another thing that I'm going to demo is our mobile verifier functionality that is recently has been we've worked with the community and it has been currently it's in by-fold. So all of these features the features that I am talking about it's in by-fold. So if you are planning on producing your own wallet those other features are readily available. I'm going to show you a trick. So if you are going through the showcase yourself later on there is an option to enable dev mode where we have access to potentially some tech preview features. If you type the version of the app about 10 times you are unlocked. You can unlock developer options and then develop options are going to enable the functionality of user verifier capability. Their truth capability is the verifier capability. This is enable connection less proof request and they use connection vital capability. We will enable you to generate QR code to connect and you can then provide that connection proof request as well. So how we do that but actually I need to do on the verifier phone which is on this other one. So how we do this really quick. So once that feature has been unlocked now you are going to see those two options one is proof request and the proof request the other one is connection to invite. The reason being that those features are gated for now we are not entirely sure how to present that in a user friendly way. Our user researcher experience has been doing some research and doing some analysis and prototyping about how the users would better understand this feature. From this one I am going to send a proof request. As proof request right now we have decided to sort of embed baked in a number of proof request templates within BC wallet. Right now in by fold there is no template so it is up to each wallet distribution to define their own. For BC wallet we have decided to create a proof request and plate around the credentials that we couldn't have which is the credential and the person credential. So I am going to do perhaps zero knowledge proof that ask if someone is over 18. There is a little bit of typo here it says over 19 but it is actually request over 18. So it generates a proof request it generates a QR code and within with my other phone I will then scan this QR code and I use a credential that I don't have. I am going to have to get that from another wallet. I will decline I will go through this showcase and get another set of credentials. We have been working on these features very actively so one of the questions that we are working on is the credential branding OCA branding and one of the things that we are working on is we have a number of showcase and demo credentials is we are trying to experiment with how to make those credentials how to highlight that they are not for production. So that is something that is ongoing we will generate a new QR code on the left side ok there we go. So now I created a proof request I can then share that information back to the mobile verifier on the left hand side it takes a little bit but that information then has been received it gives that green banner again all the cryptographic signature and the requirement has been validated and therefore it gives that green banner it should always get. We are working with the concept of maybe this is you are working a kiosk and you are trying to validate a number of people one after the other there is always an option to generate the next one and maybe the next person can then scan the QR code share the credentials and so on and then you always have an option to keep going generate a QR code validate next and so on. Ok so now I will go back the other way that you can do that mobile verify is I can create a connection and then I am going to be connecting connecting first with the device and then from here we do have the messaging available so let me go back here I see the message I can type a message one side it is going to show on the other side and so on so from the mobile verify if I already have a connection I can also send a proof request from here this one will not create a QR code it is just send a proof request I will do the same proof request here send this proof request I am just going to go back a little bit I received the proof request I will share that information now the verifier will now have that information to have the option to open and see the information that has been shared and I will stop here we are almost over time and I will give a couple of minutes for questions great demos really interesting to see the flow of using your credentials to access court records and the zero knowledge proof and messaging to a nice interface and user experience a user experience is something that we are very committed and we have been working quite significantly if we want to release that to the general public it has to be very easy and simple for the average person to understand and go through the flow yeah absolutely we are getting to the end of the hour but does anybody have any questions in the last few minutes I was just going to add to your point I think this is a way to get to see thank you very much one quick question do you have any send box that let other people come and play yes so I will paste the link in the chat that is public available anybody can go and play with those flows as our SBC wallet itself it is public available it is available on the app stores anybody can download them great thanks and I think the only thing I want to add especially when you are talking about you showing the does it zero I am sorry the yeah thank you for helping me with that so the ZKPs I think one thing I struggle with I am just showing somebody's name in a lot of situations they are not there because yes if you are just going to a movie or you can just flash a name and maybe a picture the combination of fake ideas with the fake pictures and all that coming in I think the question becomes how much additional proof you need to really show that it is actually you you are not really showing somebody else's face not really showing somebody else's name and things like oh I am over 18 I am basically admitted to this place here because here is the binary decision on that so from Marius case perspective we begin lawyers they follow the rules to the T because otherwise they are subjected to getting to their privilege to practice law revoked so there is a number of things here there is the the trust registry part or the governance side about the verifier needs to know what credential from what issue they trust so it is not just a matter of asking for an individual name or age or validating that information as well or maybe ask the question about do you have the name from the member card issued by Law Society of BC and the same thing for the person credential I want that name from a person credential issued by the government of BC as opposed to anybody who can create a person's scheme or anything like that so it is a little bit of the governance around that the verifier can codify that validation on their side as I said we do leverage the service BC identity proving process so that means either you have gone through the process of validate identify yourself that you are who you are in order to get that person credential as I said that's what raises the level of identity assurance and if the person has the authority to somebody else to use their credential that's already kind of it's almost like fraud so again they are subjected to the existing laws in place right now I think I'll probably get my some questions because I'm sorry I also have a hard stuff but I do have some follow-up questions I'll probably circle back and I think maybe one question Shah I'm assuming you're going to capture these links here and place them on our wiki yeah I will do that right after the call thank you so much yeah yeah absolutely wonderful any other questions sir can you please put my information contact information the agenda on the wiki yes I will do that if somebody want to reach out maybe they can reach out to my email yeah absolutely I will make sure that that is on there well thank you so much Claycio for a great demo and presentation super interesting to hear about and thank you all for joining the call and for jumping in with working group status updates and yeah we'll see you all in two weeks thank you Shah thank you very much thank you bye thanks