George Mulhearn: Hey, Craig?
ckowald: Hello.
George Mulhearn: Nice of you to join us.
George Mulhearn: Am I in the right place? Yeah, you're in the right place, hey, Patrick?
Patrik Stas: How folks.
Patrik Stas: Hey, George? And I see we have a new joiner today.
Patrik Stas: Hi.
ckowald: hello! Is this? Is this meant to be just a discussion between you 2, or am I allowed to sit in?
Patrik Stas: No, no, definitely you can. You can join in a a, and anyone is welcome, you know, as far as your is, as far as you're concerned about the
ckowald: So usually we we don't have not
Patrik Stas: many, many joiners here. But yeah, definitely, you are welcome here.
ckowald: Excellent. Thank you.
Patrik Stas: So, yeah, maybe since since connected for the first time.
Patrik Stas: So you just like shortly introduce yourself. You know
Patrik Stas: what company or come for, or why are you interested in the framework. What are you doing with it? Things like that?
ckowald: Yeah, sure. This is. This is technically the second time I've joined full disclosure as I work with George.
ckowald: So
Patrik Stas: I joined the very first time that George sort of introduced himself to the community.
ckowald: meaning to come to these from an interest point of view. To be honest, George is the
ckowald: the more involved technical person you know, on on the ground Why, you know him more than you know me.
ckowald: but usually I've got something on this time of night. Well, for me, it's this time of night which distracts me. But this evening I've managed to free myself up to just sit in and quietly see if that's allowed.
Patrik Stas: Yeah, yeah, I understood. Yeah, that's cool, Sure.
Patrik Stas: Okay. So let's let's get started. So
Patrik Stas: Am I sharing screen?
Patrik Stas: Yeah, I should be there.
Patrik Stas: Okay.
let me open up the
Patrik Stas: and
Patrik Stas: Yeah. Okay. So by by hyper ledger rules, I should keep this this place for a little bit. So just in the meantime, as we have this and that trust police notice opened up.
Let me just.
Patrik Stas: Oh, well, let's let's leave to to to a short moment for
Patrik Stas: for for the for the notice.
Patrik Stas: All right, so I think we can dive into the meeting, so usually we start just like just to check. If there's
Patrik Stas: you know anything you would like to in particular, discuss today, so we can. We can adjust the agenda appropriately ahead of time.
Patrik Stas: Do you do you guys have any points?
George Mulhearn: No, it looks good.
ckowald: Yeah, nothing from me. I'm: i'm just here to learn and and catch up.
Patrik Stas: Okay, cool. So in that case it's more of a like a usual planning and review kind of meeting, I guess. So.
Patrik Stas: Yeah. So
Patrik Stas: well let's get through the recent work which has been done so
Patrik Stas: notably there has been a release. 0, 51 one which was released just shortly after 51
Patrik Stas: and the 51 those release after quite a long time.
Patrik Stas: But basically I believe that throughout the previous month this was the the first release since December fifth. So.
Patrik Stas: more than a month
Patrik Stas: a later it had a quite, a quite a bunch of tasks and merged. But I i'm not gonna go through all of these as this has been previously basically discussed on the individual meetings.
Patrik Stas: So so i'll leave it As it is, anybody interesting can take a look at a better. Look at the change a lot.
Patrik Stas: and i'll move on to the 50 51.1
Patrik Stas: i'm missing. We're missing the apparently we are missing the change here. But
Patrik Stas: there's 2 additional merit to request which this fix release contained
Patrik Stas: most importantly, the kernel dependency upgrade, which fixes certain issues for Ios and Android.
Patrik Stas: where on the mobile devices you will be for you, You would have to make sure that environment variable. P. Z. That
Patrik Stas: TV is set up as a as a variable for time zone, otherwise the logging library would try to get the current time for the purpose of looking, but it would fail it. It would literally panic on, unable to
Patrik Stas: an inability to determine the time zone. And
Patrik Stas: And so the kernel dependency upgrade is fixing this problem.
So we bumped it to the latest 0, 4, 23
Patrik Stas: additionally. This also contained a pull request to trim down.
Patrik Stas: and the bindings from Vdr tools so previously. The Ios Ios brepper not only contain bindings to live Vcx Library itself, but also the Vdr. Tools Library, which.
Patrik Stas: and which Vcx is using. So this was the this doesn't seem very clean, and
Patrik Stas: I believe that this didn't really have any use case, either. So in order for us to proceed and start streaming down these dependencies. We remove these bindings, and if anybody wishes to.
Patrik Stas: you know, re re revert, returns some sort of functionality. We should be doing it just directly by propagating. This calls through Libby 6 as 5, instead of trying to hook into some third part, essentially third party library.
Patrik Stas: So this is release 0, 51 1
Patrik Stas: before that
Patrik Stas: and before that we had a few other pull requests. These were included in 0, 51
Patrik Stas: well, non-technical one was the upgraded, a renee's documentation and architecture diagram. So i'll just briefly go through that, although
George have already seen it as he's the one who who who is reviewing
Patrik Stas: so so the main with me pages to be nicer, hopefully, more inviting for the newcomers to kinda they dig through. And also
Patrik Stas: the the really itself is is changing nuance
Patrik Stas: a little bit in terms of making sure that the area these things is clearly the
Patrik Stas: first first-class citizen citizen here, Whereas, the lib. Cx is just.
Patrik Stas: you know, one way out
different approaches. How to do this, how to do fsi to mobile devices
Patrik Stas: Maybe 6 is. One of them is that, as I mentioned on other on the previous calls, definitely an encouraging, encouraging anyone. Planning to use a is V. 6 to to look out for alternative ways, but to do fi other than other than the V. 6 itself, and the existing
Patrik Stas: ios and android wrapper, as the
Patrik Stas: If I approaches some of the out there.
Patrik Stas: But the the the the idea is here. The Wv. 6 is not the main artifact of this repuls story. It's really just the the rust library and the the sub crates. It it comes with
Patrik Stas: also. Yeah, there was updates, the other pieces of documentation as well. There was a separate sort of getting started for Libby X. Now including architecture, diagram that the architecture diagrams has now been split as a again separately for Levy 6 and separately for Aries, Vcx.
Patrik Stas: So from Olympic X perspective. We have the loop pcx. Create the mainly big 6 credit, which depends on the Area's: Vcx. Rust implementation.
Patrik Stas: They both optionally are using the agency client. Great.
Patrik Stas: I would, you know, integrate with the Me Mediator implementation of V. 6 agency node.
Patrik Stas: And yeah, obviously, we have. If the 5 wipers being hooked into.
Patrik Stas: So we have Java and Ios Grapper, the old school ones, which are linked into Api, C. Portion of Loopy Xiang, and then we have a no just wrapper just freshly merged.
Patrik Stas: Actually, we just build it differently than it used to be, for originally the no jazz wrapper was sitting here next to the aisles
Patrik Stas: linking into the binding into the Api, c. Layer oblivious. But that's no longer the case. Instead.
Patrik Stas: it's a know just they're now using other fi approach, and it's more tightly integrated with the Api we see expire itself, and it's that saves a lot of Lots of low-level handling. We had to do previously.
Patrik Stas: and I'm. Moving at Aries, Vcx documentation. There was also update. It was also updated here, so there's for getting started. There's some says for short section about message mediation, as you might opt into using V. 6 agency note, although
Patrik Stas: in the long run.
Patrik Stas: and we don't really expect to do much more development here.
Patrik Stas: If if anything, we might, might, we should. Implementing some
Patrik Stas: rust implementation on top of a is the 6 itself for the mediator. But yeah, so so the the the Vc. If they just you know this, some will that it's it's not really Aries
Patrik Stas: the client to agency api for downloading and marking messages is not the every speaker protocol. So hence we we don't really
Patrik Stas: plan to work on it, working much more will be ready looking into completely new
implementation.
Patrik Stas: And then.
Patrik Stas: yeah, there is a there is a short tutorial how to kind of get started, how to build it.
Patrik Stas: The unit test integration, test
Patrik Stas: dependencies which are needed. You need to run the in the pool.
Patrik Stas: And then, lastly, there's Architect new updated architecture diagram which only looks, which only describes the every Vcx sort of universe without that
Patrik Stas: the Libby Sax on top of it. So
Patrik Stas: that's here.
Patrik Stas: We have the agency client, this optional dependency now trying to kind of
Patrik Stas: uncouple it from the call base.
Patrik Stas: We have the handlers for the basically individual. Every protocols
Patrik Stas: which are using state machines.
Patrik Stas: What typically happens is that these handlers use the
Patrik Stas: plugins module to inject some data or objects into the protocols implementation, which
Patrik Stas: internally then used
Patrik Stas: the dog and a his message is great.
Patrik Stas: And as for the. As for the plugins, module goes, it's basically contains 3 interfaces, now one for unknown credits, ledger and wallet, and these have different implementations.
Patrik Stas: either by Vdr tools, or in the in the old, old, old naming.
Patrik Stas: or the module modular libraries. Ak Vdr. Tools in the shared ars, and there is as far in the future
Patrik Stas: now going forward. Obviously, in our in our 2023 roadmap we discussed last week.
Patrik Stas: One of the goals for this year is to basically get completely rid of it.
Patrik Stas: or as as much as possible.
Patrik Stas: and start using the modular
Patrik Stas: a library implementation.
Patrik Stas: So we Don't have to maintain 2 different implementations at the same time as we do now. So let's let's trim it down and simplify the maintenance.
Patrik Stas: That's the idea there.
ckowald: So sorry, Patrick, on that I'm, seeing a general move away
ckowald: from the indy wallet to the ascar wallet. Is that
ckowald: is that planned as well.
Patrik Stas: Yeah, yeah, definitely. I mean, we are seeing it across different frameworks, different different areas. Implementations.
Patrik Stas: We we as well have such a plan.
Patrik Stas: Who would like to first
Patrik Stas: first to this migration with the
Patrik Stas: primarily with the credits library and the
Patrik Stas: in the the the Vdr tools, which is for the for accessing connecting to the ledger, and one once we have this done. We will then move on to
the ascar.
Patrik Stas: One of the challenges we have currently with Ascar, we to George, running to is that
Patrik Stas: basically if you try to use ascar as a alternative implementation here.
Patrik Stas: I I think, a a new box here for the world implementation. There are certain dependencies. There's certain rust dependencies
Patrik Stas: which are
Patrik Stas: conflicting between the Vdr tools, dependency, and the ascar dependency. So they both have some dependencies.
Patrik Stas: and this transitive dependencies require a certain rest package on particular version. But these versions are different, and, unlike Np. Unlike Node, Js. Where you can have like 10.
Patrik Stas: Well, you know you can have one dependency. It's 10 different versions, and it works in in rest. It's not quite a case like you need to.
Patrik Stas: You know your your project holistically need to be in like sync like. If one of the libraries says that it needs one of your dependency states that it needs a library. B. It's a particular version.
Patrik Stas: and
Patrik Stas: and your another dependency says it needs to be different particular version. You will get that compilation error.
George Mulhearn: Yeah. So there's lots of very, very old dependencies in video tools.
ckowald: Right.
Patrik Stas: Yeah. Yeah. So so what we want to do now is try to trim down Vdr: tools
Patrik Stas: from the dependencies it doesn't need. So then we would to minimize the You know this kind of conflicts as much as possible.
Patrik Stas: I think the main problematic dependency actually in Vdr tools right now is the sequel X.
Patrik Stas: And I. I was looking at the currently to be the the the sequel X
Patrik Stas: version being used
Patrik Stas: by Vdr. Tools, it's actually a Fork created a long time ago, and there's been a bunch of new version of SQL. X. Which I did, in which, if we upgrade the sequel X dependency. I believe we'll actually
avoids
Patrik Stas: the the conflicts we are seeing right now
Patrik Stas: with the the
Patrik Stas: the credits, libraries.
Patrik Stas: the ascar libraries. Yeah, the
ckowald: Thank you.
Patrik Stas: Okay, this. Let's see what else we have here. Okay. So one more item on the list
Patrik Stas: is a: that was just a minor pull request, which is fixing with B. Cx in terms of
Patrik Stas: error, handling or mapping of in the errors where
Patrik Stas: before this? Pr: If you enter Invalid Key.
Patrik Stas: Yeah, trying to open what you would get Libby 6 error kind living the error 207,
Patrik Stas: which essentially is like kind of representing.
Patrik Stas: and in the error which is not mapped to anything particular in Vcx. Which doesn't seem kind of
Patrik Stas: reasonable. So we instead created. Now a new error. Kind will access failed.
Patrik Stas: which we map this in the error into
Patrik Stas: Additionally, there was a few other mapping changes.
Patrik Stas: not really changes, but adjustments, where certain errors.
Patrik Stas: certain errors were simply mapped into this kind of January Wevr tools error
Patrik Stas: with the error code, but, in fact, it could have been mapped somewhat more sensibly on to the existing Aer's. Vcx, for example, the invalid transaction
Patrik Stas: most previously just mapping into this generic error. Now it naps into invalid a larger response.
Patrik Stas: I think this this whole error in this era mapping still can get some tweaks.
Patrik Stas: and the the error kinds in ours, D. 6 itself could be
Patrik Stas: could be reviewed.
Patrik Stas: but they just attempt to to make it a bit more better be more sensible than it was before.
ckowald: Is that is that going to cause any sort of
ckowald: back with compatibility issues or concerns remapping error. Codes like that.
Patrik Stas: Yes, so if you to depend, you know, if you would particularly rely on this error code somewhere, then
Patrik Stas: it's something to be to be aware of. But
Patrik Stas: I think
Patrik Stas: these are sort of the obscure cases, you know. Typically
Patrik Stas: Typically, most of the in the errors are handled by
Patrik Stas: typically most of them are head, are are met into some sort of every every 6, every kind.
Patrik Stas: and then and then for propagated, as
Patrik Stas: if you look there. But if if if you somewhere in the code are using, you know Vdr. Tools, error. And then looking at the er code, then this will be breaking change
Patrik Stas: for you.
ckowald: Alright, cool.
Patrik Stas: Yeah. Additionally, that Pr. Contained a bunch of refactored tests and the bcx.
Patrik Stas: and the last item here was finally merged, You know, Jazz rapper
Patrik Stas: with a reward. As AI internals
Patrik Stas: it's a it's it's improved the performance significantly. It's a 400 x on with no jazz 18, and as opposed to
Patrik Stas: the old if I approach, and I would just 18, and it's 20 x you promote against the old if I approach on on no just 12.
Patrik Stas: So, and also it definitely seems more stable. In Ci. We were seeing intermittent issues with no just testing previously, which is mostly related to the
Patrik Stas: to just framework itself, and the fact that the library was constantly re-initialized in those test workflows and now we we see that it's like we're way more stable and
Patrik Stas: it's faster, and we we managed to wipe out 5,000 lines of code, so much more manageable as well maintainable.
Patrik Stas: Okay. And then, as for the award in progress goes that slightly links into what we would we touched on in the when we're looking at the architect architecture diagram
Patrik Stas: about the Vvr tools so as as as per the issue which has been created. A couple of days ago. 5 days ago
Patrik Stas: we we started moving
Patrik Stas: Vdr. Tools under the Area's Ecx repository itself.
Patrik Stas: So
Patrik Stas: up until now well, it's technically Still, right now we are using a particular fork.
Patrik Stas: Oh.
Patrik Stas: Vdr. Tools
Patrik Stas: also Vdr tools from this fork. So this was for from ever-name version of Vdr tools, and Vdr Tools itself is fork of what originally used to be known as living the in Hyper Ledger in the SDK
Patrik Stas: repulsory. So what we are doing now we are taking this particular revision we have here from this fork.
Patrik Stas: and we have
Patrik Stas: well, we have open. Pr. Now, where we kind of picked out the the get 3 from the for repository. For this particular piece of the reposter we are interested it, which is the Vdr tools a directory.
Patrik Stas: So these are pretty much. This is dating back to the comments from
Patrik Stas: from ever name
all the way to our latest
Patrik Stas: a modification in the fork.
Patrik Stas: And yeah, the idea is we're gonna bring it here under under our, and this will give us better flexibility in
Patrik Stas: trimming it down
Patrik Stas: and just cutting down the cutting of the dependencies.
Patrik Stas: and eventually just removing this
Patrik Stas: portion of code completely, or possibly just leaving, like the minimal, really minimal set. Maybe if we want to keep the the what implementation in parallel with us car, or you know, at least until the uscar is ready, and we have migrations and stuff like that
all all clear on
Patrik Stas: on this piece.
ckowald: Yeah, if i'm understanding correctly, you you, you're taking a copy of a subset of the video tools code. Is that
ckowald: so? You kind of decoupling it from that? So any future changes to the main branch.
ckowald: you you're not. You're gonna have to replicate if you care about them or you're thinking. Eventually you'll abandon that and just go to as car, anyhow.
Patrik Stas: Yeah. So we are basically taking copy of the portion of the repulsory, and we'll just yeah start trimming it, Start trimming it down. So we're gonna have a
Patrik Stas: we're gonna have a new Directory here now, Vdr: tools, and we will use that instead of the Fork Github
Patrik Stas: dependency. But yeah, eventually we want to. You know, to me, down to the point where
Patrik Stas: it doesn't contain much code.
Patrik Stas: Yeah. And yeah, possibly, you know, once we have to ask our implementation in integration ready, then we might even delete the Vdr tools completely.
ckowald: Right?
ckowald: Okay. Cool.
Patrik Stas: So we can like, you know, this this way. We are really just, I guess.
Patrik Stas: of of officially taken lead with that fork, and not expecting any updates from ever name anymore, we which which we could kind of sink into or hardness, just make it in completely new fork, but
Patrik Stas: not in the some remote repository, but under Aries DC. To make the development more transparent, and use the same governance process
Patrik Stas: here
Patrik Stas: as opposed to just doing something on our own in some the plot fork somewhere else.
ckowald: Okay, can I? I can. I ask a sort of maybe related, but maybe not question. I i'm, I'm very new to the
ckowald: SSI d I community and concept. So there's a lot of history that i'm not aware of.
ckowald: I don't know if you can answer this one. But
ckowald: I
ckowald: is. Do you understand why there's a general shift away from the Indie wallet to the as car wallet is there?
ckowald: I I
Patrik Stas: because, you know, if you look at that in the SDK repository, basically nobody is really maintaining it anymore. I mean.
Patrik Stas: oh, okay.
Patrik Stas: move the last commit move in active maintainer and marriage status.
Patrik Stas: I I don't know if there's any active maintainer any more at this point
Patrik Stas: is there.
Patrik Stas: So there's some names segregate.
Patrik Stas: But yeah, there's very little activity here. And
Patrik Stas: basically the what here? Those those 2 implementations of the wallet in the in the SDK:
ckowald: Yeah.
Patrik Stas: one of them was I like the I Was it the? And that was the native usually used by devices.
Patrik Stas: The other one was kind of
Patrik Stas: for plugin architecture. There was a post for a post-second implementation.
Patrik Stas: But basically
Patrik Stas: the problem with this part of this implementation is especially with the postc 2. One is that the code base. Just
Patrik Stas: it. It's old code base, and it's not using us in a way at all. So any, for example, if you use the post for sequel what you know a new mate, and it took you a 50 ms round trip to the post recipient.
Patrik Stas: It will just block CPU for 50 ms. So for these reasons it was not really usable, you know, at scale
Patrik Stas: and
Patrik Stas: and people just moved away. For for one, I guess that was one of the reasons into those smaller repositories, and also just by.
Patrik Stas: I I guess, like just general practice kind of like code architecture practice. It was a monolithic repo. And
Patrik Stas: if you think about it, wallet.
Patrik Stas: ledger access and dealing with credentials are, you know, all kind of
Patrik Stas: really separate problems.
Patrik Stas: But here it was just intertwined into one code base, and that had lots of
Patrik Stas: you know, things to be improved, for example, the
Patrik Stas: and maybe to give you like additional background story. Basically, why are we now, you know, in there is, we say, using Vdr tools is what happened. Is ever name the original contributors and maintain there's this in this the key code base
Patrik Stas: because of some
Patrik Stas: like the the community, and ever the ever name and community couldn't come to agreement on certain terms. So they for this whole repulsory
Patrik Stas: under the you know, the Vdr tools.
Patrik Stas: They rebranded it as Vdr tools, and they've implemented like a bunch of really great stuff. They did as sync avoid wall ads.
Patrik Stas: refactored. Call base a lot.
Patrik Stas: And so that's why we kind of migrated over there because we, you know it. But it was maybe a year ago. We didn't really see any future here. We started using Vdr tools. Now
Patrik Stas: the the community can. The original community from in the SDK moved on to those module libraries which are, you know, I think, away they are like nice, clean, modular. So I think. Yeah, that's kind of the next step, because the Vdr tools itself as well, is at this point not really maintained by ever name either.
ckowald: And now we're moving from V. Our tools towards Ascar.
Patrik Stas: Yeah, no, no, yeah, exactly. And temporarily, you know, we are taking basically started to maintain the Vdr tools for on our own. Now, moving into the a. Is V. 6 repository with the go of eventually eliminating it completely.
ckowald: Yeah, I suppose my follow up thinking was, You know, as long as we understand why we're moving from via to as car.
ckowald: The how do I express this?
ckowald: If If the VR tools gets updated so that it sort of becomes, you know, in quotes better than as car, whether or not we'd ever want to move back, but it doesn't it doesn't sound like that's a likely thing given that the nature of em. It's sort of discontinuing support for this stuff.
Patrik Stas: Oh, yeah, Well, you know as far as to what you know definitely the future is in those like modules, right? Libraries like credit for the credit. Well, more precisely, I guess. I'm on credit Rs for dealing with credentials.
Patrik Stas: And then.
Patrik Stas: yeah, in the Vdr. For dealing with the ledger. But as for the world goes, you know we are me as a representative from upset. We are actually using the my sequel implementation of the
Patrik Stas: Vvr tools.
Patrik Stas: and we are happy with it. So
Patrik Stas: it's for the uscar goes like we definitely want to add to support that in this kind of modular fashion. At the same time I don't know if we will read, You know, as the Upsa, we will really want to migrate to ask our, because currently we don't have any issues with the Mysql implementation for, like the issue very far
kind of software
Patrik Stas: but for the mobile devices. I guess
Patrik Stas: I don't know how different the uscar is from the the implementation Vdr: tools. But I think, yeah, the optimal solution for the world would be just, you know, have multiple implementations and
Patrik Stas: and let anyone choose to one they want to. They want to choose. But I know maybe we'll run into complications with that approach to change the perspective.
Patrik Stas: But
Patrik Stas: I can see at this point it's like go going, you know, in mid medium term. We would like to maintain.
Patrik Stas: We would like to keep at least the wallet out of Vdr tools, but definitely want to dump all the other stuff like the credentials and the ledger stuff.
ckowald: Okay.
ckowald: I I I had the impression anecdotally that the Indie wallet was. There was some sort of performance or scalability issues, but I guess that
ckowald: I guess that would be on the
ckowald: You know the postgres sequel side of it. You're talking about not using the away Async kind of functionality. So it sounds like you're saying that the
ckowald: the Sq. Light side of it's pretty good, and you're quite happy with it.
Patrik Stas: Yeah, you know Generally this when you look at like the kind of the those wallet interfaces in Vdr tools, they are all like asking Oriented, whereas in the original it was just synchronous calls. So whether it's like what, whether you know, when we we talk in terms of sequel, what or or
Patrik Stas: some database will at like.
Patrik Stas: those can all be implemented in sink a white fashion, you know, with Vdr tools, implementation cool, I understand. Thank you. Sorry for the distraction.
Patrik Stas: Oh, it's a it's it's you know the the meeting is to have discussion. So i'm a happy one.
Patrik Stas: Thanks for people. People ask or discuss.
ckowald: Thanks.
Yeah, so that's that's what's going on right now, and
Patrik Stas: for the upcoming work. I guess i'll start with this one, because this mostly ties to what's going on. I saw I saw that, George, you're pushing some comments today into the the verifier. I didn't have time to look at it, but I guess
Patrik Stas: in in in that sense they could move this piece
Patrik Stas: into the progress, so can you give a short update on this? Have you managed to fix those those some failing tests? Right? Have you managed to overcome those issues.
George Mulhearn: Yeah.
George Mulhearn: I I just put a Pr. Up for it just before this meeting
George Mulhearn: moved it from the draft to ready to review. But yeah, it was just an issue with error. Mapping
George Mulhearn: and credits was kind of wrapping up the error in a weird way, so I had to
George Mulhearn: figure out how to unravel that. But
George Mulhearn: yeah.
George Mulhearn: it's a short Pr: so it shouldn't be
George Mulhearn: to that. The the issue
George Mulhearn: Critics: Pr: will be much bigger.
George Mulhearn: And yeah, that'll be the most telling. Pr: I think.
Patrik Stas: Just wondering. Have you? Have you had the chance to, you know? Do any sort of attempt into any, into into into issue, or yet, or it just something still ahead of us.
Patrik Stas: Yet.
George Mulhearn: Yeah, it's it's mostly ahead. I I mean, there was some existing Apis that were done with my original Pr. Which were issue a related like the ability to write a did
George Mulhearn: was done with credits.
So
George Mulhearn: there is some riding
George Mulhearn: existing right to ledger functionality that's been written in.
George Mulhearn: Sorry not credit in Indivia.
George Mulhearn: So some of that's done.
George Mulhearn: And then yeah, I guess
George Mulhearn: just need to give it a go. It it shouldn't be too difficult sort of following the same pattern that
George Mulhearn: it's already been done
Patrik Stas: right right, I guess. Like, yeah, my, my my main concern is just the the compatibility. So I would like to make sure. I know when when we do this, if it's possible, if it's possible.
Patrik Stas: I would like to see if we can
Patrik Stas: like, accommodate case where
Patrik Stas: you create a let's say credential definition with
Patrik Stas: video like we'd.
Patrik Stas: Pdr tools, implementation and
Patrik Stas: from desk
credential definition. But using the
Patrik Stas: you know, the the the credits, libraries.
any any issues with that?
George Mulhearn: Yeah. And the way how it's it in wallet or something like that.
George Mulhearn: Yeah. Yeah. Good idea. Yeah. We kind of need to test the like the different permutations of it.
George Mulhearn: you know. Indeed, to indie in the modular modular to indie modular.
Patrik Stas: Yeah, I I I guess I will then like we we wouldn't necessarily need the modular to the Indie is like, I think nobody you know, would be making that kind of step backwards like starting with credits to the to the Indie. Would you plan to delete? But just just kinda moving forward.
Patrik Stas: See? We can. We can implement it kind of
Patrik Stas: some sort of migration support.
Patrik Stas: or if not, then not, you know.
Patrik Stas: Yeah, I guess we'll see what kind of challenges is is there ahead of us? But I think like
Patrik Stas: that that could be a good approach to just like start
Patrik Stas: like start small, just find like one
Patrik Stas: area to migrate, for example, creating those traditional.
Patrik Stas: literally. Basically yeah, maybe issuing a credential right? So
Patrik Stas: you would
Patrik Stas: you could you could we we could have a test to recreate
Patrik Stas: the credential
Patrik Stas: with.
Patrik Stas: We credential definition and schema with
Patrik Stas: with Indie, and then just implement the you know the functions necessarily for issuance, and try to see if we can actually issue from that
George Mulhearn: original credential definition.
Patrik Stas: and then move like.
Patrik Stas: move forward like you know. I guess if we see that that works, and we can start implementing like other other functions
Patrik Stas: for the for the issue, or like, maybe start writing those schemas and
Patrik Stas: credential definition revocation registry, this kind of stuff.
Patrik Stas: But
George Mulhearn: yeah, that doesn't make sense. Yeah, yeah, definitely.
George Mulhearn: i'll get on to that after
George Mulhearn: that Pr: the verify up here.
Patrik Stas: Maybe we can. Actually, I have.
Patrik Stas: I have created the like
Patrik Stas: some issue to address this testing.
Patrik Stas: but I think I didn't really describe it much.
Patrik Stas: But yeah, this is like kind of full bone. And but I think this is actually too much to get
Patrik Stas: like
Patrik Stas: this is to
Patrik Stas: big
Patrik Stas: piece of a. K. To start with.
Patrik Stas: Yeah, I I think we should. We should describe some minimum W. More minimal scenario.
Patrik Stas: Just so we can go incrementally because this is assuming everything to be implemented by
Patrik Stas: by the by, the critics approach. But we can take a smaller steps.
Patrik Stas: So yeah, i'll try to add, like some additional proposal here for for the test we can
Patrik Stas: start with
Patrik Stas: after the meeting.
Patrik Stas: Oh, okay. And as for the stuff we have, yeah, the upcoming upcoming things. So
Patrik Stas: a task which I took over is I started to look how we can improve. Ci. Currently, there's a stability issues because sometimes code code
Patrik Stas: just fails to kind of receive the coverage data, or I don't know if it's networking issues in
Patrik Stas: Github pipelines. I don't know what the issue is, but sometimes we get like
Patrik Stas: error codes from the or or just some time out, or something like that from the servers of Code Code Covio. And
Patrik Stas: and so we could kind of
Patrik Stas: solution could be that we just. We try to re upload the coverage files. The problem is right now. It's kind of bundled together with the running the test itself. So the idea is to split the testing with code coverage Ca: calculation separately, and then have separate job
Patrik Stas: for uploading the code coverage we could, which could implement some sort of rate. Try logic if we get to fail failed response from from code to
Patrik Stas: I/O,
Patrik Stas: So that's that's one. See improvement
Patrik Stas: After this I believe that the the Ci should be really stable, because we no longer have the
Patrik Stas: no just issues, and this is also common source of a failed pipelines so sure, much more stable afterwards
moving to the next point. So
Patrik Stas: I guess i'll move here first. I think that's more important. Actually. So, like going forward. We'll want to try to start streaming down the Vd article base
Patrik Stas: just by like kind of brief look. I saw like few dependencies which did not have to be there. There was some unnecessary in in a. In a progress, and working on
Patrik Stas: this Pr. Previously with the Vdr. Tools or mapping, I've noticed there's
Patrik Stas: number of errors in Vdr tools which also don't really make sense anymore.
Patrik Stas: Just, for example, there was
Patrik Stas: errors related to payments
Patrik Stas: in Vdr tools, because originally V. The the in the Ledger was supposed to support payments to
Patrik Stas: with some tokens. So there's errors like payment source does not exist.
Patrik Stas: And obviously this just like not the type of errors we need to deal with or think about anymore. So there's stuff like this which can be cleared up, and consequently to also clean up the code, base
a little bit
Patrik Stas: as well.
Patrik Stas: also removing some dependencies. Hence producing chances of some sort of dependency complex when we are integrating new dependencies, like Arizona, for example.
Patrik Stas: So we will work on like trimming down the code base also, possibly
Patrik Stas: just completely wipe out the portion of the Vdr to call base, which deals with
Patrik Stas: functions related to holder. And
Patrik Stas: as this all has been already implemented with the credits libraries.
Patrik Stas: and
Patrik Stas: yeah.
Patrik Stas: so so basically if we implement, support.
Patrik Stas: kind of integrate this into
Patrik Stas: the the credit, support for holder and
Patrik Stas: prover, to the make sure that it's backwards comp compatible for the existing what they can still keep, proving with the old credentials
Patrik Stas: which they should.
Patrik Stas: Then we can, yeah do it. Probably significant portion of the Vdr tools which just deals with proving and and holding credentials.
Patrik Stas: and I guess and basically they will be like the theme, the the strategy going forward. For you know, once we kind of manage to
Patrik Stas: implement the support for the for the issue and verify, we can again
Patrik Stas: remove the portion of the Vdr to school base, which which deals with those issues, those problems.
Patrik Stas: And and that yeah, then the the
Patrik Stas: or when they skipped here, kind of after a long time, a creative task to actually add something new to the code base. So there's an issue created
Patrik Stas: to to come up with
Patrik Stas: the design that you tried for Video resolver.
Patrik Stas: We could have implementation for that dissolved basically port kind of fitting the existing code under implementation under the initial implementation
Patrik Stas: for this new trade. We could then also add
Patrik Stas: implementation for did ending as a new new, the Id method which will be supported on in the ledgers.
Patrik Stas: I don't know what the timeline are, but I I would believe it's this year.
Patrik Stas: and also considering, adding like something like
Patrik Stas: resolving through a third trusted third party to trust a third party, such as you need resolver, although obviously this.
Patrik Stas: it's not ideal to resolve the Ids through a third parties. But it could be like just experimental.
Patrik Stas: Yeah. And I believe this this whole thing probably could be like, create on its own like. I imagine this could be useful for
Patrik Stas: other projects.
Patrik Stas: you know. Whoever wants to resolve the the the Id documents in rust. This could be pretty generic create which you can use to, you know. Resolve.
Patrik Stas: resolve the Ids whether it's did solve the Dnd, or you know, possibly might other. We might add other kind of native implementations.
rust implementations for other
Patrik Stas: and the adding methods.
Patrik Stas: or, in the meantime
Patrik Stas: just hook into a trusted party like you. You need a resolver.
Any any thoughts or comments about this. One
George Mulhearn: looks good.
Patrik Stas: all right.
Patrik Stas: so I guess that brings us to the kind of end of the meeting. We covered everything
on the agenda.
Patrik Stas: So unless
Patrik Stas: unless there's anything else from your your guy side.
we can finish the meeting.
Patrik Stas: Do you have any any discussion point? You might have thought, you know, throughout the meeting.
Patrik Stas: if, before we close all
George Mulhearn: I started working on a unify rapper
sort of proof of concept thing.
George Mulhearn: No real objects yet. But
Patrik Stas: I guess hopefully, there's an update next week, and i'll let you know that
Patrik Stas: awesome that that would be really interesting to see. I'm: sure people could their inspiration when building new new wrappers or new new applications.
Patrik Stas: Oh, yeah, that that's exciting. Thank you so much for this effort.
George Mulhearn: so good. Oh, also I noticed something earlier when we were looking at the
George Mulhearn: the read me for Aries Vcx.
George Mulhearn: So I guess in the read me, and
George Mulhearn: what I've been doing, and what you've been doing is
George Mulhearn: pulling from the
George Mulhearn: the docker image that you've uploaded to Docker. Hub.
George Mulhearn: Oh, yeah, yeah. I was wondering. Is it possible
George Mulhearn: for it to be published to Docker Hub sort of on the
George Mulhearn: Hyper Ledger Aries, Vcx, rather than
Patrik Stas: we could publish it. I I I don't know if there's account for hypology on the Docker app. We we could publish it on the
Patrik Stas: the Github get up registry instead.
Nice?
George Mulhearn: Yeah, we can do that for sure.
Patrik Stas: Yeah, yeah, these are all do for images. And apparently there is actually some in the pool here.
Patrik Stas: but i'm not sure.
Patrik Stas: I'm not quite sure.
Patrik Stas: And obviously in the Ci we are using in the pool with local host. I don't remember if we are building it. No, we are using the the one from the docker Hub as well.
Patrik Stas: But yeah, apparently we have some old in the pool images here, which is not really being used. Not many downloads. I'll take a look into this, and i'll ping you i'll i'll. I'll ping you on the discord.
Once we have this sorted out.
George Mulhearn: Okay, Great thanks.
Patrik Stas: Okay, I guess. With that
Patrik Stas: that being said uncovered.
Patrik Stas: you have 8 min left extra of your time. I we meeting. We are finishing this earlier. So thank you both for joining in and also thanks for anyone for tuning into the recording. Possibly.
Patrik Stas: So. Yeah, have a. It's it's almost weekend. So
Patrik Stas: have a have a nice weekend and the rest of the week.
Patrik Stas: Thank you.
George Mulhearn: Thank you. You, too. Thanks, guys.
George Mulhearn: Thanks to you.