 Hello, hello. Hello, hello. All right, let's start with removing this bot from the meeting. So with a moment, see if we have any other joiners today. All right, let's start off. So I'm sharing my screen and adjusting case just to be consistent. And I'll still display our hyperledger and I trust policy notice. All right. So let's get into it. So for the start of meeting discussion, a copy paste at this points from the last week, there's not much of updates here, but I believe, I believe that, well, we can actually take a look. So the mentorship program should be able to find some links. I was posting previously. Where could it be? Well, it's a little bit difficult. Oh, there we go, there we go. Any updates if our project proposals got approved? Nevertheless, the proposal review timeline goes still today. So it should be completed by today. And let's try to see if there's any updates on our particular project. But no, they are all still pending review. So no updates here. I guess we'll have more news next week. Just a short good first issue review of this initiative. So I think there was no new good issues created. Nevertheless, the two issues, which our contributors have picked up are still ongoing. Plus, I know there's one more person who's now picking up this testing task to write some unit tests. So I guess we should be expecting some PR. Well, and that's four days. So let's move to the overview of the recent work. So we finally merged the brand new messages created. That was a huge effort. Lots of comments on this and lots of comments, especially lots of time and hard work. So this is done and it's not being yet used. It's not yet integrated within the code base, but it's ready for being used. Great. Great. Just know that this was a great job. Worked on really nice. Yeah, the integration is in progress. A bit of a pain in the neck, but that's how these things go. And there's no PR just yet. There is a branch. I created a branch, but I didn't make a PR yet, especially because there's like this kind of has to be a whole or nothing kind of thing. So I'll basically make the PR once everything is integrated in general messages, like the old messages. Great. Maybe just as a note in terms of how the integration is going. So it's like, this isn't necessarily something that we will, I know, maybe I'm not choosing the right words, but not necessarily something that we'll be particularly proud of is more about retrofitting this so that we can actually start with that very CCX as well and the state machines and everything else. So just that we have a consistent approach. And you know that you and I have been discussing about this, that it is annoying that and maybe I would sometimes feel like better off just to start from scratch, but that would also be a great effort and create some stuff. It's definitely not a good approach either. So it doesn't really seem to be an easy way to go about it. But we'll stick with this retrofitting and just ensuring that everything still works as it used to before. And then we want to better start and refine the CCX. Yeah, I see. Thanks for update. Just wondering, would you mind to push like a published that branch you have, it will be maybe published. It's published. It just not. Yeah, there's no PR on it. And I guess the main reason why I didn't make PR from it is because I don't want to keep canceling the, the CI stuff. As I said, because things are not really working right now since I'm in progress with replacing the message is great. So until everything until it gets replaced everywhere, the CI is just going to fail. Yeah, maybe maybe I'm thinking, maybe I'm thinking like, that's a good point. Like, because it is, it is annoying to like cancel it all the time if you've pushed a lot. And maybe we could make a tag similar like we have some. So we could make a kind of a tag like skip CI entirely. And then you could perhaps create a PR as a draft. Like I would personally appreciate it because then I could see like, you know, very easily and like see if I'm changing something, I could easily see like, oh, if I do this, we're going to run into conflicts. Maybe I shouldn't change this part right now, you know. All right. So we can do like a small CI upgrade. I'll just note it here. So we kind of go ahead of ourself, but that's fine. Create CI, create tag to skip CI. So yeah, that was the message is too great. Now continuing in the overview. Yeah, we have merged this guidelines which we've been discussing actually on like our previous two calls so far and then a little bit more on the PR review of this document. So it's a number of main kind of ideas which we should follow when we implement state machines going forward. I'm not going to go over again because there will be the third time and we already covered it. It's here for anyone to read. So just leave it at this. I'm going forward. That was a small refactoring from myself around the profile layer of VCX where we, which separates the underlying libraries from the like Aries business logic. So that was just some refactoring in that area but nothing significant, no changes of logic or anything like that. Next up, yeah, there was two more PRs merged from MiraSLA from Mira and those were about the approach we were previously taking in our Node.js artifacts where we declare peer dependencies and kind of misuse them in a way. So here Mira is, Mirgi is explaining the way the stuff we changed and basically it's changing the package systems, packages and files and declarations for Node.js artifacts we are publishing. Yeah. And then that's pretty much it as for the work we've done since the last meeting. Yeah, then we have a check on progress. We already touched on this. We've done this busy now integrating the new messages created into Aries VCX. We'll create the job for skipping CI. So this ongoing work can be visible as a draft PR. And then, yeah, we have also this refactoring going on from Steven. So there's been a review going back and forth. There's still some pending items here to be addressed, but the last ones this is done. I think it'll be a nice improvement around the issuer portion, issuer side in particular creating the encoding credential values. That should not pose any significant risk in terms of conflicts as that's pretty much separated from the all of the state machine stuff. So even if someone starts doing some state machine refactoring, it shouldn't significantly collide with this refactoring. Yeah. And I think that's it for what's going on right now. There's an upcoming work. So obviously the messages integration that's going to take a while. And then, yeah, we have the state pattern refactoring pending kind of open question is if and it's kind of, it's too bad that George is not here today because I had one thing to discuss with George. In terms of whether or whether we should not try to align the existing state machines, at least partially with those state machine guidelines we have put together. So I actually have a PR completed, not PR a branch completed where I've modified the holder state, the existing holder state machine such that it doesn't have any sent states. I removed a bunch of bunch of IO from the state machine and pulled it up onto the handler layer. But then at the same time, I know, so it was kind of an exercise for me just to see maybe how difficult it would be and it wasn't. But at the same time, George has open PR where he already started rewriting the state machine into the type state pattern, although it's separate. And I guess there's like, this will yet to be kind of reworked because it doesn't follow those guidelines yet. It has these sent states. And therefore I assume it also contains IO. But yeah, I'm just not quite sure if I should, if we should be doing the work. I would deeply appreciate it. We wouldn't be merging stuff into your BCX right now unless like, yeah, and that's the second thing. Exactly. So that I can finalize this messages integration because if things change, then I have to change things as well. Yeah. And I think a lot of conflicts. Yeah, you are the second on my mind also. I mean, I know that you'll be having a Delta's all over the place. So I don't want to make it more, more difficult than it already has to be. Yeah. I have that branch. Maybe I'll like, maybe I might use it later may turn it into PR after, after messages integration. We'll see. Also we'll see what George or other people's opinions are on this. So I'll just hold back for now. And yeah, I guess that's kind of it. I covered everything. It was a short one. The end meeting discussion. Yeah, I already touched on this just now. And I personally don't have anything else to discuss today. Any, any items on, on your side book them. Nope. It was a quick one today. Just went through, run through the agenda. Got a couple of updates. Busy with work. So we, we all, we both have 40 minutes of our time back to our day. So let's, let's leverage it. Thank you. Thank you.