Can you hear me now? Much better. OK, great. So just talking through some of the details of what's in what we're now calling the licensing profile, as Kate described, their SPDX from the beginning was focused on representing licensing metadata for software. But as part of the expansion of use cases, we're pulling that out into a separate profile. So what this profile consists of is classes and properties for the different components of how to model licenses and license combinations, as well as the fields for the properties and the metadata that store information about those licenses. So a lot of this is going to be a refinement of what you'll have seen before if you've used anything relating to SPDX licenses in the past. And if you go on to the next slide, we've included links for where you'll find the current model definitions for the different classes that make up the licensing model. A lot of this pulling together pre-existing content from the RDF model or from other aspects of the SPDX spec. You'll find the link for the definitions of the different properties for licenses. And then finally, because these are properties, and I'll touch on this in a bit, because these are properties on defines to be tied to files or packages or snippets, the properties themselves for concluded licenses, declared licenses, and so on. These are currently stored in the software artifact subset in the software profile. So we'll touch on that in a bit. Go on to the next slide. So the components of a license model, and you'll see this in just a moment in the next slide about how these reflect, but the primary pieces are going to be things that you're familiar with. So the idea of a license, either being a license that's listed on the official SPDX license list, or the ability to define custom licenses, just like you've always been able to do. There's also one thing that is changing in SPDX 30 based on recent discussions of the legal team. There's always been the ability on the official license list to also include license exceptions that are defined on the list. We're now adding in the ability to define custom additions, which are additional text that supplements a license, and we'll touch on that as well. Just as before, and as you've always been able to do in the license expressions, you can use and or to reflect more information about how multiple licenses are combined, plus to indicate that you're talking about a license or subsequent versions, or the with operator tied to exceptions or additional text. And then all of this tied to none, or also being able to say none or no assertion if you're not specifying a license in an SPOM. So if you go to the next slide, you'll see that these are, so the overarching class is any license info, and I don't think you should have the spaces in there. I think those are by mistake, but any license info is the kind of abstract parent class for licenses or accommodations of licenses. None and no assertion are defined also as separate classes. If you go to the next slide, you'll see that's something we're sorting through and there's a, you can go on to the next slide. I think there's an open issue to resolve between the release candidate and for three hour, we're gonna sort through whether to be representing none and no assertion as separate classes or how exactly we're going to represent that. So that's one of the open topics for discussion currently. If you go on to the, I think in the next slide, you'd see an example of how this license expression, the way that it appears in source, in currently in tag value files or in more often, you'll have seen this in headers for source code, SPDX license expressions that combine multiple licenses. These are using the different classes that we just showed, those can be modeled in a syntax tree style. And again, there's nothing about this that's actually new. This is always something that you've been able to do in SPDX 2.3 and earlier, it's just because of the way that we're defining the classes, defining the models, I think a lot of this is going to be elevated and more visible and a little clearer how to translate license expressions into this format. So we can go to the next slide. So as I mentioned for licenses themselves, these two concepts, listed licenses and custom licenses have been around since the beginning of SPDX. Listed licenses being those that are on the official SPDX license list and custom licenses being those that are user defined in an SPDX document. So changing the name slightly to help clarify their purpose and reflect some of the changes in properties that are available to define on each of these licenses. So we go to the next slide. And again, for listed license exceptions, this is also something that's been around since, in this case, since SPDX 2.0, to be able to use on the right side of a with expression, any of the exceptions that are publicly defined on the official SPDX license list. But if you go to the next slide, something that's been a topic of discussion for a long time is how to represent things that, there's been a desire to represent things that are not fully official exceptions to license conditions or additional permissions. And so in SPDX 3.0, we're adding the ability to define custom license additions, which are essentially additional texts that is not itself a standalone license. So this is gonna be, you see here, an example in the bottom with addition ref to be used for additional text. Just to be clear, the exceptions list on the official license list is going to continue to be only official exceptions, things that are truly exceptions to license conditions or additional permissions. So go on to the next slide. And then the other major point is just that we're kind of rationalizing and cleaning up some of the property names and unifying them across packages, files and snippets. I think in the past, there's been some different names for these properties and different ways that the names are used. And so one of the goals for 3.0 for the licensing profile was to align on common names in terms for the properties across the different types of software. Now, the way that they apply or the way that they're reflected may have slightly different definitions, but that's part of what you'll see as we go into, as you take a look at the property definitions for these. So go on to the next slide. And then finally, so there are a number of open issues, a number of some of which are more technical or mechanical, but a handful of which are open substantive questions. And I'm not gonna, given the time for the moment, I'm not gonna get into these right now, but you can take a look on GitHub, please come, please join in. We'll be looking to discuss these in upcoming SPX legal team calls, balancing, talking about the licensing profile and continuing to do the work we do on maintaining the license list. So we'll also likely be looking to schedule additional joint calls with the tech team and the legal team to move the licensing profile forward, just as needed between now and the three hour lease. And I think with that, I'm gonna turn it over to Jeff. I think we're gonna look at a couple of use cases for the licensing profile. Thanks, Steve. So I'm relatively new to SPDX. Kate and Rose asked me to talk about use cases a little bit regarding the licensing profile. Before I jump into the specific examples, I wanted to bring up one point, which is having done lots and lots of license scanning and use many tools over the years. It's pretty common for tools to think of a file as sort of an atomic piece. Sort of the, you know, we think about software components in an S-bomb. You have packages, you have files, you have snippets, you have other artifacts, binaries, et cetera. It is very common from a licensing perspective to find multiple licenses in one file. But that doesn't mean that all the licenses apply to everything in the file. It's very common for one license to apply to a snippet and another license or set of licenses to apply to another snippet. So we're gonna talk about that a little bit with these use cases. In fact, here we have an example showing in the file header that we have the Apache 2 license and then immediately below that we have a comment indicating a specific component and we show another license or in fact two licenses here. So one way to look at this is say a scanning tool might scan this file and think of this as, okay, all of the licenses just apply to this file. So we've got this license and this license and this license and in this particular case we're making the assumption that GPL is unspecified. So it is a custom license. It's not one of the standard license because it's also extremely common for people to be lazy. Go figure, especially software engineers. We like to be lazy. We like to just do things quick and get them working. So that's just fine. But it can lead to confusion. Oh, by the way, this wasn't a part of a plan in the talk but I'm just gonna pitch, please use SPDX license identifiers always, thank you. So this is pretty common for a scanning tool to look at the file and come up with this result. But another way to look at it is we have Apache 2.0 and because of this second comment we have the next phrase which is MIT or GPL. And in this case we've gone ahead and made the assumption that it's GPL 3.0 only. But what I like to see is this case which is you don't have all of these licenses apply to the file. What you have is you have two distinct snippets. You have one snippet that is Apache 2.0 and then you have another distinct separate snippet which is MIT or GPL 3.0 only. And in this case in the S-bomb each of these would be a separate entry in the S-bomb. These are both snippets and they're separate. Even though it's one file you end up with two entries in the S-bomb. So the next use case is a license that's pretty common except that it's been modified a little bit and this is actually not unusual at all when it comes to licenses. People, again software engineers, developers are humans. Okay we're not talking about AI here that's a different session. And when we put the license in the file header sometimes we add extra comments. So in this case we have standard GPL 3.0 or later and then we have an exception that's pretty common, the auto-config exception but there's some extra text added. So currently in SPDX 2.3 what we end up with is most, it'd be common for scanning tools for example come up with this concluded license of GPL 3.0 or later with the auto-config exception except in this case because the exception has extra text added to it it's not a standard license or a standard exception. So we end up with a custom license. That's okay, SPDX 2.3 allows us to put this custom license in except that, I don't know, I talk to a lot of lawyers it's a pretty common thing for me and lawyers like to see, lawyers do a lot of license compliance and they like to see things that they already know about and understand. So this could be a little bit harder to understand just because it's like, oh it's a custom license what's this, I haven't ever seen it before. But what we can do now is we recognize that oh this is maybe the auditor or the scanning person would say oh this is just a standard thing plus one extra little bit. So I can handle that, it's really simple. What we have is we have the standard GPL 3.0 or later and we use the with clause which of course is always been there but we have this new custom license edition and it's this addition ref auto conf GPL 3.0. So what this is is we're not using one of the standard license exceptions that Steve mentioned, there's a list of standard license exceptions. This is a modified license exception. So instead of having a completely new custom license we have a standard license with a custom license exception. So I think it's much, much simpler and straightforward to understand.


Kevin, you guys had a 12-point lead a half-time and then the third quarter goes away, you guys can't really get it back. What do you think the difference was in that second half? Giannis put his head down, got to the rim, got to the free-throw line, that slowed us down. Have you ever remembered seeing Steve getting even closer to that animation? Yeah man, we watched him play for 28. I've been on the court with him when he's talked crazy to the rest. My first few years, Steve used to talk so crazy to the rest. So when he didn't get attacked as a coach, I'm like, because he's feisty. But I mean, you gotta handle yourself differently as a coach, but sometimes you just want to go out there and fight for your guys and I think that's what he did tonight. Does that make a difference for a team to see a coach go like that? It might make a difference to some players. I mean, I don't mind. I don't care. Either way, I mean, I know my coach is there for me. I know he supports us and wants the best for us. So him getting attacked really don't enforce that in my mind even more. It's just, I like that he was excited about the game and into the game that much. But he's always like, he's always into the game. You know what I mean? But I don't think that proves a point to us, to me. I don't know about my rest of my teammates, but to me, no. Kevin, you guys have a plus 30 second quarter this weekend. So what do you think has been about that quarter where you guys have been so dominant in being able to get your act together? I don't know.  I mean, second quarter is cool, but we want to have four quarters of good ball. But we're a good team, so we're going to have spurs. We're going to play in spurs sometimes, but I want us to play full games. When you look at the last couple of games, it's been back and forth, socially charged. What would you say has been the biggest lesson that the team has gotten from these four games that you hope to move forward in? I mean, just taking an L is always tough, you know, and there's always a learning experience. So just watch your family, what we did wrong more so than, you know, the stuff that we got right. I mean, I think that's always going to help you as a ball club when you can look at your weaknesses and try to make a tournament to strength. So we lost the last couple of games, some little things, and, you know, so it's going to be good to see that and try to get better at it. But we got another game tomorrow, so, you know, that's the beauty about the NBA. Speaking of that game, when you watch Luca from where he was in his rookie year now, how would you describe the type of player you see? I'm not about to do this all year with you, Nick. I'm not about to praise these dudes all. I respect them. Luca is who he is, but we're ready to play tomorrow. They got a good team, even playing great basketball, but I'm not about to go in depth to how I feel about these guys every day, but I respect them. What do you think you guys need to clean up most going into tomorrow night? I think our defense was pretty solid tonight. They were under 43-44% most of the night. They got loose there at the end, but for the most part, I think we were connected. You know, we got to continue that going forward. You know, we got to just be guarding the best players in the league night after night. So they're going to get there because they got the ball in their hands, but it's all about making as tough as you can. Tim, you guys got that good little spread at Admin in the first half? What do you see of him? I love the minutes. I love when he can get to the rim. He's so quick and athletic that he can put pressure on the rim for us in that second union. I think that's what got us going. He said the second quarter was big for us. I think Admin was huge. His momentum, his energy as soon as he stepped into the game, just kind of, we fed off of that. So we need more of that from him. You know, it was good to see him get his rhythm. Nine points in six minutes. Four for six. I like we both.


Hi, my name is Chris Jacobson. I'm the creator of Vallejo Historic Home Support. I made Vallejo Historic Home Support to help my friends and neighbors who had questions about their historic homes. And though this isn't a historic home question per se, many of my friends and neighbors have been asking me pretty much over the last six months. About six months ago we had the California wildfires and PG&E started turning off our power. Right now it's April 2020, beginning of April 2020, and we are right in the middle of the coronavirus crisis. And I'm still getting calls from friends and neighbors asking, you know, what happens if power goes off? So what I'm going to do today, I'm going to show you a couple of different options, and we're breaking these down into several different videos, one for each of these options so you can get the details. So this is a little power station. There's many of these. It's about 100 bucks. We're going to talk about how much it can power and what it does. This is called a power inverter.  We're going to talk about how that works. You put this on and turn it on. Over here, this is another power inverter, sort of a smaller, and then maybe I would call this a medium-sized power inverter. It's actually hooked up to a deep cycle battery. And the last option, which I don't actually have an example of today, but I used to own one and that's a generator. So we're going to talk about, especially the Honda EU generator series. They're amazing. They're ultra quiet and they kick out a lot of power. It's a gasoline motor. So check the next video and we're going to run through these one at a time.


We'll get back on this post-security bill in the 22nd of June, and I'll go and wind it up that we can have it reported, whatever it is, and ready for our faction, perhaps even before the Republican convention, we can decide on that, whether we take it up before or after. But we can get, we can run, and we've got most of our language written so that there won't be a long delay in the time we make our final decision. If you do that, that'll do more for us this year than any other single thing that we'll do to up your tax bill, and that's already behind us, but it'll be the most positive, affirmative, future thing that we'll have. Let me ask you this to get your judgment on it. I'd rank it number one. If we pass it, if I can't get something, if I can get more than 13 votes on it, I'll vote you, and I'll vote you, and I'll vote you, and I'll vote you, and I'll vote you, and I'll vote you. What percentage do you want, 13 out of 15? That's 90%, isn't it? Yeah, but I mean 13 out of 25. Oh, no, no, no, you don't expect to get Republicans. They're going to be against any proposal I make, all of them against poverty, every single one of them, but they're not always against those security. I've got them in a bind if they vote against the Republican as well. They won't always be against the other, either, if you ever give them a taste of it. I'll tell you this, they all vote against social security when we enact it, when I start it, but they won't do it if you give them a taste of it. No, I know that, and they all want to be for these cash benefits, and say, there's increased cash benefits. And that's going to, that too is very helpful. They care to say, if you have to be in the committee before we quit, and what we're talking about is the last, the three-pronged approach he goes into, which would have some hospitalization connected with social security, and there's cash benefit, increase, plus improvements to the prevails. I beat all three of those, you could put that fourth one in on it, you're 13 if you didn't, that way I could get them all together. Because I think if you don't, why, you just murder the other one, and I think the other one's what's got sex to you. Yeah, now, if we didn't put it in, what would the Senate put it in? I don't think so. I don't, I doubt that ever you can take it out. I imagine if you don't get that out, because you lie at first, I'll have to get them back here between conventions to handle it. And I just, I would do that if you had it, because I think it's the best thing that we can have for 50 states, and I've been in a good many of them, and I'm going to a bunch more this weekend. When I get back next week from California, I will have been in states that have 100 million population. It was the first six months of this year, like yesterday in Massachusetts, like the day before in Pennsylvania. And when I get through with Michigan and California, I've already been to Michigan and California too. When I get through with them, as an astronaut, I'll have 100 million. My judgment is that is by far the most popular thing that we've ever touched, and it will do us more good than all the other put together. And I put taxes and civil rights, poverty, education bills, all of which we will have passed. I don't think this one's compared. Remember what President Roosevelt said, you don't get any mileage politically out of taxes. Well, I think we are, because we're having prosperity.


Everybody forced here. I'm ripping it's 2022 top triple threads baseball hobby nine box case number 66 picker team Avike with the Giants Brandon L. A's Brian y Padres Christy Cubs Christopher L. Marlins Edward P. Cardinals White Sox Dodgers Diamondbacks in Rangers Eric R. Mariners raise Greg B. Guardians Gregory M. Yankees Joe D. Pirates Jonathan L. Royals Josh H. Angels Justin H. Metz Kevin B. Reds Costa K. Blue Jays Mike A. Braves Nick A. Twins Rob W. Phillies Roberto with the Rockies Scott V. Orioles Scott F. Tigers Steve C. Nationals Steve R. Red Sox Todd D. Astros Troy D. With the Brewers. Good luck y'all. Here we go. Is it like 45 million is a first nose 32. I thought I thought it was hot. I thought it was like really high. It's supposed to be like around like the top salary is the position right but not quite somewhere around there like not the highest obviously but although I wish it was like that. There we see a lot more free agency franchise tag sucks. I don't think you I don't think you'll sit. Yeah the running back franchise tag is done ain't no running backs getting franchise died I can tell you that. Take one is like the one that you're like OK maybe like that's crazy 29 mil. Thanks Zeke. Thanks Cowboys. Good for Zeke for taking that deal. Good for any NFL player for taking lots of money. Taking deals. That's a song. That's a song. That's a someone just said in a in a YouTube chat gram to 150 Buster Posey Giants to 199 Jaren Duran. Red Sox rookie Kyle Tucker Astros to 36 October at thefts on the game use triple relic Jersey Auto Astros Kyle Tucker to 50 to Kyle Tucker's. Tucker's break there ever was J ran the two ninety nine guardians Santa 125 yet a million cardinals game used bases triple threads triple auto Fernando Tate's junior Manny Machado and Jake Cronenworth seven of 18. Oh my goodness Padres Brian Y. Tate's Machado and Crohn's own. That is so weak. Take one is definitely not easily replaced. Definitely not easily replaced. Jersey could Brian Hayes Pirates to 18. It's up on New York. All right. I'm putting running backs on a roster. You can do that. It's easy. There's a lot of running backs. It's one ninety nine Anthony Rizzo Yankees rookie to 75 Torkelson Tigers triple Jersey Auto Dylan Carlson to 50 cardinals. Yeah. Donnie can you take a bite of those bases? Make sure it's not a bagel. Yeah. I'll get right on the Jersey card raise Vidal Brujana 48. Thank you Donnie. Right. You do that anyway every time. Take one separate place. Not saying that you should pay a bunch of running backs because you can get you can get better value but you can't replace it. Like say when you have to figure it out somewhere else to two fifty nine Babe Ruth Yankees to two ninety nine Manny Machado Padres spending money and running backs is just like is usually just not good. No one no one wins a Super Bowl with like a running back. The leading rusher being like a lot of money. It never happens that way. Mike Trout to 18 Angels. Game used triple relic and Jersey Auto Astros Kyle Tucker again a seventy five. Back to McCabery is the one that you would pay whatever money you want. No they're great. They're great. I'm just saying like the last decade or so. Yeah I get it. If you are spending a lot of money on running back position you're already like behind the eight ball. Yeah. No I agree. To two fifty nine Yachty Molina Cardinals to two ninety nine Chris Bryant Rockies to twenty seven triple relic Manny Machado game used. No Padres. And Jersey Auto Tristan Mackenzie Guardians to ninety nine. I think I'm all the running backs I'm paying the most I'm paying is going to be like McCabery and then Henry behind her. Other than that at this point no chance Henry should be getting more than the sake one. No chance dude. To two fifty nine Freddie Freeman Dodgers to two ninety nine Corbyn Burns Brewers future phenom triple Jersey Auto Alec Bum Phillies game used on the truth on the jerseys there. Yeah no I won't want the Patriots side of big name running back I would hate for that. Ricky Jersey Vidal Brujana twenty seven Reyes. That's what I'm saying. Every time the Patriots won a Super Bowl it was like James White Ligera Blunt.  You're better off spending it on the offensive line the defensive line. The quarterback your receivers your DB's. That's what I'm wondering with like Miles Sanders and his situation that he's going to like want like a lot of money like. They should they shouldn't bring it back because like I mean depending on cost obviously if you can just get him for like oh here's three or four million. Yeah sure. I don't think we should go on our way. I think exactly exactly. Yeah you have Hertz Hertz is the guy that is going to do everything like that's the one you got to take care of. You have Hertz your brownie of Smith. There you go. It's very sure. Build around that to one ninety nine Javi Baez Tigers to seventy five Luis Robert White Sox. Make sure your old line is good because you need that too. Yep I agree. Tatsy Striple Jersey Otto one of three Padres. No time to lose.  No time to lose. Fifty to one quicker than any shortstop in history. Pretty good. Congrats Padres we'll get that Mag Padres killing it. Jersey Padroid a thirty six Red Sox. The run game is important. It's very important but the running back position itself is just not as important. The twenty five Freddie Freeman Dodgers to two fifty nine Ernie Banks Cubs. Like the Chiefs last night we're just scheming up great runs against that defense in the second half. Yeah twenty seven Al Tube game used triple relic. The Astros. Jersey Otto Rangers of Dulles Garcia twenty out of fifty. Strategy always always have running backs that are on the rookie contract. Like the Eagles won't miss Sanders like they might be like oh this kind of stinks here like he's this guy's not as good but as far as like replacement level. Yeah just draft a guy like the third or fourth round again. Yeah. Yeah I mean even drafting in the first round of running back is tough.  Like drafting in a pie. Would you rather drive higher pay a running back a lot of money. Drive hot. Yeah. I wouldn't drive the running back though. Craziness craziness. Crazy. Tray down to drive Bijan. Crazy bad. Three ninety nine Margarine Rivera Yankees to one fifty Clayton Kershaw Dodgers. Warner Franco triple Jersey rookie Otto Tampa Bay Rays. Congrats Rays. Ninety seven to ninety nine. Eric R. and trout Jersey to forty eight for the Angels. Two ninety nine Ricky Henderson A's to one fifty Trevor Storie Red Sox. Even the last time the one the one the Eagles won the Super Bowl in twenty seventeen. I think like a Jiu. It was who was the the receiving back the receiving running back they had. I got a touchdown. Clements or something Corey. Triple patch to three Phillies Reese Hoskins. Smashing stretch that's really cool. Powder Blues in the center there. Yeah. Corey Clement and Jersey Otto Barrios for the Blue Jays to seventy five. I need to spend both times in chiefs when it was like Damian Williams and it was like Isaiah Pacheco like. If you're good enough offense you do not need a good running back. Running backs and carrying offense like Derek Henry has Christian McCaffrey has but. That's also. Bad times bad times bad times. Yeah Greg yeah twenty twenty three getting quarterback Russell throw flags and the rest. Yep. Yeah I'm cool with the Patriots system of drafting running back in the third or fourth round and that's your guy. Damian Harrison Ramondrick Stevenson's both of them. James White forever picking up the carrot blunt for super cheap from the Bucks. To one ninety nine C.J. Abrams Nationals to ninety nine Luis Robert White socks. They drafted Sonya Michelle one time he wasn't as good as all those third fourth round picks that we had. And nice pirates game use triple memorabilia McCutcheon Hayes and Stargill to thirty six. Yep. I was a dolphin first. You know really we had like a hit like a thousand like a pretty good year with the dolphins one time. Yeah. Here's the auto to ninety nine Josh Hader Brewers. I'm pretty sure that's why we picked them up. Because he had like a thousand a year and I'll be signing the dolphins when he came to Philly. Or sure. Yeah. Hundred percent. Hundred percent. To ninety nine Bryson Stott Phillies to two fifty nine Hank Aaron Braves. Whoa. That's a big redemption there. Triple threads autograph relic combo book. Yadier Molina Nolan Aronato Lou Brock Orlando Sopada Paul Goldschmidt Mark McGuire. Our Pujols Scott Rowland Ozzie Smith and Bruce Sutter names. Monster Cardinal redemption Edward P. That'll be number to 10 or less. Monster. Amazing players of today and legends on this one. Crazy crazy crazy. And a Sapphire patch to three Nico Horner Cubs three colors. This has been a overall create a really really really good case. Master case I mean this one and the last rate together just just awesome. Someone was saying this one wouldn't be good. That happens. Fon said hot mama. Fon we're changing Donnie's name to Morbius. No. He's also a Guardians fan now you've missed a lot today. Yeah. Also a Cavs fan. Yeah. The Cavs thing is it was him but we can we we we help we help convince him to be a Guardians fan. Yeah. Swayed him away from the Rays at least. To one fifty Randy Johnson debacks to fifty Ricky Jair Duran Red Sox. Nolan Aronato to thirty six triple relic. Game used 34 homers and a Jersey Auto Casey Meyers Tigers to ninety nine. Fine. Perfectly fine. Yeah. Donnie's all right. This is lovely to two ninety nine Stan Musio Cardinals to one fifty Tatees Padres. This is this is great right in my face. This is Red Sox. David Ortiz. Oh man. To 18 triple threads relic auto Steve are with Boston. Big poppy big card big poppy. 80 extra base hits. 80 extra base hits 30 homers times five. Well that's disgusting Jersey Card twins Byron Bucks into forty eight and Jersey Card Rangers Corey Seeger to thirty six. Game used Bucks and player Warren Seeger. They have on it hurts. Sometimes it hurts pulling cards really nice Red Sox cards like that. That's how Donnie's going to pull these nice guardians cards. Yeah. Oh man. Ozzie Smith is on my TV right now. Actually like that.   Maybe that's like the maybe that's our key to keep people sticking around like coming back because they want to find the answer to all these questions. Why I asked so many questions. Let me get you guys a link right here for drip. If you have not signed up for drip yet. That is the link. There it is. Got to click that link right there. And you should get fifteen dollars from our that's our referral code right there referral link. Anthony Arizona twenty seven game use triple relic for the Yankees and Kenzie has no queue right now over on drip. Over on drip. That's the only place to get a personal side. Also no personals here tonight. They're all on drip and redemption. Zach Wheeler triple threads auto single jumbo relic for the Phillies amethyst parallel there. Scotty I'm sure you're not the only one. Sub Scott and the game was OK. Jeremy ran to one ninety nine no one hour auto cardinals. I can't get that ending out of like my head. Yeah I know. Drag it down big time to two fifty nine. Nationals Vladimir Guerrero. Exposed to go to the Nationals. Jackson Cole our rookie triple jersey auto for the Royals of seventy five. Great I'm pretty sure Sam works Sam works five days a week. Yeah. Jersey card to Brian Hayes Pirates to forty eight. Use your Saturday right. He definitely did breaks on last Tuesday Wednesday Friday Saturday. Yeah. Yeah but you know what he's worked more days I agree great good point. We should we should schedule Sam seven days a week. To one twenty five Babe Ruth Yankees to one ninety nine. And then on the next show here with Tony Angel's blue Jays.  An on card rookie auto Mackenzie Gore Padres to one ninety nine. Oh what's Randy gonna say. Brian's giving me some ideas every time we get cake in there on the straight grimoises run around screaming at number. Oh that's awesome Brian there it is that's awesome Brian to two ninety nine Giancarlo Stan Yankees one twenty five Garrett Cole Yankees. Ash's host the altubit at 27 ending and beginning Triple Threads Autorellic Astros and on the back is a Ben and Tendi Jersey Royals 27 game used Benny Teddy Sam and I should have a show the skipping Shannon type show I'd win every debate. I'll be the Who's the person that like gives each like the moderate or the host the host I guess yeah Host Donnie. All right, here we go guys recap relics first Andrew Ben and Tendi Boba shut Kebrian Hayes Anthony Rizzo Byron Buxton Corey Seeger Nolan Aronato Nico Hornet of three triple pirates there McCutcheon Hayes and Sturgill a Hoskins to three Mike trout Dusta Padreia Jose Altuve Vidal Bruhan Manny Machado Mike trout Vidal Bruhan Kebrian Hayes Kyle Tucker autos now we had a Jose Altuve Mackenzie Gore Jackson Coar Zach Wheeler triple threads autorellic single auto single jumbo relic amber this parallel for the Phillies Where's so many words Casey Meis Josh Hader Jose Barrios a Dolis Garcia Alec bone Tristan Mackenzie Kyle Tucker Dylan Carlson and Kyle Tucker There David Ortiz 14 of 18 triple relic auto Red Sox Take one there triple Jersey auto rookie Wanderfranco rays They're worn One of three triple threads autorellic Fernando Tatis Jr. Padres Padres again triple base relic auto Tatis Machado and Crona worth seven of 18 and A deca cardinals Autorellic combo book card Yachty Molina Nolan Aronato Lou Brock Orlando Sepeta Paul Goldschmidt Mark McGuire Albert Pujols Scott Rowland Ozzie Smith and Bruce Sutter dang dang Well, we're on to gilded on the flies now. Thanks everybody


Cool, I think we are we're alive awesome. Yeah, I know I'm very grateful for for the talk here I think this time as this hyper ledger Conference is starting we want to change a little bit like the dynamic we would not do like a 40 minutes talk only And we just literally do some some discussion with Matt. Let's introduce ourselves briefly. Yeah, for sure So I'm Matt Nelson. I'm a product manager that helps manage basu at consensus So I've been working with a bunch of the hyper ledger community now for about six months and working on the merge You know for even longer than that so very excited to talk about kind of what we view as the Next steps post merge how we want basu to be able to serve a bunch of different use cases clients needs you just get on that and You know basically how we see the client evolving in this landscape. Cool. I'm francesco I'm part of the form Consensus I'm working mostly on on devrel for for protocol metamask and infura and I'm grateful that we are today explaining the merged next steps and Anything that to do with with hyper ledger basu Cool, because we can start it will be very interactive. So feel free also to ask questions I know we are many today in the audience But but hopefully we get some people's ask good questions online Yeah, we just recap. Hopefully how many people know what's happening actually in one day and a half a little bit more I don't know what's happening. Yeah, everybody know probably but yeah, why the merge why we are here what's happening and And and and yeah the progress in terms of ecosystem that we also overview baseless execution client and and then what's post merge infrastructure will look like Let's just start and feel free also to jump in these are literally like we said, okay How we feel in 40 minutes. So we literally I put a lot of like interesting slides just to give an overview but we need to Yeah, we can just quickly quickly show like how a web 3 and digital assets in terms Of like reaching out audience we put some numbers here I don't know like Matt feel free also to add things but those are quickly quick slides before we are getting to the important parts I Think the the next slide. It's it's quite interesting. So how how is the theorem ecosystem look like? How big in terms of like user addresses and and the transaction per days So this is something that is is growing a day today and and yeah And I don't know what I think the latest number around the 400 400,000 active depths And we're also seeing and you know the builders market is is remaining intact and it's still growing compared compared The token markets that we see today. Yeah, but Yeah, cool. I don't know any questions until so far or anything to add Let me jump so why the merge I will stop speaking here But Matt you want to you want to say quickly what's what's the roadmap and why we're here? What's happening in one day and a half? Yeah, yeah You know as the first bullet outlines, there's an increasing urgency around proof of stake The reason being is that aetherium has roughly the carbon footprint of the country of Finland And that is something that we're eager to get rid of for a number of absolute reasons the you know kind of less Sustainable points under that are that we think more enterprises will be interested in cryptocurrency and blockchain technology when the You know nightmare of sustainability is resolved and then the network So we were really eager to get rid of that so that more and more folks can come online without having the You know the frankly embarrassing carbon footprint that aetherium has today There's also a desire to democratize access to the network proof of stake in this case will allow more and more nodes to come online That are not basically concentrated in the hands of mining pools And of course there's optics around The usage of these things as I mentioned and there's going to be changes to the economics of the ether token that we are really excited About and those around the issuance rate specifically But there are some other tweaks that I encourage you to read about online to how the economics that work The other is that you know with the merge kind of sets the stage for the emergence of kind of a set of protocol upgrades in aetherium Specifically around roll-ups other L2s and other scaling technologies One of the misconceptions of the merge is that it will decrease gas prices. It will increase Scale and speed on the network, but that is actually not the case But it does set the stage for some upgrades that will Allow those technologies like roll-ups to become first-class citizens on the network Which will hopefully see a lot of these Improvements come down the line much much faster now that we're also removing the biggest obstacle to upgrading the aetherium roadmap If you go to the next slide it talks kind of more specifically around what we're looking at Some of the points that I had mentioned previously again The the reasons why we think that more and more enterprises will come onto mainnet after the merge Are around these kind of four points the energy efficiency is although listed at number two is personally my number one The you know diversity and openness of the network as I mentioned as we remove the need for hardware intensive mining operations to participate More and more Validators and clients can come online and participate in the network and we're going to see I hope a lot more enterprises join Yes, you still need a capital investment in order to participate in proof of stake Although for a lot of the enterprises that I think are are ready to join the public network that Investment is not quite so large The third and fourth point are really about the hard work that's been put into the merge from an architecture perspective around the seamless transition So API's will largely not be changing as Dano mentioned the Randall opcode is one of the only ones that requires a change So we're really making this easy for developers to continue to use the technologies before and after Yes, Basu has had to undergo a lot of changes in order to kind of go through this merge transition But as far as developer experience is concerned and those building on top of the client I think that it's you know, it's going to be pretty much the same before and after with additional components around proof of stake The last is number four. It's better for DeFi. That is really based around the economic changes that I mentioned Changes to the issuance of ether changes to the way that if ether is You know burned so essentially, you know with in combination with some previous things mentioned or I encourage you to look up EIP 1559 Then you know, we're going to see a lot different economics around the way that ether is operating Yeah, I think definitely also like the I mean what you're saying about openness and diversity of Ethereum clients will play a big role because today as we know we are kind of on a monopoly and having a Differentiator in clients is playing a big role. Yeah. Yeah, we're seeing, you know, Basu has grown tremendously in the past few months We're really excited about that But it's frankly due to a lot of the work that people in the community have done to help develop a client for Ethereum Mainnet and making sure that we are doing press around what that looks like for diversity participation and for getting enterprises involved Key takeaways we can I think skip this I'd rather go straight to questions Exactly. That's that's that's a longer. I mean, that's not long, but it's quite interesting exactly where we talk right now around around key takeaways Cool. Yeah, merged timeline. I think we are ready kind of like past pasties I but but it's quite interesting to have an overview. I think Bellantrix was successful with some bugs. Yep, right? September 6th was the beginning of the merge countdown The actual date and time is predicated on network conditions But there is a prediction that it will be sometime around Thursday morning on UTC So if you're in the United States like me, that'll be probably Wednesday evening And if you're in Europe, it's probably sometime Thursday very early morning We might see the hash rate and the network drop and delay that timeline a little bit as minors exit the network But we're hoping that it will stay relatively stable and the merge will be completed sometime on Thursday. Yeah, that's All those things to say that timeline is quite long because there's a long and storied history of the development of the V-conchain and it's been very exciting to participate in that but you know really it comes down to what we're looking at here on the screen We have a proof-of-work-based Ethereum today And we have additionally currently running proof-of-stake beacon chain, which is the consensus layer as it's called And as we go through the merge the current kind of proof-of-work stack will be called the Execution layer and that gets us to kind of the crux of what we're looking at here with with basu's evolution from an Ethereum one client to kind of an execution client and the reason around that Split is that the consensus layer has been intentionally removed from the kind of execution Because it one allows us to run consensus in a way that is based off of proof-of-stake but to it it splits out kind of the complexity of Executing and operating on the smart contract layer from the consensus mechanisms So this doesn't immediately provide the speed and scale that we might think with the merge But it will set the stage like I mentioned for a lot of changes to wait that those two layers work separately To allow us to make some very interesting protocol upgrades. You might have heard of sharding. That's one of them I Encourage you to look up EIP 4844 if you're interested to learn more, but basically As you can see still well my head's kind of blocking it, but it's on this bottom layer So the the data availability that sharding is going to provide will be on the consensus layer So splitting these out into two pieces has provided us the ability to really innovate and it allows basu Which sits in this blue? Box the execution layer to become a lot more lean and a lot more focused on Serving different types of use cases and at the end of the day we get a scalable sustainable ethereum But we also get a lot of other kind of benefits of this as basu is not just compatible with ethereum mainnet Because it's an execution client that we're interested in right here. It's executing EVM based smart contracts. It's executing You know in theory transactions that don't really require kind of all the baggage of the EVM And it's we'll get more to this in in the future slides as we go along But it's again splitting this out has allowed kind of basu to reevaluate what we're looking at as a client And we really want the community to help us kind of shape what that looks like going forward And how can we add you know more consensus mechanisms? How can we you know plug this layer out and put something else in on the bottom? You know, so that means support for different kinds of networks Dano just gave a talk on how they use the basu EVM and hadera You know in theory you could use the hadera consensus service to run a network where basu just does the execution And that doesn't even require using all the overhead of the other hadera pieces So there's very interesting things that are going on and I think that if we continue a little bit I can kind of break that down some more, but we can also pause for some questions. I know that was a lot I'm excited about the the layer of infrastructure. We're posing for layer twos That's definitely one thing. How many of you guys know the beacon chain exists. Just raise your hands. Okay, cool Nice cool. Yes, please So the question is how how it will impact the security overall yeah for proof of stake versus proof of work, so that's a great question and the you know There's a bunch of different answers and they all kind of approach this from multiple angles with the beacon chain itself The the reason that proof of stake is effective is because there are monetary Requirements to attack the network so that you know, you might have heard of a 51 percent attack That's the same in proof of work as it is in proof of stake if you control 51 percent of the consensus power Let's call it of the network you can make changes to the way that the ledger operates and then you can validate those changes with your Percentage of the network to make sure that it appears valid So in proof of work that was prohibitively expensive for a number of reasons due to to mining power essentially requiring hardware In proof of stake It's prohibitively expensive due to the fact that you would have to own over 50% of the market cap of Ethereum And if there was a centralized entity that would be approaching that threshold It would be extremely visible within the public ledger of the network to say you know XYZ organizations own 51 percent and therefore would control a number of validators to do certain things There are a lot of other kind of nuances to how that specifically works and a lot of it comes down to there's also kind of self-policing within the network after the move to proof of stake so validators can Slash or nominate to slash other validators when they misbehave so say I try to fake that I have 51 percent of stake I use my keys in my validators to pretend like I have two stakes when I only have one if somebody notices that fact they can Effectively reduce my stake to zero and are rewarded for that fact So I think that we're gonna see you know kind of these watchdogs come within the network We've already we had our a couple of slashing events recently people are I hope incorrectly putting their validator keys in multiple locations But but we're we're starting to see kind of an uptick of people who are Penalizing others in the network one to reward themselves but two to really keep the network secure as a whole Yes, that is true We would hope that everyone would not so the question to reiterate for the stream and for everyone that wants to hear is that the You know as folks exit the network the number of validators would go down and therefore the amount of value needed to attack the network will decrease Yes, there so there is an example for where you could say oh I would exit a ton of validators over here and then start like a bunch really quick so that I have Quickly have a percentage of the stake and I can take it over However, there's cues to both enter and exit the network so in theory that up attack wouldn't be possible kind of like As like a flash loan sqx plate And to the hope is that as we add withdrawals and exits from the network the demand for staking will not go down It will go up because the more liquid stake becomes the hopefully the more validators will come online There's also the notion of liquid staking in general where I don't necessarily need 32 E to run these validators So you're using a technological approach to add more validators to the network So there's things like rocket pool like Lido where they match up eat basically smaller steaks with larger steaks to create one unique validator Yes, you have to presume that those organizations won't collude against the network as a whole I think that we are going to see kind of centralization around certain entities that control portion large portions of network steak like big exchanges or these groups like like Lido, etc that control a lot of these steaks but It is hard to say how this will play out in reality. I'd encourage you to read up Maybe my understanding of how the secure the network would be is an open question but the the again the costs have moved from basically The the hardware perspective to an actual stake in the hundreds of billions of dollars And if you look at the breakdown of the top sets of validators So, you know these accounts since the validator keys are basically there's public keys for all these things you can in theory Look and see who controls what portion of stake. We're not quite at the point where we have to get worried about centralized entities controlling like like, you know XYZ exchange has maybe 20% of all online validators We're not quite at the point where we're worried about that yet But there are some open questions though. I think as far as the merge transition is concerned A lot of the kind of mitigations come down to like the technological components as opposed to the economic components so We're feeling very confident in the way that the merge is going to progress because of the kind of One the robustness of the actual consensus algorithms. So the proof of stake is based on something called LMD ghost which is just a fork choice algorithm So there's a lot of like nuance in that there's kind of nuanced mitigations to certain edge cases Researchers have been spending years trying to figure out what they could be for this exact scenario Once the things level off after the merge. I think like you said, we'll be able to really evaluate what the validators I think my computer No, it's all good I think that the validators will have to see how the chips kind of fall But I again, we're not really approaching the point where any specific entities have Even nation states like would have the ability to create these kinds of Yes, but in so think about it this way as more mission-critical Applications and things migrate to the network more and more folks will be participating directly or indirectly And you'd hope that more value comes onto the network distributed via decentralization whether geographically whether you know politically To the point where the cost to attack the network increases as there's more participation by users. It's definitely a concern But again, there's a lot of none of these things happen instantaneously There are a lot of signals to this kind of thing. It is a public distributed ledger So you would presume that nation states would be watching what each other are doing if they're accumulating hundreds of billions of dollars worth of ETH and Specific, you know, locales. I think that that would be something that people would want to look at for sure I think we should in the interest of time continue forward But yeah, I'd love these questions Just wanted to show the 51% attack would be around 25 billion Yeah, be constrained status. This I think was like a couple of weeks ago, but around 400,000 active validators. I don't know what's what's today the amount, but it's it's I don't know more and more are coming online, frankly by the second as people get ready for the merge So the the activation queue is getting quite long, which is good And like I said, these cues are designed in such a way where It's impot you can't just jump on the network all at once and can start immediately controlling a portion of the stake And there are also execues to prevent kind of the opposite where you can't just withdraw all of your stakes so that maybe somebody else has a 51% stake Yeah, I think we should get straight to the bulk about basu as Mentioned before basu is a monolithic ethereum client What that means is that it essentially tries to do everything as Dana was mentioning It serves a variety of different use cases not just within proof of work or proof of stake But it also serves BFT based consensus algorithms And to this point, it's been quite, you know, great actually. This is a pretty good view of the architecture right here the pieces to note that are kind of Unique to public networks are probably the engine API that is unique to ethereum based public network consensus And again, we have proof of work consensus click consensus and BFT consensus down here The big the reason that the EVM is in a dark green box right here is because as dano mentioned in his previous talk It is actually separated out from the rest of the components of the architecture It can be removed and put in other networks and use the sustainable module and it has been intentionally designed that way through dano's very hard work to make that happen and the reason that we want to do things like that is because whether we like it or not the EVM is coming to gobble up a lot of the smart contracting world for applications that are Created today a lot of the other talks and a lot of the other hyper ledger based projects Their goal is to bring EVM compatibility to other things or to create interoperability directly with the EVM And you know, again, I'm not here to comment on whether that's a good thing or not but it is What it is and within basu it is a first-class citizen and what we're trying to do is make a lot of these other boxes dark green as well where the Components are not necessarily stuck in this layout and you don't necessarily need all of these components So the reason that these kind of things are dotted lines is because they are optional Those are privacy related features. You don't necessarily need to use them You don't necessarily need to you know not use them and they kind of touch a lot of different areas Which is why things can get kind of messy We like this picture for what it is But we're really trying to move kind of towards a new paradigm And I think that that's being driven in part by the fact that we support a lot of different network types And that we want to continue to support different network types and we want to support more network types And they might not use POW. They might not use proof of stake. They might not use BFT consensus You know, we we want to kind of lean into the pluggable consensus We want to lean into the fact that the EVM can go away and you know or not go away rather but exist in other Components exists elsewhere because our users want different things. So if we go to the next slide here Francesco Like what is this kind of boiled down to what are the users and developers want? They want an execution client for Ethereum proof of stake. Sure. They want to be able to run on main net They want a client to connect to a consortium network. Maybe they want to join, you know One of the pre-existing Ethereum based Private networks and they want to be a node that validates transactions running proof of authority or BFT consensus They might be an infrastructure you know Software provider and they want to build a business with a blockchain They don't necessarily know what that means and they don't necessarily know what all of their requirements are right now Because frankly the requirements reveal themselves much further into the line of developing blockchain based applications Then you would think up front And they might want a diverse software to connect to many different kinds of networks This could be like, you know, noses chain for example some other L ones They we can provide basu as a piece of software that connects to those different things. It could be a chain link node It could be you know a bunch of different applications run Semi-adjacent Platforms to a main net Ethereum or they run entirely different chains with different chain IDs And we want to be able to serve kind of all these different things or they may just want EVM execution So the users really don't necessarily know what they want up front Which is why a monolith appears enticing because you get everything in one box However, we only serve kind of the one basu thing and if they just want One of these boxes they have to get the rest of the craft to kind of with it So what needs to change right? Kind of two things that I view and again, these are this is a proposal for what we want to do with basis So this is an active discussion. We want to actively bring people in You know, we have a binary distribution, but we want to go to binary distributions multiple. We want to move to A proof-of-stake distro. We want to have a distro for private networks for proof-of-work networks. What what have you? We don't want to provide everything that users don't want to need and we think this is kind of a step one That's a quick win where you can decouple some of these components in a way that makes basu leaner and quicker And it's for example I just want XYZ for my infrastructure and that means we can give them modularization and componentization Where I for example need to run Just the EVM for my infrastructure because I want to make an application for my new layer one that I don't necessarily It hasn't been built yet. It's a new blockchain technology. It hasn't been built yet I just want an EVM or I just want to run a chain link node Like I said, and I don't need all of the stuff to do with proof-of-stake consensus. I just need RPC I need RPC from basu to be able to run Queries I just want to get data from the network I don't want to participate at all then you can have state storage within basu And you just pull the stuff out via the RPC. So it's a If we go to the next slide actually It's basically like how do we make basu just this execution client, right? I'd like to skip actually two slides ahead in the interest of time This one, sorry, this is perfect Plugable execution, pluggable consensus Possibly pluggable storage we have to figure that one out But it's something that we're looking at very closely because there's a lot of nice use cases that are enabled by pluggable storage and then networking pluggable networking You know what like that that one is unique I haven't we haven't thought too much through that yet, but you know there as Dano mentioned We have different kinds of networking and we have different kinds of interfaces that are not just JSON RPC How do we create a modular code base where I'm a new developer? I have this basu client in front of me, but I know that I have a hard requirement for GRPC I slot this thing out because you know, I have a very clean interface between JSON RPC and my execution And then I'm able to replace that right. I have a very clean you know line between For example the EVM and this potentially, you know, I use engine API here But I think that this is frankly could become a lot bigger to mean any external connection to the EVM Where I have a roll-up and I just want to plug like we can already expose the engine API in a way today Since since proof of stake has opened up this kind of big Rethinking of how these clients actually build blocks Execute them and then move on with their day Why don't we just open this up so that any like any consensus mechanism that happens in theory outside of basu land can work Right away with this engine API, which is already designed to interact directly with the EVM directly with state storage You know not necessarily with networking, but basically it's a it's a big line in how do we turn this into a much bigger notion, right? so I think that the Client that we're looking to build serves all of these use cases because it's designed to have Exposure to what you need and then you can drop in the rest and it's an open source product Right if I want to tweak basu to serve my certain needs Or if I want to build a plug-in that extends the engine API or extends the JSON RPC I can you know As we move to a modular architecture, I think that that's what we want to see right is Opening these connection points up so that folks can come in and design exactly what they need and drop everything else Not because it's you know one because we want to move to a more sustainable code base But two because I frankly think that we're moving towards a multi-chain world that will require You know some or all of these components and we want to be able to serve that because it's the best way to bring in more Developers to basu it's the best way to bring more developers into the Ethereum and Ethereum adjacent ecosystem And you know it's the best way to build the best execution client we can Let me take a breath and see what we have here Any questions I think modularity is the next big thing yeah, it's you know, it's like That like cacti the cactus team is now becoming the cacti team and they're building all these interoperability components But imagine if you got a lot of that for free by just exposing the low-level API's that you needed to interact with the blockchain state And the blockchain virtual machine Not that I don't like those projects. I just think that we can go bare metal on this one and avoid a lot of that stuff by opening up these kind of four layers consensus interface Execution and then you know the rest is already essentially build your own choose your own adventure because basu has plugable storage to a degree We have several options and you can write your own plugins to do whatever storage you want anyway We have relatively modular networking and we have a kind of plug-in interface which I haven't discussed much because I Frankly think it needs kind of a revamp or it needs to be opened up a little bit more or even created into the thing that I'm trying to describe here But you can already extend basu to do most of what you want to do through this plug-in interface But yeah, it's you know Legos Dano kept saying talking about Legos and it's this is really just a bunch of components and you only need some to do what you need to do and My goal is to make basu kind of a prolific piece of infrastructure software and to do that I think that we want to accomplish something that looks a lot like this And then again back to the privacy thing. I think that you know once we Solve the problem I made on the previous slide We get this for free Plugable consensus plugable networking and then to Sarah as an optional component of the basu code base not going away just moving I think we reserve couple of slides. Oh, one more. It's like a animation slide. I need to get rid of this crap But so why again, why why am I doing all the stuff that I just where why is that like the why do we want to move basu towards this kind of new mission statement and It's right here, right? We want to enable network participation I don't know what that looks like in two years and I don't really want to know I just want the client to be agnostic enough to serve The network like the users of the infrastructure to participate in whatever network they want to whether that's again Ethereum something different something yet to be created I think that all the building blocks are relatively the same and also we want basu to still be relevant in five ten years and if Things shifts away from this kind of vision if we have a modular lean execution client we will be able to adapt to the changing landscape regardless and Hopefully our users will not have to Change away from basu or to throw away what they've already worked hard on because the client will evolve kind of with the landscape So again to read what I've written up here. It's basu enables network participation for institutions It supports Ethereum post merge private networks mining networks And we aim to evolve for a multi-chain EVM compatible world around, you know EVM compatible virtual machines roll-ups hybrid networks sidechains more all that good stuff with a familiar license Familiar programming language Institutional grade features and hopefully keeping our nodes very low overhead as we move to a kind of lightweight approach to stake ether to do Interactions with any blockchain networks that run on similar Tech and we want to be the best and most flexible infrastructure for people looking to participate in blockchain networks That was that that was a peach. Yeah, that's the pitch This is kind of a boilerplate why do you want to do or why do you want to run on public networks? So I mean another of the big reasons that you know, Francesco and I are here today is not to espouse basu It's mostly to talk about why do you want to participate as an enterprise in public networks? This doesn't just mean Ethereum. I'm talking everything like we want to see enterprise We think enterprise will converge on kind of a mainnet focus within the future anyway So getting your toes wet now is definitely valuable And we think that basu is a great means to do that and it's rewarding you can get literally paid to do this You know, as I mentioned, there's a capital investment in actually staking But the staking rewards will likely be around 12% post merge, which is pretty great That number will go down over time However, it's slated to stay around 12% post merge for a little while as more validators come online We'll see that come down But it is a literally rewarding prospect for enterprises to learn how to run node infrastructure on public networks And that means getting the right approvals to do so with your organization's infosec teams Learning how to set up the infrastructure in a way that is highly available and fault tolerant and all that other good stuff And making sure that you have like everything kind of squared away so that when again When these things come to disrupt what your business does you don't have to be reactive You can be a little bit proactive Because I believe that a lot of the public network infrastructure will Disrupt many enterprises, of course not all But I also believe that that enterprises can feel safe and secure in participating in public networks for a number of reasons However, I'm working with Hyperledger to provide a bunch of different workshops on what that actually means So I know Antoine one of the basu contributors has run a great recently a great workshop on how to Operate and extend hyperledger basu Extend as I mentioned There's that plug-in interface where you can change the way that the client operates And operate is self-explanatory. You have to actually know how to run it. Um, but there are more details I think the next workshop is october 5th So check out on hyperledger and they will the wiki has the dates and I will be hosting a workshop on enterprises running public network infrastructure And we may even stake some fake eith, so that'll be fine That would cool. Yeah, we also have a bunch of like developer communicals also on the protocol side from consensus There might be worth to check out And the contributor call also on the basu side might be also cool Yeah, I think that the rest is just questions. Oh, actually, no, that's right. You're princess go Oh, no, no, that's the boring stuff But I mean, I don't know how boring is that but basically like super long story short is I mean, I don't know everybody saw the vitalic paper on on the verge You know merge verge search all all those great namings But literally it's what what matt is mentioning the post merge. Nothing is is finished It's it's literally like a process and you know sharding is the next big Etab and and yeah, and I really also recommend and free also to to reach out for for the slides Like a couple of links always on the on the merge research and and the specific also resources On on on podcast and it's exactly like explaining all this paper Because I think it's it's full of great information on on the next progression and roadmap of of east Yeah, this is like something super interesting that we find out on on reddit visualization But it's a mix on on how how now If you will look like in 2025, I think for digesting this I talk maybe like two weeks But for what I'm understanding is literally like a mix of those four for Top top and left. I don't know sidechain layer ones. It's quite interesting I don't know Matt if you know more but around those volitions and Validium's and obviously roll-ups we know it's ready But I don't know if you if you know more a little bit on yeah, it boils down a lot to Data availability and proofs So there's some complex cryptography in Through volitions and validium's improving how certain data interacts and exists within the network Again, it takes more than the three minutes. We have left to explain volitions But I think that the key the key pieces as francesca mentioned is that like We are going to continue to see side chains in l ones We're going to continue to see ethereum execution layer consensus layer and shards And then focus on roll-ups here And and you know, what does this all look like is basically how do we provide data to users cheaply? How do we continue to scale? How do we serve a multi-chain world? I think that the ethereum roadmap has actually been smart in evolving to Not presume that it's the only l one that will ever exist that has smart contracts So I think that making all these things first-class citizens is kind of like 2025 like this long-term vision for ethereum is how do we Combine everything together as opposed to trying to segment the network And I think that that's You know done through a bunch of these different bridges that have been proven to be a little air prone up to this point But working on that and using zero knowledge proofs and other proof systems To basically tie everything together and use ethereum as this kind of settlement layer for this new vision, right Is is taking in all of the different blue boxes Which are doing variety of proofs a variety of mathematical calculations to ensure that the data either exists Is correct or hasn't been tampered with and then it sticks them on that execution layer in the state storage And then it communicates out to the rest of the network via so this pink box Cool any questions so far We have like a minute, but 50 seconds But I think yeah, we'll put some learning Resources that might be cool. I think team also speaking visually today for tomorrow tomorrow. Yeah tomorrow More on the merge tomorrow with some folks from the ethereum foundation speaking Yeah, we also did a bunch of interviews that have connect on on the merge and the next next steps with I think just in drake and team that was really helpful Any questions so far? I know there were a lot of link information I think this is something that you know, it's We can I can send it to you and uh, yeah or attach we can send directly I think hyperledger will also send them out, but we we can send these directly to you Yes Any other questions so far? We're ready to to go. I think we're literally the last talk Cool. Awesome. Thank you so much everybody


I have a construction update for you guys today. Boy, am I risking my drone's life I'm gonna have to start putting money aside to get a new drone because a couple of days ago I flew it in 60 kilometer hour gusts and today I flew it in 40 kilometer hour gusts really Risking at all, but nonetheless work is continuing at Canada's Wonderland So right here on the screen in front of me. You can see moose horn falls So Canada's Wonderland is currently doing the utility work on moose horn falls So right now they laid down a lot of the electrical You can see it it goes from the pump house to the main electrical unit and then it heads all the way over towards moose horn They're done laying down the electrical work So now they are pouring concrete and cement on top of it to cover it all up So that was really cool to see on screen But yeah, that's all in terms of moose horn You really don't get to understand and this is including me not you guys But like how much work goes into building a new attraction? So a lot of like, you know like a lot of utility work before they even start construction on the actual ride Over here at front gate very interesting They are really clearing house at front gate and you're gonna start seeing this over the next couple weeks So they now have an entirely large fence that surrounds the front gate area So you can no longer get close to it if you look really closely It's hard to see, you know a gray thing, but you can see it. It's there And they are clearing out the security booths and the security fencing No sign of the Canada's Wonderland logo coming down yet. If that logo comes down if that logo comes down I am ready to predict a full front gate run out But right now it looks like they are just doing under the Leviathan area But I am ready to make some pretty hardcore predictions on the front gate area as a whole I think I'm gonna save that for the podcast But I can already see what they're doing So I have a really good idea of what the front gate area is gonna look like now So I'm gonna drop a really good rendering and what exactly each of these things are So there is gonna be some new tech. I can confirm that really excited about that tech too There's a new mobile app launching for Canada's Wonderland any day now So expect that some of you should already be getting your notifications to reset your passwords To get ready for the new mobile app. So keep checking the app store for that update We will be getting that new app. So really excited about that over here. They're removing the Christmas lights off these trees Now I don't want to make a hardcore prediction because I'm not quite sure I can't fully confirm if Wonderland Takes down and re puts up all the Christmas lights every season I've never paid attention to that But from what I've been told they do not take the Christmas lights down and re put them up But I can't confirm that so take that with a grain of salt if that's not the case and they do not take them down Then I think I see where our new prestige seating area is gonna go I think it's gonna go in the old orbiter plot of land So over at Wild Beast a lot of you been asking is Wild Beast gonna get its reefer Well, I don't think there's retracking yet scheduled for Wild Beast because if you go back and look there was snow Covering the entire track and I'm scaling back over to Mindbuster to show you guys how we know which section of Mindbuster They're working on so Mindbuster is covered in snow. All of Wild Beast is covered in snow But this double down is Swept off it's cleared because that is that is because there's work going on it So I just wanted to show you guys that in detail So for those of you that were like well as Wild Beast getting retracking. Have you seen anything? Well, no from the drone. I can tell nothing's going on over there quite yet There is work going on inside the front gate building So on that drone you can see the garage doors open into the front gate building itself Where you would normally buy your tickets in season passes at front gate I predict that's probably where they're going to install some self-serve kiosks or completely are removing that technology to make the front gate Entrance a lot larger to allow a lot more guests in maybe add some self-serve kiosks to get in as well So that's what I'm hoping for again. No information yet Maybe I'll be able to get an answer out of Wonderland soon on that concrete Cement has been poured I keep using the both because I mixed them up and I've just given up concrete and cement has been poured On the front gate building the merch store and the queue lines to get through the security booths underneath Leviathan So that has been done. I thought that was really risky, but I guess with all the cold weather They wanted to get it done today so it can start curing So as you can see here, they're covering it because obviously there's not going to be much work going on This weekend they don't work on weekends, but there's not going to be much work going on when it's cold You can't really pour cement or concrete and negative 10 Or you can if you buy the more expensive stuff, but the stuff that Wonderland is going to want to use They're not going to do that over the Monday Tuesday Wednesday now when I fly my drone I could be mistaken, but that's my prediction. Anyways, that's it for a construction update today Thank you so much for watching. Hope you guys have an amazing weekend and stay tuned for more videos I have some really cool stuff lined up. Have a good one guys. Bye


All right, we'll just get started. I think David will get here in a few minutes. Let's just get started and hopefully you can see the screen I'm sharing. Here, let me paste it on the chat window too so I can all help you with the note taking here. Hi, everyone. Hey, Vitaly, how are you? Great, how are you? Good, good. OK, so just go ahead and get started. So we have a relatively short agenda for the last call of the year. It's amazing how quickly time sort of flew for 2019. So three topics. I mean, first is regarding the membership changes in the core team. I don't think Vinny's here on the call as of yet, but he announces departure from GitLab a couple of weeks ago on the Slack channel. Hey, David, how are you? Good, thanks. So we'll talk about that really quickly. And then a quick follow up on we had some good discussion on the Community Advisory Council. I think there are some updates that were made on the MR. David will give us a quick recap of what's happened since the call and what the next steps are. And I'll also talk about some of the community events in Q1 2020 leading up to Contribute. So those are the main topics. If there is anything else, please let me know. If you could add a topic towards the end. But so we can do that at the end. So let me quickly jump to the next slide. Yeah, unfortunately, Vinny, he's been on the core team since 2016. And I believe he joined GitLab as a team member in 2017. He's been here for a long time. And he's pursuing a different opportunity in a few weeks. And I had a quick discussion with him last week if he would have an opportunity to continue contributing to GitLab. And unfortunately, at least initially, that's not going to be the case. So he will not be able to, at least for the first few months, he's not going to be able to contribute to GitLab. So he will be standing down from the core team. So yeah, I don't think he's on yet. But I just wanted to, I'm sure, everybody has the same sentiments based on what I've seen on Slack messages. He's been an awesome contributor and a core team member. Definitely he'll definitely be missed. But hopefully he'll start re-engaging with the community in several months. And we'll hope to see him again soon. So what that means is that, I mean, so what we started to do almost two years ago now is to have, or about a year ago, is to have up to two GitLab team members in the core team. So we'll have one space that will be vacated. So we'll look into adding a new team member to the core team in the future. I mean, there's not necessarily any urgency in doing this. But this is something we'll look into doing in the next couple of months. So if you have any suggestions or ideas from the GitLab team members, I mean, you feel free to let me know. I mean, one of the things that I'd like to consider is to add somebody from underrepresented groups into the core team. I mean, one of the comments that I've heard in the past is that all the core team members, I mean, happen to be male. I mean, that wasn't designed that way, but that's how it turned out. So that's, I mean, in terms of gender and other areas that we want to have a well-represented, sort of well-rounded core team. So that's something that I definitely want to consider. If you have any, like, suggestions on people or thoughts on this, I mean, feel free to, I mean, bring them up in a Slack channel or reach out to me. But that's something that we'll look to do in the next couple of months. But let me just pause there and see if people have any comments or feedback that you want to discuss during the call. So unfortunately, neither Vinny or Remy were able to make the call today. But yeah, I think, yeah, David, you and I talked about this quickly like last week, but I'm not sure if you have anything else to add here. Yeah. I mean, I'd say if everyone has seen any contributor doing good work, that might be a good candidate. It'd be good to send a suggestion. I think we're still using service tests. So that might be a good way. Another thing might be as well to announce it somewhere like the company call within GitLab as well. And yeah, I'm explaining this proposal essentially to make sure that the new candidate, one of the, so one of the deciding factors as well of contributions would be to make sure that we create a more inclusive and diverse community as well. Right. Yeah, that's a good idea. I mean, there's certainly a lot of people within the GitLab team. I mean, people, both that have been around for a while and even somewhat recent that have been really good about working with community members. So I think we should have a lot of good candidates. But yeah, I mean, could probably open this up even within the company on the side channel might be a good idea. So any other thoughts? Oh, go ahead. Sorry. Maybe I'm right. Sorry. Maybe one place to look for is a mad request coaches and if they have any suggestions. Yeah. Since they collaborate more often with the community. Right. Yeah. OK. Any other suggestions or thoughts? We'll just move on to the next topic and the next slide and I'll turn things over to you, David. I made some slight tweaks from the slides from three weeks ago, but hopefully that reflects what's what's happened in the past few weeks. But I'll let you lead a discussion. That's right. Yeah, thanks for the updates. Essentially, it's a continuation of the discussion on the last call. There have been some changes, but I haven't been able to spend as much time as I wanted it on it. I think the bulk of the proposal is essentially done. We had discussion on the size and we tightened the definition of how often the team would meet. I think the only thing that's missing in there, unless there are other comments from the participants, is creating the process for nominating issues and MRs from the wider community. And this is something that I was thinking to keep simple, to perhaps create a group in the same way that we have the core team group and then add some documentation around the process and let people be the community advisory council to nominate something that's for discussion in public. So I think what I'll do is I'll add that process and I'll remove the working progress on the MRs request and then look for comments and further approval. And then in parallel, I'll start reaching out for initial members and start asking folks who might be interested in joining the initial incarnation of the council. But yeah, I was going to say, if you've got any comments, then feel free to add them to the MR or feel free to reach out to me directly as usual. Any thoughts, comments? We'll move to the next topic. So I wanted to talk about some of the community-related events that we're planning for, particularly in Q1. So one is not a big conference per se, but this is an initiative that we wanted to try out as one of my OKRs. It's what we call hackathon in a box. Obviously, the virtual hackathon that we've been having every quarter has been pretty successful. And wanted to replicate that so that people are able to create an event where it's create a fun environment for people to start contributing, especially for new contributors, when there are face-to-face events or need-ups. And I mean, Takria is on the call. Like he's been very good about this, and he's already done this in the past in Japan. But I've been talking to some of the heroes and a couple of meet-up organizers where they have a regular cadence for meet-ups and then creates an environment where people can get together and help each other and get new contributors involved in contributing to GitLab. So there's a link to a relevant epic there. So you'll see some of the things. There are mainly two things that I started working on in Q4. Like one is creating some introductory content. So you'll see links in the epic. One is just an overview presentation on here's how you contribute to various areas of GitLab, like including documentation, UX design, translation, and in addition to code. So it's a short deck. It's a variation of a slide deck that I use as a tutorial a couple of hackathons ago. So that's been refreshed. And then the other thing that I started working on with the GDK team is to create a series of videos for GDK. We had a GDK introduction video that was done by David Anton, like probably at the first hackathon, that was one of the most widely viewed videos on the hackathon channel. They had over 1,000 views when I checked about a month ago, which was good. But the GDK has evolved pretty significantly over the past few quarters. So there should be two videos there. If you go to that epic, let me just go there right now so you can see it. So there's a GDK playlist under the unfiltered channel. So we just recorded this several hours ago with Tiger Watson. He's one of the back end engineers, but also maintainer for GDK. So quick, if I made a video on how you set up a GDK, and Tong had a somewhat more advanced topic on using GDK for auto dev ops, that's probably more relevant for GitLab team members. But I think community members might find this interesting. But we want to build this library of videos. So there are probably a couple of other topics that I'm going to tap a few GitLab engineers on. Just do a quick video, like a five to 10 minute video session, so it's easy to consume. So those are sort of the two things content-wise that we started working on. And the other thing that we also want to offer, and Takuya can chime in here, because he's got a meetup scheduled on the 16th, like one day next week. So he's going to hopefully pilot some of this content. And then I also sent him some GitLab merchandise that he can give out.  So fun prizes that you can use at like a face-to-face meetups where people contribute and they get rewarded immediately. So I want to try that out at a couple of different venues over the next few months and put together sort of a hackathon in a box material that various event organizers can use. So I mean, Takuya's got an event next week, and then he's got another one in January. But if there are other like a meetups that you're typically involved in, like locally and in your countries, I mean, please let me know, I definitely would like to see if we can put something together for your event. We also try to do this for, right, the docs in Australia, but it was like a too short of a notice. Like a lot of the sponsorship and all that sort of came together so we couldn't like organize something like on-site in Sydney almost about a month ago. But if there are other events that we should probably like experiment this at, I mean, please let me know. So let me just leave it at that. And I mean, David, I don't know if you have anything to add here or anything I may have missed. Well, I mean, one thing is good, I wanted to say, good work with the last video, which is a case setup. I think it's great to have something like that that's under 10 minutes. As I say, I think that's much easier than for people to consume the longer ones. But still, we have the longer ones if people want to delve more into detail. I have a question on the playlist itself. Is there any reason why the initial GDK tutorial from TUN was not added in there? Is it because it's still there? Yeah, we can certainly add it in here. I mean, there's no reason why it can't be in there. I mean, I can certainly like add it. I assume there's no issue of doing this because this GDK channel existed in the unfiltered account, whereas the other recording was under the regular GitLab account. But I assume that's not an issue. I haven't tried it yet. But that's a good point. Let me see if I can at least add a link there and see if it works. One thing we can do is try to download a video and move it to the unfiltered channel where it comes to worse. OK, cool. Any other thoughts or suggestions? Do you expect the kind of contribution in Hakka in the books? I'm sorry, Takuya, can you repeat that, please? Do you expect some kind of contributors in this Hakka zone? You mean like contributors to attend these events? Or like? Yeah, and we can see many kinds of contributions, like having a talk or organizing meetups. But I think Hakka zone in the books can help us to have a code contribution. Right. Yeah. Yeah, I mean, so I think having talked to a few of the event, like a meetup organizer, because it'll depend on sort of the type of the meetup that you're running. So this sort of the hackathon activity that's targeted more towards code contributors should be, I mean, it'll be like one of the agenda topics in a longer meetup, right? I mean, some of the meetups from what I heard from some of the organizers, they sometimes run like a three to four hours. And it's possible that during the three to four hours, you'll carve out some time, like an hour, to just have a workshop working with the contributors. And then you can have other talks and discussions. For example, on DevOps or other aspects of GitLab. Or I mean, it's possible that somebody might want to just run an event that's just focused just on code contributors. So I think both of those options work.  But I think it's also OK if you have a decent amount of time allocated for the meetup to have this as just one of the topics that you'll have at the meetup. But I think it's up to the organizers. But is that answer your question, Takuya, or like? OK, I think. OK, cool, thanks. Ray, perhaps another comment. We haven't discussed this, but I'm seeing this on the same page. It might be worth perhaps thinking whether there's something that we might want to do at some of these events, either for thermo or scale or both. Having we've talked about having contributor workshops, so I think start to contribute, but perhaps with also a triad running a hackathon there with some prizes like that we could do live. I mean, FOSM might be a little difficult because it's a little bit more chaotic. And then we're not going to have a dedicated GitLab session. But I mean, for scale, I think that's definitely more under our control. Like if we will talk about this in a minute, if we're going to have a track that we're going to organize on our own, it's completely appropriate to have a carve out some time to run a workshop for contributors. Yeah, it's definitely an option for something like scale or for some of the other events like a GitLab might be sponsoring down the road. I mean, I didn't list it here because the events, I believe in Q2 in May, I believe GitLab is going to have a bigger presence of a right to docs in the US. So I mean, I've been talking to the technical writing team about running a workshop on focus on docs contributors. So opportunistically, I think we can definitely do something not just at meetups, but events like scale and write the docs. Right, so we'll move on to the other events that are on the slide. So FOSAM that's coming up, that's usually the first weekend of February. So I believe this time is like a February 1 and 2. And there's a relevant issue that you can take a look at where a number of discussions have already been happening around FOSAM. And then if you wanna join a Slack channel, like in Slack, there's a pound FOSAM channel, if you wanna join discussions there, it'll probably get more active like after the holidays as we get closer to the event. So we'll again have a stand during the entire conference. When I actually submitted this CFP, I actually requested Saturday only, but the feedback I got from the organizers that GitLab is a big open source project, so we should be there for the entire conference. So we'll have a stand for both Saturday and Sunday. And there are also a lot of dev rooms that happened at FOSAM and a number of GitLab team members and myself included have submitted talks for various dev rooms. I mean, John Coughlin and I submitted proposals for the community dev room, but I know there have been a CFP submitted for like a Golang dev room. And I believe Ben Kochi is also one of the organizers for one of the dev rooms. I believe it's like monitoring. I forget the exact term for it. So you probably see a lot of GitLab team members there in general. So if you are planning to like to come to the event in February, just, I mean, please let me know. We'll probably have a decent presence there anyways. And I believe that that room schedules will start to get announced like starting like this week or next week. So you'll see which talks have been accepted. So that's just a quick info on FOSAM. And yeah, and for, I think most people here probably know FOSAM always happens at the same like a university campus in Brussels. So that won't change there. The other event that might be new to a lot of the people, it's called Scale. Southern California Linux Expo, I think that's what Scale stands for. And David has more experience with this event than I do. I mean, this year was the first time I attended at least part of the Scale event. And it's very similar in type of people that attend like FOSAM. A lot of like open source enthusiasts, people that are passionate about open source like in general attend that event as well. And the Scale is already, I mean, as you can imagine from the name, it's always held in like the Los Angeles area in the March timeframe. So there's also a relevant issue there and as you can see in the second bullet, David and I have been talking to the organizers about sponsoring a half day track focus on GitLab, both on the community and our product side of things. And I think this is where we can sort of have a session focus on like attracting new contributors sort of run a workshop. I don't believe Ben's on the call yet, but we do have like a few community members that are in the Los Angeles area. If they can sort of participate and help out in sort of running that workshop, I think it'll be pretty effective. So, and also the Scale event this year, it's sort of in the same week the Git Merge event also happens in the Los Angeles area. So it's sort of dovetails like nice, like a Git Merge event dovetails nicely into the scale. And we, I mean, last year what happened with Git Merge is that it happened right before FOSM. So it's interesting like this year, they decided to do it in LA right before Scale. So one event sort of leads to another. So that's sort of, I mean, the two events that I just wanted to give you a heads up on. I mean, if you're like, if you're planning or interested in participating and or attending any of these events, I mean, please let me know. And I feel like I may have forgotten something either about on FOSM or Scale. Like, I mean, David, did I miss anything on either one of these or? No, I'm just trying to think of anything else. But yeah, I mean, let's say if anyone has good feedback on either of them things that we could do or things that we could do differently, then feel free to comment on those issues. Right. Yeah, and then I think David, you and I are both planning on attending both FOSM and Scale. So just an FYI. Cool. I think that's the end of the slides. Just want to see if people have any other topics that people want to discuss or anything I may have missed. Everybody's really quiet today. Ray? Yeah. Regarding the community events, I think it's worth bringing this up a few months earlier to the court meeting so that we can plan any calls, proposals we can submit or something because the CFPs are closed for all of these events at the moment. Yeah, that's a good point. Yeah, yeah, I mean, I think for, especially for both FOSM and Scale, I probably should have given people the heads up about, like especially for the CFP a few months ago. That's a good point. I mean, on Scale, since we can sort of schedule our own track, I mean, if there's something, George, that you're interested in maybe talking about, I mean, let me know. Then we can definitely see what we can do there because that's sort of, we have the time in the room and we can, I mean, within reason, we can sort of schedule it the way we want it that half day to go. So let me know. But yeah, next time, it's probably worth talking about both of these events, like right after people come back from the summer holidays because I think that's when typically FOSM starts communicating about the debt rooms and proposals. That's a good point. Yeah, and I think I talked to David about this on, especially on Scale, if this half day track goes well, I mean, who knows, like we might decide to expand this to a full day next year. We weren't quite sure if it will have a full day worth of content, like just on, because since this is sort of the first time we're trying this, I mean, there are other communities like OpenSUSE and Ubuntu, I mean, they've been, had presence at Scale for a long time, so they typically have like a full day event. But we'll see how the first one goes this time around and then if it's successful, there's no reason why we can't expand it the next year and extend it to a full day next year. Any other topics or questions? All right, I guess that's a wrap. I mean, this is, like I said, it's the last call of the year, so I assume a lot of folks will be taking some time off for the holidays, so do enjoy the holidays and look forward to seeing you and talking to you all in the new year. Cool. All right, have a good day. I'll see you guys later. Cheers.