DIF BiWeekly updates call
3:00PM May 13, 2020
Hello, a quick quickly before anyone jumps on, Boss, I need to get an email if you have some money for stuff but just identity stuff, make stuff that's been in our budget for a while this year and just haven't used it for anything so we shouldn't get it off the books, someone next few weeks welcome just kind of like us it basically just gets clogged back. So I was thinking you just give it a diff or some sort of event that you guys you don't have to have a whole plan. Like we have to.
You mean Microsoft?
Daniel pan or something and then oh, my back. No.
Yeah, you're back. Okay.
Yeah. First take second email to Pam so that you can pay something My back 10 character. Cool.
She's here now.
All right, Pam, starting with the event thing that we're talking about with the money that we have.
Oh, yeah, correct.
So what what do we need to do? Like I know we have, we need to like
well, so my preference if if it works for you all, and you're you're welcome to give me a different different feedback, but our goal is interrupt. Right That is that is what we want. We want to make sure that the community can interoperate. So if someone hurt you know, if, for example, the interrupt project had a proposal for how we could perform a an online interrupt and how we could use that money to further our goals, you know, I would be happy to have you all decide how to do this. Rather than have me come down and you know, make
them use their deadline to make that decision.
Yes. The money turns into clouds at the in June basically. I mean, if we can have the proposal by end of May that would be great. I'm always asking what we're talking about. So I have money in my Microsoft and T budget. Bam.
Can Can Can we can i circle you back to the meeting to talk about this in like five minutes? Just Just
Yes, absolutely. Sorry. I was just asked a question. I'm, I'm sorry, I didn't have
perfect No, no, no worries. No worries. It's super, super exciting. Just want to make sure more people hears it.
Other agenda items that might be one of the gentlemen
in the other items.
Are there any other items I'm just sharing the screen for the Meeting. Is there any other items that we should be talking about those who are on the call?
Yeah. So I think I had a couple updates around some contributions we'd like to make and I try to get everyone looped in from the broader and our group was one of them was that z Kp stuff and the others puffy stuff.
And the other one was, it's a secret secret recovery
Perfect. Then let's start. Kali. Are you on the call?
Nope, she's not here.
All right. Then Bam. Oh, ah,
under a secret name here,
Kalia or Llewellyn Can you please Are you ready to do a short presentation on the glossary project? We can't hear you.
Yeah I can do that. Let me go find the link
is Margo here are Germans know
me? Are those here?
Good Martin's here we can tag
Okay, here is a link to the
I go am I sharing it or am I sharing Steel the meeting minutes. We see the we see the presentation. Perfect. Sure.
So this came out this group started at the last at ITW 29. And it was a broad community inspired effort that we chose to host a diff, but it was open to anyone in part of my own inspiration was the work of Eugene Kim. And he I'll put some links in the chat after I stopped talking specifically around developing shared language for technical communities to be able to talk to each other and have, you know, make sense to each other. And also the original identity gang lexicon that really got the ball rolling in terms of how you know the open ID and information cards and all those guys way back in the day started talking to each other and I want at us to, you know, find a way forward and the the process that we actually invented to do this. I'm really proud of and I think we're going to write some, I want to write it up and see if we can get it published somewhere just to share it with other communities.
Go to the next
slide, I think. So we,
we we started
out by trying to figure out where we were going to work on definitions and it wasn't at the most deep technical level because all the different communities writing specs are doing that at their own at, you know, on their own for whatever the needs are for their specifications. We wanted to let like, move one layer above, really focusing on the needs of the informed lay person, product man Managers talking to their potential clients marketers talking to the market. And we also understood we can't force anybody to use any language. So one potential path we could have taken was to define a bunch of concepts and then give them names. But we were like, we're more interested in how people are actually using the words and what they mean. And so then we innovated this process and we next slide we surveyed the community to see which can you go to the next slide blush,
we surveyed the community and SSI came out on top and we executive Lee decided
to tackle that and tackle the next three terms, while it agent and credential. And then if we go to the next slide, and I'll hand it over to Margo and she can can New sharing.
So some of you might have seen this presentation also at i o w or in the CCP. So we're going to cover our research process relatively quickly. And then as I mentioned, we we hope to write this up and find other ways of sharing, if you will. So we we sent out a second survey to all the mailing lists we could think of basically provided some context around why we were doing this work. And then if you move to the next slide, and we asked specifically about those three top terms agent, wallet and credential and we were looking for a current working descriptions from the individuals and companies that responded. And importantly, we didn't just want to understand those nodes. We also wanted to look at the edges or the relationships between them. So looking at the relationship between an agent and a wallet agent credential while credential, next slide. So we had about 27 respondents In total, representing different companies and individuals that came out of the network that we were able to cap and make you if you were one of people that responded, representing a pretty balanced set of business models ranging from B to B to B to C. Of course, there's many ways we could have broken this down. But we just wanted a glimpse into how the different respondents were thinking about their services and who their end customers were. You can see that in this graph, go to the next slide.
Cool. So we got tons of data back and we spent several months meeting as the glossary chairs and also with other community participants. And we went through a pretty cool digital ethnography type process that involves pieces of service design, and categorization of responses. So we took all of that different information, and you can, you can go forward
and go to the next slide.
Nice. Okay, so we took all that information and we read through during our community meetings and we inductively built up and named groups for each category. So for example, we're looking at credential here, you would read through each individual response of that working definition or working description. And then we started to build up a name groups as we went based on the information that was provided. And then we were progressively able to rank those groups to from highest to lowest number of responses and use that as a tool to start to build off towards some shared language around each of these terms and also their relationships. You go to the next slide.
So this is an example of what some of those groups look like for just those primary terms grandchild wallet and agent. We also have done this separately for the relationship. For example, for credential you can see that information about structures and standards was really Notice responses as well as the relationship to identity data for wallet. Keys and secret storage words are really common in those responses as well as credential storage. And finally, for agents, we saw a lot more diversity in those responses. The meeting theme was representative of a subject. So there's 21 responses that had some version of that related to agent. But beyond that, it was pretty wide open. And there were a lot of different themes that we saw related to that definition. Next slide. Obviously, we're running through this pretty quickly and you have the deck I think we're dropping the link in the chat. So you can also come and look through it yourself. But And finally, when we had finished analyzing all this information, we were able to pretty easily arrive at a couple of sentences pretty easy for two to three days, where we kind of felt the day naturally built out of those most prominent categories or groupings. We have created four credentials, we found that a common or shared description could be that credentials provide a true standard for accessing identity data for a wallet, they provide storage of keys, credentials and secrets often facilitated or controlled by an agent. And then finally, for agent, we, this one was the hard one, we struggled with finding a simple definition or a simple kind of shared description here based on the grouping. One community participant had recommended going back and looking at the dictionary definition, which was a person or thing that takes an active role or produces a specified effect. And we while we like that simple to finish in, we do want to also acknowledge the nuance of what we truly saw in those groupings and just reflecting that observation back to you all and it was closer to an agent as a software representative on subject. Most often a person that controls access to a wallet and other storage can live in different locations on a network versus local To facilitate or perform messaging or interactions with other subjects, clearly the more complex of the term period agent, go to the next slide. And then finally, we want to share with you the relationships that we, we found this actually be the most interesting part of the analysis work. And rather than getting stuck in just looking kind of head on at the individual nodes of wallet rental agent, it was really insightful for us to be able to look at these relationships. So for example, we boiled up from all those community input and found these are some common trends about the relationship between a wallet and a credential. A wallet except Sander presents a credential a wallet stores keys, cryptographic material, and store credentials. credentials are often used to access wallets. Next slide. Between credential and agent agents mediate exchange and storage of credentials, agents help manage full license credential lifecycle. An agent has credentials to prove authority. And agents perform vetting or verifier functions. Next slide. wallet to agent relationship agents may have wallets. wallets can be agents, agents store credentials, keys and our messages in a wallet agents that you work with and connect to wallet. Agents support delegation and agents backup wallets. Next slide. So just looking at these all together, we tried to really put these in pretty business layperson terms. I can't remember the exact expression you've been using Kalia informed a person that it?
Yeah, I think so.
But we want to note here, this is not us prescribing definitions or prescribing how these relationships should look. This Is Us surfacing up observations from what this subset of the community had to say about these firms in these relationships. hoping that by looking at this together as a community, we can understand how the market might find some challenges consuming this technology and what our opportunities are to standardize and have some shared language around the different key tools as we're, as we're moving forward in building a market. Go ahead and clear, you want to come back in? Sure. Great.
So, um, we had some outliers. And I don't think there's a ton to say and so this other one of the issues we found, of course, is that wallet has some shared design pattern and meaning outside of that society space and yesterday at the CC CCG call, folks were suggesting that may be an area for us to focus next and you go to the next slide. We are going to continue working on hopefully some next terms. anybody who is interested, I encourage you to join our next phone call which is next Monday at 2pm Pacific. And we will be deciding as a group what we want to tackle next or at least you know, exploring possibilities. Both Margot and drummer are staying involved but stepping down as co chairs. So there's also a chair or two position open to continue the work but my I hope that we can get at least three more things to find before the next IWA and continue this process. It's been pretty
fun and I think it's going to help us as a community. Get this language right for a broader audience. Request.
Thank you guys.
Awesome. Thank you a lot. Yes, super good. So anyone who wants to take a look, you can take a look at the link. Also, you can join the group and as Scalia said, they are looking for new chairs to sort of further divert and look at other terms. So there is more to discover. Is that link available?
def blog, so that's a action item I'll have with you blush.
Sorry, if I send that link to folks inside Microsoft, it's not just you don't have to have any office.
I, then if there are no more questions, then we would move forward. Okay, so I put in this topic, I would move it to the very end of the meeting. And so if it's not so important, like it's just maybe we could talk a little towers AWS, what sessions were great and those who might couldn't attend or couldn't attend that given session can maybe, like, revisit the notes and recordings, I assume. So come back at the end of the meeting. And Pamela, can you tell us about what you just started at the very beginning?
Again, so mostly This is Daniel's how to wrangle, if you will, but we have some money for interrupt. We don't have we have to spend this money by you know,
but we don't necessarily you know, we we have to pay the money out and we would like to sponsor diff, to make some interrupt efforts. So Daniel and I need to hammer out the details. So we're, you know, we are hoping that we can define some specific areas of focus Where we want to see progress and to interrupt, and then you know, create an event and a framework that's going to help us get there. So
I brainstormed over slack. I think last week was telling you about some ideas about an hackathon where I know whether we could make this as a grand like, okay, certain people could win if they whoever built the best two or three, I know, interoperability demos or something. I'm not sure whether we can earmark it this way, or whether it and how much flexibility we have with
Pamela It sounds like you know, different, more or less defined the event and then we just sponsor the event and it wouldn't be like you don't have to direct exactly exactly of how dollars are spent.
Yeah, that will be my purpose. My, you know, the only string that I would attach if I were going to attach a string is I would like to see us focus on verifiable credentials. Right, like I would like to see us, you know, my, my, if if we can do a thing that ends up with us being able to tell a story about how verifiable credentials can move between agents and wallets. And I, I feel like that's the definition of success. So I don't know if you'd call that a string or not, but that would be my, my request the very least.
That sounds good.
Okay, perfect. And, Danielle,
what I guess just to close it off, I think the next step would be Danielle Balaji. And I work on some proposal and then share it with a few folks and see whether everybody's kind of in agreement and then we launched this type of event.
And it doesn't have to be like right away. It just needs to be like in a reasonable timeframe, you know, hours,
we can come on, that one event looks like and so we can
Little too. Okay. Okay.
Thank you. Thanks.
Danielle. What are the contributions you were talking about?
Yeah, so let me just I'll share something here. So one of them is something that I had been working on with MSR for quite a while it kind of got buried in some pretty bitter. Oh, how do you do that? Oh, you mean like just zoom like the actual word but
yeah, so that, okay. 150 is usually a good. All right.
Is that better? Okay. Okay. So this is something I've been working with MCR for a long time. It's actually been done for like 13 months. It just got caught up in some like corporate stuff, trying to get it processed, I don't know. But basically, it's a secret recovery scheme. I kind of alluded to it. It is a scheme that I tried to really Over the common stuff like in the, in the industry like mnemonic phrases, you know, which have these really no properties that they're actually pretty terrible but they're used everywhere. And then there's also the Shamir stuff, or, you know, social recovery, which, which is cool is nicer and more elegant and a lot of ways but still is, you know, full holes. And so MSR, you know, we worked on a riff of a scheme that was like first mentioned in literature like in the mid aughts and and kind of came back a little bit for biometric template in the mid teens of 2020s. And now, you know, sort of repurposed it for a scheme that has all the features of Shamir and locks in the sense that if you know your inputs could be when whatever you want your TFM can set thresholds. It's information theoretically secure, like Shamir know, the order of the inputs is agnostic, like, all these all these good features. And it's actually an encryption scheme. So technically, you can encrypt. It's not like a seed derivations Or you just, you know, your words are seed, you can actually encrypt large volumes with this and recover, you know, files. So our thoughts are, this might be good for, you know, storing private key seeds, storing wallet files, you know, or cotton D context files wherever you want to call them. So you can like, have a way to boot between wallets and transfer this file securely. So this is something that Microsoft Research has white paper, we have a kind of kind of, I would say not great implementation in C only in the sense that it was written by the cryptographers who I worked with, and they're not like, super good programmers, they kind of like good mathematicians. So it's very hard to use is what I would say I had, I struggled to get it running on like a pristine Linux build, so but we want to go build it out in the community. So my proposal is going to be to do this in the IMD group is a blog posts that I'll publish and then we have the white paper will do and then my commit resources to building Like an open version of the scheme anyone could deploy. It's just a series of functions really, it's nothing more. So that's that's the first proposal. And then I don't have something to show on the second one yet. But I'm going to be writing up a zero knowledge proof explanation of the zero knowledge proof investigations and work we've done on a snark based scheme that has some interesting features that are kind of like not covered out there yet in the schemes that are present in the market. Our hope was to do this as a contribution with other groups into the claims and credentials group in diff, and one of the other groups that seems like a great fit would be the BBs plus work from matter. So our goal was to maybe do a joint def post with them to say, hey, look like we're we're all kind of going to contribute some stuff into the appropriate group and you know, work on something that can interoperate between schemes, you know, whatever they are even outside of these two or whoever wants to pile on and make it you know something where you can pick and choose whatever is best for you, and then all sort of work together. So these are the two kind of initiatives we want to kick off to help the community next month. That makes sense,
The first one is it getting is there? What's what exactly is getting contributed? Is it a white paper? backhoe is?
So we have we haven't we have an implementation right now see implementation. I mean, it's kind of like like some of the libraries, the flat map libraries are kind of academic. I can only find some academics, you like playing math lovers. So we need to like actually reduce them. Find a math library that covers the finer field stuff that uses which is not like super trivial. And so at this point would just be the white paper but bypass all the math in it. And so you could execute against the white paper if you wanted to, but we're going to contribute over the coming months like Asia from our plus one Dev, myself or someone else will work with her to write the necessary components to make it more production quality as it were.
So there's a team at Microsoft that will maintain a repo and implementation and will be responsible for ensuring the cryptography actually works and that you're not just like committing like a repo to death and then waiting for somebody to pick it up.
Right. Yeah, that's
okay. Awesome. Thanks for that clarification. And yeah, thanks for the contributions that will be coming through.
And no, I think sound sounds great. I think it would be interesting to set up maybe your conversation with the credentials and claims folks matter. So like, I think Wayne Martine and Daniel and, and whoever wants to join me to talk about their contribution around the CCNP stuff.
Yeah, I've talked to them. I've talked to them. I've talked to Martin before, we definitely talked to Tobias. Like he thought it's a good idea. So like I've I've talked to each of them individually, we just get together and try and like make a, you know, sort of a decision about how exactly we're going to roll that out. or part of the next CNC color something would be good. Yeah, for sure.
Perfect. And that we closed down the general updates. I posted a poll on general on slack on an idea to host the face to face virtual session. We sort of an eye with a goal to have an open virtual meeting, which would mean that other community members beyond this membership could join and and listening. That would also mean it's not primarily an IPR protected class. But we'd enable us to a better understand what each working group is doing in a more detailed fashion and enable a lot of the others, like those who are like not leaf members to get a better understanding. And we could have a session for following that is an IPR protected. There is not a clear agenda. We are just like looking for a date. And suggestions. What it should be about is just since face to face was cancelled, we thought that that might make quite a lot of sense to still have a session. There was also a question on how interrupt projects future it's going to look like and and definitely that's something we could talk about, maybe as a first step towards it could it could be that like, fine during that meeting. We also find tuna hackathons idea later during the summer, and we just like put out the goals what we should be doing. So there are like a lot of flexibilities just to actually be together a broad community we like as many participants as we can do. Yeah, grow the community. So if anyone wants to like, give an idea or custom vote, then go to general and look for the poll. It's not too far up. I posted it. Sunday, I think. Great. So working groups, markers or some I saw markers here. Can you give us a brief intro? We are at halftime. So we're pretty good.
So try to make it quick. There have been a lot of interesting new topics and new developments in the working group. Daniel already mentioned the secret recovery scheme that they are contributing we we have that on the agenda for the for the next call. There's been quite a lot of interest in carry Of course, which Sam is working on. Also, on this week's Working Group call an interesting presentation by people from slack it regarding trusting resolvers, trust trusted resolution returning proof metadata from resolution requests, how they do it in their community. Also, regarding universal resolver, we're still working on deploying that on on dif infrastructure and seen a lot of new driver contributions, I think, five or so five, five new drivers recently for new methods, updated documentation a little bit we received them an audit from touch foundation on accessibility for the for the web front end. So the web UI that we have for the resolver, which runs on updates to improve accessibility. So yeah, lots of new topics and interesting things we we decided after talking with Sam to change meetings which are currently which have been on a bi weekly basis to change that to weekly for now see see how that goes. So next call will be on Mondays discussion coming week with probably talking about Danielle's secret recovery scheme and and carry those moving topics what makes
Thanks. There are no questions. Are there any questions
I forgot to maintain domain linkage I wasn't very closely involved with that maybe already probably knows that. But there has also been some some additional discussions on how to associate the IDs and domain names in both both directions.
So we have a special back for defining on the website side, how did they're linked and Daniel has been proposing arbitrary JSON to be posted somewhere for going the other direction. I think Tobias actually originally proposed that and there is an open issue on the well known did configuration about how do I link from a good back to a domain. So it's open topic for discussion. I think there are some proposed JSON floating around. My request would be that we do that in the existing spec, and we formalize it, you know, concretely and we not create another speaker. Just do it. Now randomly. Daniel, you want to add anything about
Yeah, so there's basically a service endpoint descriptor that I was thinking called links domains, very simple read domains, better link doesn't work. And I can just paste that in the issue. It's a rather simple snippet.
Thank you. Then claims and credentials I so weigh in on the call. But I don't see all the forces.
That's we're waiting for for when storage compute. We have no SDS. So what means temporary hold? Are we closing it? Yeah. I think that we should close it down. I think the SDS word I, you know, we're going to have to have something that we can produce the interfaces that look like some sort of, you know, application that will create a store that has logic beyond but SDS, I think is going on in the end, but I think yes, yes, work is going to take long enough that it just doesn't exist to continually have this on the agenda and on the site. And closing down might give us the opportunity to start Fresh when you have SDS done with a group, it's more targeted. So we could just produce the thing in an IPR fashion that we actually want versus such a broad group. So I think closing it down makes sense. I can try and email any other real active people that were in that group to see to make sure they feel the same.
Other great, thanks. Just
giving a quick update on claims and credentials, most of the work has been moving to presentation exchange format. And for everyone who's not familiar with that is if you're trying to create a credential from an issuer, right, you want the issuer needs a way to say what they need to create this credential, right? And presentation exchange tries to solve that problem. So really, on the last episode of claiming credentials, it was exciting because we noticed a lot of similarity between some of the JSON LD framing that Tobias and team has been using for the BBs implementation, and also presentation exchange. So there's a lot of discussion how did those two play into each other? Are they interested? same level of abstraction is one feed into the other. And we think we're close to those answers and in a good collaborative way, taxonomy update, we were supposed to focus on COVID credentialing. But that process has been a bit more complicated than anticipated to put it lightly. So one really enlightening conversation that happened that II w regarding credential subjects was a chat that I hosted in order to give really useful feedback about like, we're not going to find taxonomies that work for everyone. We need to figure out those that work for ourselves and like three others first, right as that approach, so just evolving our thinking and what would actually be valuable to the community observing in that way. So that's a brief update from claims and credentials and on the agenda is talking about some of that zero knowledge work that Daniel is working on in the next meeting and continuing our work on the presentation exchange format.
Perfect, thanks. So are there any questions to him or to the group? And if not, then let's go to the doubt. Oliver, I saw you on the call. Yeah.
There's basically no major updates. We saw another did psyop presentation by radical lecher, which is a, which, which is not a member yet. The implementation is based on a Chrome extension, but it's not 100% compliant with the signup spec. Some features are missing like encryption. Then a few more issues came in on GitHub, sort of Josh from Microsoft created a few.
What we will do
this week is our try to merge the large PR, because we already asked people if anyone would object and nobody objected. So we will merge Just logically are, and then we will encourage people to create prs in case they have any issues. And the point when we have no pending, you know, specification issues on GitHub any more than and we have 100% compliant reference implementation. The idea would be to send this back to the steering to get final approval.
So currently, there is validated ID who works on reference implementation of signup, but it's not feature complete, again, features that are missing, for example, the GW stuff, so encryption, which is quite critical.
Um, that's basically it.
Thanks, Ali. Are there any questions to the depth and the No then did come some
good discussions recently about, particularly service endpoint details have got some prs with with lots of commentary on them, which is really good. Also some about message structure and some other stuff. So we're mostly sort of moving past the initial discussions about the zero on trip stuff. And getting into more of the details. And so we anticipate lots of good conversation around those technical details. The service endpoint tells us specifically what goes in a in a did doc so that you know, the other person speaks did calm and how the the things that are defined there are used to communicate. So that's a, that's a pretty relevant piece of it that's been requested by many folks. And so getting it in there and beginning that part of the discussion is really useful.
Thanks, Sam. Are there any questions to the group and maybe I would have One just a bit like IV top topic. There is also an idea and that in that face to face meeting, we would invite some of the CCG folks and maybe further hammer out the did calm choppy discussion and also like it for me it was clear that there might be some like not a constant communication going on so maybe to find ways that how we could improve not just the outcome but like generally diff and CCG because it seemed that they might be complimentary and not nothing more. Yeah, just an idea. And then Daniel or or a for citrate. Sorry, are there any questions that did come?
No, Daniel or Rory?
Yes, we've made great progress on the Satori spec. I we still expect it to be done this month and ready for publication in terms of like a review, hopefully other people Take a look at it. I've got like 20 spec bugs assigned to me, I've got to finish them. And I'm trying to do that in the next like, week and a half basically. But the core protocol is looking pretty solid and the reference mutation is not far behind the spec. So, so that should be aligning at the same same time. Just so anyone is aware like we're going to be doing our push of the ionic mutation this month. That will go into bitcoin main net, I'll probably be mentioning, obviously, you know, worry and other folks that have worked on, you know, Troy and other folks that have worked on the spec and other implementations as well as to try and make sure they are getting their credit. But that's no, that's all rolling out this month.
Are there any questions?
All right, Daniel. Is there a date for the ion release?
Yeah, so I'm gonna believe right now. It's scheduled for sometime on the week of 25th.
Okay, thank you. And then Kalia on the secure data storage.
Secure Data Storage is going well. We're just sort of getting started
go like you have this great mic, can you pull a little bit closer? It's hard to hear.
That's where hi
because the one is not i'm not talking, I push it all the way over there. Sorry, thanks. Um, we're just getting started and we're really tackling the input documents and going through issues from them to get it Get Started. I don't have a lot to say Really?
I might have a question. But it might be just my missing knowledge. Have Been there any active discussion with the solid folks?
Yes. Well, I mean, Dimitri, and Dimitri used to work with solid directly and as far as I know that they are engaged. Okay. tracking the work.
Yeah. Okay. And we're,
I mean, I've been, we had I've reached out to the my data community, they have the data operators group in from that group during the call last week, he's going to share what we're doing with them. I think we may do mutual briefings soon. So yeah, we're really trying to reach out to anybody who's touching this space right now and making sure They know about the working and getting involved. So if you if you're listening to the recording and your work touches on secure data storage, personal data vaults, encrypted, whatever we want to call them join us because I think we have a we have a strong vision of you know, through a lot of hard work of getting an alignment on the charter and I think we have the energy and momentum to get there so
perfect. And if you are listening you can get in touch with different than we will make sure that you're at the right place very quick. Yeah. And interrupt current status Ori.
Yeah, so my most interrupt is is I'm not really sure what's what's going on with the with interrupt. at DEF, so I'm excited to hear about, you know, sponsorship opportunities instead of rekindling it, it seems like it kind of needs a boost. I know they're David Crane winner from Accenture, Accenture is sort of looking for work to do related to Iran. But it's not entirely clear to me what the goals of interrupt are and the fact that it doesn't have a reoccurring meeting and that it doesn't produce directly code, integrates existing code, I think has potentially structurally caused issues with it. So I'll leave it at that. In the CCG. There's a number of diff companies that have just completed a major interrupt milestone initiative, companies working with the Department of Homeland Security, Silicon Valley innovation program and that work, which I'm sort of I think it's it is it's the end Up work that I'm involved in right now. There's an HTTP API around credential issuance and verification, which is being standardized at the CCG. There's a open source implementation at transmit pass of that, that we've we've done some work on to support. There are credential handler, demos, Chappie demos around that. And then there's an interrupt, some interrupt demo websites that allow you to pick and choose the issuer and verifier from like, six or seven different vendors for verifiable credentials interrupt. And so that work has just sort of concluded Well, it's the first first piece of that has kind of just concluded, and we're expecting to see continuous updates to the Visi HTTP API and the CCG credential handler, API specification stuff in the CCG. And and then there's an internal interop test suite that is written basically allows you to show that you are, can support the same API's as all the other companies in the interrupt test suite. So that's, that's kind of an entirely CCG update on interrupt. And I, yeah, I'm eager to figure out a better way of getting interrupt to work at diff. I'm not exactly sure what the best path is forward from that. But obviously, it's, it works really well. And you have this giant, you know, government entity that's funding interop work and forcing a bunch of companies to work together at diff, we may need some other structural incentives to get in or up work to happen here. And the other alternative is, you know, we could just actually focus on interrupt work that's happening at the CCG and kind of piggyback on that and drive contribution into those areas. So that's interrupt update
hey, I'm super keen. Do you know once we polish off this presentation exchange presented to them as nothing that hopefully plug some of their holes, holes like the credential manifest? No, no, I was miserable find these credentials, there's no way to discover them. I mean, just the act of giving a credential over the wire is like a tiny, tiny piece of this. And then, you know, this diagram kind of might help shed light, I think on the entirety of that flow and kind of put all that together. And so hopefully, we can make this this possible, the actual route versus interrupt on 20%. Yeah, I think
this we will not solve this today, but I think it would be. I think the combination of we have an event where we might be able to sponsor some activities or some hackathon or some other idea might be a nice way to kickstart some of the job questions and work So maybe we we set up some time between Dan and Ori. And if you're whoever wants to join, obviously, just to focus on like how that could look like and what could be beneficial outcomes, and then we can maybe combine this.
Yep. And whoever wants to join, like, we will try to make it very open. And then we have 11 more minutes. Ori and those who are actively attending CCG, or maybe someone else can you give us an update on what's going on in the last two, three weeks.
On the last call, they started the chair re election. Seats are up for grabs, and I think there was a note in general about that and they're looking to get new members and so there that's as an operator. For more interoperation between diff and CCG, and possibly merging more perspectives into CCG, such as from the cryptocurrency industry, or from hyper ledger familiar, folks, because there hasn't been, you know, I'd say that there's an opportunity for a better representation there. And then I think there's also been a continuation of the educational credentials discussion. That's my knowledge. Anyone else feel free to add more
question about that? Are is the current leadership looking to not be current leadership? Or are they just sort of reopening it to see who's interested in having an election?
So two out of three, Joe and cam are running for reelection as the chair, but I believe that
the Chris Allen is deciding not to run again. Thanks.
Yeah. So just to add to that, like, I think it would be incredibly valuable. If one The new chairs was from hyper ledger and maybe one one was diff, and then you know, the other one would have been a CCG full timer. It's kind of like Dream Dream scenario for what might happen there. In order for that to happen, someone from those communities needs to sort of show up and wave the flag and represent, you know, the community that you may have had more experience with. There's also the zero knowledge, BBs plus signature suite was moved to the CCG as part of the link data suite, you know, track there so that that spec is there. It'll continue to be updated. There's also a revocation list spec in the CCG, which provides some revocation capabilities and herd privacy and works with all of the linked data proof formats. So that's an exciting new spec in the CCG. That's under development. I have a demo of it, which I set up I've tested it out if no work sort of works. It's a little a little interesting in terms of developer support right now, but it's basically brand new. And I think that's pretty much it for CCG items.
And if there are no
others, yeah, I think the idea to have someone to like have someone like hyper ledger and someone from defense or influence CCG core, that would be indeed amazing. So if someone feels they've been, please move forward. And I guess those who are attending the call can like, potentially stand behind. Just
I am throwing my hat in the ring for one of the chair positions for CCG. But don't let that discourage you. I think most important is that we have a bread from here to there, and not necessarily who exactly that is. So feel free to also
Thank you. And he's, we could get my data update if there is such an easy topic because my data is pretty big. I
mean, the big news is they, they released their operators paper,
which has 48
protocol operators listed in it. And they have this. The mitre operators group is fairly active and they have a common endpoints group. That's actually a place where I'm a little bit concerned about how we actually get this stuff to all connect up together. And they also have had a funding crisis and our have their staff is all working part time. I think
what's happening there. Oh,
thanks cut. Yeah. And so that would be the more official part of the discussion. And then maybe in the last six minutes if, if everyone serves another,
there's another initiative if we're going to track things outside ourselves is the CCI, right.
so the COVID credentials initiatives sort of, it's unclear exactly how it started. And that doesn't really matter at this point is brought together folks from around the world who are aware of verifiable credentials and decentralized identifiers and sort of asking the question, how might these apply in some future use around code COVID Test status. Other things like our, you know, one, one person I know is actually working for us state in the United States to issue credentials to track tracers. Right. So if someone shows up in your door and says, I'm,
you know, an official from the state of
How do you know they are? And they're asking all this information about where are you in because they're actually a tracer. So there's a bunch of new credentialing that might happen as a result of COVID-19 stuff and sort of building a community. And so what's happened is there's a bunch of SR projects is how they frame it. And so it's really been about knowledge sharing between projects who are looking at implementing credentials for their contacts, and they have a rules group that's working on governance frameworks, potentially for this And a tools and a use cases group. So it may be a fruitful source of finding folks keen to do interrupt who may not be familiar with interop work across the community so far.
perfect. Thanks clear. And yes, and Ori posted a couple of links at the end related to interrupt and CCI. Thanks sorry. And we have four minutes, maybe then just do like a quick round. What were the best i w sessions and then anyone can visit it because I don't think we can really talk about it.
Any other question? Are there I mean, there's a report about it will be published at some point. And what about the recording? Some sessions will be recorded, whether it be will it be up as to or do
we, at the very beginning, we talked about some if people who went to sessions recorded their sessions and posted them on YouTube or Venmo or whatever, or Vimeo, then they're in the notes, but we also were aware that this sort of live conversation aspect of it might be suppressed with everybody feeling like they were on tape and everything they said would last forever. So we encourage folks to like if they were doing sort of a formal presentation and wanted to post that like sure, right, take that put it up on your own YouTube send us back a link but
we had 138 sessions. And I think we're only missing four sets of notes so we've got better notes than ever before and some recordings for some things.
I think the two I would suggest available I think for that was there was a session about ditch calm and choppy like one on one kind of session I think
Yeah, that was recorded.
This one will be very valuable to be posted here if someone gets them yeah. Ah, here we go. We have someone in the chat. So if that could be possible great. And the second one was I think the stuff BBs plus stuff from the metro team. And they recorded this as well. I think this even online I think I've seen already recording about there
might be something we can that we can find.
It's that's it's ii w.id. Commons. dotnet is the wiki where they are. I'll put the link in
Yeah, and for me the matter session on BBs plus was the highlight of i w for sure. It's tremendous work really awesome.
I just found the YouTube video about that which is here. That's the matter. Introduction videos plus
awesome actually wait. Yeah sorry, can I ask for updates
Yeah. And informal group sprung out of i w
so if you Have a personal blog and you want to get back into blogging either for the first time or just like the old days. We have a blog pod group on the IWC Slack, sort of for peer support. And then I'm working with info minor on doing an aggregated blog of all the personal blogs in the community, and potentially also an organizational one and that company one, so I don't have a URL for those yet. Okay.
If so, then please mention and we are at the very top of the hour. So thanks, everyone who joined today and those who will watch the recording. And here we are talking in two weeks, and let's move forward the topics that we covered, and thanks a lot for joining.
Thank you all. Good week.