 Move forward then. So welcome everybody to the technical steering committee for hyper ledger, everybody's welcome to attend this meeting and be respectful of the other participants here. Questions on what that looks like you can always check out the code of conduct that we have linked in a variety of places, including the agenda. We've got some work in flight that there's no report out today, including what you see there for the CI CD. And then one thing that didn't make it onto the list that I'm going to drop into the chat forum on chat hyper ledger.org is an earlier proposal for some cross language support spoken language. And it would be helpful if each of the projects took a look at that report and or took a look at that proposal and provided some feedback on how that would work or not work with their particular project and hyper ledger. And with that, I think we can go right into the quarterly reports. If I could for the for the CI CD committee, we had a fairly good turnout last week. The next meeting is tomorrow. We would of course like more projects to be represented. So if you're doing CI CD, please do join the meetings because we we want your input on the future of kind of where this is going. Thanks. Okay. All right, so we had the saw tooth update go in. I think yesterday. So I don't know if it has been widely read yet. Somebody had the link for that handy. I'll post it in. Thanks. It looks like it's been reviewed but all but two of the TSE members. Which one was this saw tooth. Oh, I had, I, yeah, I looked at it on the plane last night, but I wasn't logged in. So, thanks. Okay, great. And then thanks for pasting that link, but that's to a PDR. There we go. Yep, I fixed it. But we would like more eyes on on that pull request. So. All right, so any, any questions or comments on this update. Andrea as long as I have one question then. Yeah. Yeah, I saw the thought was had supported the PBFD. So how about the performance on the large sustainability. So on a large network, what kind of performance characteristics is that showing. Yeah, I think it's a native PBFT and meditation, right. Yeah, it's a rust based. I'm remembering correctly. Yep, it is rust based. You, you get any number. Yeah, I think the question is, how good does how well does it run if you're running on large networks. We're at what level of you tested it. So we've been running some LR network tests with 10 nodes, I believe. I don't know what the, we're able to do a lot more than what poet can do currently with the settings, but I don't know the exact numbers off the top of my head. And are you testing. Have you tested. Failover and. Adding or moving notes. Yep. What's the level. Okay. Yeah, we have, we have shut down notes and restarted them. And we've had some nodes. Due to some hardware issues. Die out on their own and we're able to bring them back. Okay. Thanks for the information. There's also some RFCs that we have around consents around PBFT consensus that might be interesting for the community to look at to one that comes to mind for the question about leader election is a forced periodic leader election. And so that might be interesting for people. And once that gets implemented, that would of course ensure that that feature is constantly under test. Yep. And all of those RFCs are already implemented within the code base. Okay. Andy, any, anything else that you would like to highlight on this? We are. Yeah, go ahead. No, go ahead. I was just going to say that we are working towards. One dot two release, hopefully happening. Within the next couple of months. As a part of that, the PBFT will be released as a one. Oh, as well. Also, we have some new mobile SDKs. So you can write. So to the applications in Swift and. And so Java so for Android. I had a question on the diversity of contributors. You talk about there being 13. Different domains. Is that. Like do you mean 13 different companies, if you will, or. So I pulled a stats for that. And what I do is I parse out the sign offs. And then I, I grabbed the domains off the email signatures for that. So there's 13 different domains that are contributing. I've been trying to go in and scrub the numbers this month to see if there's. Any sort of overlap. Okay. Because it says there were 41 committers and 13 different domains. So, all right. Yeah. So you would expect several committers to be from the same companies. Right. Yeah, I just was. Yeah. So I would read that as a high water marker or an upper bound on the potential companies that are contributing. Okay. Yeah. Probably something a little bit less than that. Probably people using their Gmail account and stuff as well. All right. Cool. Thank you. Yep. There's now quite a few repositories. So the script does a lot of work for me that I don't want to do by hand. Any thoughts on making that available to everyone for all the projects. Sure. Sure. Yeah. When I suggested that before several months back, Tracy showed me a script that she had that she was using that was a lot better than mine. Oh, okay. But I've put mine up as a gist somewhere. So I could, I could find that link again. Okay. Well, I mean. Pull requests for Tracy's scripts are, are, you know, also accepted, right? They're in the hyper ledger labs repo somewhere. What, what does she use? I use get DM. She used a get and bash scripts. Oh, okay. And like unique, you know, UN IQ and mail merge and all that stuff. She used. So get DM is like that, but it's written in Python and I hate Python. The rust bindings to live get to are pretty amazing, but, you know, rust is a pretty heavy lift for something like this. Hey, right. This is James. I remember that conversation we had on rocket chat about running Tracy's scripts and you needed pretty high level permissions across the repose. Yeah. You know, even, even with like the publicly visible information, it was, I wasn't able to do that. I mean, you know, you can get your back up to the, you know, the purposes of the data to be able to get across the repose and even, you know, even with like the publicly visible information, it was, I wasn't able to exact that stuff other than against repose where I had. Contributor rights. Well, I don't know what her scripts are doing. Her scripts just work against the public. Get. Yeah. I was gonna say it was, it was an API token thing. It was, it was something, it was something weird. Maybe she's changed them some center or maybe they, there was a mistyped URL in there. And so it was trying to use admin access to access the Hyperledger account on GitHub because the full URL didn't resolve. I pushed a PR to Rai about three weeks ago or something to fix it. I don't know if it's landed yet, I can check on it. But yeah, there was one that was misspelled. It was like the healthcare working group, but it was spelled Heath care. There's something like that. Yeah. But basically, yeah, I mean, all that stuff is in the GitHub, so. Yeah. I was running those scripts on privilege. That's how I found it. I drop all my privileges when I run these things that are supposed to be for public consumption. Yeah. I like you. I don't know if it's Solona on it, but what's the status on getting sort of, you know, the vanity metrics and stuff up? I know everybody hates them. I know Brian hates them, but everybody asks. And I think it'd be useful to sort of make it public to sort of encourage. I see that Solona's on, but she's been out this week. We are working with the community bridge team to bring those metrics in. That's what I heard. Right. So that's... Sorry, I took a little while for me to find my mute button. Someone's like, somebody has a cold. Yeah, I think it was a little worse than that, but I'm doing a lot better now. I can move without pain. So yeah, right now we're working internally with LF to try to get to where we would like to be in regards to gathering those metrics. We haven't gotten there yet. Rye and Dave have been, obviously Tracy have been doing clever things behind the scenes to try to get there. We're also, that's one of the reasons also, Chris, for wanting to do the... Solona, I think we lost you. Well, that virus took a sudden turn for the worse. Am I on? Sorry. Yeah. I dropped out for a second. Rye, Dave, and previously Tracy were working on some internal scripts, but we're trying to get some of that stuff a little bit more production-wise. And we are looking at trying to gather other numbers beyond just off of GitHub, but also Confluence, Chira, and Chat. So it's just slow progress. Okay. Always a good idea to have a reason for data first. So we don't need to discuss it more now, but just dumping a bunch of numbers. Oh, I need all those numbers. My team doesn't know how well we're doing. Our team doesn't know the status of the different projects very well, unless we do know how contributions are going and how all of that is working. So they're very much so needed by our team. It's just we've got to work within a lot of different, varied constraints. Okay. So we kind of covered the fabric last week, but were there any questions? Yeah, so Chris gave us a quick download last week. And it looks like everyone's already reviewed it. Yeah, there's only a couple of questions I tried to answer. The ones that had been, I don't know, everybody. So Mark, to your point on CUBE, and so for this, not quite in alpha, but we hope to get it into 2.0. And then Nathan, if you're on, and in regards to ERSA integration, that's not currently planned. You know, maybe we can get an update on how mature that is and so forth and figure out where it fits. And when, you know, is the right time. And then as far as idMix, idMix is in there, has been since 1.2. We finished a lot of the work in 1.3 and I think in 1.4 we added the revocation piece, which was sort of the last remaining support item. And so that's in there. And what, in what ways that integrated in, is that? What do you mean, in what way is it integrated? In code it's in the, like the SDK support, or that's? Yeah, it's in the Java and JavaScript SDKs. Don't know if it's in the go one, I'd have to ask Troy. And I don't know, I don't know about one. Maybe you know if it's in Python, but... Not yet. In terms of the supported SDKs of Java and Node, it's in there. I think Java actually might have been in 1.4 as well, but the Node was in 1.3. And yeah, so I mean, the support is there, right? It can be used. I'd have to go and double check. It's been a while. I believe we have an example, you know, tutorial. Okay. Well, Chris, about the idMix, I have one question. In the documentation, they are missing there's still some limitation for the idMix, right? I remember one major one, it's a limited organization number in the network. So do you know, is there any plan to improve that? Oh, you need to add in sort of random people, kind of support people that are not in part of, in the consortia. Yeah. Yeah. I'd have to research that. I don't know the answer. Okay. I think if you ask on Fabric Crypto, they could tell you. Any further questions? Cool. All right. Thanks, Chris. On to the architecture work group update. I think this was Rom. I don't see. Is Rom on this morning? Yeah, that's the Rom. I can answer most of the questions if it's Rom's the one that's in it and Rom's down and I put it together, so. Okay. I didn't see any questions on it and it's basically the, there are two parts of the message. The first is that we're continuing to make progress. The second is, and this is, I just want to make sure that everybody sees in the issue section, we are writing about your platforms for both the system identity and privacy and confidentiality. We are writing based on our best knowledge. We have reached out to participants and contributors to each of the platforms. If you don't get back to us, you're stuck with what we write. So that's the nasty part of it. The positive part of it is, please, we need your help in clarifying some things. So if each of the platforms could make sure that they reach out to Rom, stay on there myself. I will point you to the documents in the sections that we've been writing up for. So. Hey folks, Tom here. Looks like I was using the privacy and confidentiality feature and couldn't find myself on here. Thanks for covering that, Nick. Yep, that pretty much was it. Okay. Well, I think with that, pointer to next updates coming from the identity work group, Iroha, and I guess that's the two that are the soonest on our list here. We don't have any further agenda items. So I'll give just a minute for TSC members that wanted to raise something, but didn't get a chance to get that on the list. But in general, it's best if we do have agenda items, we get them up there first so that people have an opportunity to prepare and we have constructive use of our time. We need to discuss the backlogs. I think, I don't know. I mean, today, Solona is ill and that's postponed project readiness. I just heard from Dave that he's not ready to present today and Mark and I still need to work on the overall engagement. So. Sorry, Ray, I didn't mean to interrupt. Go ahead. Oh, I was just gonna apologize to TSC for not being ready with the project readiness stuff. My daughter broke her foot and I've spent the last three days in doctor's offices and so I've been unable to prepare my presentation, but I'll put it on the calendar for as soon as I can. I'll have to look at where I'm at and it'll likely be next week, but I think that's gonna butt up against internship stuff or something. I gotta look at the calendar, but yeah, as soon as possible. And again, I apologize. Sorry to hear about your daughter No apology necessary. You weren't on a specific deadline for that. In fact, I think it's best that once you have some ideas put together, make sure that you get those circulated on the mail list and then we'll be able to have a more thoughtful discussion when we do get it on the agenda next week or the week after. Yeah, that's really the piece that's missing Dan and thanks. Yeah, I was gonna float it on the mailing list last Friday and we can talk about it over the weekend this week, but yeah, I'll do that as soon as I get it all together. Thanks. All right, well with that, thank everybody for their time and we will speak again probably next week. Thanks. Thanks. Have a good day.