 Hey, hey, long time no see. Yeah, some back Back from holiday Yeah, yeah, I had like a week or so. It was good Did you travel somewhere or just stay around? Oh No, there was a festival in Byron Bay that I went to So it was like being type thing. Right, right. I'm gonna Hey, those are festivals some sort of music festival, I suppose. Yeah, yeah, it was Camping like multiple days that kind of thing. Yeah, nice. I'm not sure if Oktan is joining. I think he mentioned before But he's actually not Not gonna be able to join today, but he's online So, let me just check. I think that's the case because usually Bogdan's one of the first to connect So I guess we'll just get started like this But search and there'll be stuff to discuss and some things to get you up to speed which you might have missed And it's been a while and there has been things on the move and Things on the horizon So let me just Prepare some of my Windows here on my computer. I'm almost ready. It's good. Let's find the Aries Vcx big page and Let's get started Ah, we have a man as well. Hi, man, you're just getting started. You haven't missed anything. So Now that we are all here Let's kick these off What is Yeah, okay. So yeah, welcome to July 2007 2023 Aries Vcx coming to call Hyperledger and Tetris policy is in effect and let's see. What do we have on agenda on agenda today? Maybe before there's no new No, new new joiners So Just before we start I want to make sure that we have everything listed on in our agenda. So Is there perhaps George or an ion or Mira anything you would like to add here? Nothing for me. Yeah, nothing for me I don't think so All right So let's hop into them Mentorship updates. So like since we have you on the call and once again Would you like to? Just say a few words about your your status and how things are going okay so Right now we are quite on track in regards to the expected project plan that we had and So currently I'm in the storage parts That's coming in nicely The storage trade is being finalized and that's going to be ready by this week the next parts are the integrate with ABC CX and support establishing Died com connections. So that's for later right now. The storage part is like it's Coming to an end mostly. So I have a Understanding bigger protocol is done and designing trades is in process My sequel implementation is being done in parallel with the designing of the trade and yes I'm also including unit tests along with all of this. So yeah, the storage part is going to be done this week Great, I think actually we could go ahead here and You know, I'll leave it. I'll let you do it I think it's kind of satisfying to make those check tick those checkboxes yourself. It's kind of rewarding So I'm not gonna do this for you. I think I think you could actually check some of them I mean even perhaps like including airs you see exist Project dependency we kind of went through that and it compiles now It's just a matter of like initializing and actually start integrating it So there's still some work to do. But yeah, I think I think you can Yeah, you know and and don't don't worry to like basically jump ahead and you know, you know Check those Tick those checkboxes like ahead of In even in like further stages if you happen to you know do something Kind of earlier and also don't be worried like you know, for example the storage part like it doesn't have to be perfect I'm pretty sure that Once you start like Implementing further on you'll realize that there's something you missed and you need to store something more or you need some more methods So by no means this this needs to be like perfect like it's reasonable to assume that you will need to get back to it and Probably make some changes to the storage light from Right. Yes also like I'm also Implementing the pickup protocol at least in the test server. So unknown unauthenticated Implementation of the pickup protocol. So that's also coming in. I've already implemented the status Request Like stage six kind of like Sprinting ahead a little bit, but it was just great, of course Right, I guess you could actually check something from from the stage six Yes, so in that we have Into it is we see X message great. So that part is in there like it's it's more of a dummy Data model inside this test server. So yeah, I haven't that because of that, but the implementation responding to the status request that Is being done right now, so right can send in this and receive a response that is being there That is there Sounds great. All right, looking forward and it's exciting to see see you progressing It's really great I think you're doing well George how's perhaps since we don't have What no on the call no? Yeah, you have an update how you know how the FFI stuff is going. Yeah You want to click on the project plan? Oh, yeah, for sure Scroll down a bit of time Um Yeah, so where's it at? Um, so so I'm not has a PR open and that PR is basically the script for building all the Android binaries and building the The generated wrappers and placing them into the right place Within a sample app that he's working on Last time I spoke with him. He had the sample app bootstrapped and the the script working there were some Build things we had to work through as you'd expect but Got through that Yeah, and Haven't yet seen the whole thing of the sample app Calling into There is vcx because I was sort of the the main goal, but the two says definitely exist Yeah, I didn't have a chance to catch up with Swapna this week If you if you saw in our discussion channel Yeah, so I'm thinking next week that sample app Will be there and ready and that PR can go Okay, okay. Yeah, I was wondering as well. Is that sort of how You guys wanted things to go. I'm sort of incremental PRs for this mediator project I think like I'm Personally fan of like incremental changes. So I think that's fine. We can like merge The stuff which was done if it's like and I guess if it holistically kind of if it does something holistically If it builds and compiles or it doesn't have to be like fully complete, but But I guess like If it kind of makes sense that the things started in that PR were kind of finished then I would be fine merging it and then making another PR for like next steps next I I see you kind of have outlined like these PRs ahead of time for like different features So, so yeah, I think I think that's a good plan Oh, okay, I think it's actually preferable to wrap large PRs Much much easier to review and you see How the progress is going so Okay, great. Awesome. Thanks All right, let's get back to the agenda. So So now a quick overview of the work done Nothing like really significant. I think The the node is migration PR We just previously merged has been reverted because it was causing some build issues I'll get back to those build issues. Well, I'll be talking about stuff in progress. I'm working on now There was some clean. We have deleted the mixed beard mixed breed test profile. So We have like significant coverage with all kinds of combinations of the profiles and things have kind of The testing coverage and the infrastructure kind of improved since the mixed breed Was invented. So Don't see don't deem it necessary anymore. So we got this deleted kind of cleaned up a little bit of the testing features and then lastly another kind of Clean up Refactoring Was this PR? It was mostly shuffling the files around to To move stuff out of these like general source slash in the directory into either unencredced ledger or There's a typo here or wallet As As to kind of make it clear like what are we going to be deleting and would not because For now, we're gonna gonna be we want to keep the in Lidia twos wallet So they will stay and then we'll be progressively deleting these other two parts and right now We are starting with deleting the ledger and I guess once that is completed. We'll go ahead and And I get rid of the unencredced as well, but I suppose the world will live for a bit longer until we have some I guess Oscar alternative Yeah, so this was this was done here there was also I think I think you can at least some some issues with this PR we merged it I want to apologize here. We merged it kind of prematurely. I guess we didn't wait for George to do To like have his review Yeah, you've deleted some You have like I just did a Step in the CI which checks builds with various combinations of feature flags Yeah, yeah, I know which I mean Yeah, why need the policies? Oh I have missed it Yeah, why did you do that? I Don't know exactly right now on the spot why I did that. I think yeah, I had some like issues I actually deemed it as unnecessary, but I don't I can't reason about it right now. I don't remember. I'll have to take a look I guess because yeah, I was also doing some changes to the features features in the on the VDR tools level to make to to enable compiling in in the wallet without zero MQ dependency and then somehow I Guess I was tweaking some some of our own cargo tomos and I came to conclusion that like Some feature Apparently I came to conclusion that some default feature is necessary, but let me have a quick look if It makes any sense. So yeah, this was literally just kind of a Refactoring is didn't make any functional change I believe and is there any other feature changes I did Perhaps I was doing some other changes and which are revered which are reverted and For those I have originally Had to adjust the CI, but maybe doesn't really apply anymore. So yeah, I'll have a look Yeah, it's it's it's no worries there's sort of a coincidence that I had a look after as much than noticed it, but Hopefully you understand the intentions of those checks They yeah, I put them in after There was an issue with compiling for only modular libs and without the default features because video tools our default feature and And personally the way we can shume it is in that manner just modular libs without video tools So yeah, I was just putting a check in to make sure nothing gets regressed Yeah, yeah It's a it's a good catch and I mean the features are supposed to be additive So definitely should compile without default features Yeah So Yeah, so I guess that's where the PRs which have been merged since the last week and then in the progress There was an ongoing effort to pioneer the exchange protocol and like we'd come with the making it IOLS and Applying the state pattern from Mira I Don't know if you want to drop any comment about it Mira or I Would not I would not say pioneer there are already existing implementations for a while But yeah, you know in a sense Hmm. Yeah, I have I have in progress a Prototype implementation let's say and yeah I've perhaps I've said it recently on this call. I'm not sure I I'm Basically using ath to test the correctness of the prototype implementation and Yeah, recently recently I did support for Bitki as a recipient key in out of the out of an invitation Yes, it's defined in the RFC we previously or currently are using because it's not much yet using just make it base 58 encoded Ed to 5519 key and so Yeah, after it's fixed basically This the current status is that The a cap I fails either as a as a responder on receipt of requests because the request that any ccx currently sends in the direction protocol uses the peer and A cup I does not support the peers on the main branch yet and Similarly, it when it's a requester it fails on receipt on receipt of response Again with the same with the same issue Now Reese these these issues can be overcome by simply not sending the peer Which I could not be required to manage changes to the implementation so I can do that to test whether Something else breaks down line, but I don't think so I Know there is not much that that can fail after after I'm not sure but Yeah, so that is the current status I Would say that like overall I think it's going according to to plan in a sense like the Testing so far confirmed my suspicions as to what needs to be implemented And discovered some issues with the current state of that is ccx good base and Needs things that need to be either refactored or implemented from scratch things like JW signing Which a cup I as I confirmed that does does use gws signatures, so we could also Supported with signing and signature verification Yeah, and there are many many things like like this Things which are complicating Implementation that such as the legacy the document Which basically if I'm trying to like localize the usage of the new the document Implementation and the did exchange document the implementation it It forces me either to be copy pasting stuff or using converters between the old and new versions of the command which is better prone and So Like bloating the code code code size, it's not it's not pleasant to look at at all. So Yeah, but perhaps we can deal with it temporarily Yeah So what I would like do is or what my plan going on is to finish off this first type of implementation just to Well, first of all, I Would like to try to run the a capai branch with jail working did peer implementation locally This would also significantly Speed up my my Feedback loop, let's say because yeah, I wouldn't have to rebuild of grimages and stuff. So And I would like to test Using peer dates in the in the exchange on our side if that fails, I will I will support for for the For the legacy per vice, per vice dates And and and Finish off basically the a working working Implementation which passes the ATH test against a capai in itself and Then use this put the implementation as a reference for A final more Well, I would I would finish this for type implementation And then work on work on the issues that came up As I was saying like there aren't many many smaller build tasks that need to be done And then I would I would proceed with with the final implementation Implementation of the exchange protocol after these things are implemented. So that's It's good Like a well thought through in a laid-out plan. All right So that's the exchange status and Then we have I so this is the task I'm currently working on Is the is a switch from From vdr tools ledger clients to in the vdr implementation And the issue is I have the PR ready And technically it works, but it doesn't work fully and everywhere and Not not that it doesn't work, but it doesn't just doesn't compile yet fully In all of the environments. So if I look at the ci right now Basically, I'm getting failures for when I compile stuff on alpine linux. So that's a m usl target And then also an android and ios For the vcx and it all fails with compilation of zero and q Zero and q6 zero 11. It's the same failure everywhere Now it's it's so difficult It's relatively difficult to reproduce the ios build and android builds But it's so much easier to just Kick up alpine linux instance and try to compile the stuff in there So I reproduce this error in container, which is like I think great first step to actually identifying what the problem is That's hard to tell from this error. Honestly, it's some Some some compiler issue. It's clang clang and Yeah, well, you'd have to find what uh, well the issue and the fix is for this, but it should be relatively doable now Once that I have it reproduced locally essentially and so I I'm I'm hoping that the same fix which will apply for these Alpine linux will also work for our s and android Um, yeah, so that's that uh, but in general this pr, uh, which is yet lacking description it's removing all of the Ledger Slash pool related code From live vdr tools. So essentially leaving live vtr live vdr tools to cover only wallet and almond crates So it's on 20 000s code lines of code deleted and Obviously, I had to do like a tweaks On like r, you know in in areas vcx as well So then everywhere we would use actually um the Individually our client Um Yeah, that was those relatively all right and And the tests are passing If the things compile apparently all tests are passing. So that's good Um, sorry Was it android and ios build working? Yeah, no, they they don't the live vcx android Okay, but it seems like the same root root cause Okay, do you have any thoughts by chance? This is around q issues. Um Uh, I'll I'll look at it. Um, I mean, I've done it before like uh, have it working on android and ios. So Maybe I'm convicting that can help you. Um Yeah, I need to have yeah, I wouldn't be surprised. It's just some configuration It it falls everywhere a little bit differently, but at the same time it feels like it's the same Thing, but I don't know what it is It's always fell. It is zero mqcs, but as you see the error messages a bit different Um errors occurred Um Is there anything useful in this one? Here I don't really even see the error really. I am not sure It fails when it runs cmake and Yeah, I don't know what the problem is Yeah, so hopefully this will be like Un un un blocked soon and then it can be merged and we can like get rid of like huge Huge burden we carried this uh, live vdr tools Hmm. Yeah, it's an awesome awesome effort sorry Sorry, I think my internet's bad, but I was just saying it's an awesome effort 19,000 Yeah, oh it was it was actually like just you know a bunch of delete buttons, but But then the integration of the every zc exit it takes a bit of effort to glue it up To make it work, but it's it's it's good. So one maybe one more note here essentially after this pr The After this pr is merged The vdr tools feature It essentially only refers to n on crits implementation as the ledger will be always in the vdr And the wallet is kind of currently always the The indie one. So the vdr tools feature flag is essentially only they refer as to whether you want the n on crits from Live vdr tools. So I guess it makes sense then to actually rename the flag to something like unknown crits Vdr tools perhaps Hey, just a general question while it's in my head and maybe we can Put this to the discussion at the end if you want, but um after vdr tools is stripped of non-creds as well Are we gonna keep the traits For you know ledger and non-creds, etc I I believe so. Yeah, I think it's good. I won't What do you think mera? young I don't I don't I'm not entirely sure either way. I was I have been going back and forth on this um I think that bogdan is What was saying Something against those traits and one was wanted to get rid of them I think it's I think that I think that was your argument mera It was also my argument. Yeah, I was for a while. I was the proponent of them and then I wanted to get rid of them I'm not I don't Yeah, but I I know it like one of your arguments for like As a proponent for it, uh, was the mocking and and I think that's a good argument that you can mock now The ledger implementation essentially with with this Yeah, so I guess we'll see but in my opinion, I think it makes sense. Well, what do you think george? Should uh, yeah, yeah, I'm I'm for keeping them. Um, I'd need to think about Exactly what my argument is but at the moment I'm for keeping them Yeah, who knows if we need to migrate to something else in the future and then it might be the Being get shielded off from all the Kind of specific dependencies underneath. Yeah. Yeah might save us from that. I mean, I think everyone was Pretty sure on indy SDK and then it got dumped That's right Okay, and then Lastly, there's like this A new effort ongoing from Bogdan's Bogdan. We don't have Bogdan on the call, but essentially Just so I'm not gonna probably fully represent it As as as good as he would But the idea is and I think there's there so there's a PR. I think where Bogdan started working on this It's um, it's addition type of PR. So Uh, so, uh, no, no worries about breaking stuff Uh, where is it? I guess it's this one. So the ultimate idea is to build additional layer on top of state machines um But Bogdan here started with Uh copying out the state machine a connection state machine in particular and Then he wants to actually do some changes On the on the state machine make it somewhat Flatter or thinner and then take that logic out to this, uh, a processing layer where Essentially it should handle even more stuff for you than the state machines originally did Where you in you kind of supply the the main thing you have to supply Is a storage for your state machines and resolver for state machines So then when you receive a message You pass this message to this process processing layer And along with a message you also pass in your storage where your state machines are stored and, uh, uh A state machine resolver Where the state machine resolver essentially takes a look at the message Um, and tries to find respective state machines In the storage and once that the state machine is found You know, it's it's uh updated to process the message Do the necessary IO and, uh You know if if the if the state machine update is successful that essentially is Re-serialized the the new state machines into the storage So then as a consumer of this layer you you have like less things to worry about you don't have to concern yourself with how to You know, you don't necessarily concern yourself with parsing out like thread IDs From The message to find it in the storage This this layer should kind of handle it for you. That's uh, that's roughly my understanding of the intention here Is it is it almost just a full agent implementation? It's uh, I guess it's not like agent, but um Uh Whoa We're not explaining something wrong those lines, you know I wouldn't call it agent because I think in in in actual agent you have to do still maybe a lot more logic than simply updating a state machine Like that's like really bare minimum when you receive a message The bare minimum you gonna do it is update the state machine and see if that transition goes further But in practice in in real agent you might have to do like a lot more things in my opinion So it should be just kind of I guess A logic which tends to get duplicated in agents indeed, but then People don't have to like very duplicate the kind of same issues solving the same issue everywhere as to as to you know kind of inspecting the message and They can think in what message it is and where does Where the state machine which state machine to load up That being said it's I think it's it's kind of experimental so we'll just see how it goes and if it proves to be useful and Then we'll assess it further Cool, that's that's pretty cool. Do you know if the intention is to for us to provide Both options like the raw state machines and also this higher level handler Uh Sorry, can you come again? Is the intention long term if this goes through? Is it to are we going to support both of these paradigms? You know the paradigm where the consumer's dealing with state machines themselves and all of that And also this higher level Whether they don't have to directly deal with them Oh, yeah, I think I'm not 100% sure how that will place out yet. I think Bogdan's ideals Because this processing layer it has impact on on the on on what is really Like the assumption as to what people are gonna be using whether they're gonna be using the state machines or Or they will just or or even 90 People would just rather go with this processing layer than it has impacts on the like the overall design, right? So then if if Under the assumption that people actually wants to use this processing layer than the state machines api And the way to work with it can can be actually like A lot uglier perhaps like because you wouldn't care Maybe it would be like very very technical api or Like you would have to inject lots of stuff or something like that But then yeah, but if you assume that people Some people we use the this processing layer and some people just wants to use state machines and have a more control over Over stuff and they don't want to like implement I know this this storage trades we have to inject the processing layer They want to be less constrained Then yeah, then I think you in in that paradigm We would have to make sure that the state machine design is like Still somewhat user friendly, even if not as Simple as this processing layer That's my thinking about it Cool. Yeah, I agree Would you I mean, I I know like my introduction to this like it was fairly poor and simplistic. I'm sure Since it's kind of a bogdan's idea. He would do better job explaining presenting this but Just just kind of from what I told you Are we able to envision like Do you think you would go with something like that? Or would you want to just consume the You know the state machines as you did they as you do today without much changes It I'd need to see the full implementation. I guess it really I guess it really depends on how much control this implementation is taking Because yeah, I mean personally, I don't I don't mind the state machines Especially after the the rework They'll be even better But I I agree that probably most consumers Would prefer this higher level interface api Yeah, okay, so we'll see I I guess right now there's not much to look at it Literally just it's kind of copy of the state machine, but with some changes apparently Oh, yeah, there is a state machine storage here Uh, there is something drafted new protocols mod rs But yeah, I think it's not uh, kind of completed and I think it will do better if Bogdan makes introduction So you can also provide some informed opinion. Maybe we can have another session Somewhere else. So we don't have to wait for that for the next week Just to kind of share the idea with you and I'm very curious. What's what's your thoughts on it? Hmm. Yeah, yeah for sure All right Yeah, that being said, that's the stuff which is in the progress right now Um, uh, we have paused. Oh, yeah, maybe one more update. So we paused migration to anum creds as we identified essentially some like complications and and Some work we could identify some work. We could actually contribute to anum creds prior to Attempting to integrate it so, um Yeah, we will be joining in upcoming weeks We'll start joining anum creds are anum creds anum creds war group calls on Mondays And yeah start kind of collaborating with the folks from that area And then once we feel the things are kind of ready and maybe we better understand the future plans of anum creds and Then we'll be more comfortable Proceeding with the credits to anum creds migration You can you say exactly what it is that needs updating or isn't ready? Uh, so, uh The most challenging part actually Uh Is for the issuer The the the main difference between credits and anum creds rs is Around how revocation Uh, how revocation works where in uh in credits and like in the world You have this revocation deltas and you in they put those on the ledger But in anum creds word in the like generalized anum creds the other ledgers Other ledgers when we are You know in in turn Since anum creds are striving to be uh ledger agnostic The other ledgers typically don't have this like Catered capability to Store revocation deltas like in the in the ledger desk. And so for other ledgers the implementation Uh, typically goes just by publishing the like entire state of the revocation list rather than just delta So we just kind of put the current state of the the revocation list and and in order to like, um Support these differences. Yeah, they had to do Things are a bit different in in anum creds rs and then it's a bit tricky. Uh, yeah, it's challenging to um to integrate that without Forking out the staff and forking, you know, creating alternative anum creds in interface implementation and There's also challenges that Bay, uh, I know what one of the challenges is also that The ledger interface is returning Like indy types, but then anum creds um In anum creds you are working with these generic, you know anum creds types and So you resolve something on the ledger, but you cannot really pass. It's a different time from different library You cannot really pass it to the anum creds library unless you somehow convert it and book done have done this like kind of poc and I I didn't fully review it but from his Just from his description You know, it kind of worked, but it was like work around and work around and He just he just made that PR for a future reference, but not really with intention to get it merged right now Patrick You said you were talking about the revocation list Having to pass the whole revocation list. Um, this Uh, it's actually not um subject to to change Um, or is it Yeah, yeah, it's not. I mean that's just the changing part. It's a complication. But yeah, but george was george was I think asking What what needs to be changed? So Yeah, yeah, so just to be clear Yeah, it just that yeah, this was like challenging part like which will stay challenging Probably and we'll have to think about it. But in in conjunction with those other issues that different types and And stuff like that. It was like even more difficult and and additionally like as Bogdan was like Kind of trying to integrate it. He found some of the apis in nano crates Like that they could be designed better. And so we had a session with uh, steven curran and some other people and We agree that we'll essentially start contributing to anum crates to make things a little bit better for the rust native You know consumers of the anum crates library. So we want to do this preliminary improvements first before we actually try to Do the integration Yeah, so we are Yet to schedule a meeting with Andrew Whitehead and other maintainers of anum crates rs which we plan to do Correct. That was one of the outcomes of the meetings of the meeting last week. That's right. Yeah, and also, uh, we kind of committed in in like further communication That we will get a PR in over some or Bogdan Bogdan said that in the mail that We will get a PR in by the end of next week approximately with I'm suggest the changes we can then discuss perhaps further Oh, awesome. Thanks. Thanks for explaining that um afj Are they using credex or non creds? I think the uh, perhaps just race. I think I saw something I was like listening through br so I think so I saw something about on on crates. All right, so Um, I'm not sure what's the status. I think they have some implementation, but Given that I I don't really know afj state just just like a Total assumption here, but given the fact that they are more mobile focused I think there's not really like, you know, is your production use cases. So perhaps it's it easier for them because They might be able to afford Kind of do do more breaking changes on the issuer side, but I don't know. I'm just I'm just Totally guessing and assuming here Yep, yep Well, that that got me thinking. I was wondering if by any chance we could actually if we if we separate out The Those issuer and issuer and holder Uh Traits on on crates trades if we could perhaps actually support on on crates For mobile because it might be easier But uh, I'm not sure just uh brainstorming thought maybe Well regarding splitting the trades. I thought that's the assumption Or like that. That's that that's the If we are going to keep the trades, then we we will support them and Definitely adjust them Yeah, yeah, yeah, so But then yeah, then we could have some features right and you could perhaps for a prover and holder Maybe you could opt into the unencredged version But still there is a problem with the types and you would have to do some sort of conversions Uh to kind of make it work and it might be It might be awkward implementation It's easier to do these things in in in java script or or python when you don't you don't have a hard types and when they are just Look the same, but there are different types than you have a work with it Yeah, I have done um like the base and on creds trade the the prover and holder methods um Using a non creds rs and I do remember like the annoying part of having to convert between the revocation status list and and deltas and I sort of just copied the afj implementation but As you say, not the issuer parts. They're probably much more difficult Hmm Yeah, yeah, so I think we'll take a little bit more time to to Put put focus on this for now. I'll stay with critics and this is uh post for for now and uh We're actually uh busy with this other other things um Do you George do you uh sense like Is there a motivation or reason for you our business need to switch to uncrets rather than you know being on critics or is it's rather just like uh That it feels right or is there like, you know, concrete reason why you want to use uncrets Um a reason that that we did it Uh I don't know I I sort of Took a whim that everyone was moving towards a non-credits rs and um Went for using that instead Hmm, right. Right, but actually like a cup by I think the main a cup I release it's I know they merged recently and like some also in a cup by some uncrets integration, but uh But I believe that Even a cup by like maybe the last release or so is uh actually still running on critics So it just kind of like around this time. It seems like all these frameworks Around the summer are now trying switching Uh trying to switch. Well, we are trying to switch on uncrets, but it's it's relatively fresh. I think we are not far behind as things been running on critics and and uh critics Is like still Getting like security updates and stuff. Whereas vdr tools is not So so critics is I think still like alright implementation, but yeah, definitely like Like um midterm long term will will be moving there and that's definitely intention and want to Uh fold the specification, which is Uh larger agnostic Yeah, yeah, I think I think akipa is definitely the big consumer of critics and they're sort of pushing a lot of the updates. I think um, I think recently they Put the effort to get rid of ursa um, and I think they've done it already and moved to the like the standalone ursa cl signatures Yeah, yeah, so that's with the new critics release. Actually, we should probably Oh, that's that's actually, uh, I guess, um a to do work. We should do rather sooner than later Uh, we should update uh critics versions of the latest release which contains some some updates. I think that's zero four but Zero four or is one point all? I'm not sure, but um It shouldn't be too as far as I know it On a rust level There's not really a breaking changes. I think so it should be rather smooth Oh, yeah. Yeah, that's it That might that might resolve a lot of dependency issues with um, oh, yeah, because it was taken ursa, right and now it doesn't and ursa had lots of bloat in it kind of Yeah, okay. This might be really good Hmm. Yeah. Yeah, that's right And I think also once we trim off the vdr tools get rid of the zero mq there again the the some of these Dependency issues can be again mitigated and and solved Sure All right. Uh, yeah, so that's that's that's it. No just vdr tools To critics world migration. Yeah, this is currently paused due to the ci build issues, but it's being worked on Upcoming work state pattern. Yeah, that's like, uh, that's a that's a long story kind of Issue And well, yeah, we are it's not really upcoming. It is upcoming at the same time we are working on it And in conjunction now with this processing layer which may like shuffle things around let's see We should have a call all of us together with bogdan as well And then the cli demo That's I guess that's like open task for anyone anyone to pick up. I was actually thinking man, you know, if you it it can actually be like interesting task for you or maybe even for swapnail, I guess, uh to to kind of See see how How to use every vcx basically the The idea here we want to do is implement this Simple demo where you like when you run to you know in cli you run two windows One the windows starts like Alice. We all call her Alice agent and then a favor agent and then they establish the Establish did call connection together, you know using the the connection state machine, which you'll be actually using and just exchange some message and perhaps then integrate more protocols, but but Yeah, it's it's it's kind of open task for for anyone So if you would like to pick it up, maybe after you gain a little bit of experience with rgcx in in the mediator Then you know, you can feel free to actually take it if you'd like to Yeah, I'll I'll provide more info and you know, don't don't feel any pressure It's not like you need to do it and just out there for anyone Including you or or swapnail or anyone else Yeah, and that's I guess it we didn't have any more topics we took the whole hour for this meeting actually so I didn't expect we would but we did So Thank you. Thank you all for joining and have a great rest of the week So you too Good day