 All right. Well, the recording has started and I'll see you later. Cool. Thank you. Glad you're here with the late notice of being the meeting being in our our earlier. So it's now updated in the calendar and well I think we should be good now so let's hope this is the last time we have to move it. So of course the next time comes up that we have to move it, but let's hope that doesn't happen for a while. Let me see. Meeting notes in chat. Awesome. I think we can get started and maybe someone else joined still. But let's get started. Let me see. I need to remember to remember you to abide by the high political conduct and antitrust policy. If you would like you can add yourself to the tennis list. People know you've been here and can reach out to you if needed. Is anyone new here today that would like to introduce themselves. Yeah, hello. It's from my first meeting. Which I am. My name is Aziz. I am from the SAR and we use it is framework or script in our projects. Yeah, it's me. Thank you. Cool. Good to have here. This is Saroj here. So I'm also joining the meeting for the very first time. I'm from India and I'm using the whole like areas framework and I'm trying to integrate with it by fold application so I can have a mobile visit mobile region for my project I have been asking a lot of questions recently. So I have your doubts so if we'll have the time I'll go through them also thank you. Cool. Yeah. Nice to have here. Anyone else or otherwise we can just get started. Cool. Okay. And let me see. And let's quickly go through all the status updates. Was there a bifold meeting this week. Update on or whether you know it was this week. Alright, I can at least give an update on the work we've been doing with bifold is slow. Can people hear me fine or is the connection choppy. You are a bit laggy before but it's fine now, at least for me. Yeah, please let me know when that was against maybe I can switch to my hotspot then. And yeah so I've just been working continuing to work on like the move to the shared components removing in the SDK and using the area Oscar in the VDR are on our credits. That kind of works we just need to still test the migration script that's being added but like checking that if an in the SDK was this correctly upgraded and once that's done, I think we should be able to merge. There is the issue still like supporting older Android versions which I think the busy golf team is looking at currently. No, I was a bit late I sent a message that I think we can have a meeting about tomorrow and then they will look into it, but that should probably start I think late this week still or next week. Okay, yeah. Okay, so that's it on the. Yeah, bifold creation but yeah it fully works in in native now and yeah we hope to have them bifold updated to a fj zero four zero soon with shared component libraries. Yeah. Where's my screen. Yeah, I still also hope we can soon get expo to work. If you're building a custom wallet with shared components because I think that will make for the easiest setup but for at least for now like the bio project doesn't use expo and that that's working. Yeah, fine. So, yeah, let's hope we can really soon make the stable releases for for all the dependencies and then that probably a lot of books to fix that we will discover because there's been a lot of changes but yeah I think we're, we're getting there. We want to test it out already I think now would be a good time to do it if you pick latest afj with the latest shared component libraries and add them to your react native project it should work out of the box. As I mentioned expo doesn't work yet so you need to do like a plain react native project but then you can just add dependencies set it up and it should work so yeah. So just to test it out and provide some feedback then are like test it out and see if there's any issues that they could also be appreciated. Cool. Then on the RS call I wasn't there but I think they talked about the fear again was anyone at the air at the air is called. I think Ariel you were right or. Yeah but I, I joined it late so I don't know. I don't know exactly what I think that they were mostly talking about the OCA, because Stephen did a presentation but I joined as I say they joined later so I have not so much. Yeah, OCA bundles Stephen kind of did a presentation for the pretty much the whole meeting. I'll see if I can find the link to his presentation with sir. Rather his. He should have kept it he gave it there was a link to a GitHub repository Ariel did you get that. No, but I can, I can look at see if you can dig that out. That was all there was entire meeting. Okay, cool. Then yeah, if you send the link then I'll add it here. By forces, you are open for sure. And it. And you can add the link here. Cool. Okay. This will be to a p three. Any updates on that in the last week. All right, then for the shared components as I just said, works in reign native now we have a PR open in by full just need to check with the migration script but otherwise were as good as go to release I think we're now on what is the Oh, I think these are the so. This one. Yeah, so no support for older Android versions yet, but otherwise they work. Cool. Okay. Any questions for the more on the share components or the bifold integration or the whole zero for zero release or. Okay, then let's move on to the agenda. Link to as one you mean the link to this document. I'm assuming so so I'll share this. Cool. Okay. Yeah, so quickly announcement is that there's a new time for this meeting. It's now is the hour before the to see and it's also anchored in the US time zone so it will be nothing new to see anymore. There's a new link for it and I'll update it to. I'll update it to in the wiki after this meeting so people can find it for future and I think it's also mentioned in the AFJ. Yeah, in the AFJ repository. I don't know if it's in the bifold I don't think probably only the bifold link but yeah if you find an occurrence of like a link to anywhere. Yeah, please update it to this new link because the old one will stop working. I wanted to discuss to get a burner limitations for a bit that has been popping up but I didn't have a lot of other topics for the agenda for today so I'm curious if people have topics they would like to discuss. Maybe later I can, I can show you the, the individual proxy that I mentioned last week. You know that, yeah, maybe when, when the issues on on Android are solved. I mean, the Android versions, maybe it will be needed for some uses uses but maybe for others, it's, it can be useful so maybe I can show you. Cool. Yeah, I think that that will be nice. I think it's also like with being behind the firewall this has been an issue before so yeah. Cool. Yeah. On the last meeting we briefly talked about the 050 the feature release planning. I don't know if I had a chance to think about it of some of the other features or maybe somebody else has something else to add. Sorry, I need to quickly switch my internet, I think it's not working today. Is it you, is it me, can anybody else hear me. It's Tim, it's Tim. Maybe we can continue discussing about the 050. No, I think Tim is pretty straight. Yeah, you're switching to assault. Okay. I guess not. Yes, I just heard something. Okay, okay. Can you hear me. Yes. Okay. Perfect. Sorry. I just switched to my hotspot. I hope it's better now that internet at the office here is sometimes really bad. Okay, cool. Sorry, what were you saying pleasure because I missed the important part of your sentence. I think that's not what you were saying. I just typed in chat so you continue the conversation about prioritization for 050. Or was it the next release. Yeah, yeah, yeah. That sounds. Yeah, I think that's a good one. Let me copy the notes from last week. I did like this. Cool. Okay, anything else. Okay, then let's get started. And so I wanted to have a quick discussion on the get the burners limitation is that since recently hyperlature not hyperlature get up has started enforcing a rule they've had for a long time is that you they hyperlature has 23 runners. Which means that they're now completely always overloaded because across hyperlature a lot more runners are being used and that means that for a quest have been queuing for a long time. So it makes it harder to merge PRs and get the CI to pass, and it doesn't help that we have flaky tests because then like re running can literally take hours and hours and it's been quite an annoyance so I think point a here is. Please be aware of that that it can be at the moment quite hard to get CI to to run so that it may take a bit longer. Be it. Maybe we can look at reducing our load a bit because we've never looked at that but I know like we have tests in four different node just versions I think there's pure opportunity to tune out because we drops from note versions but. Yeah, maybe there's some things we can do to minimize the amount of resources being used and the question was also somebody maybe wants to take a look at that and see like if we can can optimize it a bit. Well, but no, no, that we are going to only test on node 18, I think it's 16 and 18 right, so we will reduce a little bit the load. Yeah, but I think 20 will come out in a few weeks I would say I think it comes out in April. And I think we should add that as soon as possible. I do think we can maybe stop supporting like non LTS versions I think they have like always the, like the odd ones are not not long LTS and even numbers are, I think. So we say like we support 16 1820 or something. Or would you say like we support everything also 19 and like everything that is currently not end of life. Well, actually, I don't know, because up to now we were we were running on 1416 1719 right. But yeah. Well, what's the reason of that I mean that for the seven because this is 17 is more, more or less like 18 right or, or isn't like that. Well, I don't know. Have you found issues on 17 that were not in 19 or Yeah, like experimental right there experimental and the even ones are the long term support ones so odd as if you want to try brand new features that are going to come out probably in the next even numbered one. But the ones that you want to use in production are usually even. Yeah, that's a thing also what I like I never know people that run know just 15 or 17 you're always like you move from the even to the even ones unless you're. So that was thinking that this also is like a bit of a less like matrix we have to support but then we have like the 16 which is in maintenance we have to 18 which is long term support and 20 when it comes out we added but like 19. We can then skip just to like make it a bit less of a target we have to support and have to test for and deal with. But it's probably like, I think if we support 20 and 18 I think we'll support 19 out of the box there's not too many breaking changes always in no chess releases. Yeah, I think if you can support the. I don't think we need to support the releases in between necessarily. So I agree the thought process for me that reduces the hub runners issues, as well as maintenance that we need to do to troubleshoot issues on the other versions. I think for react native it's also not an issue right I think that also worked with quite a broad number of no chess versions usually to like which you need for react native development. Yeah I think doing the CI is. I think the good CI options for testing across a variety of react native versions. So, I think the node, the node tests is where I would probably stick to and then rely on implementation rely on bifold tests to handle that with the react native pieces. Yeah. Okay, cool. So it's quite an interesting thing that you like. We don't test in react native afj but there are certain features that are like with all the different issues you have like just core and Hermes and that not everything is supported in every engine which sometimes makes it like a bit of a trial and error and see like if we add this doesn't break. Yeah. And it is challenging to test. So it's definitely I think we've done a good job at handling that so far though. Yeah. Yeah, cool I think bifold is also good place there to just like test out if things break and make sure we can fix them. Okay, then I think not much on that anymore I think I've led to probably come with some sort of solution and I know they had some self hosted runners we may be able to use some of them and we can reduce the resources being used a bit but also like as an FY it can take longer to get things. Merks, and it's always, I still want to look at the merge queue for AFJ I just wasn't sure how it works with squashing and the signed off by because currently what we often have is there's a lot of PRs and we all want to merge them then, like we run one PR that then succeeds but in the meantime another PR is merged so then we have to update the branch again and then the CI has to run again but then another PR merge and then like the CI has run like six time on the six times on the branch and it hasn't been merged yet because every time another PR is merged so it's sometimes difficult to have an order in which we merge PR for which the merge queue could be really useful of course. So I think it's also something we can look at to not have to manually. Yeah, go at each PR and just update them all. Every time. Cool. Okay, anything else on this otherwise. I think, and we all can show us the individual proxy. Okay. Cool. I'll stop sharing. Let me know if it's. Okay. Can you see the screen. See. See, perfect. Yeah, I don't know exactly why but the guys from animal have started to speak in Spanish between themselves. I don't know if it's for my influence or what. But yeah, it's, it's only one word. See. No, but the other day they say gracias amigo, which is also fun. Well, this is, this is, this is a repo we have been publishing. We have, I will send the link after the idea of these. This proxy is to allow. It can work for any application but based on a of shape at the main idea is to, to allow a mobile application based on a of shape to access in the objects. Without the need of embedding the in dvdr client. So, what are the reasons why you will want to do that well. We can say for instance that we can make the application a bit lighter so because we are simply using an HTTP rest API to to access to every every lecture instead of having to open. hundreds for for each lecture you want to support. And also, we can solve the problem of some, some. Traffic filters that there are that prevent mobile applications to access seven q sockets like the ones from indy. And also, well, in this particular case that we are having now that we have a problem with the with the dvdr that is not working on Android versions below. 11. We can skip that and work on on any. Any, any Android versions. After seven, at least. So that's why I have this emulator. It's an Android seven emulator just to show that it's working. It was a bit hard for me to use it because I, it feels like a bit a bit old right. But, but so here we're here I have the, well, I have the proxy server, a proxy server running on my local machine. In this case, the app is, is using it. And I will use the animal demo, the classic animal demo. Just to show a bit. How is it resolving the, the dates and schemas and so on. So we have, we have our, our application here. And I will do the connection. I choose John. Here I have this. So I scan the, it's like my, my, my PC is getting a bit slow with the screen sharing. Okay. Now we are connected. I swear that it, my computer will work a lot better without the screen sharing. But okay. We have the credential offer. And when, when we accept it, we should start fetching the credential definitions, the credential definition from the, from the lecture. In this case, we are using the VC offering test network. I will see if I can show a little bit bigger. But you see we have, we have here the retrieving the credential definition, the schema and the credentials issue. And all, all of that without the need of using in the application, the, the, in the video. Right. This is more or less how I, how we are initializing the age and I will show you. We, what we do is to, to provide the individual base URL. And we have to, we simply register the, the, to the unencredited module, the individual proxy registry. In this case, I'm using also a new did web and on credit that we are developing. Because in our project, we are not using in the video for, for, for our credentials. And also, in the, this module, we have this new, this individual proxy did resolver that is based on this proxy base URL. So, basically, if we see the repo, in the case of the, of the client where we have this explanation, as I said. And in the, on the server side, what we have is a server that is also running and agents. Actually, we, we started by using the plane in dvdr library for that but then we found out that it was easier if we took advantage of all the work that has been done on, on the management of the different pools and so on. In the, in the dvdr package for, for, from AFJ. So we are using AFJ in this, in this server that can, can run in a standalone way like, like it's running in my machine. But also you can import as a module. So we are using nest, nest.js because we are using nest.js for, for our servers. So, for, well, maybe that's it. Actually, something that I would like to, to say also is that maybe this can, this functionality can be added to the, to the rest interface for the, the, the, the, every JavaScript. Next package. Next repository. But the problem I actually I wanted to, to, to add it, but it was easier for me to, to, to, to do it like, like that because at the moment it's a bit outdated the nearest API. So, maybe we can, as soon as we can release the zero four zero, maybe we can, we can do an update on the, on the rest package and probably add this this Anoncret's schema credential definitions and objects that can be useful also to, to use as a proxy, right. So yeah, so this is how, how it's working. I will stop sharing so I can leave. I can leave my CPU to have a brief. So, I want to say this is pretty cool aerial. There's a little bit of a phone overlap where in DCO has been working on the individual proxy work as a client. So we've done some implementation there and I don't know how those two should converge. Our approach was to make a similar module to like the NDPR module that you could register that in, in place of NDPR would use the similar functions and there's a little bit of awkwardness and timing based off of we were trying to do it while the middle of the zero four zero refactors were happening so there would be a little bit of refactoring we need to do I think but there might be some things where we want to conversion our approach. Okay, yeah, in this case actually if you see if you look at the repo you will see that there is not so much code added to what has been done and I will show the, I will share the link. And because we are actually using mostly what is what has been done on the NDPR package and also respecting the same API for the resolution. So maybe I don't know in the case of in DCO your, your development has been done for, for AFJ clients or, or for any client. I mean it's a general API or we were specifically focusing on the AFJ client. So the mobile side being able to use the exact same call to I want to get a credential definition. It doesn't necessarily know that it's going to use the NDPR proxy or for it's going to use any DR. We were just using the, in terms of the actual server we were just using that straight out of the gate that is in the in the NDPR repo itself. So we didn't do anything in terms of wrapping it with AFJ, which sounds nice because it is clunky in terms of you have to run multiple servers to handle multiple ledgers for instance. Yeah. Yeah, because I have seen in the, in the NDPR repo, there is a, there is a proxy server, but yeah, it's, it only works on a, on a, on a, you have to do an instance for each lecture you want to support. In, in, at the moment we are only using it for, for resolving the objects, we are not using for, for signing transactions. So, because it's actually, I think it's, at the moment is, it's the only use case for mobile, but maybe in the case of the verifier can be, can be added, but for the moment as a holder site, I think it's, it's enough. But yeah, maybe if we, if you are going to, to support the registration, maybe we have, we have to think a little bit about how to, to pass the ideas or I don't know. And about the question, yes, in our case, our mediator, but we are calling the cloud agent, because it has other features other than the mediation. In, in, in there we are adding this feature. So we have, it's, it's part of this mediator, let's say. I think the, the key thing from when we have looked at it, it's not necessarily tied half, like you can run it on the same server as the mediator, but it doesn't necessarily have to be the same server. So you, it's not tied to it, but it can be. Exactly. Yeah, yeah, yeah, exactly. Yeah, in this case, you can, you can run it in the same server as you say. As we are using an agent. An AFC agent under the hood because we have to instance it to, to run the, the individual package and the unload the young on credit package and so on. You can use the same agent for, for your mediator and for, for your individual proxy, if you want, but if not, it's, you can use it as, because in our case we are using also if AFC for for mediation. Actually, we are using AFC for everything in our solution. I, I thought there was an idea or proposal to for that to be kind of the same way that ACAPI and agents have feature discover mediator would have that feature as well and kind of wall out just out to discover that the mediator support media and auto configure things. So, I, I, one of the things I'd say is that we had talked about a variety of solutions and I don't think that one's off the table of from a short term perspective the Indie VR proxy is a really good option, but from a long term perspective it would be really nice to be able to directly to the nodes via HTTP or talk to them via did come or talk to a proxy that's sitting in front of the, the ledger, whether it's a proxy for the node or you set up the mediator to do be able to query the ledger on your behalf. So I think that we talked about a variety of things and that hasn't been implemented but I think it's still on the table as an option is just a, it's a longer term option than than the Indie VR proxy. Yeah, yeah, this is a solution for today. Actually, but it works and but but yeah for sure, it will be better if the nodes can talk directly on HTTP. I don't know exactly why they choose not to support it. Right from the start. There should be a reason for that. Maybe that there is a problem that we have to think about is that we have we usually connect to, to multiple nodes. So, so we have to have a connection to to four or five or no, how many nodes at the same time to check the transaction so maybe that that can be still an overhead in a mobile environment. Even if it's HTTP or Bitcoin. I think the option that we're leaning towards is a having a proxy. I say we, I think the discussions that I've had with the DCO and or related conversations has been leaning towards the option of a proxy server. In front of each individual node and allowing them to communicate over HTTP or HTTPS. There's a little bit of a issue there in that the nodes would prefer to be able to use just IP addresses and you can't do standard. So, so science certificates may give us issues on the mobile end, which is what you have to do for the, not having a domain name. So there's a little bit of digging that we needed to do there but I think that's the option that was last discussed most in depth. And I would be quite curious in like if this is the, like, how easy would it be to like if you say like every node hosts their own proxy and an agent would connect like how easy would it be to have like a single proxy or I don't know how we would call it right now but that it's just a pass to window. So, for example, the proxy just connects to a list of nodes and you just send the request to it which is already signed and it just submits it and it returns the transaction for you. It could also be possible or yeah, that's still the client verifies the responses from the ledger it's just like passed through the proxy so you don't need like to connect on the TCP level to the nodes itself, but you could still I think, keep a list locally or something so if I want to connect to the indicio network I could still have the genesis file on my end and just verify the response against the different like whether it's signed by specific nodes with that also people's force that would like really complex or. I think that's the other option that's been discussed and we've talked about putting that mediator itself. I think one of the concerns that was expressed with that option is there's a privacy concerns. So for instance, if you have someone who is running a service of this, you could see what schemas revocation registries they're actually attempting to fetch. versus if you compare that to the mediator the mediator can't see any of the messages. While if you do something in front of the nodes directly the nodes are going to be seeing what you request anyways. So, I think that was one of the things that was expressed there. Okay, yeah, because isn't like how all other. networks like normally you always connect to an RPC URL. That would be exposed to that same concern and right or is there a today solve that in a specific way. I'm not sure, honestly. Yeah, our requirement since we're specifically. I think our community is very privacy conscientious and so there may be additional requirements we have in terms of the, like the any ledgers that we've done so far. But I'm not the expert on that topic so. Oh, it's cool. I see it's already open source and so it works with AFJ. So for zero. And it's just a plugin replacement for the individual module right so if you use this client, then you don't need to add the individual module to a but you use this individual proxy module. Actually, it's it's not a module yet. It's just a bunch of classes because. Actually, I, well, I think we have to rethink a little bit how, how the modules will register in terms of the unencredited registries and on the, because at the moment it makes it makes no sense to to create a module for that because you you really still need to provide the, the, the instances to the, the module and the unencredited module. So that's why for the moment it's just a collection of two classes actually. And you, you manually, you just imported from the package and you manually add it to your constructor. It's a bit weird with some modules that it's that you explicitly provide what you want to register and with Sunday just like do that internally. And I'm also not sure what's the best approaches yet I think the one thing it's a bit more explicit and it allows us to know exactly like what you register so we can correctly type the agent. But it's also weird that in some places you have to register it explicitly and some ways it happens implicitly. For example, the Oscar module registers to storage service and the wallet, but for in the video you have to explicitly say, even though you register in the video module that you want to use the in the video that was over. So we could just register it in the individual module of course by default, but that's. Yeah, it's sometimes a bit like if you then don't want to use it, then it's your limited. So, yeah, not sure what the approach here should be. So for the case of the resolvers or sisters and that stuff. Maybe we can allow them to be added dynamically. And they can be added on the initialization and on the initialize method of each module. And we cannot do that because we are inserting injecting the the resolvers right at the instantiation of the of the module. But if we are if we maybe in the for instance in the in the individual module, we have a method called initialize. And that method calls the API and add the registrar or as a resolver, maybe that could work. Yeah. Yeah, we should probably explore this a bit further. Maybe we can discuss it during one of the next eight jacals since like how do we want to how do we want that API to to work and make it a bit more consistent in how that works. Is that something you would want to do some research on Ariel and maybe, like, think about it and come up with a way we could do it or. Yeah, yeah, maybe we can think about it. Cool. Okay, cool. Let me see I think I added the link to the to the, you know, edit. This is from. It's here. Yeah, I edited here. Okay, cool. I think one thing related to which I just thought about is that recently is it here. Yeah. So, in if chase, starting from in 030 we already required you to set the indie namespace but from 040 it's going to be really important what the name space is for things because we start using fully qualified identifiers. And it's important that everyone is going to start using the same. I created an issue here in the internet works where this should eventually end up and I looked at what's currently in the universal resolver. So this is the list we currently have just curious like if you. Yeah, if you start using a J0 for a zero, you need to know the identifiers I would recommend to look at this list and if you are involved with any of these networks. If you look right. Yeah, please say so because then I think if we can make sure everyone aligns on the identifiers now then we won't have another issue that we have applied identifiers but people aren't actually using the same identifiers to talk about the same network which would be. Yeah, another issue we would have to deal with them. Would it be a good idea to create types for like all the letters that are listed here so you can have either a string so they could do something custom that isn't listed but then have types so that it's a little bit more easy to have it be consistent. So that might be a good one that we can do either string or one of these so you have some type hinting. We wouldn't be able to add like the Genesis transactions I think that that's something we should leave to people themselves because those can updates. Well, but yeah, maybe we can add this list to the Airways JavaScript docs website as well and then we link to where you can find Genesis files for each of them and how to use that network. Yeah. Yeah. Cool. Could you open an issue for that in the AFJ repo change I think then we have at least documented then we can look at it at some point. Cool. Okay. And it's here. I saw. She also mentioned a thing on a proxy thing is that something can elaborate on that a bit. It's also related to what you're talking about because I remember bring so I brought up with the dnd method that the namespace might be or maybe a domain resolvable to enable all the conversation about maybe auto discovering Genesis file, auto discovering of VDR proxy or other features, or even some metadata about the ledger to the production and production. And a bunch of other things down the future. I'm looking for the specification. I don't know how far it got I know that Steven clothes is accepted, but I don't know as the final wording was. There's less study provided that where it has like sovereign and be the domain of that ledger of that organization. Yeah, okay, really interesting. Yeah, that's cool. But I think yeah, has this been documented or because it would require the namespace identifiers to be changed right. Right, that's why I'm confused because it has been to discuss on the Indie contributors and I don't know if Steven close know there's a comment saying that it was accepted it'd be made optional, but I just looking at the documentation for Indie methods I didn't see any animation of that. And I also didn't see anything related to it. So I think it was a great but not never like action done. Okay. I'll make a comment asking for words that is but again I'll just brought it up. There was something that I've, I've noticed from the mobile wallet perspective would enable us to kind of auto discover ledger we can scan a cure code. And we will be able to bootstrap that without necessary, maybe to know where to get a Genesis file and get it going. The governance is to apply whether the wallet will, will trust the ledger such a different question, but, but you'd enable to discover new ledgers and download Genesis files and so on. Yeah, okay, yeah that makes sense and I think in the end it's probably mostly up to the fair fire also to see which ledgers. It wants to support so for wallet it makes more sense to dynamically like add ledgers than for a fair fire. Correct. And James yes that would be per ledger. I don't know. And the idea is that the ledger would support a high available in the, I don't know VDR proxy that could be linked to the underlying nodes or not I, I'm not entirely sure. Yes, that could add some add some centralization and dependency on like the DNS system to then do discovery of the Genesis and if it's a proxy also then yeah it would be more handled by the net the ledger which is always the question like is there one person that hosts that in that case then. Which can be complex I think sometimes yeah. Okay, I think see we're already one minute over time so let's stop it here. Any other discussions I think. Yeah, let's continue this one next week for zero five zero and then we can. Yeah, continue the discussion. So let me add this here as well okay thanks everyone and yeah so remember that the meeting time has changed now in the zoom link so yeah if you encounter old links please update them or notify me when I can update it. Awesome. Thanks everyone has all the links and the meeting being updated through hyper ledger meetings. Yeah, that one has been updated in the calendar. So I'll update it in the wiki and the high AFJ repost still but there's maybe some other places scattered where the zoom link is is mentioned or like link directly instead of pointing to the wiki. Thank you. Sorry, like I had raised a question.