 Folks to the July 12th 2023 areas working group call We're glad you're here. We have some cool stuff to talk about today. This is a hyperledger call and so the Antitrust policy of the Linux foundation and the code of conduct for hyperledger are in effect links are available in the agenda You are Invited to add yourself to the attendees list or make any other adjustments useful to the community in any way or help take notes or any of that in the Edge in the in the wiki that it drives our meeting notes And we're glad you're here anyone new today that would like to introduce themselves. Hi, this is Patrick I'm here after after very very long time For those who don't know me. I'm a maintainer of one of the maintainers of areas VCX project and Yeah, just just came here say to see what's around and Try to Rampant our engagement with a wider community a bit Awesome glad you're here and I thought I recognized your name so you spoke about a slight surprise But glad you glad to have you back after a while. Yeah Thanks Any others? I'm glad all of you regulars. You're here, too Any Any of the code bases or the projects want to offer a release status or a work update? It's maybe semi-related, but there was yesterday. I believe we had the AFJ workshop Is anyone able to report on that? This is Tim here. I Guess this there was a great workshop in terms of walking through the changes to AFJ 40 point 0.0 Especially the new modules and changes in architecture My number of people on this call around that so I don't know if there's other other thoughts But I think it's from marketing and getting the message out there and what's what's happening. I thought it was really successful Awesome, thanks Tim. Hey Sam a couple of things on Credex there was a bug found in the credits implementation such that On verification when there are multiple Multiple Revocation registries involved The verification would fail even though it was a valid presentation So that is fixed in zero three three And as well there is a breaking change version coming out real soon now that I believe it's actually came out last night that is a new version. So it'll be 1.0 and It has some breaking change Changes and a bunch of performance optimization. So it uses the new Removes the dependency on Ursa and changes it to use the CL signatures library CL signatures library has a pile of new features to it and new optimizations So things like generating a revocation registry is half 50% speed up or something like that so it's We unfortunately had to This was discovered last night. It has to be called 1.0 because of a Pip some chance some handling in pip That was done. So just prevent breakages in the community It It was named to 1.0 rather than the zero four As what might be expected Pip requirements motivated the 1.0 version update. So there you go So that's what's going on there. The CL signature's library is Is that had the most work it's had for quite a while. It's got a bunch of new things in it and A non creds the non creds rust implementation will transition to it as well Oh, and I should say that the credex Bug fix only was in the actually in the Python wrapper So it did not affect other other places where it was being used Awesome. Thanks for those notes and be sure to hit up those releases for fixed bugs and new awesomeness Yeah, so basically 082 and Akapai did pull in the new version. So 082 will have that Obviously, if you're pulling in the requirements, you get the zero three Version in older versions of Akapai, but if you are using the Images You won't get that new one unless you go to 082. So there you go awesome Any other updates? I'm not not necessarily an update, but so basically One of the reasons I arrived the for this meeting as I had a talk with Clasio from BCGaF and we were talking about RGCX and he suggested that I come around sometime and and talk about a bit about What would we are doing because apparently we are a bit of a mysterious project. We haven't been engaging might so I have I have some like A short, I know I call it a presentation or few drawings Layed out so I can I can show that but I'm not sure if this is the right time or later Let's um, let's add that on to the agenda And and I think we're I think we're actually gonna have time today Maybe I'm over optimistic, but if not then that's can definitely be on the agenda tomorrow Does that work for sure, yeah You mean next week you said tomorrow. I Did not mean tomorrow. I meant next next week. Thank you Steven. Yeah, I was wondering if there's some more about No, next week is fine. Yeah in other news the area is working calls going daily. Just kidding Okay Cool excellent, okay. Well with that here's what we have on the agenda for today the James Ebert has a community selector demo and in some conversation there. We also have the update with the did peer unqualified did Migration that is not yet done, but there has been progress made And so there there are some comments and everything else and want want to draw folks attention to that so that we can move forward on that and then I Helen and Alex Actually, let's do this first because you've got this this survey link, which I think would be excellent And if folks are really bored with what's going on the meeting they could fill it out And so let's actually address this first And then the we've got the VCX update and if we'll spill over if necessary And to make that happen So that's the agenda. Are there any adjustments that we want to make before we dive in? additions corrections All right, Helen. Do you want me to or Alex just one of you want the floor for a minute to Talk about the survey Nice to get Helen Go for Alex. I think you're getting the results in aren't you? Yeah, so The short version is we have a small survey that's three minutes please do it now if you can because no time like the present and It's a chance to have your say on how we communicate areas and what the priorities are in our messaging So we have a pretty good steer And we didn't run this for a few more days I would imagine But if you want if you have a sense of like oh We never say this enough about areas or it's really important that we mentioned this right up front Or this is not important why do keep dwelling on or whatever it may be or if you've got resources When people come new to areas if the developers are exacts and you always point them a certain direction There's a space in that in that survey to put those links into help other people so you can build a really great getting started type resource for this so Please do that any questions that either of us know And we'll give you the results shortly and weave those into our new fairies marketing comms Paying to add to that Helen Yeah, just to build on what he was saying with you know as in terms of resources that you direct people to We would like to incorporate a sort of community resources page to the website or kind of to the webpage so Yeah, if if you have recordings or meetups or white papers or medium posts or whatever That you would like represented From you from your company from your organization whatever On that sort of community page. It's a great representation to show that you are You you you your organization your team whatever is part of areas. It's a great just just in terms of you know a visual marketing Etc. If there's somebody on your team who we should talk to about marketing about you know Incorporating other links whatever Please add those because again, we just want to show the diversity of the community We want to show all the different ways that people are using it Using areas are building on areas are contributing to areas. So yeah any any Meetups ask me any things et cetera. Please include those links. Um, and that would be helpful. Thank you again in advance Awesome. So there's the link. I'm also going to drive Or to copy this and to the meeting. Oh, steven already did it Read my mind. So please, uh, please follow the survey and and I huge thanks To hella and alex for for driving this forward The the marketing of the work that we do as is as important if As the the work itself and and we have Us developers have done a subpar job with marketing and grateful for for alex and helen and and working with us to make this happen. So They need our they need our input And and please participate Grateful for that Anything else on the marketing? I don't think so. That's it for now. Uh, we will have another meeting of the aries marketing working group At at the end of the month Again, all are welcome Let please reach out on discord or whatever if you have any questions or if there's somebody on your team Um, who you think would be a good fit to have those discussions. Um, you know very very low bar Bar, you know for barrier for entry for the aries marketing group anybody and everyone is welcome Um, so please spread the word For folks to join Awesome. Thanks And next on our agenda is the community selector demo by james And uh, hopefully james doesn't miles all stop screen starting james. So you can set up hopefully james doesn't mind a little bit of a prelude Uh, we we have talked about the concept that he's about to show several times including an i w and um and and to talk about the complexities of deep linking in mobile apps and notably The differences between android and ios and how to actually accomplish that um and James got tired of of the talking and the not progress and he made a thing Um, and so with that I will pass all the attention over here to james to talk about the thing he's made That was a great intro sam Yeah, so, uh This is the traditional deep link that has been proposed and and used so far with our community and as sam spoke to i've uh Gone with an approach of using the android intense to actually launch the android portion. This isn't anything super special the part that's a The cool part here is uh, what what i've done with the ios, uh universal links So i'm going to jump into just showing you what this actually looks like in practice for the user and then we can talk a little bit More about the details of what i've done Uh, so I set this up as a Service that i'm posting and this can be put in front of any issuer The invitation just goes into the out of band query parameter. So This can be stood up without the issuer actually knowing in front of it So i'm going to go ahead and do the android portion first and To bring up my camera and scan the qr code And this opens up the standard Uh dialogue for choosing which app you would like to use which is awesome in the open source context I'm going to use uh horror plus because that's what i've got set up to do it And this will add the specific, uh contact Uh, let's take a look at the ios, uh portion Which my phone looked so I had to restart that And this one I sent myself the Uh same link so to demonstrate what that would look like Being sent the link There's a large delay screen share apparently, um, but it brings up this dialogue, uh option for Ios in Which where we uh display a variety of apps that can handle the Um invitation Uh and this will uh depending on what the user chooses will allow them to open the invitation with that app This is a list that would be managed in the open source community and Points to the individual user universal links Registered by each of the individual app creators so Yet again, I'm going to do horror plus because that's what I've got set up And that immediately pulls me over into the App and establishes the connection It looks like the screen share uh stopped, but uh, that's the behavior that happened there You're your session we saw a timeout on your screen in one hour the screen sharing out Ah Oh, it looks like it. It just was really slow. Um Uh, but yeah, that's that's the behavior of the The ios is opens up into the app and and opens the Uh contact up um This is configured utilizing a uh Jason uh list of configurations so a individual uh organization could um in a Github config could add their Uh their app and where the ios uh universal link is and the their icon and And potentially other items such as what kind of things they support as in Do they support to conv2 do they support? The specific goal code and center there's been a couple of ideas that we've talked about that could go here But this is the basics at least Uh, and the final thing is that um I guess I guess there's two other things. I've also set this up to be able to do a proof of concept on uh showing that it's possible to do URL shortening with this in which uh You put a URL shortening here and so if you have really long uh invitations this can also handle uh that as part of the process and um One of the benefits of how this is set up Is that uh you are able to scan this with a standard camera and actually be able to Resolve this page still uh while being uh pretty closely Tied to how the out of band uh URL shortening is specified in rfc Uh So then the final bit is the the thought that this is something that could be Uh The not URL shortening version uh is a front-end web page only and can be hosted By any issuer, but it also could be something that is hosted by the community such as at dcom.org and um Uh, that could be a standard place of managing the the community Having a community selector that is managed there. Um Yeah, uh Sam's there thoughts you want to add because I know you you had some wonderful thoughts that you added that the Dicom users group 100 percent of this on Monday. So at the risk of being a little over clear about what's happening What this revolves around a a url that can be loaded in a browser And then when you load that url magic happens will you describe the magic that happens when the when the url is loaded in a browser Does that question make sense? Uh Yes, so um, when you load the zero on the browser, uh Oh for android when you visit the page it'll immediately try and open up a application using an android intent Uh, so One of these guys and if they have an app, uh, that is capable of handling, uh that it will, uh Why you just select the app and and open the invitation uh On the ios uh behavior Well, hang on before you leave there. What happens if you don't already have an app installed and it tries the android intent Uh, it uh will fail and um, we'll leave you on the page. And so, uh, what we probably want to add to the Behavior here is Uh information for downloading a having a list of of options for downloading an app if you don't already have one Right, so I don't have that here yet, but that would be ideal And so when the page loads to skip up skip back one second Um, it does some some JavaScript evaluation to figure out whether you're on ios or android Yes, and then if it's android it does the stuff you just described and if it's ios then Uh, then keep going yeah, uh for ios the behavior is that um You will get to the web page and then, uh, once you Choose, uh, which option you want to go to This url that you click on would take you to, uh There's the two options if you have the app already installed It will detect that hey, you're trying to go to um, I'll actually just click it here This is the the url that I configured it to be on and uh, if it if you already have the app installed It'll immediately take you into the app and not actually resolve this in the browser If you don't have the app installed it'll take you here and you'll want to have Uh, marketing information to indicate. Hey, this is how you install on ios and take you over to the app store Yeah, did that answer your, uh Question i said it totally did Sorry What do you mean it detects if the app install or not? Is that based on the domain that you were mousing over? Yes, so uh specifically this domain here i've set up a apple uh app site association so It will detect if I Visit the specific url and will Bypass the browser and put it into the app Okay, but in your case is the did calm dot james something Uh, I set up the Universal yeah, okay, but you're proposing that we have this selector somewhere. Maybe did con page I did con domain or something like that Yes, and the benefit here is it allows Uh, the user to choose from a variety of applications versus Um Or having it be between issuer and as the specific holder All right, but but in that case then they're There shouldn't be an app register correct So the the ability to register the apps or as the automatic thing Allows for Uh, those that do have an app that they want to promote Uh, they can uh, they can of course take this code and or any modification of it and then and then stick it Uh, and configure it to launch their own app by default The uh, the idea of a community selected one is for those that want the invites to work with a variety of apps and art Uh, promoting a specific app themselves could then use the community hosted one in order to make that happen Okay, so I suggested that you the app vendor say bca app holder You could if you have your own domain register you go directly to your wallet do not suggest any community Um selector whatsoever but If you want to support the community selector Um, then you wouldn't be whole you would be using that domain you'd be using it Did come domain or the community domain? Yes, and and there would be no app on ios specifically linked to that community domain. There would be no preference there Okay Thank you Is there a way to say if your preference once you um Because you don't want to use this every once you have an app installed and you're using it all the time You may just want to say that I always want to go to this one I've thought about that and um, I haven't actually implemented anything But I thought that you we could utilize some form of cookies. Um, especially if it's a more consistent community selector then Uh, I could see that being done, but I haven't actually implemented that behavior Thanks Kim your hand is up. Did that get answered? No, um, I was gonna say that um The community selector we'd likely want to make that open source so that If you wanted to have custom branding on your own landing page or something you could do so But still have the list of community available apps totally and the in the list of in the configure list of community apps can be Obviously hosted in like a github repo and that asset could be read out by anyone Even if you're not using sort of the community hosted version of it So this config file was what it's based off of and that and that could be uh, that could be pulled and utilized And so when people had an app that they wanted to be involved in the community selector that that would happen just via a pull request to the The pr that or the the repo that holds this configuration file In that way that could be open for and again the whole thing is voluntary both for the configure configuration and the usage of it But but he has some really nice advantages for the for those that do want to use it So I kind of missed the start of the demo when you're doing android, but I believe when I tabbed over or tabbed back to hear that the um from the questionnaire Didn't that open up the android app picker? And if so like doesn't at least in android's case doesn't have like a choose this one by default It does most of the annoyingness That's being solved here is The fact that ios doesn't have an intent system like android does and so we're compensating for that And removing as much of the jankiness as possible Okay, so if you're on android it simply Tries to launch the intent and then android handles that intelligently both if you have it installed and if you don't So really the remember my choice is is an ios Related issue via cookies anyway is is an ios related issue because it doesn't have anything of the sort So for those that don't understand If you do attempt to launch something even from a protocol perspective on ios The in and you have one or if you have more than one application installed that's capable of handling that Then the the which app opens or gets it is like A semi undefined behavior like it may happen randomly Which is really unhelpful and so Rather than rely on the same type of a thing that That from a protocol perspective that ios supports Then falling to the universal links, which is weirdly named but but but is is linked to a specific app Is the method that james is is using here So this is an attempt to provide each os with the best that that os can can manage and there's a lot more hand holding required on the ios side So the idea behind the community selector is for those that don't are not promoting a specific app And and certainly you could use this code in the open source way as As kim mentioned You can uh You can always copy and use it yourself, of course of to great utility, but there's there It also kind of makes sense to host a community version of this that prefers no app specifically In order to to make that happen the the other thing that could be done to avoid preference James talked about we had some ideas that you might want to indicate that a specific goal code or or something was Was involved and you could specify that or the the community could selector could respond to that Meaning it could auto filter by the types of apps capable of receiving that sort of thing in in order to guide the users And we could also After the list is selected it could randomize that list To show no preference one over another You know when that's created on the community holder Again to to avoid showing a preference there Since this is a didcom kind of issue even though it's heavily of a concern of the areas community One of the proposed places to host this would be on didcom.org Which is hosted over at the diff with the the users group there Simply because it is a didcom specific issue and this would allow for any didcom You know out of band invitations to to you to link through and then leverage that community selector So that would be of use to us but not necessarily something that this community would have to do independently Any other questions? Awesome. Thank you. So so to be a little more direct Is this stunned silence as in this is amazing or is this stunned silence? Is this the dumbest thing I've ever seen? Even if you don't have anything to say about it and getting a reaction from things you think would be useful would be helpful here I'd give it a thumbs up I mean there was a really hard problem in iOS that's not made it easy And the danger of all of this stuff is going back to the lndc world where only a few big providers are ever Included so now this is a great great approach for some concern to try and resolve Cool, and there's a thumbs up from from akif as well And a comment from Tim anyone else want to voice an opinion or flash an emoji on the reactions thing I think it's actually pretty amazing because Not only like are we Having this you know selector that says choose your app that you want to launch But this does provide that sort of Advertising avenue where if someone goes to one of these links and they've never heard of one of these apps before They get To view sort of all the different apps that are available and check them out Nice discovery process that way Um, I think this is great. I I think the only maybe thing would be provide a hint where the Maybe the user verifier may have a opinion Maybe a wallet support a specific protocol in a way that they need to provide So the hint where the user verify can also Have opinion about which one or which ones to choose So you're talking about the community selector, which is supposed to have no opinion But that the creator of the invitation could express an opinion about the ones they think got to be at the top. Is that the idea? Yes Cool idea And I think given that that's the the inviter that's their preference. I think that that would be a cool Yes, it would be their preference again if the inviter or the verifier, however is creating that The link doesn't have any preference and that's fine. It goes into the the list right, which means that there's a uh Yeah, that's a nice halfway ground between um using the community selector with no opinion and uh, and and then have it and then creating your own of course Which expresses your opinion. That's a nice middle ground to be able to express preference. So given that and dried we'll Maybe take it to a dead end if the app is not installed Would maybe the same approach address that? It could be you can't you can't really detect on ios or on android actually that the app is Installed without just attempting to throw the user over there Correct, which is why they're gonna have to click on the you know, they have to use the the nascar selection page here to make that happen So one what could be done though is that if they don't have any apps installed or if they like paste it The specific they they paste it into chrome it'll load the page without actually auto directing them and you could have We could have information like oh need to install an app and and And give them a list of options that could also be configured alongside ios ones That that could be an option there Right, uh, so colton mentions in the chat um the um The issuer Request a wallet with with q&a support banal a wall support q&a. There's the the terse way of doing that would be a goal code um, but certainly I have thought about An enumeration of the of the type of protocols being supported and a way to derive That out of the invitation with as little hassle as possible In order to sort of recommend the apps that support the types of protocols that you would need And so obviously That you want to approach that sort of a thing with care But but definitely the more useful we can make this without without getting ourselves in trouble the the better And by getting ourselves in trouble it wasn't a sense of app preference But just making it so complex that no one can use it is what I meant by getting ourselves in trouble But this is a this is a fantastic shot Uh, thank you for comments any other I don't is anyone in particular. I think this is a bad idea We've we've heard things and voiced in favor of it, but I don't want to awesome This may have been obvious from what I said before but I think this is this is great We talked about this and about the conceptual like how you would handle this sort of a thing and and uh, james just Did it instead of talking about it. So awesome Uh, steven gets thumbs up as well cool Thank you, james. I just want to ask i'm assuming there is some type of governance or approval about who gets into that list mainly to avoid potentially bad actors or hackers who have Clone wallets that are open source and great Ones that are not great Oh, I see what you're saying So the governance is going to end up being controlled by the repository that this is put inside of Um, and so the community that to to sort of manage that this uh is the I think is the didcom users group um, and And uh, any what that's open anyone can be involved there and have an opinion, uh, etc And any conflicts or issues would be resolved by the maintainers of the repo, right? That's the the the governance that By default when things are managed to get a repo And so uh, so that that would apply there But uh, but james, we're likely going to need to in the repo itself describe a little bit of that just a sort of baseline governance That could be expanded later if we need to help people understand what's going on here and and who makes the choices meaning those In the community that that serve as maintainers, etc In that way that can all be observed in the in the actions of the github repository that manages the the config file and the code if I I just asking to avoid really bad actors that are hackers call on things and want to sideload an app that is potentially just Broadcasting other I don't know private keys and stuff There's a possibility saying we have part of that governance some like verifying the app is on the the Like it it appears to be coming from a correct author on the individual app store or something like that Yes, well, there's also the issue of good intent but failure to deliver which means that someone has built an app and And it has the best intentions in mind, but but the the user experience going into it is not great Like what do we do as a community, right? There's a handful of edge cases there There's the there's the bad actor thing, which is a lot less hard to to ferret out There's also some issues of like, you know, or what happens if you have an app that is no longer supported But was in the list, but now is having issues like how do we how do we handle those sorts of things, right? Yeah, and then that that's a piece of governance there as well that's necessary So absolutely I believe the way i'm understanding this is there's two parts. There's both There's the code to do this and then there's deployments of the code one of which could be at didcom.org Yes, that's correct. There's so in other words There could be a pan canadian hosting of this Which only needs the governance from the pan canadian community and so Absolutely. Okay. That's what I thought so that that can lead to different governance For the what could basically choose which one to use at that point Yes Okay The the the goal behind the didcom one dot one is not that everyone uses it But but that people can use it if they don't have a reason to have an independent one, right? And then anyone who does have have more strict requirements And I imagine governments will have opinions about this sort of thing can of course Run the code themselves, which can point to whatever config they want and they could only allow Specific applications that have been vetted according to their governance process Yes So a really good example Is the url shortening Where we may not want to host all of that infrastructure for the back end on didcom.org But someone who needs the url shortening is a good use case for them having their own instance of that Yeah That's a good example Kim I'm going to voice an opposing view here for a moment. Um We're under the assumption here that people have multiple wallets installed on their phone. Um, it might be Perhaps my perspective here is that I'll be much like browser for people will have one app That they'll choose to manage their wallets under and so this Problem that we're trying to solve may not actually be a thing um, so If there was a universally good way to indicate that on ios and android, I would agree with you Um, and the mechanisms on android can allow people to say no, this is the app. I want to use Or actually in in android if there's only one app installed It just goes directly to the app and doesn't give you the selector So in that case that the the problem you indicate where most people will only have one is a non-issue on android On ios they may only have one, but we can't actually detect that Um, and so we don't know if they have zero or one or more installed And so this is a reasonable compromise by allowing people to to pick that application And then perhaps checking a box that says remember my choice that will then effectively Bypass that automatically and then launch it into that application in the future for that user So I I think that uh in in the android case If that happens then then it's actually really fluid and it doesn't happen But it also gives the user if they click a link And they don't have an app installed they can guide them to install that app, which I think is really useful So, um, I think you're right that the common case is not more than one app But even in the not more than one app case, I think this still provides a substantial amount of utility to the user In order to make this happen and certainly some utility to the to the issuer or the person You know producing the qr code invite because of the abstraction that it lets them have And also it does one of the things I think it's important It removes the risk very real risk the issuers and verifiers will just lock it To a specific app if they don't have a mechanism kind of like this So I mean that's what that's what apple wants you to do right their whole design is for for for An app to be tied to domain and that's the only app they can launch So that's that's the flip side of this is that the issuers would just start to say I'm only going to support apple wallet wanting to support this for that So And they still may but at least at least yes, please there's an option here. Yeah, at least we're giving them an option that makes sense Cool any of the comments? I was just going to say that uh with the case that kim brought up of Like how you know people might have things stored in One browser or whatnot Like even my phone since I have multiple browsers on my phone It still brings up the selection popper whenever I open up links because I've not set that default browser It's the same concept with windows. You open up a photo editor and you know, you may only have one photo editor So it will come to default But if you happen to have more It'll ask you until you pick that default Good point awesome Thank you james for obviously doing the work, but also presenting with us here today um, I think further discussions will happen on On the community hosted version of that are likely to happen in the didcom users group And we can provide updates as it happens, but I think the main discussion will happen over there And then we can begin to experiment and correct and improve it etc based on the the work that james has done So thank you for that So, uh Next up on the agenda is the unqualified did migration update And this is the the goal to summarize of moving off of any unqualified dids that remain in the ecosystem But in a way that transitions them to did peer dids, which can help that to happen I have done A little bit of work. I had volunteered last week. The first one here is that I've made a couple of changes to the to the the did Peer method spec for numalgo 3 as suggested by by daniel bloom and so It actually moves from a lowercase hexadecimal encoding to use a multi hash base to see 58 btc encoding So you're you'll notice the z here, which is the the indicator of what of what the type of this hash actually is And so and the examples have been updated to make this happen There's one notable one here in that the the starting thing that we hash with includes the the dot to make it consistent with the instructions that existed here meaning we We exclude the the did peer to prefix But that leaves the dot as the as the separator value for for this to actually happen So so here are the changes that I have made to the spec and according to that But and and this definitely needs some review by by folks that that care To to make sure that that has been done correctly I got comments from both daniel bloom who contributed a fix or a clarification and daniel hardman as well That that's going to do this. So he mentioned he will merge by the end of the week unless someone objects And so so that's there So please speak up if you see corrections or improvements that need to be made on that The other thing that that I that I had committed to do was to Was to write the beginning of the unqualified did's transition community coordinated update which I have done here And so the This is a new rfc that follows that same pattern That actually talks about what needs to happen with the the links to the relevant places And and in the steps that will actually occur as part of that I preliminarily targeted this At the middle of october But of course this whole thing is subject to debate and there's actually some pre-work that needs to happen meaning everything It has to be nailed down before we can really like You know change the status on this and it's something that we're targeting is as a community So I just wanted to highlight those steps forward and the need for review and feedback there Steven An hour ago Has has made a couple of of really good comments Including this one. I did not mention the that the public dids that are unqualified need to be transitioned to whatever Appropriate did method there is so did solve might be one of them There we're still rolling out support for did indy across all the ledgers the code's been written But but updates are required to make that happen And so and so that needs to be addressed here And then steven you also mentioned that there's some open issues on this legacy did transformation And that perhaps the transformation ought to be Included in this repo directly as opposed to linked to a separate repository Any comments you want to make there or is that enough said Yeah, I open some issues. I maybe what I'll do is just do some pdrs against his Teemo's repo But I still think I'd rather see this be just a link to an appendix of this of this pr Or sorry of this rfc rather than in a You know in Teemo's Account that's all Right and I I hit waffled on that and ended up linking it so that it would come up in discussion And then we can certainly reference back his original work I don't want to remove credit for the work that they've done, but it would be really useful to have it just aligned You know with Yeah From a repository perspective be stored alongside so that there aren't any confusing issues or whatever else Cool So you also mentioned There's are these a couple more things that need to be resolved That looks closed. I think we fixed this And so And I think this was Daniel's issue 50 which which I which I'm addressing with the pr um, what was 53 That's closed So, um, so I think the I think the issues are done pending that that merge um and and then we have the um We of course have the the issues against what Teemo has written just to make sure that any clarifications land there um, and then um And then and then we could actually kind of make this happen We had discussed last time these are these are notes copied over from last time About did peer versus also including did did peer 3 And so this is this is the the indicator there one of the remaining issues is that I believe we need to Indicate somewhere how you can discover support for the did method of did or the num algo of did peer 3 with the discover features Protocol and that would allow you prior to transitioning a message over to did peer 3 You could detect support for that on the other side And I don't believe that's been documented anywhere about how that might actually occur Which I think would be a necessary part of adding did peer 3 support did peer 3 being an optimization of did peer 2 That both parties can use as long as they support it And so detecting support on the other side turns out to be an important piece of that And of course, we have the discover features protocol. So that's the right way to do that I think within within did comp, but we haven't described what indicator Should be used in that protocol Any questions or comments about anything related to the did peer Unqualified did migration I I was trying to find a pr that you mentioned about Going from basics far to base 58 That is That's here. It's a pr 55 on the peer method Okay, can you To my pace that Um, what is the motivation behind that because space 58 is not Is not a package or algorithm that is provided First out of the box to note. So we need a kind of a third party library um the this was um Daniel's recommendation uh base 58 avoids Should you end up in a circumstance where you have to transcribe something it avoids confusing characters Which is the why the reason it was created And so this is the issue that that motivated this And this is really to remain more consistent with the other methods. So did peer 2 uses the same encoding? Sorry Yes, so did peer 2 Uses the same encoding and so did peer 3 using the same coding presumably doesn't add any additional code complexity Because of the existing dependency So if the motivation behind is to make it easy to transcribe and I understand base 58 Again, bitcoin uses that for removing kind of ambiguous characters zero And let oh and so on to be easy to type it Is this a direction that we're moving to make it Easy to type it in No At this point that was just the way that did peer 2 was written And so this is just maintaining consistency with what did peer 2 was doing. This is not a change. So it did peer 2 was done It's it's been doing this all along. Um, there's definitely no recommendation Of course that an invitation you want to be transcribed, but it does help when you're Looking and debugging stuff to you know to be able to look at it as it is But the real motivation is just consistency Is that it was done before and there isn't a super compelling reason to not do it given that it's not an additional dependency that we're adding in this step okay, um, and I guess where i'm going is that is Again, you said there's no direction, but is that set precedence now ob and all those Payload for URLs to move towards base 58 or not necessarily No, not necessarily. This is just within the peer that the did method the peer did method spec itself Okay, thank you. Yeah Um, so here's that uh, here's that and I can drop that on notes as well um The other thing that ought to end up in the notes here is of course this 739 has the new the new pr here I'll definitely need to go address those comments that of course steven made and then anyone else makes as we make this happen um, so that's awesome Any any any other comments on this? so an issue of timing I have the audacity to take a vacation and uh, and I will be um gone, uh, certainly the um the Next wednesday and probably the wednesday after that and steven has agreed to um to Uh handle the meeting Or handle those meetings. Um, I will be I will be out and relatively offline. Um, and so From a timing perspective, I can go ahead and make these updates Steven, uh, any anything else would have to wait till I'm back The idea there was that everything is resolved as possible. Um, it doesn't have to necessarily I just happened to open the pr And so anything that we can resolve as sooner rather than later would be helpful for that to receive a community vote and then move forward Um, the idea is that on this on this particular Um update here that we would select an agree upon dates and then officially move to Um to the the to working to accomplish step one, which is we all add support for this into our code bases um, and that and that will give us the um The the the progress to move forward and move that into our development timelines, etc to do that So so from a timeline perspective, I'm going to try and update this as much as I can today and tomorrow So that I'm not holding things up And then any in the the next two areas calls The goal is to reach consensus on on on this so that we can Have that voted and and and merged as soon as possible even if it's before I'm back Um, but certainly hopefully not long after that if that's the case Does that make sense? Good to me, Sam. I'll do it. I apologize for not scheduling my vacations around areas, uh, rfc work I'm kidding a little But uh, but uh, sounds good Uh, thanks folks for coming. Um, we didn't get to um to the vcx update patrick. I apologize for that We ended up discussing the the community selector longer than I had anticipated the uh, but certainly uh, steven that could be a good topic for next week We'll look at next week. Can I assume plan that? Yeah, sure. I'll I'll be there looking forward to it Thanks, folks. I hope your week is a great one. Take care.