George Mulhearn: Hello.
Patrik Stas: Hi, George!
George Mulhearn: Hey!
George Mulhearn: How are you?
George Mulhearn: Hello! Can you hear me?
Patrik Stas: Excuse me for just a minute or 2 before we get started? I just want to prepare a few more things.
George Mulhearn: Okay, now it is.
Patrik Stas: Hey, is there Sorry, George, Can you hear me? I just realized I had the probably my speakers off.
Patrik Stas: Okay, and I didn't hear you. She said something.
Patrik Stas: yeah, that was probably the issue, can you?
Patrik Stas: I was just adding few more things. Few more points to the agenda last last minute. But I think we can get started now.
George Mulhearn: You
Patrik Stas: Okay,
Patrik Stas: So
Patrik Stas: let me share this screen
Patrik Stas: so as usual.
Patrik Stas: i'll.
Patrik Stas: I'll leave this antitrust policy open for a bit
Patrik Stas: and visible in the meantime.
Patrik Stas: yeah, I would like to welcome you, George, and anybody who's tuning in the recording to he's going to call on first first time in 23
Patrik Stas: on January 5,
Patrik Stas: 23
Patrik Stas: yeah, and today there is a
Patrik Stas: bit more interesting at the agenda than usual. As a as I would like to
Patrik Stas: not only go through like the last week day to day. Operation they today work and prs
Patrik Stas: but also kind of review the 2,023, and think about what might be important going forward in 2023.
Patrik Stas: So yeah, let's let's get right into it. So i'll start with the the the usual usual
Patrik Stas: agenda. it should be fairly quick, and then move into the interesting part. So so. As for the recent work done, we have removed, and the
Patrik Stas: public agent
Patrik Stas: a portion of the code base, resulting in nice decrease of 1,000 lines, always always happy to Cprs like this, where we are reducing complexity.
Patrik Stas: So this public agent, abstraction. There was something was pretty much as used for the institutional issue, or very far a use case one
Patrik Stas: so probably not. No, nobody really touched anybody who's using V. 6 on the device.
Patrik Stas: and those this small small pole here.
Patrik Stas: Well, it's already closed, I guess.
Patrik Stas: and I was this short P. Before doing this work, where apparently nobody is really using it. Also, somebody really was using this.
Patrik Stas: So this is gone now. there was some minor refactoring prs which are probably not worth the going into into detail.
Patrik Stas: and then as for what's going right now?
Patrik Stas: we are working still working on the completing not Pr. As base bindings for the no jazz brepper
Patrik Stas: this is also before Pr. In a sense of removing 7,000 lines and adding 2,000
Patrik Stas: in instead. so it's nice reduction of complexity for sure.
Patrik Stas: the the node breaker is much simpler now. it's much faster. It runs with an old 18.
Patrik Stas: It seems to be more stable in Ci. The only piece of work we are now missing. Here is publishing the
Patrik Stas: the
Patrik Stas: and the wrapper to
Patrik Stas: and to the Npmgs, which is a bit more trickier now as we are building
Patrik Stas: because we are building now.
Patrik Stas: note Modules binary file, which we need to distribute along with the repair itself.
Patrik Stas: The along with the javascript files, and that's that's something noble to us. we haven't done before, so we'll have to
Patrik Stas: figure out how to publish it correctly and help publish it for the multiple or different architectures. But it'll be definitely nice
Patrik Stas: also leading to Nice like usability improvement, where basically, when you want to use the Vcx vcx with from Nodejs.
Patrik Stas: you'll no longer need to first compile the rough binary yourself, and then put it into like a system path, and then run the wrapper
Patrik Stas: instead. You will just put that
Patrik Stas: put the
Patrik Stas: A is. This is your dependency.
Patrik Stas: in your note project, and it should download. You know everything I need it, including all the pre compiles for architecture.
Patrik Stas: yeah, so that's that. then
Patrik Stas: we started
Patrik Stas: expand and expanding support for new mediated connections
Patrik Stas: into
Patrik Stas: basically to expose it on the fi layers.
Patrik Stas: there's 2 prs regarding that.
Patrik Stas: and then lastly the the Pr. Which is currently in draft from from George
Well installed. Quit, I guess.
Patrik Stas: yeah, the the Pr. we just adding, which is using critics for verify. But since it's since it's so draft, and and you are here. George!
Patrik Stas: what? What's needed in this Pr. To.
Patrik Stas: you know? Turn it into a Pr. From the draft state. Is there?
Patrik Stas: Is there? Is there stuff missing? I see it's pretty sure, but i'm not really sure how much work is there to do? The very far with the critics.
George Mulhearn: yeah, there there wasn't too much work. There was only really one verify a method which needed to be filled in which was just verify a verify proof. and it it, it seems to be working.
George Mulhearn: have some tests failing because they're not throwing the correct errors.
George Mulhearn: The tests are expecting like a Libindi error code.
George Mulhearn: So now i'm
George Mulhearn: trying to figure out the best way to go about fixing that
George Mulhearn: because I think the right move would be to move away from relying on living the error codes. And yeah for sure for sure, Probably some sort of my custom, maybe customly define error. And then in the in, the in, the in the implementation of the verifier
Patrik Stas: sort of map, that in the error, to whatever a custom a is V: 6 error we need to have or something like that.
George Mulhearn: Yeah, yeah, exactly. Yeah, I I started doing that. and yeah, I just need
George Mulhearn: bit of time to finish that off when I get a chance. but yeah, doing that error stuff will put us in a good place for
George Mulhearn: doing the next set of what is the issue of Api is because there'll be a lot more errors there.
George Mulhearn: and more. It has to do with it.
Patrik Stas: I see I see awesome sounds great.
Patrik Stas: Okay? And now, yeah, now, this is this is for the week, I guess, and
Patrik Stas: going into the interesting stuff. I said, 2,022 review
Patrik Stas: and the and the current state.
Patrik Stas: So yeah, I I think 22 is like really like significant move forward
Patrik Stas: in in
Patrik Stas: many different terms.
Patrik Stas: And maybe i'll jump a little bit here. But actually, I will start with this this this piece here this point here
Patrik Stas: as the increase coming to focus
Patrik Stas: basically like starting for like late summer this year. we started
Patrik Stas: put more focus on like getting more coming, the direction and become more community friendly.
Patrik Stas: so.
Patrik Stas: But we've increased our like discord, activity, and responsibility, and started doing these community calls.
Patrik Stas: and I think it's turned great. because
Patrik Stas: we we we we saw a number of contributors in the Q. 3. Q. 4
Patrik Stas: I guess more.
Patrik Stas: It was. most notably, I would say, you yourself, George, is is, you can with a really awesome and huge pr
Patrik Stas: contribution with the credits integration.
Patrik Stas: but also just recently we saw on discord.
Patrik Stas: added open. Yeah, we we saw a interest from Dinos to implement
Patrik Stas: flutter for.
Patrik Stas: So that's that's that's awesome. How easy, even. he says that he's even planning to open source that and contributed later.
Patrik Stas: yeah, there was also a number of other other contributors,
Patrik Stas: namely, credits to bonfire, and G I. G. 3 P. And t
Patrik Stas: call rps
Patrik Stas: also
Patrik Stas: and then I guess.
Patrik Stas: yeah. So so this this this is important driver for.
Patrik Stas: for
Patrik Stas: I will say, no, actually few few achievements this year.
George Mulhearn: yeah, I think I think it's definitely more welcoming now. Vcx, because, you know, we started looking at in Q. 3
George Mulhearn: of last year, and it was a little mysterious, because there wasn't too many messages and discord, and
George Mulhearn: it's hard to get a glance of what's happening. But there's a lot more interaction now, and it's really good.
Patrik Stas: Oh, yeah, that that's really that's awesome to here. I didn't know that you've been around for so long. Actually.
Patrik Stas: yeah, okay, then, then moving on to more technical technical parts. those definitely progress in modularization and decoupling. So we started splitting out the the individual crates. So now we have a ddo trade
Patrik Stas: messages create, and there's efforts to for the split. Other other bigger crates which for now are like divided into modules. So, for example, recently, Levy cx. Has been, has been split into Api, c. And api vcx.
Patrik Stas: whereas so they are. Comp. And the at the the Api is completely unaware of the upper layer, Api, c.
Patrik Stas: And it's also possible to compile the Vcx.
Patrik Stas: We we dialed the Api see itself, simply excluding it by configuring the rest Cargo features.
Patrik Stas: and then also importantly. And this has been paying for for a long time. We are trying to get rid of the V. 6 Agency Mediator dependency, and just kind of make it optional you know, for at least for now.
Patrik Stas: as although it's it's a pretty useful for the mobile use case, and I think people are using it
Patrik Stas: at the same time.
Patrik Stas: it's. It just makes it much harder for anyone to try out there. Easy 6 right now, as you are kind of
Patrik Stas: It's just this extra dependency extra service you need to have running somewhere.
Patrik Stas: And yeah, that's just like extra barriers. So
Patrik Stas: we'd like to make this optional Also V 6. The mediator itself is not really useful in case you are trying to build. If you're or very far with a is Vcx. So this just kind of adding really extra complexity for such a use case
Patrik Stas: and hands, the work we are currently doing with, adding support for the non mediated connection protocol.
Patrik Stas: and even with the nominated connection. Protocol. You should always still be able to, you know, use the mediation, perhaps aside yourself. But, we don't want to bake it into the Area's Vcx. Itself. Too much
Patrik Stas: so might be useful optional dependency. But we don't want to force this particular medie to implementation.
Patrik Stas: yeah.
Patrik Stas: Then for moving to the next point.
Patrik Stas: I just kind of generic, but lots of lots of energy has been spent on the refactoring and simplifications. I don't have any sort of numbers or metric for this right now.
Patrik Stas: But
Patrik Stas: yeah, that was
Patrik Stas: those
Patrik Stas: along with the testing improvements, I think it's just it's just we. We've been trying hard to make it easier to to read the code and to modify it. This is actually like
Patrik Stas: tides, a lot to the increased community focus. We're in past what we still been paying like old old technical that
Patrik Stas: it would be difficult to actually on board new contributors.
Patrik Stas: But now, with the kinda
Patrik Stas: codes clean up, and technical depth payoffs it's it's. It's really easier, and it makes sense to start
Patrik Stas: start building community, or it's easier to
Patrik Stas: good new people on on tools going on
Patrik Stas: and then the last 2 points was a ith integration. there was a work done by mainly made us now a colleague of my to to
Patrik Stas: increase the the ith coverage.
Patrik Stas: so we have,
Patrik Stas: we have
Patrik Stas: regular integration in interoperability tests now with a of J. And occupy which is it's just nice combo, because
Patrik Stas: many people are using occupy for that for sure. On the other hand, I think many people will also be using Fj. For the mobile use case, so I I find those like a 2 main
Patrik Stas: main pairs to test against. But
Patrik Stas: yeah, going forward, there's still space for improvements for that, enabling more
Patrik Stas: more coverage
Patrik Stas: in the in the short term
Patrik Stas: of December last month of the last year great progress on the
Patrik Stas: No just proper implementation.
Patrik Stas: as I already mentioned in the weekly Progress. we we started using different fi approach, which works like multiple magnitude faster. We know the 18, then the old one
Patrik Stas: And I just also much more maintainable. And say, for all the good stuff
Patrik Stas: at that being set
Patrik Stas: I would I would want to encourage. Yeah, and anyone who was like using as V. 6 for a mobile use case to
Patrik Stas: to
Patrik Stas: either like, try.
Patrik Stas: try, contribute, you know. Try explore different approaches for different approaches than what we do currently with the Java and aisles Ver as I believe there's there's better ways now.
Patrik Stas: and we are solved in the upsa. we are not planning to contribute too much into the Java and Aisles proper anymore. So the fun looking for like contributors in this area. So even in this, in this sense, it's it's great to to hear that
Patrik Stas: dinesh! Is is thinking of contributing new new, more the flock to wiper. So kind of a new approach giving giving new options how to consume the library from the mobile.
Patrik Stas: But yeah, I think there's probably more modern approaches at this point than the way we currently do with the ios and job of
Patrik Stas: I don't have any specific tips. But
Patrik Stas: I believe that there's similar like, with no jazz rapper.
Patrik Stas: I think there's probably better approaches now.
Patrik Stas: perhaps. perhaps. George.
Patrik Stas: you have. You have more knowledge on how to like do at the if I like modern Ffi integration mobile with mobile right? Because you've been mentioning the
Patrik Stas: the the Ffi Library.
George Mulhearn: yeah, I think I think unify Rs is the main one
George Mulhearn: I kind of believe in is
George Mulhearn: being one of the best at the moment.
Patrik Stas: And and when you are like building like with Unifi, you are building just directly on a. Is Vcx. I presume you are not attaching Live Vcx.
Patrik Stas: Part of the code base.
Patrik Stas: Yeah. Nothing to do with Live Vcx: yeah. So I guess. Then there's there's multiple ways somebody might choose to build on. Build some. You you need fi on to on top of Api vcx portion of Lady 6, or perhaps even just directly on
Patrik Stas: there is Vcx
Patrik Stas: which might be actually better option.
George Mulhearn: yeah, it's it's a good question about what would be the better option? Just because I I think unify, has
George Mulhearn: so many great features like being able to automatically generate.
George Mulhearn: you know, full struck types in swift and cotton.
George Mulhearn: and things like that. You don't need to use handlers or things like that. You can just
George Mulhearn: upset
George Mulhearn: what's the cool features like that?
Patrik Stas: This this might be interesting. I guess discussion point for
Patrik Stas: maybe something to to
Patrik Stas: just make sure he's aware of before he come in to the father. Wherever with certain approach
Patrik Stas: as a I know we we in in in like no Js. The the no jazz wrapper we have
Patrik Stas: It's been kind of built on top of handle, so it's hard to run away from me. Now
Patrik Stas: we don't like huge
Patrik Stas: huge reward of the thing.
Patrik Stas: but yeah.
Patrik Stas: maybe, since since this is UN, if I can, can actually generate structs and stuff like this
Patrik Stas: might be better to actually start this
Patrik Stas: on a. Is V. 6 itself.
Patrik Stas: without the that
Patrik Stas: being being and forced to work with the handles. But
Patrik Stas: yeah, what's the next? Take on this, or if if he sees advantage
Patrik Stas: going with the in his case.
George Mulhearn: Yeah, I i'm not. I'm not too familiar with
George Mulhearn: flutter to be honest.
George Mulhearn: or what tools exist there.
George Mulhearn: yeah. Another great part of unif is the the error handling, and how errors get past, you know, through the layer.
George Mulhearn: yeah, it's pretty cool.
Patrik Stas: Nice, nice.
Patrik Stas: yeah. I would be definitely curious to to see that you need fine. Do you think you'd be like you? You You briefly
Patrik Stas: touch touched on it before that?
Patrik Stas: Do you think you'd be able to contribute some like short demo example, like for the actual approach. You know. How does it look like? If you build.
Patrik Stas: you need 5
Patrik Stas: kind of if you you know layer on top of a
George Mulhearn: yeah, yeah, sure, I could try a a proof of concept demo
Patrik Stas: branch. There will be interesting, maybe, for other people to, you know.
Patrik Stas: to to to get in just for inspiration, I guess.
Patrik Stas: But yeah, it's it's if you have resources and time, and if you can do it, it'll be great. That
Patrik Stas: that's I. I'll I'll leave it at that. You know it's it's up to you, but it'll be for sure. Appreciate it now, looking into ahead in 2,023 outlook. so
Patrik Stas: it should be in the the 2,003, I believe, should be in the team of fortification, and just further modularizing and decoupling stuff across the board.
Patrik Stas: and my suggestion here in this issue.
Patrik Stas: also to kind of start this
Patrik Stas: start this
Patrik Stas: gratification.
Patrik Stas: with
Patrik Stas: Who? The message is great just by starting publishing it on a crates. I/O, and I believe this should like drive, drive us to improve the documentation for the create, and also to think more about the Apis like which basis of the create should be actually public.
Patrik Stas: and which should be private.
Patrik Stas: which so far I think we are. We we haven't put so much
Patrik Stas: energy effort into this.
Patrik Stas: And many things are public just because it's convenient. But perhaps not. Everything should be really published out of the freight.
Patrik Stas: And so yeah, I think this this will kind of drive us to to think about. These things bit harder and do things better at the higher quality.
Patrik Stas: and the idea is to start with the messages to kind of learn the
Patrik Stas: to explore the boilerplate, how to actually publish
Patrik Stas: the how to actually publish it from the from the Ci, and how to approach the versioning. Should the messages and the other creates be kind of kept at the same version? Or shall we just start versioning everything separately, you know. Questions like that. Things like that.
Patrik Stas: And I think, yeah, this can be applied. And further to the other
Patrik Stas: crates and modules in the in the current code base as well.
Patrik Stas: I already closed it.
Patrik Stas: we we can do the same thing, for like they do, they do create and video resolver create. Once we implement that
Patrik Stas: or the Protocols grades. And I I imagine this could be like, separate, you know, really kind of individual, well documented, creates on a crates I all people could use and build upon, and and perhaps, you know, contribute into these crates without necessarily
Patrik Stas: dealing with working with as V. 6 itself.
Patrik Stas: The the main a is V. 6, but perhaps we can. We can gain more traction. These, like lower level
Patrik Stas: components which could be shared by other projects which wants to deal with the Aries in in the rest as well.
so trying to find, like a discount.
Patrik Stas: shared the denominator
Patrik Stas: for for different projects.
Patrik Stas: which which you might not be necessarily Irish. Vcx projects.
Patrik Stas: then, the next point here. with I was thinking about this, which I find important, although we just like currently one issue on our repo who is implementing video resolver.
Patrik Stas: and just just generally drive the code base more about Ddos as they are.
Patrik Stas: This I I believe they should be kind of first class citizen in the cold base. And
Patrik Stas: And yeah, I mean it's it's shared
Patrik Stas: kind of data structure across the ledgers. So if you want to be ledger agnostic, which going forward long term, we definitely want to be.
Patrik Stas: Then we should definitely think more in terms of the Id documents.
Patrik Stas: and this is a yeah issue which is briefly describing some issues and things we should think about, and
Patrik Stas: probably can get started with a bit soft in the methods soon, I suppose, During the 2,023. There they did in the met that
Patrik Stas: be supported by in the ledgers.
Patrik Stas: And
Patrik Stas: and also I believe vdr tools itself, not no video tools in the Vdr itself.
Patrik Stas: so we can. We can perhaps implement this as well. And then
Patrik Stas: as a sort of experimental feature, we could perhaps try to harness the the Uni resolver
Patrik Stas: as a way of
Patrik Stas: resolving videos all those. Obviously, this is relying on the third party
Patrik Stas: for the resolution which is not ideal.
Patrik Stas: and
Patrik Stas: it just nicer when when the users can resolve the deals like natively and so sovereign manner without a trusted party.
Patrik Stas: but yeah, the nice nice thing about this obviously would be. Then suddenly we could resolve like videos videos across the board, across all the ledgers. Bit criterion, you know,
Patrik Stas: all, all of those tens of different did matters which exist today
Patrik Stas: not only like your but yeah, just just pretty much everything
Patrik Stas: moving to the next point, I think also important achievement, for the 2,023 would be finishing the migration to to credit libraries.
Patrik Stas: I think we have like.
Patrik Stas: I mean that we are definitely like in Midway, or perhaps perhaps by midway to accomplish this.
Patrik Stas: as we have the holder and the we are part pretty much done.
Patrik Stas: But
Patrik Stas: Well, actually, even the verifier seems to be quite quite easy.
Patrik Stas: And
Patrik Stas: now it's a matter of finishing off the word with the issuer.
Patrik Stas: which might be more challenging in terms of implementation. But then also the
Patrik Stas: the migration from the old
Patrik Stas: from the old Vdr. Tools
Patrik Stas: to the credits libraries
Patrik Stas: not sure what this is, gonna
Patrik Stas: what what it's gonna take. But
Patrik Stas: definitely it's important for us to enable the issue who started
Patrik Stas: on the
Patrik Stas: Vv. Our tools
Patrik Stas: should continue operations with critics credit libraries, and
Patrik Stas: I don't know. I guess it depends how things are being stored in the wallet, and things like that.
Patrik Stas: I'm. Not really sure exactly what this challenges are, but the the the the data structures in the wall, it should somehow stay intact. So switching to the credits, libraries should
Patrik Stas: should be somehow possible for the yours.
Patrik Stas: Then yeah, Well, once we are, I guess. Once we are done with this.
Patrik Stas: we can.
Patrik Stas: we can focus. We can continue focusing on the areas as car support
Patrik Stas: which is now challenging because of some conflicting dependencies between the critics
Patrik Stas: and in the media and the Vdr Tools Library
Patrik Stas: So we will. We'll see how I guess how this goes, and then we'll
Patrik Stas: we'll continue looking at
Patrik Stas: what it takes to to move on to Aries as car wallet
Patrik Stas: so actually, maybe I can edit here. I think it's good important point, and it should deserve it. It deserves to be on the list.
Patrik Stas: I guess I think
Patrik Stas: I think support
Patrik Stas: and it's for
Patrik Stas: for Aries as well. That's
Patrik Stas: and I guess
Patrik Stas: Products library libraries on the issue of boss
Patrik Stas: very far.
Patrik Stas: and while it there should be some enable enable migration
Patrik Stas: of Vdr to
Patrik Stas: you, sure
Patrik Stas: to become a critics issue.
Patrik Stas: I'll save it like this.
Patrik Stas: yeah. Then then there's again a bit a generic point here for 23. But just generally you want to improve the code quality getting
Patrik Stas: there's still space for improvements in terms of like utilizing, you know, being more trade focused
Patrik Stas: do more typing. There's okay. There's number of
Patrik Stas: the
Patrik Stas: cases across the board in the code base where we're passing strings where actually we could, whereas we know it's particular type of string. For example.
Patrik Stas: at the Id there's places in the code base we are passing the Id as a string. But
Patrik Stas: It will be just much safer to work with the the code base if we had some sort of type for the did itself, whether it's just like alias, or it's actually something more in the end, which can, like cereals, serialize the
Patrik Stas: stuff like that.
Patrik Stas: And and this could be applied for not only the Ids, but also like
Patrik Stas: keys, public keys and
Patrik Stas: perhaps Urls
Patrik Stas: might be more.
Patrik Stas: And then and then, lastly, also. Importantly, I would like to speed up the test execution.
Patrik Stas: just like a recently, I think a month or 2 ago I was mentioning
Patrik Stas: the improvement, like multi
Patrik Stas: like magnitude, order of magnitude, improvement in
Patrik Stas: in execution of some particular test, where we, where we removed the Mediator Agency, and and instead started using sort of in memory channels instead for that, for the communication between 2 parties in the test
Patrik Stas: which which led to a really huge
Patrik Stas: test execution, improvement.
Patrik Stas: and it would like to, you know, driving. Continue driving this for further on the more test, and just make the integration test really as fast as possible.
Patrik Stas: and it's kind of like closed loop, I guess you know. Then the more we improve on the code quality and the test execution
Patrik Stas: the easier it's going to be it's gonna work on the next point right here the common thing engagement.
Patrik Stas: if the if that if the code is better, easier to read safer, easier to contribute
Patrik Stas: it. It tests easier and faster. It's also easier to gain more traction with the potential contributors.
Patrik Stas: as it's easier for them to to get started, and and that's something I will still like us to to improve. There's definitely gaps in the documentation right. Now.
Patrik Stas: it's just how to get started.
Patrik Stas: And but also more in terms of more technical documentation. Is
Patrik Stas: as there's not really any like
Patrik Stas: Ward. Word documentation on the area's Dcx level. There's a document all the documentation on the live B cx layer, which, however, might be even per
Patrik Stas: outdated and in some cases.
Patrik Stas: but yeah, I would like to just mainly focus on the aeries Vcx As a crate and as a as as an and it's individual sub modules and sub-
Patrik Stas: and focus on getting that as a core core piece of the whole project getting getting to the best possible shape with a nice documentation.
Patrik Stas: and making it easy easier for people to get started. So these also ties to to the agency. We are the the Mediator Agency. We are removing now as a
Patrik Stas: because right now you it just it's it's being
Patrik Stas: an extra barrier to get started.
Patrik Stas: so we would just like to have some
Patrik Stas: really simple, ideally some simple example built on top of Eric's Dcx code somewhere on the main rhythmic page, where
Patrik Stas: you would see like
Patrik Stas: how to
Patrik Stas: how to do something you know how to send.
Patrik Stas: let's say a did come message over over using ours, Vcx. Or maybe issue credential or something like that, just like really short, concise demonstration of ours. V. 6 Api. Which will be able to run
locally without much obstructions
Patrik Stas: and much pre requirements.
Patrik Stas: I think this has like improved a lot in 2,022 actually where we're originally.
Patrik Stas: you had to
Patrik Stas: bills.
Patrik Stas: Vdr: tools slightly bindi first.
Patrik Stas: and set it up into your like system path. And then you had to build
Patrik Stas: the live Vcx, and and it just had this kind of indirect dependency. It's runtime dependency, and this has been removed that the like towards the end of 2,022, where right now we can run cargo, build in Ariz, Vcx, and then just build all the dependencies.
Patrik Stas: so it's it's simply batteries included, and you don't really have to go ahead and and pre build Vvr tools manually, or something like that. But yeah, there's still ways to, I think.
Patrik Stas: Make Make it easier for people
Patrik Stas: to get started. And yeah, I guess this is related.
Patrik Stas: It'll be. It'll be great to see more
Patrik Stas: project examples.
Patrik Stas: whether it's like as a 5 repairs or agents, or
Patrik Stas: it's pretty much anything, and I guess at this point we have.
Patrik Stas: Well, we we could say that we have a few of them right now.
Patrik Stas: I mean counting Lib. Dcx is one of the craze being built of a a. Is V. 6, that's one.
Patrik Stas: But then, for further, we have.
Patrik Stas: and now we have rust agent.
Patrik Stas: we just
Patrik Stas: build directly on top of a
Patrik Stas: Then we also have
Patrik Stas: right now, just as a pull request. But we have a further iteration. On on top of that we have a cli
Patrik Stas: program.
Patrik Stas: a build on. These Ares v. 6 Rust agent, which which lets you to to perform basic operations from Cli using a
Patrik Stas: and then you know,
Patrik Stas: this flatter wrapper from from
Patrik Stas: or perhaps if you, George contribute some unifi
Patrik Stas: example that would be awesome or actually just like, I would love to see any kind of projects built of what build on areas Vc. Eggs.
Patrik Stas: Perhaps that kind of like side project I have personally in mind. Are we building my theater with which is now
Patrik Stas: again, thanks to the dec decoupling from the
Patrik Stas: the Pcx Agency Mediator. Now it's possible because
Patrik Stas: you can use you can use as connections
Patrik Stas: without mediation, which, in fact enables you to build a mediator on top of.
Patrik Stas: So that's it's kind of a project which would be cool to see as Ross is super fast and
Patrik Stas: and and and mid mediator is kind of like a middle middle middleware type of project, and I feel like a rust is really
Patrik Stas: a good candidate for for this kind of implementation.
Patrik Stas: yeah, and then and then finishing off this list.
Patrik Stas: obviously will be nice to I had a new protocol support, I think, namely, and and most importantly, the did exchange protocol
Patrik Stas: probably a a probably update support for the
Patrik Stas: the new versions need newer versions of the issuance and verification proved verification protocols, which should be fairly low. Hanging fruit, I imagine.
Patrik Stas: Nevertheless, it's still some work which is.
Patrik Stas: I have to be done.
Patrik Stas: And
Patrik Stas: so yeah, that's something to look out for. 2,023. Hopefully, we'll get that done.
Patrik Stas: and then
Patrik Stas: I think it will be also great to to dig into the discom 2 point of exploration. Although this might be a bit more disruptive work, I assume
Patrik Stas: I Haven't explored it to 2 point on the match yet.
Patrik Stas: But there's I know that there's number of differences, and i'm not sure exactly what what impacts Won't. What impact this is going to have on the is V. 6 code base. But I don't think it should be significant, because
Patrik Stas: did come is really just a
Patrik Stas: the Communication exchange.
Patrik Stas: and it does it. It shouldn't really impact the other areas protocols which work over did call so, whether it's whether it's, Ehr or presentation protocol, they are pretty much agnostic as to what kind of channel has been used to
Patrik Stas: exchanging messages.
Patrik Stas: so
Patrik Stas: possibly this gonna have, like
Patrik Stas: disrupt the connection, or did exchange type of protocols
Patrik Stas: somewhat. I'm not sure.
Patrik Stas: but I think even if we i'm not sure if we gonna
Patrik Stas: fully Blumen did come to point out this year. But it'll be, and definitely nice to at least get a clear picture on what to expect from it, and
Patrik Stas: what's what it's gonna look like. Once we start implanting it just to kind of get that better vision of yeah, what? What? What is gonna bring
George Mulhearn: So I was gonna say, yeah, I think I I think, occupy have some maybe all of did come v 2
George Mulhearn: implemented in that code base. I'm not sure if they use it. But there's definitely those files set up to
George Mulhearn: you know. Pack and unpack. V. 2 messages using ascar.
George Mulhearn: I'm not too sure if it's possible to do it
George Mulhearn: using live Indie
George Mulhearn: just because Libby and the only has the pack and on pack
Patrik Stas: methods, you know. Yeah, yeah, right? And also I think there's there's like there's other differences other than encryption, I think, like you actually specify transports
Patrik Stas: in those messages you are sending directly, so as I, as as far as I heard, basically did come to point out, kind of eliminates the need for the for the connection and the Exchange protocol
Patrik Stas: to some degree. I'm not sure. I'm not really sure. Maybe i'm not sure if i'm correct here. But that's full. I remember there's this nice website, I think, where which is describes the differences.
Patrik Stas: did come
Patrik Stas: me too.
Patrik Stas: this is this guidebook, I guess.
Patrik Stas: Well, I know why it's so slow. No, this is not exactly what I was looking for.
Patrik Stas: yeah, no, no, it was different. What?
Patrik Stas: What's new or something like that? What's new in that come to? So this. This describes it but nicely, and there's
Patrik Stas: few main points here. But I guess let's not get into technicalities here too deeply. We can maybe. yeah, set up some meeting, some, some some of the weekly calls to kind of look through it that directly, in like a kind of workshopy, collaborative way, and just
Patrik Stas: i'll learn together about
Patrik Stas: how to implement it. Come to.
Patrik Stas: into an into how to integrate it into in the
Patrik Stas: yeah, i'm not sure. What did I what I meant with this last point? Maybe I used to
Patrik Stas: right something more, and then I didn't
Patrik Stas: so.
Patrik Stas: I think i'll just delete this off. I think it's an error.
Patrik Stas: And yeah, that brings us to the end of the list.
Patrik Stas: So yeah, that's
Patrik Stas: that's it. So we have
Patrik Stas: also work to do in 2,003, and it's really exciting to see more people coming on board, which
Patrik Stas: makes me more confident about the all this stuff actually getting done as opposed to a big portion of
Patrik Stas: like pre 2,000 to 2,022 and pre 2,022 we we didn't have such a come into focus. And there was less people always the less people coming in and and contributing
Patrik Stas: So
Patrik Stas: yeah, it's, it's it's exciting to see
Patrik Stas: new people joining in and
Patrik Stas: having really nice contributions.
George Mulhearn: It's a great list. It's very exciting.
George Mulhearn: Thanks for putting it together.
Patrik Stas: Yeah, yeah, awesome.
Patrik Stas: I don't know. Do you have anything, any, any any thoughts, or
Patrik Stas: whether it's on 20, maybe 2023 kind of plan or anything else you would like to see
George Mulhearn: I think I think we covered it all really.
George Mulhearn: I think.
George Mulhearn: Personally, the protocol stuff.
George Mulhearn: I think, will be pretty exciting. and also
George Mulhearn: turning Aries Vcx into its iron crate.
George Mulhearn: that that can be published.
George Mulhearn: you know, To create tire
George Mulhearn: will be a a cool journey, I think.
Patrik Stas: Hmm.
George Mulhearn: Yeah. Just because, you know, they'll be
George Mulhearn: a few hurdles, I think, like, I I think, to get things published on crates. I you can't have any get dependencies and things like that.
George Mulhearn: So then, you know, we might have to
George Mulhearn: publish the fork of video tools on creates I as well, or something like that. And
George Mulhearn: Yeah. Oh, okay, I see
Patrik Stas: right right then. We are using now those good dependencies a bit.
Patrik Stas: Yeah, I guess we'll. We'll have to cross some cross, some gaps, some.
Patrik Stas: But
Patrik Stas: I think if we start actually, we'd like those lower lever like, I guess, publishing as a create might be a bit challenging in in in exactly these terms as you describe. But
Patrik Stas: then, if we start with like those smaller crates, and those sub sub-crates
Patrik Stas: might be actually easier than because they themselves have very few dependencies Like when you think
Patrik Stas: about the
Patrik Stas: the the messages, or did Chrome Cr. Or
Patrik Stas: perhaps in the
Patrik Stas: for the calls
Patrik Stas: great. Once we extract it, those should be fairly simple ones.
Patrik Stas: so
Patrik Stas: I guess maybe not not so difficult there. But they're not. Once, once they move up the stack, then
Patrik Stas: maybe we'll we'll get a few more challenges, but in the end I guess you know I I I guess it's still just driving it. It might be challenges, but it's really just driving us
Patrik Stas: to the that right. Directions, I mean
Patrik Stas: project sounds definitely Sounds more sounds to be more mature if it doesn't have get the dependencies right? If it actually depends on the other trades which are
Patrik Stas: properly published.
George Mulhearn: So yeah, exactly, yeah.
Patrik Stas: yeah, just it's remove removing the
removing, drive us to remove the cold smells and
Patrik Stas: and
Patrik Stas: improve the recommendation.
Patrik Stas: The Apis. I think it's gonna be it's gonna have a nice second order effects
Patrik Stas: the the publishing itself
Patrik Stas: any I would be, I would be really excited, I guess, for 2,023 if if we publish some of these crates like not Aries Vcx. But let's say Aries messages.
Patrik Stas: and it will be exciting to see someone else building different projects, maybe different, every implementation whatever.
Patrik Stas: but actually somebody utilizing those, you know, sub crates for themselves and and and having contributors who are interested in.
Patrik Stas: I don't know did come, or did resolver create?
Patrik Stas: But not necessarily Aries dcx great, and then
Patrik Stas: start start working on those the the shared pieces together.
Patrik Stas: That will be really cool to see.
Patrik Stas: All right. yeah, we we spend almost 1 h going through this list.
Patrik Stas: so it's it's pretty much, and
Patrik Stas: and time to wrap it up.
Patrik Stas: I guess that being said, yeah, this is the first time we are speaking, George, this year, Isn't it?
George Mulhearn: Yeah, a New year.
Patrik Stas: Yeah. I also also have been here to yeah, anyone who who who tune in today.
Patrik Stas: again
Patrik Stas: anybody who is listening. we are very much
Patrik Stas: we are very much happy for anyone to to join the meetings
Patrik Stas: feel free to go ahead and modify the agenda. If you would like to attend the next meeting on 12. You can just
Patrik Stas: come into this week, Page and
Patrik Stas: and i'll add points you would like to discuss here.
Patrik Stas: Yeah. So feel free to join. Thanks for listening. Thank you, George, for being partner. My partner here discussing the the library outlook
Patrik Stas: and the reviewing it's it's much easier to to talk when when there's somebody somebody to talk to. Actually.
Patrik Stas: So. Yeah, thank you very much for your time.
Patrik Stas: it's almost weekend, so enjoy a weekend, and
Patrik Stas: and i'll be here next week again.
Patrik Stas: No worries cheers, thank you. Curious, Thank you.
You.