 All right, Jonathan. All right, Chris, we are at Quorum at this point. Just checking have been or Greg joined. All right, Chris, regardless, we are at Quorum if you're ready to get things kicked off. Okay. Good morning, good evening, good afternoon, good night. That was our antitrust policy. Don't do anything stupid. On the agenda today, we have an update on the EU hackfest. And hopefully we can start closing on that. Revisit the Hyperledger training and education working group proposal with Tracy. Dan would like a few minutes to give an update on Hyperledger sawtooth. Then I'm going to regale you all with the first project report. On Hyperledger fabric. And then we have heart with a white paper working group update, update. Does anybody else have anything for the agenda today? If not, then I think we can get going. So Todd, you're up. Yeah, sure thing. So European hackfest, thank you for your patience here. We have found a venue in Lisbon, December 5th and 6th. Events team is just finalizing the contract for that. But we will have the registration site up before the TSC call next week. So excited to move forward with that. A little bit non-traditional of the venue, but I think it'll work great for this group. And really excited to close out the year, bringing this back to Europe and see everyone one last time. Any questions there? Otherwise, please stand by for registration page and further details in the next few days. Super. All right. Cool. Looking forward to it. All right, next up is Tracy and the Hyperledger Training and Education Working Group proposal. Todd or somebody, Tracy, can somebody ping the link into the chat so people can follow along? Yep, one moment. Oh, looks like Dan dropped it in. Thanks, Dan. All right. Tracy, are you on today? She may be traveling back from Sybos right now. From what I recall last week, we can have this discussion, Chris, if you want, or post-Pontel, Tracy's back, either way is fine, up to you. I was hoping we could review what has actually been changed. There's a number of comments in here. For Chris, I hate this stupid window. So there's a number of unanswered questions from Bawa from what looks like this morning or maybe yesterday. I think we're gonna have to- I'll get it. Just frickin' wonderful. So I have a contractor coming. I'm fucking believable. He's coming an hour and a half early, so I'm gonna have to drop off, unfortunately. Chris, why don't we just move forward into the updates for now and circle back on this, okay? Yeah, let me just do mine because this guy's gonna be here in a couple minutes. He's coming now. Sorry about that. I don't have to drop. My wife just got back. So, all right. Anyway, let's go to the updates then. So Dan is first. So I've asked Zach, DoubleTall to join us. Zach is one of the Sawtooth maintainers and he recently finished up a feature that sounds like it's pretty cool and it's adding a new capability that I thought people would find interesting that incorporates telemetry information. And so without further setup, I'll hand this off to Zach and he'll ask him to just do a short version of this. And then after the TSC calls, the Sawtooth team does a technical forum where everybody is, of course, welcome to join. And we'll be going into greater detail on this new feature. This is Zach. If I were to click this little gray boxy looking thing, would that share my screen? Oh, no, that's made full screen. Ah, show. There's now an option. We'll do that. You've been given the power. Drop my screen. You guys see my website? Yep. Excellent. All right. So, yeah, one of the, I think more interesting potential applications is supply chains. You've got a lot of different partners, a lot of different steps in the chain. I think there's a lot of potential uses to decentralize that, to allow for some interesting auditing of the supply chain. So we recently tackled building a proof of concept supply chain app on Sawtooth. Builds off some previous work we've done and really quickly we're calling it asset track because it tracks assets and it does sort of two things, one you might expect, one you might not expect. One is it does provenance. So if we create a user, I did those in the wrong order. So we create a user and then create an asset and this web app is all hooked up to the blockchain. So anything we put in here is going to be built and signed in the browser. The transaction is going to be built and signed in the browser, let's say, and then submitted onto the blockchain. And we're in Dev Mode consensus, so it's all very fast. But you can see we can very easily create an asset, this asset one, two, three, I am the owner of it. It has a location which brings us to sort of the other little thing which is telemetry data. So none of this, so these are just a few fields that I picked, I defined for the sort of generic asset type. If we look over here, weights, location, temperature, shock, same like useful things you might wanna track. Anything you want could potentially be submitted by like an IoT device or something like that. I actually got a little script to submit some updates. So if we look at some of the preceded updates I've got, some of them might be more interesting like this light bulb coming from Japan here. And so you can see as an IoT device would be submitting data about an asset on the chain. It goes on the chain and then something like this web client here can reflect those changes. So this was about a one month project. It's still in pretty early stages. There's been some weight fluctuations on that light bulb. And it was interesting. Any questions? Is this already in GitHub? Can we get it and play with it? Yeah, so it's been spun off onto its own repo which I will pop into the chat here. We're still sort of cleaning it up, I'd say. The deployment story isn't great on it yet, but you can pull it down. And if you wanna bug me on Rocket Chat for some hackney directions to get it running, I can help you with that. And the deployment story will be better shortly, something we're working on now. There are the beginnings of Docker Compose file. Any other question? So is that map continuing to update as your script is running? Oh yeah, so if we go back to the map was made to the US, this is a very fast plane. Probably some gravitational waves pushing it along with those weight fluctuations. Yeah, that's the least exciting part of the presentation, though, all of these aspects continue to update. I think temperature is probably a better one to look at for graph that one updates a little more frequently. But you can see as there's been temperature fluctuations and this is all in real time. So you can sort of see the difference between when I started, when I created it and when I actually started the script running to see updates are coming a lot more frequently now. So each of those updates is like a transaction of, I can paste the GitHub URL. But each of those updates is a full blockchain transaction then? Yep, yeah, each updates a blockchain transaction. The permissioning about who can send updates is all pretty flexible. We have this concept of owners, custodians and reporters, so as an item gets physically transferred between people, you transfer custodianship as it illegally gets transferred, the ownership, you transfer that and then reporters are just public keys that are authorized to submit updates on one or more of these properties. So you can have different reporters for every IOT sensor, one for temperature, one for whatever and authorize them individually or what have you. Okay, so we can kind of think about those like oracles or something about for that particular asset. Yep. Great, well, I think we'll get in, go ahead. Question, I know that you wrote about it on mailing list. How open would you be about writing a blog post about it, describing all of it to wider public, making sure that our community knows about it? Sounds good to me. I think I want to get the Docker compose file finished up so there's not like a 10 step startup process on this thing, but yeah, write a blog post, get it out there. Great, so if you could email me martedledexfoundation.org, I'll work with you on it. All right, well thanks for giving us the teaser on that, Zach, and then in the next hour, we'll be going into greater depth on the architecture and implementation, I think. Sounds good, great, thanks. Thanks. So as everybody got the link, we can get going. So this is the first of the Hyperledger project quarterly report readouts, following the template that we all adopted and approved the past couple of weeks. And so I'll just sort of give the synopsis here in the hell. So we continue to grow and mature following our one-to-one release. I basically used the past quarter of elapsed to fill this out and we published our first release in the very beginning of July. So it's roughly been three months. And we've got a growing mix of contributors. Basically, we're at a point where IBM comprises 42% of the overall contributors and amazingly enough, we're at 49% of the commits. So again, we're seeing a significant balancing of adding additional community contributors and having their contributions growing over time, which is really good to see. There's been, since the initial one-to-one release, we've had 69 developers comprising 14 companies and a bunch of individuals that I can't obviously figure out if they're affiliated with anybody because they're already used their GitHub ID and I don't know these people. Oh, stop it. 143 commits, about half a million lines of code changed and we've published three bug fix releases. About once a month, we published a bug fix release and we're working towards a one-to-one preview release that we hope to get out by the end of the month. And that should include about 21 new features or improvements to performance and scale along with obviously with bug fixes and so forth sprinkled in. In terms of the chat and email and Stack Overflow and the various forums that you can ask questions and so forth, there seems to be quite a bit of activity continuing. We have about 750 questions in Stack Overflow. There was a spike of questions and traffic on the mailing list in August. I think that was due to the publication of the 1.0. People started to pick it up using having initial set of questions. And but that settled down and now we're about where we were with the traffic with roughly about between 175 and 200 messages a month and lots of follow-up. So most of the messages have follow-on chains of one or more people responding and so forth. So it's pretty good activity. I guess the couple of areas that I think we could obviously improve is the visibility and the transparent. I wouldn't say transparency because we're totally transparent in terms of all our planning. Problem is that we're not doing a very good job of planning and it's hard for people from the outside to sort of figure out what we're up to and where we are in terms of cutting a release and so forth. So I've been in talks with Dave Huesby and with Brian and Tracy to see if we can't get some help getting JIRA configured to be better and more useful especially in terms of external people tracking and so forth. So I think that Dave is on, he can confirm but I believe that they've been authorized to go and find an expert as a contractor at least for a while and to work with not just the FABRA team but any others that are using JIRA to help get it configured more suitably to help with planning and so forth. Because right now we're just basically using the out of the box basic JIRA sucks configuration and we could really use some help in doing things like adding story points to bugs and so forth so that we can actually do planning and measure velocity and so forth to figure out if something's gonna make a release or not. Anyway, that's basically where we're at. It says all of that in the deeper dive places there, maintainer diversity that didn't get covered above is actually increased because Ben and Morali went to State Street and so now we actually have 10 IBMers, three from digital, I'm sorry, three from State Street, two from digital assets, Hasara, Huawei and Salesforce. So questions, comments. Nice job on that, Chris. Was it, how hard was it to pull that stuff together and work with the form? Took me about, I wanna say it took me less than an hour to do the write up, gather the information. I ran some analytics and so forth to count people and so forth. That really only takes a few minutes but there's a little bit of setup and then most of it was just sort of going through and trolling Jira to get the set of epics and features that we're working on and those types of things. It took less than an hour basically to pull it together. You know, I think we should use that video tool that Dan showed us back in the day, right? Oh, yeah, we did that for the one.o release. Yeah, I'm sure that Gary with one point, yeah, one or three, yeah, full is wait. We'll update that or something. Can you do one of those maps that Dan showed in Chicago of all the code? Yeah, this one. That's what we're just talking about. Yeah, yeah, yeah, exactly that. Dan posted a video, Mark. You can see it in the chat. All right, thanks. That's in the wrong window. If there are no questions, no comments, to Tracy's not on. So I'm not sure if we were supposed to vote on these, just acknowledge them and record them again while they're recorded there in the wiki, but. Yeah, many people are here. Like most of the Edmonds Foundation guys, the Hyperledge guys are here in Toronto, you know. So Tracy's here. Dave is giving a talk just now about blockchain security and I don't know if Brian is feeling around. Yeah, most of you are at the stand. Well, and I guess we're good to go then. I don't think we need to have a vote unless anybody feels the need for a vote. Oh, I don't know what we would be voting. Yeah, right. There's no like, it's not a proposal report. I think it's good. All right, and to follow up on what you were saying, I mean, in the meantime, we have to thank Dave Inion from IBM to try to fill in the gap that Chris was talking about with regard to Jira and getting a higher level view of what's going on. He's actually been maintaining a spreadsheet that kind of gives a status update of where we are. So the goal is to basically replace it with something that would be in Jira directly. So we don't have to manually maintain that on top of it. Yeah, so I'm not a big fan of spreadsheets. Number one, number two, also then again, this provides yet another place where there's a source of truth about where we are from a release perspective that isn't necessarily immediately obvious to people coming in from the outside. That's my main problem. I've tried to, in our dashboard, as noted in the report, provide one of the tiles in the dashboard, gives an update on where we are with those issues. The problem of course is that not all of those features or epics are kept up to date from a comment perspective to give a sense of where people are and how likely they are to finish the work and so forth. And that's a lot of what's in the spreadsheet. I think it's possible to do these kinds of things to configure Jira certainly with story points and so forth so that people can get a sense of when it started and when it's likely to end and so forth. So yeah, I think we need some custom fields just to summer. And I think we need better hierarchy and groupings. If we have a grouping, then it's gonna be a lot easier to understand oh, this one to four is like six weeks, but we need this before the next one. That's why we cannot release on October 22nd. So the more of that you can zoom out and then it will look like a spreadsheet hopefully in the end, but automated like I don't suggest it right. Yeah, so we're always in sync. It requires some work. Yeah, Jira is complex, it's complicated. Right, nobody knows how to configure it. And if they did, they don't have access to it to configure it so it's a little bit of a catch 22. There was one point when I was fumbling around trying to configure it and then apparently somebody got in trouble. So anyway, well, I will say Mark Ford did a great job with our view of it. I know that it's still similar problem that to get deeper in, you probably need different credentialing, but Mark's done a nice job with a sawtooth dashboards. Okay, next up is Hart. Somebody's powered up. Hey, so I just wanted to provide a brief update from the White Paper Working Group. So I think we are finally nearing imminent completion for what we will call an introduction to Hyperledger. And we wanted to encourage everyone, particularly the TSC members to read over the paper. You can find it on GitHub in the Hyperledger WP directory. If you'd like to take a look or if people want, I can send it out to the TSC list. So we feel like we're in a pretty steady state at this point. We're happy with the kind of overall structure and layout. It's written up basically as we agreed or rather as the TSC agreed back almost a year ago. So yeah, that's about it. Please take a look, give us feedback. And if you have suggestions, then you're welcome to issue a poll request and suggest those changes. Does anybody have any questions? Should people be using? Do you have the link for ease of access for everybody? Yeah, everybody's been posting it in the chat there Dan. Oh, I see my chat hadn't updated. Got it. Should general stuff like that go to the announce list versus the TSC list? Does the announce list have a bigger audience? Do we know? I think the process that we were using was to sort of have the TSC sort of review and give them an opportunity to weigh in if they hadn't already been doing so. And then we can send it to the various spam lists. And then probably it would be worthwhile to have Art, maybe you or Mick put together a blog post to sort of announce it, give it a little bit of context and that we can use for promoting it. Yeah, sure, I think that would be a great idea. That's a great idea, go ahead, Art. No, no, no, I was just gonna say our future plan is to give it a couple of weeks of review and then pass it over to some of the technical writers that helped with the things like the architecture document to make it pretty. And then we'll hand it off basically to the marketing department from there. And I know Brian's not on, but I think the last time we ran it up or we started, we were talking about letting the board have a look at it as well. Yeah, I don't know what the procedure would be for that, but if they want to take a look there, welcome to. At least give them a heads up and so forth. I'll ping Brian and copy you and we'll figure out if that's necessary. Okay, thank you very much. All right, let's start. PDF at the build of whatever the last was of the last version of the source doc. Yeah, paper.pdf is correct. Any other questions? I think we're good. So unless there's any other agenda items, I think we can probably call it a day, give everybody half an hour back. I want to make a quick announcement, if you will, that performance and scale working group has moved to a weekly meeting. We're actually working through what a transaction is and how to measure throughput, things like that. And it's been some really interesting technical discussions. Meetings are Tuesdays at 9 a.m. Eastern time. If people want to just sit in and learn, I've been learning a lot on these calls. And it's really interesting because it seems transactions pretty simple, but when we get into distributed ledgers, and when it's final and things like that, it's some really interesting discussions. If people are interested and want to join the conversation or just sit in and listen, feel free to join the call. Excellent, I'm glad to hear that. And actually, Mark, I answered an email to the fabric list this morning, somebody was looking for performance numbers and I basically told them nicely to Consand. I wonder if we could maybe even just have in maybe the Wiki page for the performance and scaling working group, just sort of a statement that we aren't publishing numbers about any of the projects here at Hyperledger and then give some of the rationale of why that would be inappropriate at this point in time and that the performance scale working group is looking to work on that. Would that be something you could do to update the Wiki and then we can just point people to that? Yeah, that's a great suggestion. I'll make sure that gets implemented by the end of the week. Cool, thanks. Well, if that's it, then I'll give everyone a half an hour back and everybody can join Dan in half an hour. Thanks, everyone. Yeah, all right, thank you. Thanks everybody. Thanks. Bye.