 Hello, everyone. Hi, hi, hi. Hi. Hi, Nan. Hi. Good afternoon. Yeah, good. Good morning. Yes. All right. I guess let's start. So let's see if anybody else connects while we are kind of kicking it off. So I'll share my screen. Just a second. Just need to do a little set up for my friend sharing. One more moment, please. Okay. Almost there. All right. So welcome to July 13, 2023. Here is V6. High-pleasure anti-trust policy notice is in effect. And let's get right into it. So, yeah, there's no introductions today. We all are familiar with each other. No new members today. So we can skip that step and just go into the mentorship updates. So since I think we had the one skip meeting last week, I think just before that we have completed these project plans for our, oh, what is this? Okay, this is a wrong link. This is not what I wanted to put here. Let me fix that real quick. Is this built wrong? Oh, that's good. And the lights is trapped. That's strange. Okay. Either way, I'll fix it later. Works in my browser. So we have project plans for the mediator and for the mobile wrapper. We have a nice checklist here of the stuff which has been done. So we can watch the progress kind of life as things are progressing. Yeah, and we have also the same kind of a plan for the pi wrapper. We have only nine on the call today. So would you like to give some kind of update on the mediator project? If you have something, it's fine. If you don't feel ready, it's fine. But if you have something to share how things are going, you can do that. Yes, I can give a quick update. So as you can see in the project plan you can see the website. The one you just linked earlier. Yes. So we've started on the HATT server. Finally finalized on Axon framework. We have done the research and selected it finally. And we have now started the coding parts. So initially I've been doing a scan it in service and that's been going nicely. CI and everything also is being put into place. I haven't linked the project there, but I think that was great. Yes, so we've got CI on there. We've got implementation of an E2E test and just included logging. So yes, the basic structure is taking form now. This week I will be studying the pickup protocol and about using database to store our messages. So that's what we'll be doing this week. So thinking, yeah, taking stock of all the protocols and the details and trying to formalize a structure in the database and stuff like that. So that's the stuff that's going on right now. Formalizing the data structures and the rough sketch of what the media service is going to be like. We need the data part. Yeah, that sounds good. Sounds like a plan. Yes, thank you for the update. Is there a repo where we are pushing the comments where we can have a look? Yes, yes. Maybe we can post it in chat. Yeah, so you can just post it in chat and we can have a, oh yeah, awesome. There it is already. So this is the test server. It has just the basics. This is not going to be the mediator. This is like the sketch and structure. Just to try things out first. And then this is kind of the basis for how the media is going to be. So we're just doing the basics here. Yeah, yeah, yeah. Right. Okay, okay. Cool. Right. So let's go further. About the, we don't have a softmail here, but I'm neither George today, but I did see that there is, that there is some for the progress and there's a PR. Initialize unified demo and script. So it's quite a chunk of code, apparently. So this is in progress. I'll have a look at it later and see maybe from a softmail. How is this some sort of update? What's the state of this right now? I think, I think George left a message about me missing this to this meeting. I'll have some updates at the end. I'll need to review the union if I build script ASAP. So I guess it was about the PR. Right. Then next up, kind of overview of the work done. So we've completed in the past two weeks, migration from VDR tools to credits migrating the wallet. We already have the like code support and the integration support for a credit library for a while. At the same time, we also did some changes to libcx to be able to run it with credits and on credits and in the VDR ledger client. There's a PR still open with this failing some one random test. It's very close to completion. So hence, I just put it here. Then we had UniF5 wrapper. We covered that. We have under review PR from Bogdan about adding support for migration through Node.js wrapper. So this is yet to be reviewed. Looks pretty simple. And then we had messages create, fix. I don't exactly know what this was about. Bogdan, can you shed some light? What this fix was about? Yeah. So in like a short, it was about updating bumping the third day dependencies and the fact that some internals and third day changed. And that was messing up the release message deserialization. So this not only takes care of that, but actually simplifies the release message deserialization so that it relies on less internal stuff from third day. So that should essentially lead to less breakage in the future. I actually am not expecting this to be happening ever again. The only things that are now internal and used from third day are the buffer type, the content, and the content deserializer. So these are pretty much there to stay. There's actually, I don't know how to name it, but there are, it is being planned to basically expose this as public API at some point, rather to allow implementations of this, which relies to provide their own buffer types. But that apparently is pending on the default associated types, which are still unstable. Yeah. So I honestly don't expect this to be happening anytime soon. So here what changed is that tag, what's it called, tag content visitor and the other stuff that was being used there regarding that. And we no longer rely on that. So that should be, that should be fine. If by any, I don't know for any reason, we're still going to have problems in the upcoming future, maybe in the near future, especially then, I guess we can change it and just rely on public stuff. Even though it would be a bit sad, but nonetheless. Right. And maybe for people that are not up to speed regarding what this is about is basically just our makeshift implementation of a tagged enum, because that's what the messages are. And this allows us to basically deserialize, like further deserialize into a specific message type based on the message structure, message data type, let's say, based on the message type field itself, which would have otherwise been convoluted or annoying or complex. Right. Cool, cool, cool. I think that kind of explains it. I remember when we talk about, I mean, I remember when we kind of, this looked a bit mysterious at the time of merging the PR and there were some concerns that if the API changes, it actually happened, but it's good that we, I mean, as you explained, it should be a right. I mean, it's not biggie. Even now we solved it with ease. Yeah. So it was mimicking the, the derived implementation that Serdi provides for types when you, because that's where the inspiration came from. And it was mimicking that more closely, which it doesn't do anymore. It's a more custom made, let's say, or tailored for our use case. I see. I see. Thank you. Yeah. By the way, I think we have, we got a Abishek joining the call. Welcome. Just maybe I'll just stop for a second. Abishek, would you like to add anything on agenda? If you have anything particular, you, you, you came here to discuss or something like that. Yeah, well, hello everyone. Yeah, so I'm just trying the iOS demo to the CX and I installed the latest V6 framework as well and studying the header files of Swift. So at the moment means, yeah, Patrick has helped me in various, to understand various fundamentals and concepts. So I think by the next week, I will be able to contribute to you guys as well. So for now I am just trying the V6 as demo and once I will, I will be able to hit all their functions and matters properly. Then I will try to update the repository as well for the latest core. So that's my plan at the moment. Thank you everyone for helping me out. Okay, so I see where you're coming from. So I'll just put here in, in case you, you know, if we have like a time left and I think we would, we can like further maybe, you know, talk, like talk a bit about V6 or whatever comes to your mind if you have some questions or anything. So I'll just put here like V6, like V6, this question. All right. I'll just put it there. And let's, let's continue in the, in our agenda. So we covered this one and then, well, it's pretty brief, I think. So it's stuff in progress. I think it's pretty clear what we are busy with. So, so we have kind of a research about the credits to unencredited RS migration right now ongoing by Bogdan. And then we have did exchange stuff. Also, I would say like research because it's like pioneering kind of a new approach for the state machine implementation from, from Mira. So maybe let's, let's stop at the first point. If you could kind of give an update, public update on this, on this, on this progress Bogdan. An update. Yeah. Yeah, basically just trying to accommodate that essentially let's say that our infrastructure was mainly built around Indy and unencredited tries to be or aims to be, I guess, ledger agnostic and that poses some problems in terms of implementation. That's, that's pretty much it. I'm still working on retrofitting it, but not retrofitting, but just fitting it into our, our current API. And still struggling with that from, from some aspects, particularly the replication is something that, and everything related to that is something that's let's say drastically changed. Yeah. So not really much of an update, really just trying to, to figure it all out. Yeah. Maybe just, I mean, I'm kind of repeating myself, maybe from like other calls or even like private calls. But, but if things get tricky, I think we always have the option to, I think kind of keep all the API, kind of, well, just try to go with that approach that we wouldn't try to preserve issuance of the old, based on old credential definitions, post migration. And, but I guess we would need to keep the revoke. Okay. That's the tricky part actually. Right. Yeah. Yeah, I mean, bottom line is that we could sort of disregard what we have right now and start from scratch, but that means we cannot really properly test it. I mean, we can, but that would involve like a lot of work in its own right. Whereas if we managed to implement it into our current infrastructure, we would be able to reuse all the tests and everything that's already in place, especially from a migration standpoint, and ensure that things keep on working. So it's really a chicken and egg kind of problem. You either do it separately, but then you cannot really test properly or you try to make it and force it into our infrastructure, which is really painful, but then you at least get to be able to test it properly. And maybe as well worth mentioning is that the overall plan is if like when this is ultimately done and it works and we have tested it thoroughly, we can pretty much drop the credits and video tools implementation. So this will be the only one because it relies on the actual on on credits V1 specification. So that's supposed to be universal at least. So then this won't be a problem anymore. It's just a matter of really this this transitioning that we want to be careful about. And that's posing problems as well. Yeah. All right. Well, we'll see. We'll see how things go. How things flesh out after a week. I guess maybe we'll have some clear idea picture. Next up that did exchange protocol. I know that you're also like facing various challenges and you identified some some possibly like preliminary like work which could be done. So can you can you do some sort of like update or you know share your thoughts on things to be done maybe ahead of the exchange itself. Well, the update. There is a very group like incomplete hacky and just very, very bad implementation. If you can call it that ready right now. And I'm trying to get a very basic end to end just passing to have at least something. But as you know, there is still as you said, there's still a huge list of to-dos we need to get to before we reach any kind of acceptable level of implementation. And so what has been done so far was mainly kind of to do discovery, I would say, rather than reaching some kind of robust or even usable implementation, I guess. So I have those to-dos prioritized and I will just be going through them one by one when I'm done with the test. I guess like there is no need to like go through these to-dos right now. Like there are some are bigger, some are smaller. Most of them is just like they are not particularly difficult. There is just a lot of them. So there's like no blocker except there is a lot of to-dos. Well, that's kind of better, I guess. Case one. Although there is lots of to-dos, at least we know what to do. We include less about it. And also everyone beware that like Miro is overly self-critical. So I'm sure that implementation is not as bad and hacky. All right. Yeah. So I guess after we have this, this will be kind of kind of canonical example implementation for the next state machine re-implementation. So it's good to have a high bar and this will also enable us like a much better testing. And then we have one more item in progress from George and I think that's kind of relates, basically it's kind of a simple mediator. Extremely simple mediator. Just like a message queue or like message store or something like that with just a few end points. I think this is mainly to help out to shield him off from complexities of the message, you know, football message mediation. So just kind of very simple message story could use. And also I think George wants to use this in a kind of Alice Faber demo, showcasing how RSDCX can be used. So yeah, this is in progress. I don't know how far off, but I don't expect to be this like too complex. So it might be that this is almost close to completion as it is, I think. And what else? That's kind of it, I suppose. Let me check out pull requests which are open. If there's anything I have possibly missed. And so you need to find from Swapnail a migration. This is mine. Just to be fixed the last test there. We have the relay for testing and then some older PRs. Most of them stuck for one reason or another. I don't think these are going to be much in time soon. Yeah, so I guess that that's it. Upcoming work, busy with critics, busy with the exchange. And I guess one more important like item will be the ATH back channel update mirror. Is this something you are planning to do in the end before the exchange? Or what's your thoughts on doing the That would be like the best way to verify that it works. The digital implementation. To update the back channel and try run the exchange test against other frameworks. Yeah, I'll be definitely create confidence confirmation. I guess after we have our own local test right there will be maybe the reasonable next step. All right, sounds good. So that kind of brings us to the end. Now we have like time to spare. So if you have anything you would like to or anyone actually also Nayan or Abishek or anyone else. We can we can spend some time. So maybe before we like go into here. Does anyone else have any any kind of a topic or thing you would like to discuss together? So should I go ahead? So I think we can go ahead. Yeah. Okay. So as per your suggestion I was looking at the question that is given my purpose is to generate the invitation link so that I can use it in our methods. So currently provision button is working partially working fine because I'm going to be able to get use the media to link and also getting the response from the unit method, but later it is a few seconds it is breaking maybe in some background. It is breaking which is on low priority at the same time. So I think it is working fine. So my next step is to test the invitation link and accept proper. Except the VC. Right for that. I need to use some favor or something to generate the except sorry invitation link. I we also have a means temporary server where we are generating the VC. And the offer the invitation link but maybe we have to generate the link so that it is not working in our demo. So for now. I'll just stop you for a second. So now when you are like doing this testing, are you using that that third party demo? For the application. Yes. So that means that the version of VCS does the version of VCS running in that demo. It's probably fairly old, right? Okay. Yeah. Let me check that actually. So we have where was it? VCS. VCS. And I know if you are linking demo from here or not only VCS. And you are using. This one. Yes, second one. Yes. I was demo and let me see. I can buy a chance find out what's the version of VCS here. Some pop file. Maybe not. No. 042. That's like very, very. I bump VCS to version 042. Yeah. So like that's like really, really old. Like. Well, according to the last at least three years old. So, so I don't know where it depends what you are using to generate invitations, but you know, chances are that perhaps since this has been released. The maybe the. The, the kind of the modern invitations you might generate from some library. They look a bit different than what we worked with three years ago. So it might be difficult. I don't know. I'm not sure what would be. What is the latest version of VCS. The latest version is 50 056. So that's like 056. So that's like, you know, like. It's almost like 40, 40 releases ahead. Well, three years of time. So. Yeah, like the, the, you might try it like accepting the invitation. I don't know. You might get it working after all it was, it was like standards which didn't move so much, but it really depends. I guess what software you are using to generate these invitations, but it might work or it might not. And there won't be like, there's not a reasonable, like easy way to kind of support you if you run into any issues. So it would be, it would be like my, you know, maybe you will definitely, it's longer road and maybe, you know, you run into different challenges, but at the same time much more straightforward. If you rather try to update the V6 version to, to the latest and then you'll run into like issue. Oh, some function maybe doesn't exist. And the API is a little bit different. You'll have to fix thing or two. But then once you reach the point that you are trying to accept invitations, then it will be much more, you know, easier to argue about or debug or try to figure out what is wrong because it's the latest version and it's working with like a copie or these like other issuers, the other frameworks. So I would recommend to primarily try to update the V6 version first. Now it will be easier to, you know, to kind of argue about. Okay. Yes, perfect. So yeah, I already downloaded the latest XC framework already and it's stored in that separate POC. So I am trying to implement it. But first of all, I'm understanding every method. So that's where I'm at the moment. So can you guide me in a different, in a second position, like how to generate the invitation link if, if I will be able to run the new XC framework. Right. Yeah, so I guess one way it would be you could use the V6 framework itself to, you know, to kind of build kind of a server application for like generating invites and accepting connections kind of like server side agent or maybe easier. Again, just a different type of challenges. You can just run the other option will be to just run a API. Are you, are you familiar with a copie? No, no. So there is a, this like very popular. Institutional. Not a copie, a copie. This is, there is this popular implementation and it's like server side. So this is basically a service which institutions would typically run, you know, like some, some company, a favor would run this and generate the invitation and use this to issue credentials. You know, this is like a full-blown like REST API with the DITCOM and VC areas capabilities. So we can run this, I think in Docker and then generate, use the REST API to, to create invitation and then pass that invitation to your, you know, to your mobile application and you should be able to establish connection and then consequently you would be able to issue credential through this API. It will be easier than I guess building your own issuer. Okay. But yeah, it's a, it's like based on Python and it can be sometimes tricky to run Python stuff locally. I think, but I think you can run it in Docker and there might be a lot more straightforward to get, get, get up and running. I'll post it in a chat so you can just have a look at it. And maybe one more thing to just kind of give you heads up about is that, you know, we have, we are running this mentorship program now and we have two mentees and one of them is like working on the UNI FFI Aries V6 wrapper. So as you might be aware, we have this POC right now with a little bit of code. There's not much rate means it's kind of a work in progress. And we have this mentee kind of working further on this. Here's a PR now. It's lots of lines at it. I haven't, didn't have a chance to review it, but apparently they're just, just to let you know that there is, you know, work on going on this. So maybe, maybe eventually like within a few weeks you would have like kind of a, a third option to, to try to go with, you know, this UNI FFI. Okay. Okay. Anything else from anyone? Just one thing. Am I audible? Yeah, yeah. Go ahead. Yes. So tomorrow I have a, like I'm giving a tutorial as a little workshop. So is it fine to. Delay tomorrow's meeting to next Tuesday? Yeah, sure. We can, if you can, then we can shift it to next Tuesday. That's okay. Yes. I wanted to make it, but the, the tutorial is at exactly the same time as I said in meetings. Yes. Yeah. It's okay. Or if you want, we can just move the time tomorrow, but if you just can't attend, then we can do Tuesday status update. That's okay. Yes. Yeah. So Tuesday would be good. And I will try to get in touch with you and also Bob. You mentioned, you mentioned about the message. So yes. I will get in touch with the team today itself. Okay. So a few things. Going over the code and stuff. If possible, I'll get it done today itself rather than doing it tomorrow. All right. All right. That's cool. Yeah. Okay. All right. So I think we can wrap it up. You guys get five minutes back. So thank you for connecting and have a good week. Thank you. Have a good one. Okay. Bye.