 Hello, morning, morning. Hey, so let's get started. It's like it might be just two of us plus our innocent utter innocence other pilots today. So, nevertheless, this is August, no, this is August 10th, August 10, 2013, RSVC experimental and I trust policies in fact, and I was good into it. We have someone else. Oh, I met her. Yeah. All right. I think it might be a brief one we'll see if anything if we if we enter any sort of rabbit holes there. We don't have our mentees, but nevertheless, I had a update from George that the PR for the union by stuff it should be coming soon. There's just some very some minor minor tweaks, which soft belongs to do, and that should be ready for review. And likewise, likewise from nine, nine just connected here and nine is connecting microphone and alia. Let's give her a chance. I was just mentioning, you know, going through the like mentorship status and I was about to describe your status updates and say I thought you're not here today but you just connected in very in that very moment you, you appeared. So. Yeah, I so you left the pull the pull request for reviews. I know I did my review yesterday. Yeah, I'm working. Yeah, cool. Yeah, but other than the I mean so you know I think generally looks good I just had some like remarks mainly about the storage and kind of stuff which stuff on top we kind of stuff implied from that story does database schema design. But in general, I think it's good it's it's in a good track. But I'm curious how you are progressing in terms of the areas V6 integration. If you had a chance to roll into that. I did go forward with it so there is some progress. So there was some more dependency issues like yesterday at the program session and we saw some of the dependency problems. So there were a few more and I have resolved them right now and now it's building properly, like that module is being loaded, and it has built completely. So now the next step is going to be to execute the initializing function inside of my main. So now it's just a module. So it's building properly and dependencies are satisfied, but I haven't actually executed it inside my main. So next step is to do that. Yes, so that's where we are right now. So hopefully by this week, the end of this week, I'll have an agent that's in a way alive, I guess, inside my repository. And yeah, about the PR review. Yes. Thank you for the review. And I'm working on the suggestions that you mentioned. I've also responded to some of the comments right now. I'm working on making the changes that you mentioned. Cool, cool, cool. Sounds great. Looking forward. And I can feel your excitement and I'm very much sharing it. It's awesome. All right, so let's go on. So yeah, I mentioned Sopnil's PR is going to be soon ready. And then we didn't have, I guess, significant PRs merged or anything since last week. If I check the closed PRs, I don't think there was much stuff there. There was some README update, but yeah, other than that, there wasn't much. But perhaps one thing which kind of came to some sort of conclusion was the state machine PR from Bogdan, as we kind of had lots of discussions about it. We kind of agreed so far on kind of the ideas which Bogdan drafted could be still applied, but we would like to have that rather on the upper layer on top of Aries VCX rather than making it part of the core, like what is currently known as Aries VCX. So maybe something like Aries VCX framework could be built on top of Aries VCX. And over time we can build out ATH and N2N tests and perhaps even the UNIF5 wrapper so it could be used for mobile maybe and basically it should be, this is the kind of layer it should be handling persistence or perhaps even convenient message handling to shield the user away from all the error conditions and perhaps like retries and stuff which people presumably commonly want to do and certain things happen in the state machines. So that's the layer which might be handling that. And yeah, I guess for now we will just keep our ATHs, but if this comes to existence then we can start kind of building our existing components on top of that and making them a bit thinner. That being said, I don't know, Bogdan, do you have any more comments or remarks or any new thoughts on state machines? Nothing really worth discussing now. Okay. Now move on. We have we have interview bunch of PRs. We used the one for the Individ-DR migration that's been already reviewed by Mira and working on addressing that. It's been tested thoroughly and it works pretty well. For some reason, it happens to, I don't know, with the old ledger implementation, it somehow managed to ignore the badly, it managed to ignore or disregard misbehaving nodes. So, out of the box, actually the old implementation was faster, but this is equally good if you make sure that there's no misbehaving nodes on the network you're using. At least there was sovereign staging that, by the way, we notified the sovereign about problematic nodes, so hopefully they'll get fixed up. Yeah, then there was this ancient PR also ready for review. This is removing open SL dependency, which is not needed anymore. I just already approved it, but you guys have a look and feel free to merge it, if you think it's good. And lastly, one more PR from me. This is built on the ledger, on the VDR tools, the 911. This is adding capability to write, endorse for the ID. It's very specific because that's what we happen to need, but this can be easily generalized to support writing and arbitrary roles on the ledger. So, I don't know, you might want to actually, I'm expecting maybe some remarks about that. So, if we want to generalize it, we can do that easily for sure. So, we would be able to write only endorse the role, but any role. And then in progress, we have a revocation state picks up from George. It's addressing issue he has created a while ago. It's just described here. This is still in progress, so we'll wait for George to give update on it maybe next week. I understand, Bogdan, you started or will start on the products update? I will, yes. Okay, cool, cool. That'll be great actually. It might be pretty simple, I don't know. I gave it a step and it was more than just updating dependencies. So, I created a placeholder and get it, make sure we get it addressed soon. It should trim off all the dependency tree and also it will be better to complete the credits migration when we know we have the latest credits in place. And then did exchange protocol implementation. It's in the works still. So, effectively, well, Mira can give an update, but as I know, it was updates in terms of ATH interrupt and there's some outstanding challenges. Mira, do you want to give update on the dex change? So, well, an update since last week is I learned some refactoring. And so now the code is more or less ready to be seen without the risk of making anybody blind. But besides that, I also implemented or made basically all the ATH tests work both ways except one where a KAPI actually performs attachment signature verification, which fails. So, just months ago, I made a quick and dirty implementation of the JW signing of the attachment decorator. And, yeah, right now I'm trying to find out why a KAPI doesn't like it. So, but besides that, like, there are still there are still plenty of to lose across the code added but and what one last but probably big bigger outstanding issue is that I actually need to write some integration test, especially for the scenarios which are not tested by ATH test. And that I can open a PR or I can open it even now if somebody wants to see it for some reason. Yeah, but that's about the state. All right, thanks. Thanks for having me. And lastly, well, as to my migration, which my wall migration node jazz you just already implemented long time ago by by bog down but then we had to revert it because of some all the dependency complexities and like in the VDR and all these modular lips and VDR tools of some combination of features, which caused the compilation to fail, but that will be fixed now, as we address the removing VDR tools later client and dependency three shrink down the bit Those issues should be overcame now. And yeah, I guess that's actually it. There's nothing more an agenda. It was a quick one. Unless anyone have anything else to discuss or bring in. I guess there is nothing more than and we can rip it up. Have a great rest of the week. Thank you. See you next week again. Have a good one guys. Thank you.