This just came down. Troy Tulawitski, no real surprise, announced his retirement. He said, I wanted to take this opportunity to announce my retirement as a Major League Baseball player. For as long as I can remember, my dream was to compete at the highest level as a Major League Baseball player, to wear a big league uniform, and to play hard for my teammates and the fans. I will forever be grateful for every day that I've had to live out my dream. It's been an absolute honor. So he's been injury plagued. Yankees took a flyer. It was like $500,000, thinking that maybe he could be the guy to replace Dee Dee while Dee Dee was out. Didn't work out. Another one of those injuries that just didn't seem to affect the Yankees at all. But still, 13 years, really good player. And I know a lot of those numbers might be exaggerated because of Colorado. But you saw he did well in Toronto. It's just super human being, good teammate, and his career is over today. Seventh overall pick in the 2005 draft I'm just looking through. I got into the computer, by the way. I'm now able to peruse all this stuff. You know what I find interesting? This is probably taking a place that is only interesting to me. But I can't picture in my life being 34 years old and being done with my career. Like he'll be able to go do whatever he wants to do now. But you and I both had an ambition in our lives, which was to be in this industry. You and I are the same age, and we came up at the same time. Sort of the explosion of popular sports media sport. You and I both grew up a sports phone and all that kind of stuff. And this is really the only thing I ever wanted to do. And I'm now 51, almost 52 years old. And I feel like I'm just getting started. I feel like I'm better now than I ever was before. And I'm anticipating being better five years from now. I can't imagine. Oh, look, he's got all the money in the world and no one needs to feel sorry for him. But to be 34 years old and be like, okay, now what am I going to do with the rest of my life is, it's got to be a really interesting situation to be in. Again, I'm not asking people to feel sorry for him. Most people would probably trade places with him to say, okay, I'd be 34 and I'll have tens of millions of dollars in the bank. Yes, all of us would love that. But it would be interesting for those of us who are passionate about what we do and to be a major league baseball player, you have to have been incredibly passionate to have made it to that point, to just wake up one day and say, okay, I've been a baseball player all my life. Now I'm 34, what am I now? What do I do next? I think that's a very interesting, that has to be a very complicated thing to feel. Sports athletes are kind of doing it in reverse. Like you just said, you feel like you're in your groove right now. You're 52 years old, I'm 51. I feel like I'm at the top of the world. I work hard to get to this point. I'm in my groove. I feel like I'm in our prime. This is our prime. We're in our prime. And it took a long time to get there. When I was 34, at the end of his career, when I was 34, I was, I still was trying to make my way. I wasn't nearly as polished as I am now. And I knew that and I had to work on it. Some guys are on a different track than others. You know, people like Ian Eagle and Bob Bushusin, they were born with a microphone in their hand. They seemed like they were doing games as fetuses, right? They were so young. But for the most part is that you get your break, you work hard and then you get to a point, like when you get to your fifties, or sometimes acting is the same way. You feel like this is, I finally got here. It works the opposite as a player. Like there is that little moment where you're rookie and you're kind of figuring it out. But then every year, you kind of slip a little bit and a little bit and then eventually your career is over. It's just, as Michael Kaye has always said, you die two deaths when you're an athlete. You die, he's no longer a Major League Baseball player and that in kind of way is a death.  We could be radio guys and TV guys forever. You know, as long as they keep giving us a job, we can do it in like into our 70s and 80s. You look at guys like Marv Albert and Doc Emmerich and Sam Rosen, you know, the list goes on and on of people that are doing it well into their 70s and still killing it. You know, and that's not a luxury that an athlete has.


Pumpkins are ideally composted to make the soil for youthants to grow. Pumpkins cannot go in the yard because pumpkins are food. They're heavy and water filled. If pumpkins can't milk, contribute to green health.


A few months ago I made a video about Fedora Kino White, and if you don't know what Kino White is, basically it is the KDE version of Fedora Silver Blue, which is the immutable version of Fedora. Now there's a whole discussion to be had about immutable file systems and immutable distros, and we will have that conversation in a video one day soon, but that is not the video that I want to make today. Instead, what I want to make a video on is Kino White itself. So when I made that video a few months ago, my intention was to do a long term review like I have done many times before. I would use a distro for a significant amount of time and then make a video about it. And I followed through with most of that plan. I used Kino White for three months straight. And while I wouldn't say it was my daily driver, I logged into it pretty much every single day and messed around with it. And at the end of the three months, it was time to make my video on it. And the thing is, is that I had such a horrible experience with Fedora Kino White, I couldn't make the video. It was just going to be a very bad video. I would have spent the entire time bashing it and saying how this thing is not ready. It's basically a beta. Don't use this thing. It's not good. And I didn't want to do that. I was so frustrated with it at the time those three months was over. I just couldn't fathom even talking about it for very long. It's just that buggy. So I didn't make the video. I took another month away from it, or a couple of weeks, however long it was, just to kind of push myself away from the mindset of how bad it was. And also to uninstall it because I wanted it off my computer. I no longer have it installed on my computer, which is why the stuff you'll see today is in the b-roll. But I wanted to just kind of take a step back and let my emotions calm down. So I didn't spend the entire video kind of saying how terrible this thing was. I wanted to kind of remember the good times, if you will. So that's what today's video is about. I want to talk about my time with Fedora Kinawight.  I have no real plan for this. So if I repeat myself often, I apologize for that. So just kind of prepare for a ramble, if you will, a good old fashioned ramble. Let's first talk about what Kinawight is. Now like I said, I'm not going to get too much into detail about what immutable means and how it works when it comes to a Linux distribution. But just broad strokes, immutable basically means that there are layers to your distribution. The underlying layer where all the Linux-y stuff happens, the root file system, all that stuff, is in a vault, basically, that you can't touch, okay? None of that stuff is anything that you're ever going to have access to. And everything that sits on top of that in another layer is the home directory and the stuff that is user-facing. That stuff you can edit and install applications on top of and all that stuff, right? And the benefits of this, as simplistic as that explanation is, is that when someone deploys Kinawight or Silverblue, which is the GNOME version of Fedora that basically they're siblings, when somebody deploys these immutable distros, they know that every single machine that is running those has the exact same underlying Linux on their system. So every part of that underlying system is going to be exactly the same from machine to machine to machine. The idea is that it's going to create stability in Linux, and it also increases security because there's nothing that can touch that root file system. So as you might expect, it's going to be a little bit different from the Linux that you or I probably use in that there is no ability there to touch that root file system. So if you want to use i3 on Kinawight, you can't really do it, at least not in the traditional way. You'd have to build it from the ground up and kind of create your own distro. Kinawight is different. It feels like you're running a different type of operating system, especially, and this is the big point here, is if you are used to having access to all that stuff.  So for example, let's just say you wanted to edit your pacman.com file if you're on Arch, or I guess in this case you'd be editing your DNF.com file, right? And there are many reasons why you'd want to do this. One of those is enabling parallel downloads with DNF. Now Kinawight doesn't use DNF outside of Toolbox, but let's just say in this example you wanted to do that, whatever. If you wanted to edit that configuration file, you can do it because Etsy's in the root file system, you don't have access to it. You can see it, but you can't edit it, right? And that's where it feels different. You don't have access to a good portion of your file system. It's just kind of unavailable to you. So the broad strokes benefits of this aren't for the tinkers out there amongst us. It's more for the developers who are developing for this kind of situation, people who use containers and stuff like that. And also for people who are going to deploy this on a lot of systems. And by having every single one of them have basically the same image on them, they can easily update. They can move from different versions easily enough. And it just makes it easier in that way for us regular users, the immutable part of this kind of just makes it feel weird, right? You don't really care if you're just a normal user, because if you just install a whole bunch of stuff from Flatpak, you're probably not even going to notice that this thing is different, right? You're just going to use your applications. It's when you start installing stuff from RPM Aus Tree, which is the method that Keena White and Silver Blue use to install applications is that's when you're going to notice things a little bit differently because every time you install something, you have to reboot your computer afterwards because it's made a change to a layer that only gets applied once you've done a reboot. And the thing is, is that if you've ever used Windows before, that's awfully familiar, right? It's whenever you install something on Windows, not always, but anything that has to do with editing the registry or something like that, you have to do a reboot. And to have that happen on a Linux machine just feels kind of icky, right? It's not a big deal. It's not a deal breaker, but it feels really, really weird. So that's kind of the overarching thing that Keena White is. It's very confusing for most normal users. And even I still don't have my mind completely wrapped around it. And I'm sure that explanation did nothing to help you out whatsoever in terms of actually understanding what this thing is. I will try to do better when I talk about immutable file systems in another video, maybe actually write some things down and stuff like that.  So let's talk about the actual distros. So outside of immutable stuff, the biggest takeaway I have from Keena White itself is that it's buggy. Like I said at the beginning, the experience I had with Keena White was God awful.  It's only been around for maybe a couple of years. Second of all, KDE is notoriously, I guess I shouldn't say notoriously, but it definitely has some issues when it comes to doing certain things. It's never been the most stable desktop environment. So some of the things that I experienced were definitely KDE's fault. But I think the biggest problem I had was that it feels like KDE and the immutable aspect of Fedora, which is the main thing of this distro, it just feels like they don't go together. There are things that KDE expects to be able to do that it can't do for whatever reason. So things like installing themes. I'm not exactly sure why they're installing KDE themes in the root part of the file system, but apparently they are.  Like it's just an error, right? You can't you can't download that thing. It just does not work. Now there are workarounds to this. There are things that you can do. You can install, you can download the theme manually and then put it in dot local, which you have perfect access to. It works okay, but the application of those themes doesn't work all that great. There are things missing. There's icons that don't show up. It's a mess, right? And like I said, some of this is KDE's problem. Some of it feels like it's just kind of two things that aren't really meant to be together at least quite yet. It's a weird experience. Now, obviously that's the thing that I noticed first, because the first thing I do when I install KDE desktop is that I braced it because, of course, I do, I want to change it from the default thing. And to do that, you have to install themes and icons and change colors and get Kovantem up and running and all this stuff. And that I wasn't able to do that ever in three months, just kind of completely turned me away from Keena White before I even got into some of the other things that I had problems with. So some of my experience past that first few weeks probably has to do with my disinterest in Keena White because of the lack of ability to theme the damn thing. But I did use it and I used it for I kept it on my machine for three months and I used it often. And at the end of the day, the thing that I noticed the most outside of the theming part is that I was getting errors after errors of random things crashing K when crashed several times. Now, I'm not sure if that's the Keena White thing or KD thing. There's been a lot of talk from me recently about how buggy KDE is and I hate doing that because I love KD so much, but it feels like there's a lot of bugs. And a lot of my experience with Keena White is the reason why I've been saying that a lot because, like I said, K when was crashed frequently and I was having problems with the settings application crashed like over and over again in this in Keena White and I'm not sure what was going on there. And somebody's going to ask, well, did you file bug reports? I've every I did file the bug reports when that pop-up came up. Like, you know, when something crashes, sometimes KDE will pop up with like a bug reporter things. I went through that and did that whenever that popped up. But it doesn't pop up all the time. Thank goodness, because I would start multiple times a day. But the thing is that I did file those when that pop-up came up. Other than that, I didn't put any effort into it. I probably should have. But the point is, is that I was getting crashes and weird errors and stuff like that. I think I even took a screenshot of one of the errors that I might put up here on screen here somewhere. It's just, it was just not a good experience. It was absolutely kind of horrid, to be honest with you. And the thing is, is that I expected better, right? Silver blue has been around for quite a while now. And I expected Keena White to be at least mostly as polished as silver blue seems to be, but it's not. Now, I don't know whether or not this is because it's a fairly new product is much newer than silver blue, or it's because the KDE and immutable aspect of it don't really go together. I don't know about that either. I'm not really sure what it is about Keena White. It just made it really bad. Now, it's also possible, and I should put this out there, that it's just a me problem.  When it comes to Linux, it happens. Sometimes I just don't know what I'm doing. So it's a hundred percent possible. There were solutions to the things that I was experiencing that I didn't actually find. So some of the problems that came up, I did Google and try to find a solution to because I mean, I did use this for an extended period of time. Some of them I didn't. Whenever, like when K-Wing crashed, I almost universally just stopped using Keena White for the day and moved back to regular Fedora or whatever I was using. Right. So there are some of the bigger problems where I was just like, I'm done with this for the day. I'm going to move on and actually do some other work. Some of it, like I said, I did Google and try to find work around. So like the themes aspect, I did find a work around for that. It didn't work all that well, but it worked somewhat, I suppose. So there is that aspect of it that it just could possibly be me and my hardware, like maybe my hardware doesn't like the mutable aspect of Linux and doesn't run it very well. Who knows, it's possible. So I guess I should talk a little bit about the good experiences that I had. So I think that my three months with Keena White really led to me to believe that Flatpak is probably the best package manager out there for Linux, not necessarily should go back to that and just say maybe not the best, but definitely the one that most people should use. You shouldn't use Snap. You shouldn't use app images. You should use Flatpak. I think my time with Keena White is the reason why I now think that Flatpak is kind of the main thing. I really had a good experience with downloading Flatpaks on Keena White and using them. They all worked really, really well. And if Fedora can get to the point where Flathub is enabled by default, it's going to be awesome because you're going to have this gigantic access to a whole bunch of software that you wouldn't have access to normally without enabling RPM Fusion or building a whole bunch of stuff yourself, whatever happens to be. Right. And it was just a really good experience. It's not an experience I ever had when I was using like Ubuntu and Snaps. It just that never felt like a really good experience. This Flathub and Flatpak integration in Keena White is really good. And I think that the reason why I thought it was really good is because you're kind of forced to use it. Right. That's the main way of installing software. You're not supposed to use RPM Ausstree to install anything. You're supposed to use as many Flatpaks as you possibly can. And because of that, I used a lot of them. And that has led me to use a ton of Flatpaks on my main install of Fedora. I have like 30 of them installed now. It's nuts. So my experience with Flatpak and Flathub on Keena White was really good. I didn't mind the RPM Ausstree stuff. I know I didn't do a very good job of explaining that earlier, but I didn't mind having to install a few things via that and then reboot my computer. It felt weird, but I didn't mind doing it. And I liked that the ability is there to do stuff against it. If you want to install like BTOP or something like that, BTOP doesn't have a Flatpak version. So you have to install that from the terminal. In order to do that, you use RPM Ausstree. Just think of RPM Ausstree as like DNF, but for immutable file systems. I suppose that's probably the simplest way of explaining it. So the Flatpak and Flathub thing is probably the most positive thing that I had to say about Keena White itself. Other than that, I don't have a lot of good stuff to say. Keena White's not ready. Now the question then becomes, is Silverblue kind of the same? And I don't know. I haven't tried to see Silverblue yet. I kind of want to put some space between me and Keena White before I give Silverblue a chance because I don't want it to taint. I don't want my experience with with Keena White to taint my experience with Silverblue. So I'm going to probably put that off a little bit. But eventually I will do a Silverblue long term review. If you are interested in that, make sure you hit the subscribe button so you don't miss it.  So at the end of the day, just kind of bottom line. Keena White's either not ready or not good. Either way, you want to look at it. I don't really care which way you look at it. I'm glad that it's off my system. I'm even now a few weeks after I uninstalled it, I'm quite happy that I never have to see it on my system again. And I say that never, maybe in a couple of years, I will have forgotten how bad of an experience it was and try it out again. Maybe it'll be better. But as of right now, I'm quite happy that I'm not using it. So that's my experience with Keena White. If you have thoughts on Keena White or any of this stuff, you can leave those in the comment section below. You can follow me on Twitter at Linuxcast. You can follow me on Mastodon or Odyssey. Those links will be in the video description. You can support me on Patreon at patreon.com slash Linuxcast, just like all of these fine people. Thanks to everybody who does support me on Patreon and YouTube. You guys are all amazing people. I really, truly do appreciate your support so very, very much. So thank you for that. If you want to support me on Patreon and support me for a year in advance, you will save 10%. So head on over there and do that if you are able or interested. So thank you for watching. Thanks for watching. I'll see you next time.


the IBM blockchain team. And he's the lead architect for the IBM Blockchain Platform. And he leads the user interface team that builds on the IBM Blockchain Protocol Console and won a prestigious Red Dot Design Award. And he's been a part of IBM for over 20 years now. And he's worked on many products as a UI architect. So at this point, I'm gonna go turn it over to Varad and let him go through his presentation. But I do wanna let everyone know that if you have any questions while we're moving through the presentation, feel free to post them in the chat on Zoom here and we'll address them. And then we'll also be posting relevant links as we move through the presentation so you can go in and engage with the community. And one thing that I always like to really promote is this is a great way to learn about projects, but we're always looking for additional contributors and maintainers. And if you're interested in really contributing to hyperledger fabric or the operations console, definitely feel free to follow up and engage with us and we'll be glad to get you engaged. So at this point, Varad, I'm gonna turn it over to you and let's go through your presentation. Perfect, cool. Thanks, John and David, I appreciate the intros and the efforts that you guys go through to set this up. So today, we're gonna talk about managing orders that don't have system channel. So, and then it'll have a brief intro and then followed by a demo. So let's get right to it. All right, so again, we're gonna talk about two different things today, right? I mean, two sets, right? So one is what is the benefit of the new fabric architecture? So fabric introduced, I believe in 2.4, the channel participation API and that removed the need for system channel. So we'll touch on the benefits of this new architecture and then we'll have a short demo after that to again show the new functionality that the console implemented to support what fabric did, right? And then we will open it up for Q and A and again, post questions like John said, right? Then as we go along. So the first thing is again, what is the channel participation API and what is the benefit, right? So if you look at the picture on the left side, right? With system channel, this is the legacy approach of managing orders. So we had the, again, fabric had the concept of system channel where it needed to know all the ordering service organizations and nodes that are part of the quote unquote sort of cluster, right? So in this picture, I'm showing a ordering cluster with five different nodes, right? That could belong to different organizations. And if you created a channel, right? Say app channel one with one, two, and three nodes, right? From again, different, the recording stopped it says, is that, should I? The live stream's going. We've got the recording on the live stream. Okay. So again, app channel one, so one, two, and three are the nodes on it. However, like when you create the channel and manage it, system channel knows about different channels that are being created and managed, right? So in this picture again, right? So let's say, I'm an organization that just needs to, as one, one, two, and three, however, if since say organization five is in the system channel, if organization five with node five is quoting the system channel, they know that that is app channel one in the system, right? So that's one of the gaps that Fabric tries to address with removing system channel. So on the right, you see that without system channel. Again, in this picture, that is of course, no system channel. And with the same set of five different nodes in the system, if I'm creating app channel one, nobody but the node organizations from nodes one, two, and three are the only ones that know what this particular channel, right? So that's one of the big benefits. It's a distributed, truly distributed architecture where there is no single kind of entity system channel in sort that knows and manages and needs that architecture, right? So that's the big benefit. So what other things, right? Again, no consortium, of course, the system channel had the concept of consortium which encompassed all the different organizations that are part of the consortium. So again, that's gone. So again, you need to think of the new architecture much like peers joining a channel, the orders are joining a channel. Like if you have that mindset, I think everything falls into play like when you, you know, the new architecture, right? It's not very complicated again, you know? So there is no consortium, nobody's managing system channel. And there is simple node creation. That's one of the things that fabric advertises as a big benefit, which I agree. So when you create a new node, right? New order, previously you need to go through this entire process, right? Where you need to create a node, get the, you know, the, you know, the TLSers, add that as, you know, into the system channel, right? You know, as the concentrers and all that, right? So, and then you need to start the new node with the new genesis which contains this node as a concenter. So it's that convoluted process that's gone. Now you just create a new node just like any other, like, you know, here you create an order with its own identity and then you can join a channel to that particular order, right? So again, that simplifies quite a bit. And then increased privacy, I briefly touched on it, right? So again, since there is no system channel, then there is nobody, not everybody in the quote-unquote consortium knows about all the channels that are being created. Again, that is, you know, that's one of the big benefits. Scalability is the other thing that, you know, the fabric talks about, right, as a benefit. Again, if you have a lot of different nodes that are in the system channel, when the order comes up, it needs to check all the other orders.  So that kind of slows things down. So, you know, the new architecture helps with, again, scalability, right? So actually let me quickly show the page where fabric talks about the benefit.  Again, you know, you can read through more of it, you know, from the fabric page, you know, there are some additional benefits that are being described, right? So, again, let me go back. And then there are new APIs, right? So the new, you know, approach, right, to the channel participation API has, you know, they added new three new APIs, right? Again, there is one that joins the channel to the orderer and now you can list all the channels on a particular orderer and then you can also remove a channel from the orderer. So all these APIs use TLS certificate on the orderer, right? So again, you need to remember that this is slightly, it is different than the general ordering service admin certificates, these are TLS certificates that come from the CA, right? Any, you know, TLS that comes from the CA. And again, just to reference, right, you know, the OAS and admin APIs are listed here in the fabric page, join list and remove all the three different operations and what console does, this is the main part we wanna cover, so fabric has these features. This has nothing to do with operations console. What operations console did is to support this architecture where there is no system channel and we leveraged these APIs. So the OAS and admin APIs are basically REST APIs, right? That are protected governed by again, these TLS certificates. So we will see how console is able to simplify this process without having to go to command line to do these operations. How can you do that from the console? That's the thing we are going to see and talk about. Any questions so far? Yeah, Rod, I think there's a couple of good questions here. So basically it looks like they're interested in, you know, how version two four is gonna be backwards compatible with version two two of fabric and so maybe you can talk a little bit about that type of backward compatibility. Okay, so that's a good question, right? So you can go to two four and still continue to operate with system channel, right? That's not like a required thing as part of two four. So again, you know, if you don't make any changes, everything will continue. You can start two dot four in the system channel as mode that are flags that you pass, you know, it's documented in, you know, in the fabric pages and IBM, you know, has operators, right? When you integrate operators, by the way, that's a plug for future talk. So IBM also open source operator, right? That is fabric operator if you look up that allow you to create nodes with again, two dot two, two dot four, it allows you to migrate from two dot two to two dot four with the right images, right? It runs on Kubernetes, you know, and all that, right? So IBM does support, you know, having a flow where you start with two dot two, you have system channel and it shows you the process to move to two dot four, you know, without system channel, right? So it is possible, but fabric itself is again backward compatible with system channel, right? And did I answer the question? I think so, I guess the corner question to that, I presume that let's just say maybe two that six or a later version of fabric then probably the system channel support will be dropped, right? I would think so at some point, like three dot two or something, I wouldn't expect them to drop support that drastically in a dot release. I think it's more like, you know, a big release would drop support, I would think, but there's no plan I don't think yet on when the system channel will be dropped. Got it, and I don't know if this is the appropriate time to go to the next question, but my uncle and I had a question around the migration of data. Migration of data? Yeah, so that's a good question, right? Because this does not change the data. Nothing changes from channel, nothing changes from the data. If you have an application channel, so the migration code and code is only removing system channel. So everything is managed independently by the orders. So zero things change in the channel. They continue to operate the same way. The peer join, nothing changed from the peer join. So none of that change, which is great, right? So it's only the fact that system channel got removed and now you have to join the channel to individual orders, the process change. Okay, so you can join the orders to the channels and then you can get rid of your blocks in the system channel if you want it. So there is no system channel, again, that's gone, right? So you don't rely on system channel to add a new consortium member.  Understood, thank you. Yeah, that's a good question, though, yep. And the other one, I'm gonna have Sonny come off and ask his question, but it looks like he's got a question about privacy. So Sonny, do you wanna just ask your question as well? Yeah, so originally blockchain was created for no third-party entities and allegedly it was considered private where no one could control it or get into it. But then now I'm hearing that it's on a public ledger and now everybody could see what you're doing. No, it's not entirely true. So it's not like everybody, right? So the way it works is again, right? Are you talking about legacy, like where people can see, you know, is that what you're talking about or the new approach? What is the concern, I guess, from public versus private? So I guess it's a system, where the blocks and everybody is able to see what blocks are being made in the community contributing and decoding. Does that make sense? Not entirely true, right? Because the blocks with the new are old, right?  Only the people in the channel that are authorized to see are the only ones that can query the blocks. Nobody else, right? Okay. If you have a channel and say the channel has three members, right, in organization one, two, and three, you define, like when you create a channel, you define these are the members of the channel and these are the right, they're admin's readers, right, you tell it. And only those operations are allowed for members from that, you know, role if you go, right? So if you say org one is only a reader, he's not even allowed to write, if organization two is using its certificates to query the blocks, they can only read, they can't do anything else, right? And if you don't have anything, nobody can query, right? Other than these three organizations that you define. Does it help? I mean, I don't think it's, unless I missed a point that you're trying to make. No, that makes sense. I appreciate that. Thank you for clarifying that for me. Yep. Anything else, guys, before we move? No, I think that covered pretty much the outstanding questions, but great job on addressing those and let's go back to your presentation. Okay. So the next one I wanna mention is the concept of Concentre, right? So Concentre Followers. So Patrick also introduced the, again, Concentre was already there, right? So it's basically you're saying these are the two nodes or not two, three or five, right? Generally is what we recommend for consensus. So these are the three nodes that are Concentres on the channel. And now there is a concept of Followers, right? So within the channel, you tell it, right? Organization one and two are the admins of the organizations that are contributing orders to this particular application channel, right? One and two. And as long as I have the certificates, right? I can use any of my orders to just follow. They are not Concentres, right? They are simply following meaning they're simply pulling blocks replicating so they are available. One of the reasons I think, you know, that this helps is, right? If you know previously, right? Let's say you have a channel with millions of blocks, right? So when you add a new node to the channel, they are like, you know, members of the channel, right? Or they are Concentre right away. And if it needs to replicate all the blocks, it takes a large amount of time during which, you know, that are members that are clients that keep trying and, you know, it can potentially fail. Like, you know, this is still coming up. They are not part of Concentre. What the new approach does is you simply, again, start as a follow. You simply say like, you know, if you look at the previous picture, like I showed on the right side, ordering so is one, two, or three are like Concentres, like that's how the application channel has the definition. And you simply voice an underscore F is joining the channel, but they are not Concentre. Again, what that does is once the synchronization is complete, meaning like, let's say you have 20 million blocks or whatever, right? You know, they pulled, they are up to date. Now you can simply say, hey, this node is now a Concentre. You can simply add it and it's like instantaneous almost, right?  So that's the benefit of having a Concentre, you know, and follower architecture. You can read a little bit more on fabric itself, but from the console perspective, we do show allow people to be follow, allow nodes, I should say, to be followers. And we show like which nodes are followers, which are Concentres on the channel from the console to make it easier to manage it. That's basically the point I wanna make for the console side of things. So with that said, let's go to the demo. So I have set up locally, right?  So on the IBM blockchain platform, I created some nodes and I imported them, but you can create them using the open source fabric console, not console fabric operator that's available. Like again, we should have a future session on it, but however you create it, you can simply import them into the console. Again, I have three different CAs, right? You know, two organizations for orders. So that way we can see how the multi-node setup works. So again, just to reference these are the things we are going to see as part of the demo, right? We will see a migration scenario from, you know, with the system channel, how do you go into a, you know, two, four system without system channel that covers migration. And then how do you create a channel with the new approach and how do you join, remove, and how do you see the consent or follower of sorts, right? That's what we will see. So again, I imported two different, or created and imported two different orders. So order one, in this case, you can see is with system channel, you can see from the console what type of order you have. One thing you do need to do right after you import, I shouldn't have done that, which is you should create a certificate of type TLS certificate. So let me actually do this. So that way, you know, people don't get tripped up when they set this up. Let me remove that TLS certificate from the wallet that way you can see how it looks like without. So I'll start first, right? So now if you go to the nodes and then say, I go into order one, you can see, you cannot see this channel listed, right? So meaning it does not have the appropriate TLS certificate. So if I go to the order one CA and then say I want to just pick any, you know, any ID, I don't have to pick admin, right? In this case, I'm just gonna pick order, and roll identity, and then I type in the password. What I do need to do is to generate a certificate of type TLS certificate, and then it should generate the certificate, then I name it order one TLS. So now I have a certificate in the wallet, right? If you see it, order one TLS certificate, and if I go to the nodes, and then roll down into order one, you can see that it is able to list the system channel or any other channel on that node, right? So the bottom section, the ordering admins and all that, those are of course relevant only for the legacy approach. So just, you know, I'll add one just to show everything continues to work. Again, this goes back to the question of migration. So in this case, I have a two-four system that is operating with system channel, you know, and it has like application channels, you know, everything operates normally. The only thing you see in addition now is that we are listing the system channel and any other channels using the, you know, the new API that Fabric provides, right? So what you do for migration perspective is again, two-step process is what Fabric recommends. So the first step is you need to get the system channel into maintenance mode so that accidentally nobody's creating channels during this migration process. You know, if you have multiple nodes within the cluster, you know, you don't want like accidentally people becoming, it's just confusion. So they highly recommend that you flip the channel into maintenance mode system channel. So no new channel creation or update is happening during the space. So within console, we added a new option that sends the system channel into maintenance mode. You just click on the gear and then you say go into maintenance and then it shows the current state, which is, you know, it's not in maintenance mode.  And I say update, that's important, right? So now the channel is in maintenance mode, right? So again, no new channels. All you do is just click on this delete button and then you paste to the channel name for confirmation. In this case, system channel is this particular one to system chain ID, enjoy, that's it, right? Now you are able to manage the node without system channel. And in this particular case, I should have, you know, if I had any channels ahead of time, like application channels, you will see them in this list. But since I didn't have any channels, it's a brand new system, you don't see any channels, but that's basically the migration. So put it in maintenance, delete the system channel. Any questions so far? I don't, you know, it's fairly straightforward, that step. Yeah, there are some questions coming through. So my neck, you wanna ask your question directly or would you like me to go ahead and ask it? I think it's a great question. He was asking about the migration demo, being on the same version as, or would it be different? So I don't know, do you have access to the chat there? You can then just take a look at his question. Okay, let me see. Migration is on the same version or the version would also be different. So if I'm understanding the question, are the nodes need to be in the same version if you have multiple ordering nodes? The answer is as long as it's a 2.4 system, it shouldn't work. The new channel participation API can only work in 2.4 system. So if you have a cluster, you know, the expectation is all of the nodes under the cluster need to move to 2.4. That's the first requirement. The second one is you need to enable the channel participation API. Those are two different steps that Fabric recommends. And in this particular case where I am removing system channel, I set up a 2.4 system with system channel on IVP. So let me just quickly show that screen. Just so you guys know, like with an IVP, how the options show up. So this is IVP on cloud. And if I create a new ordering service, I can create a new one. And I get an option to say, do I want to create with or without system channel? So it's an option. So again, did I answer the question? You need to have the same version or at 2.4 and higher and channel participation API enabled for the migration to work. When you create a new app channel in 2.4, which ones have to join first? The orderer or the orders or the peers already doesn't matter? Generally the orders are the ones that need to join and then the peers because basically you're saying, hey, orderer, join these channels. I could have like three different nodes or whatever. All those three nodes individually you're joining it. And then you're saying peer join this. As long as there is consensus, the peer should be able to join and operate as normal. But you need to, let's say, this is the case you need to consider, right? Let's say you have three nodes in the consenter and you need to join one at a time per se. And let's say you joined the first node, you haven't joined the other two nodes, you don't have consensus yet, right? So there is no point in joining a peer at that point. So you would want all the nodes to join, get consensus and then join the peer. That's ideal. The reason I ask that because an app channel that comes from 2.2 only has peers joined to it, right? So then in that case, you would have to join the orders after the peers would have joined already. Right, so you could have, let's say you have a single node, right? Orderer, you joined the peer, everything is happy. And now you need to add additional orders as consenters. Then of course, you would do it on the order and the peer would automatically know that the channel gets replicated and know that information. Sounds good. Yeah. Okay. And I guess my other question is, did he answer your earlier question or is this the right time to ask that question? Go ahead, ask the question.  The question was about configurations. So my understanding that the configurations, for example, endorsements of things that nature gets stored as blocks on the network, as blocks on the network. I thought they were on the system channel, but are they in the system channel or? They were stored in system channel. That's why it was a problem in terms of organizations within that able to see the changes coming in. So that configuration option, those are like not like applicable anymore because now you are working with the block that is stored like in console or like you stored it somewhere and then when you join the order, you give the order and say join this application channel. So you need to have all of, one of the nodes up and running to make these changes, but you're not, you're changing the channel within the scope of the application channel within the set of order or symptom centers and that. So there is no system channel in this case, right? So everything is managed with it by these orders that are in centers within the channel. Those configuration changes. I guess a really quick question on that. So when you go to two, four, do you have any configuration blocks on the system channel that need to be migrated to the app channels? No, so again, that the configuration changes are, you're not going back to any configuration. You basically the newest configuration that you have on the channel continues to live, right? So basically, there is no way to like say, like, hey, I wanna see what the configuration was like block 15, like two years ago, right? You're not doing that in this particular case, right? It's only the latest block that's persisted into that channel. Sounds good, thank you. Yeah, good question though, yeah. Okay, we got one other question that we can address and then you can continue on is from Naimra and they wanna know, is there any impact to the processing speed for the network if they have a system channel or if there's no system channel? I, in a normal operation kind of scenario where you are pushing block, I don't believe it affects the performance. It affects the performance when you start up a node and join and create channels and those sorts of scenarios. I don't believe it affects the performance in a working live application channel scenario but we can check with some other fabric guys on clarifying it, but I don't think it has an impact on the speed because it's again, not used for like consensus, right? That's only whoever is in the application channel is the only one that's doing consensus with me. Perfect. Okay, Varad, I think that's the good questions. So go ahead and go back to the demo and I'll monitor, see what else comes through. Thank you, John. So let me create a new channel, right? With the new, you know, so in this case, I don't have any, so let's save the channel. So I'm creating a new channel, choose one of the ordering services. This is the one we just removed the system channel and for reference, actually let me do that, just to show you the second node I created without. So order one MSP part of this guy and then order two MSP. So again, you see a message that this is the order without system channel and it tells me that TLS identity is not found. I need to create one. And it also tells me that, you know, I need to associate a regular admin identity. So let me associate identity, this is the MSP. Now I need to go back and the same process falls through before, right? Where I was showing, I need to create a new TLS certificate from the CA that's associated with the node. Oops, sorry, I'm back. TLS, next. And I say order two TLS. And now if I go back, it should show that, you know, it's a node channel, of course, so it's a brand new node. So basically I have two nodes, right? One from each organization, two different organizations. I'm gonna create a channel with both of the organization one and two and then join them. So that basically mimics the scenario where you have multiple organizations, each organization is trying to contribute different orders to the, you know, consensus process, right? So if I go to channels, create a new channel and channel two, then I'm just gonna say start with one. And first it's going to say, who's the organization like just members, right? Or one, who are the peer organization members? I'll just pick one. This doesn't matter for the demo. And this is the one of the important screens that's new screen that got added. Who are the orderer admins that are on this application channel? So the MSPs that you choose are the only ones that can join the order. So in this particular case, you can only join orders that belong to order one MSP or order two MSP, right? That's important, right? Because if you have just order one MSP, they won't be able to join because they don't have the right certificate. So this tells you who are the organizations that are allowed to contribute orders and then create. So what this did at this point, nothing happened at the order level. All it did was to create a block with the predefined configuration. You said, like again, we said order one and order two are admins and the order one is the member of the channel. We did that on, at this point, the console has a block, just created one. So when you hit the continue step, this is the joint flow that automatically gets initiated, right? So what the console did at this point is it looked at who the members are in the block. Again, in this case, order one MSP and order two MSP. And it also looked at the local config to say, hey, which of the orderers are from those MSPs? So in this particular case, it sees that one and two, like these are the two, they are already defined as concentrers. By default, I'll show you the process. By default, all nodes from that particular are becoming concentrers. So for the demo purposes, I'm just gonna choose only one to join, right? So to show you something interesting. So now, if I go into the node and then go down to order one, you should see that v-channel two is a member. However, I did not choose the other node, the node two as a member. So obviously at this point, I said two members of concentrers, generally you want three, of course, right? Just for the demo. So two are concentrers, but only one is joined. So at this point, the channel does not have a program. So when I try to go into the second node, I'm going to try to join the second node into the channel. So I say, get a channel from this org, right? So this is the error message or information message I want to show, right? So basically we are saying there is no program. Now you need to join using the block the console already has, right? So now if I go back to the channel with the console block, so we see that we stored the block in the console. Now what I can do is take the block, join the second node to the channel which will establish consensus. This may be a bit confusing. Let me know if it is. I can try to explain it a little bit more. But again, the general premises, right? I defined a channel with two nodes as concentrers and only one let join. The other one hasn't joined and hence there is no program and hence I cannot get any blocks from the new node. So if I click on this, now I can say use the block that we already stored in the console and join the second node. First node is already a concentrant and already joined with the tick mark. So I'm going to join the second node. That's it, right? So if I go back to the nodes and then go down into the second node, I should see that I joined and the consensus is established. So I can, like for example, if I did this, right? Well, I can't join any other nodes. Yeah, I don't have one. So I'll show the adding a follower part next, right? Because that's another important distinction I want people to see. But any questions so far in what you guys have seen in terms of joining a node, joining a channel to the node and then the consensus process and how we are able to use the block stored in the console to join. I'm not seeing anything in the chat right now, right? But I will say what you presented is very clear and excellent. So anyone who has any questions, they'll feel free to post them in the chat. Okay, so what I'm going to do next is, right? To add a third node, right? I already pre-created one. I'm just going to import one of the nodes I already created to show the follow process, right? So I'm going to add the third node. So the third node I created as part of order two MSP, right? There you go. So that's part of the MSP. So if you observe, actually, let me show you that that may make it interesting. So if I create a new channel, I'm not going to create a new channel. However, I would like to show, click on the advanced. So the channel three, so pick one, nothing changes. So I'll just breeze through these steps. Okay, one and two are the consent nodes. MSPs that can contribute, majority, whatever the policy, nothing changed. These are like, you know, things we used to have. This is the screen that's interesting, right? So by default, it's going to include all of the new channels, right? So I'm going to include all of the nodes that belong to those two order organizations in the channel. So right now I added a third one. By default, now it will try to include all three nodes into the concentrator, if I just unchecked it. But if I flipped it to like, no, don't include all of them, but I want to include only one guy, I can do so, right?  So point being, if I flipped it to include all nodes, it'll include all the nodes at that point in time that are in the console that belong to those two organizations into the concentrator set. And you have an option to flip it and choose the specific nodes that you want to choose. So going back to the original thing, right? So when I created the channel, only two nodes were there and those two were automatically concentrators and, you know, you saw that. And if I go to this... So I see that one is a concentrator and if I go to the second node, it will also show as concentrator. And the third one, I don't have anything, you know, I'll associate this. Okay, that's... So I see that again, the third node, I have the third node, node channel, right? You know, it doesn't have any channels. So what I want to do is to join channel as the follower in this case, right? So I'm going to join channel and I say get the block from order one. So next, and then I say choose the order three. So if you noticed, right? We did not get the consensus error this time because there are two nodes in the concentrators and both are like, you know, in the channel. And you see that that is a star with follower, right? So this basically says, I have two nodes, you know, this goes back to the picture that I was showing in this screen where I have two nodes as concentrators and one is the follower, right? If you go back, not this side, join. So you have successfully joined the new channel. Oh, why is that? Okay, so let me see, join channel. So first node, take this. That may have been a bug that I don't know on my local, the code fixed. I pulled the, maybe that is a bug. Of course, it's demo time, so. But what you should have seen is that third node become follower on this channel. Let me do this for you and see if this will work just for, I'm curious. Otherwise, you know, again, we'll get the bug fixed. Yeah, this seems to be some sort of bug. But again, that will become follower. The third node would, right? Did I want, oh, the last thing I wanna show is the deleting the node from the channel, right? So if I go into the, again, the details, I can again add a node or like, you know, look at the information, in this case, again, the concenter and I can also hit the delete button, right? I can say delete this channel. So what this does is again, it only deletes the node from the order, right? So this does, as a concenter or like a follower, it simply deletes it. It does not do anything with the peer, right? The peer channel continues to remain. The fabric has, I think they already have a feature where you can, you know, remove a channel from the peer. Console hasn't implemented it yet. So that is a set of, I think PRC alike commands, right?  So, here then so peer node, yeah, I'm joined. So again, it's a CLI that's available in the newer fabric that console hasn't implemented, right? But it's a CLI. That's mostly what I wanted to demo. Did I miss anything? Let me just quickly check what I wanted to show migration, create, join, remove, concenter, follower, that one, I think that is some sort of bug that we'll look at. But any questions, any other questions I should say? Yeah, Barad, it looks like there's three questions in the chat. And if you want to look at the chat and just answer and that'd be great, or I can read them off to you. Let me see. So doesn't the operation to join channel require a tool of existing participants? So joining a channel, you are joining. So it's a block that you created, right? Like all one, two and three, whatever like you included. And only the guy that owns the order can join, right? There is no other pool required. Like, you know, I'm just saying, I have a consortium of three members and it's the distinction is the order admin is the only one that can join the channel to that order. So unless I have the right credential, random person cannot join my order, my channel into the order, right? So that is implicit approval, I should say that's involved here, right? Let me know if that's not clear. In without system channel, how you're gonna categorize which peers should be in which org and how do you know which peer from org confirm consensus? So the process of the peer and order organization did not change, right, with the new thing. So when you created a channel, when we created a channel, right, we basically said, right, let me go back to the channel creation. So when we create a new channel, it's still, let me just type something. We still have the same like organization list. In this case, I'm telling the channel, my peer can only come from org one MSP. I cannot have a peer from like some random MSP. So that's kind of the, again, nothing changed there. So it's only peers from the organization can join. Again, let me know if it's not clear. Again, consensus doesn't, you know, it's basically you're telling like all these peers and they are the ones that are like in authorizing the transactions and storing them and all that. Again, let me know. What are the advantages of sitting a follower? I think one is, again, the fact that you can be a quote and put listener in a conversation, not like an active participant in a conversation, if you will. So in this case, right, so all you need to do is to read the blocks, you know, from then manage like a node with all the blocks. If that node goes down, nothing changes.   And I think one of the benefits that fabric specifically talks about, right, is the fact that, you know, the, let me see. So this particular one, the fabric, you know, that, you know, documentation doesn't quite talk about all the benefits of the concenter follower business. But if it's a follower, you know, it's quicker to join, you know, so just the particular benefits again, right? Once you sync them, then the node is in the ready state, you know, you can simply join. However, if you started with the concenter, then join, then during the time it's trying to catch up all the blocks, that node is unavailable for anything, right?  So I think that's a benefit like, you know, again, if you sync up and then become a concenter, it's a quick joint process and it's right away available for like, you know, consensus. Hopefully that helped. How can you set, how can we do set up a scenario and make an strategy? So in order to set it up, if you search for operator, fabric operator, let me actually do that, right? So just wanted to give you this plug. So there is fabric operator, it's fairly quick to set up and get it running. And what the operator gives you is it also kind of bundles if you go to the console, there is a step to include the console and you can do sample network, right? And that sample network will have 2.4. So I think you can play without system channel and all that, right? It's a fairly quick and easy way to get the entire ecosystem lifecycle working, right? Where you're talking to Kubernetes, you have the console, you have the fabric network, you can easily add nodes, remove nodes and all that stuff, right? So I think this is one easy way to get your hands dirty. So again, I think we need to have a session for the operator and how to use it set up, but should be fairly straightforward to do it. They also support kind as an option, right? You know, Kubernetes cluster as an option. So this is what I use for development locally. I don't rely on much outside, but that should help. And then I'll post to this operator also, just so people have links and then the channel creation, this link, and then the CLI stuff, if you guys are interested in, or with, that's very helpful, yep. Okay, anything else, right? Looks like there's another question in the chat here from Kristoff. And I don't know if you can see that or if he can come off mute and just ask the question directly. Let's see, Kristoff, okay, follow up. Let's say we have three organizations that each managing an operator in a given channel. Now two new orgs want to join the consortium and then approval from the existing participants before the two can join. It should not be possible for a random organization to join the channel and synchronize the blocks. Yes, right? Because if you have a third organization, it depends on the channel policy. So there is, if you, let me see. That's a good question, yes. Let me go forward. So in this particular screen, when you're creating a channel, you're telling which are the organizations that are able to contribute notes. And again, in the scenario you were describing, right? There are three organizations to begin with and two ones to join. Then you need to make a channel update, right? To add those two new organizations into the order of organization. And the way this approval works is, right? That is another policy console for like, you know, the simplicity. If you're creating from the fabric operator, the policy is one organization need to approve for any new order of organization to join, which is not like ideal, but that's a controllable policy where you can say majority need to approve, in which case you need to go through the whole, like, you know, approval to add the new guy. But you're right that the policy is decided by, you know, again, that is a policy if you decipher the block, you can see the policy. And you do need, yes, you know, the current members to allow adding a new organization and then you can add notes from the new organization into the channel. Hopefully that helps. And the process to update the policy remains the same as in 2.2 by which you have to get that JSON, do your config change, generate the protobuf, do the different apply and see, I mean, sign the protobuf and then apply, that remains the same. Right. So again, there are two different things I wanna make sure people got it, right? One is the channel member policy, right? Who are the members and how does the, you know, peers join and like, you know, work with it? That's one. And the second one is the order specific list, right? You know, organizations that are part of the, you know, to do any modifications to the order level, you need to have these approvals, but both of which require approval from the organizations. And we definitely have channel level orchestration between multiple consoles to do the organization level policy, but I think we are close to being done with the order level policy update, right? So that's not something you can do at the moment from the console. Again, we send the default to like whatever, like single order need to approve, but if you need to extend it to other cases, console does not support it yet.  Yes. And for the peers, that's what you do on the background of the fabric console, right? Exactly, exactly. That makes it easier for the peer because that's a more common scenario we have and you can do the whole dance from the console, like, you know, all the back and forth, but not for the order admins yet, okay? I think that's perfect timing. Any other questions, please, you know, send it my way, you know, or like open up an issue like we were talking about, but that's I think all I wanted to cover. Yeah, that was a great presentation, Varad. Looks like there's some other people that have a question of follow up with you. If you want, would you post your email in the chat where they could touch base with you? I think Sunny wants to reach out about a podcast. Let me post my LinkedIn, just so people have access to it. I should have included probably the, let me post that. And I think, you know, we're at the top of the hour, Varad, but let's just tackle one more question and then we'll call it good for today. And I agree with you. I would like to have a follow on a presentation by you because I think that there's a lot to cover here and let's just get on email and cover that. But it looks like there's a question about being able to set up the environment on Ubuntu 18 and an Azure virtual machine. So as long as you can run Kubernetes, you can run it anywhere. Basically, that's a gentle answer, right? So, you know, you can use kind or Kubernetes to open source the operator. That runs wherever Kubernetes runs.  So I think you should be able to run it. There is no reason why it wouldn't work because again, it's all Kubernetes. Okay, I think that that covers everything. I really appreciate everyone joining the call today and please feel free to follow up with Varad and please feel free to interact with the GitHub community there as well. And we'll look forward to the next presentation by Varad. And I hope everyone has a wonderful rest of your day. All right, thanks guys. Bye, have a good one. Thanks everyone. Thank you. Thanks everyone.


Γεια σας, είμαι Vicky, εδώ και καθώς ήρθατε στην δεύτερη εξογραφία του CREATE 8 για αυτό το μήν. Είμαι εξογραφός στάμπσης και στάμπσης από τα τελευταία εξογραφία μου από τα τελευταία μου, και για την πρώτη εξογραφία που σημαίνω σήμερα θα χρησιμοποιήσω αυτή τη στάμπση. Έτσι, αυτό είναι το X & O και μπορείς να πάρεις ποτέ σε στάμπσης όπου θα πάρεις τα κομμάτια, τα τελευταία, τα εξογραφία, όπως η γραφία για το τικ-τα-κτώ. Και υπάρχουν λαγές εξογραφές, καλύτερα για τα εξογραφία, καλύτερα για το Valentine's Day. Τώρα, υπάρχουν δυσκές πίσες και πίσες αν θέλεις να κομπιένεις με αυτή τη στάμπση και καλή δημιότητα για όλα τα κομμάτια, γιατί υπάρχει αυτό το μικρό πόδι που είναι μεταφακτικό με πλαστικές πίσες που έχουν πολύ τη δημιότητα και μπορείς να τα βάσετε μέσα σε αυτή τη στάμπση και υπάρχουν also πλαστικές πίσες, like O & X, και πλασστικές πίσες όπως τα τουλότητα, στην εύκολη και η μαύρη. So there are lots of options with this stamp set. You can use the plastic grids to go dimensional or you can just stamp and go totally flat or even you can use the matching dies just mix and match all the different pieces and have fun with it. Now there is also available this frame square and die that you can combine with these plastic pouches στους φρέντες. Λοιπόν, αν θέλεις να χρησιμοποιήσεις και να δημιουργήσεις το σχέδιο σχέδιο με το τυκ-τακ το inside, μπορείς να δεις ότι είναι καλύτερη εκεί. Τώρα, από τα σχέδια συγκλώσεις, έχω χρησιμοποιήσει το ένα που λέει ότι είναι τυκ-τακ τελειώσο, και αυτό είναι γιατί δεν ήθελα να δημιουργήσεις ένα σχέδιο σχέδιο σχέδιο, ή ένα σχέδιο που πρέπει να δείξεις σε ένα σχέδιο σχέδιο. Αυτό είναι more neutral και μπορείς να δείξεις πραγματικά όλοι. Τώρα, as you can see, I have already used the square frame and cut out a window on this piece of white cardstock, and now I want to have two different colors on my stamp, so I am going to mask off the second line that says awesome, and I'm just going to stamp the first line that says you are tic-tac totally with black ink. I'm going to remove my masking tape there, and then I'm going to close the door of my stamping platform. And just because I didn't get quite of a good, vibrant impression, I'm going to repeat the process again, and that's the good thing of having a stamping platform, so I'm doing it again. Don't forget to remove the masking tape. Ask me how I know. Now I'm going to stamp once more, and I get a great impression here, so I will go on and stamp the second line of the sentiment that says awesome. Now, just because I will go for a white, black, and red theme here for my card, I want to have this word in red. The color I'm using is called poppy by my favorite things. I'm going to close the door, and I will get a perfect impression from the first time. Now I'm going to prepare the window for the shaker elements, so at the back of my panel I used some white glue, and now I'm going to put this on top of the plastic pouch. I'm going to press with my fingers for a few seconds just to make sure that I have a nice bond. Now, for the back of your window, you can use any pattern paper that you like. I decided to go quite bold. Now, depending on the pattern paper, you can choose black or white grid. Just because I want to go bold, I decided to use black cardstock at the back, and that's why I will use the white grid to have some contrast.  I'm also going to place some of the o's in different places, and I'm not going to fill in the whole grid, and then I'm going to cover the back with the black piece of paper.  It looks beautiful as it is, but I decided to use the frame, so I'm going to add it in red, just because I think it makes it look more finished. To finish off my card, I'm going to stick this panel on top of my card base, that's in red, and it's a standard size card, that's 4.25 x 5.5. For my next card, I'm going to use this beautiful Merry Christmas greeting stamp, and I think that this is so beautiful that it can be the focal point on your card, and it's perfect for mass-producing beautiful Christmas cards. So I'm stamping that on top of a white panel, and I have actually used the stitching rectangle dies to cut it out, so this has a beautiful stitching, and I end up having a beautiful sentiment at the center of my panel. Now, to embellish my card a little bit, I'm going to stamp a few of those images from this stamp set, which is called Dushing Deer, and this stamp set has beautiful images like two adorable deers, as well as a little bunny, but I'm actually going to go with the two little birdies for this card, and I'm also going to stamp a few of the mistletoads that are available. At this stage, I didn't exactly know which ones I'm going to use, so I went ahead and stamped a bunch just to have some options later on for my card. I used my alcohol markers to add some color on these images, and just because they are so tiny, it was a really quick coloring. I used the matching dies to cut out all the elements, and now it's time to assemble my card. This is going to be a very simple-looking card, but so beautiful at the same time. Now, as you can probably notice, I have already changed the format of my monthly event created. So instead of posting eight cards in one video, I'm posting four one day and four on another day, and this is going to help my video not to be as fast forward as it usually is. Let me know in the comments below if you like this format more than the previous one. I think it's better because you get to see the products more, and it's not as fast forward as it was, but I really value your feedback, so let me know below. So if you notice, I have placed the little birdies as if they are standing on top of my sentiment, and now I'm going to do the finishing touches, so I'm adding some shine on their hearts, and I'm also going to use some Nuvo drops on top of the little berries. The one I'm using is the clear one, to dry completely transparent, but you can also use glossy accents if you have that. Now for this card, I had to go back to a stamp I used in part A, so that's the Happy Poli Day stamp set. I think those guys are so adorable, and I had to use at least one of them again. So I was debating on which one of the puppies I will use, so this guy won finally. I'm going to stamp him with licorice black ink, that's by my favorite things, and that's actually an ink pad that is friendly to alcohol markers, so it's not going to smudge or smear, and I'm going to use my Spectrum Noir to color everything. When I'm sharing more than one card on a video, then I usually edit out all the coloring that I do, and that's just because these type of videos are quite long, and I like to focus more on how to put everything together, and how to design your card, rather than how I colored all the images. And I also have to apologize about my voice, I've been having a cold this week, but I think I am recovering today, I feel much better. After coloring my puppy, I used the matching dye to cut it out, and I need a few more elements for my card, so I'm going to use this ring that says Happy Holidays all around it, there is another one from this release that says Merry Christmas, it's great for creating shaker cards as well, but I'm not going to use it as a window or a shaker card for this card. So I have this sparkling piece of paper that is left over from a card that I made for part A, and I'm going to cut out a snowflake, and before cutting it out, I made sure that it fits perfectly inside my circle. At the back of the snowflake I'm going to add a few dots of glue in different areas, and I'm going to stick that at the center of my circle. I have added some tape adhesive at the back of my puppy, and I'm going to stick him just next to the snowflake and look how nicely they nest together. So I'm adding some glue at the back of my sentiment there, I'm going to stick it on top of this white panel, and by the way I have cut out this panel by using the stitched rectangle dies, so I do have a beautiful stitching around it that always gives a nice finishing touch. Now I'm going to assemble everything on top of that. I'm going to add some foam tape at the back of my focal point, which is going to give it a little bit of dimension. Now this is going to go directly to the center of my sentiment, and although I have covered up half of it, you can totally read what that says. I used foam tape at the back of my panel, and I'm going to stick that on top of a standard card, and I really liked how nice and simple that looks, so I'm not going to add anything else on top. And let's move on to the last card for today. I am using the little girl, and this month the stamp set is called Nice List. I'm stamping her with Licorice Black by my favorite Things, and I'm going to color her with my alcohol markers, and then use the matching die to cut her out. Now I have this golden cardstock, and I'm placing those rectangle dies one inside the other to create a frame. However, I changed my mind and I decided instead of using the frame to use only the inside panel, but I am keeping the frame for a future card. I have already cut out those snowflakes out of the same cardstock as the golden panel, and now I have chosen one of the sentiments that says Be Merry, and I'm going to place it on top of my acrylic block, on an angle, so it matches the curve on the list. So I'm going to stamp my sentiment there, and you can see how nicely it follows the curve. And by the way, this comes from a stamp set that is called Snow Globe Sentiments, and these are actually all sentiments that fit nicely inside that panel that you add below the snow globe, but they are so tiny, so they match perfectly that list the little girl is holding. So now I'm going to do some assembling, I'm going to stick here on top of a standard card that's formed a quarter by five and a half, and I am using foam tape at the back since you all know that I love dimension. And notice how I'm not going to stick this panel at the center of my card base, but rather on the right side, so I do have a bigger border on the other side, and that's where I'm going to stick all those snowflakes coming out from the gold panel which is going to give more interest on my card. For sticking my snowflakes I am adding a dot of glue at the center of the snowflakes, and this is going to allow them for some dimensions, since they are not going to lay flat, completely flat on top of my card. And here are all the four cards that I shared today, using supplies from the last release by my favorite Things. I hope you had fun, that you got inspired. Don't forget to leave me a comment and let me know which one of those four cards was your favorite. I hope you will all have a lovely weekend and see you on Monday.


Welcome to Hope Today and thank you for joining us for a very special program. This is a program of prayer for Israel during Hanukkah. We all know the situation in Israel right now. We wanted to gather, everyone together, we've got some powerful prayer warriors and pastors with us today that are going to pray. We're all gonna be joining together in prayer for the land of Israel and for that situation that is happening right now.  It's from Isaiah 62, it's verses six and seven and it says this, I've posted watchmen on your walls, Jerusalem. They will never be silent day or night. You who call on the Lord, give yourselves no rest and give him no rest until he establishes Jerusalem and makes her the praise of the earth and that is our heart, that is our desire right now that we would not give God rest, that we would bother the throne of God right now with prayer, beseeching him for Israel. We have a big group here, I'm gonna go over now to Amy and the group on the pod. What an honor it is to be watchmen on the wall and thank you so much for joining us today. I am here on the pod with some incredible pastors and Rabbi Jeff Kipp. We have Pastor Zach Blair and we have my main man of 28 years, Pastor Buck Schaefer and we are celebrating and supporting Israel and this time of Hanukkah. So I wanted to ask you, Rabbi Jeff, you know, what is the significance of Hanukkah for us as believers? Thank you, Amy and Shalom, everybody. I always like to share with folks that if there was no Hanukkah, there would be no Christmas. In other words, the festival of lights has everything to do with the birth of the one who is the light of the world. And about 168 years before the birth of the Messiah, there was, during the Greek Empire, there was a very fierce, godless leader by the name of Antiochus IV and he took over the Holy Land. God raised up a rendent to fight against him, the Maccabees, which actually means the hammer. And they were fighting, you know, the greatest, strongest army in the world in the Greek Syrian army. And it's an amazing story of how God used this small band to save rendent of Israel, to actually be able to defeat Antiochus and after three years, he just up and took his army and left. And the land was defiled by idolatries. He would set up an image of himself Antioch did and command people to sacrifice swine on the altar. He actually did that in the very Holy Temple itself. It was an abomination of desolation.  And so if Antiochus and really Satan through him would have succeeded in completely wiping out the Jewish people, there would have been no messianic nation. There would have been no messianic people for the Messiah to be born into and through, you know, about 165 years later. So if there was no Hanukkah, there would be no Christmas. It is the festival of lights. Jesus himself, it says in the book of Revelation, walks amidst the seven golden menorahs. So in a nutshell, there's a miracle of Hanukkah and really leading up to the miracle of our Lord's, you know, virgin birth. And my favorite part is they only had enough oil for one night. That's right. And God did a mighty work, a miracle and extended the light. And so today, every time I see a menorah, I think it is our job and our responsibility, to bring the light and to keep the light moving. I know you have a powerful scripture in the book of Romans. Well, it's powerful that Judah Maccabees is actually down there at one of our military colleges standing up as a warrior. And what's interesting is that God would say us in America, just like the Jews, it might be time to stand up when someone's decimating the altar and the temple in the house of God and stand up for our freedom because we were founded upon Judeo-Christian values. So would we stand up, according to Hanukkah, with fighting and lighting? How powerful would that be? To be Jesus, according to He celebrated Hanukkah in John 10, 22, that we would not only fight, but we would light our lights. Amen. And you know, something significant for Pastor Buck and I, I'm not sure if you know this, but a Jewish man, Robert Levin, gave our church a free building. I mean, that is so significant and so huge and we have stewarded well that building, but there is something deep within us that is so grateful for our Jewish, Judeo-Christian connection that we have with the Jewish people and the believers out there. So what we're gonna ask you to do today during this program is we are going to pray and we're gonna each pray for different parts, but we want you to join with us. We want you to stand with us and we want you to celebrate with us and we want you to fight and be the light as well. So I'm gonna start off guys and then we're gonna throw it to the altar, but I'm gonna start by praying for the peace of Jerusalem. So will you pray with me? Father, we just come to you in the mighty name of Jesus.   So we pray right now for the peace of Jerusalem. We pray that there would be Shalom within your walls. We pray that there would be quietness within your palaces. I also pray for the prosperity of all Jerusalem in Jesus' name. And I pray for friendly insiders that you get along even as I was there and I see that the Muslims, the Jews, and the Christians all living together. We just speak over that land. You get along in Jesus' name.  And we speak peace within your walls and within your land. We thank you for the greatness that's there. We thank you for the city that's there. We thank you for the words that we live by that came from there in Jesus' name. Amen. Amen, Pastor Zach. I've been processing, when you asked me to pray, I've been processing praying for the leadership of Israel, but also for the media regarding this matter. Because in people in younger generations, they don't know what to believe and I think it's an atrocity. We have to allow the Bible to be our guide, to be the sole source of our viewpoint. And today, that has just been scattered. We don't know what to believe. The Bible, search these things for yourself, look in the Bible, make sure that they're so and they are so. And so I wanna pray for the eyes of the media to be enlightened that truth comes out and also I wanna pray for the leadership of Israel. So Father, thank you in Jesus' name that just as I had mentioned, Father, the eyes of the media will be enlightened and they'll speak truth in Jesus' name. Thank you, Father, that there will not be a voice from the outside that will influence young people within our country and pull them into hatred and pull them into beliefs of wiping out people groups. God, in Jesus' name we stand against that. So Father, in Jesus' name now, I thank you for moving on our universities, on our colleges, all across the United States for true peace and for true love and for true acceptance that only comes through Christ. And so Father, thank you now. The eyes of the media will be enlightened, they'll be opened, but thank you, Father, now as well that in Israel all leadership is guided by the wisdom of God. Thank you, God, that they know how to navigate receiving hostages back and finding ways to open up doors, God, to do things that are wise, God, to do things that are right, Father, to protect, to defend and I thank you, God, for giving this nation divine wisdom. Father, thank you. Thank you for Prime Minister Netanyahu, God. I thank you in Jesus' name that God you lead him, that you speak to him and that you guide his hand and that you protect leadership, you put the right leaders in place and Father, they unite on what is right. Thank you, Father, these things will be done in Jesus' name. Today we wanna thank God for Jews, Christians and Arabs alike. We wanna pray for the whole Middle East. We wanna pray out God's word to the Greek word, to homologio, to say the same thing that God says. Simply, and I love Romans 11, what a statement we can make today as we pray, saying, rather than because of their stumbling salvation extends to the non-Jewish people in order to make Israel jealous and desire the very things of God has freely given them. So if the world would be greatly enriched through their failure and through the fall of great spiritual wealth as given to non-Jewish people, imagine how much more will Israel's awakening bring to us all. Father, we thank you for the church arising. We bind replacement theology. There is a place for Israel. There's a place for the Jews. Father, you said in Ephesians two, we'll come together as one new man, Father God. So we pray this, Lord, and as you said, as Paul the apostle would make them jealous, Father God, and a temporary rejection, but there would be a reconciliation in the world. What will happen when Israel's reinstated and reconciled to God? It will unleash resurrection power throughout the whole earth. Father, we pray that this resurrection power is released throughout the whole earth, Father God. And if the roots of the tree are holy and set apart, so will be the branches. God has grafted, Lord, us in as like stepchildren or joint partners to share, Father God. So we don't be so arrogant, Father God, to be superior to the branches. There's no reason to boast for the new branches don't support the root, but you owe your life to the root that supports you. So Father, beloved brothers and sisters, I want you to share the Jewish man, the apostle Paul, concerning Israel's future for understanding this mystery will keep you from thinking you know it all. A partial and temporary hardening of the gospel has come over Israel, which will last until the full number of the non-Jews has come into God's family. Then God will bring all of Israel to salvation. This is our prayer today, oh God. We lift up this prayer and we thank you for the beautiful Jewish people that there's a move of God in Squirrel Hill, there's a move of God in the United States, there's a move of God in Israel, in the Arabs and Palestine, in Jesus' name. Yeshua's name. Amen, Pastor Jeff. Yes, Lord, we pray for the hostages. Lord God, we just pray for you are a God of the miraculous. You are naturally supernatural. We pray for the moving father of your angels, your angelic host, you are the Adonai Zivot, the Lord of the armies of heaven and earth. Lord, would you do another miracle? Would you once again divide the Red Sea? Lord God, people are feeling hopeless, they're feeling powerless, they're feeling tremendous despair. Lord God, we pray for just healing for all those that have just been bereft. Rachel is weeping, Lord, her children are not. Lord God, there's great lamentation in the land. Husbands and sons and daughters and wives and children and grandchildren have been decimated, have been brutalized. Many of them held in captivity, Lord God, in darkness with sexual abuse and the most abominations. Lord, would you do a miracle and just set them free? Somehow bring them back. Lord God, bring them out of captivity, let them be found, let them be discovered. Lord God, would you give great wisdom and Father God's supernatural vision and discernment to the IDF and to the leadership and Father to find, Father to prisoners of Zion and bring them out, save them, rescue them and more, Father, the most important thing would you bring salvation. Father, even to the hostages and to the people, the young men and women that are serving in the IDF, Lord God and all the people, Father, would you, Father, now begin to pour out that spirit of grace and supplication that they would look upon the one who was pierced, Lord God. You have promised that that day would come even now that we speak into it, we prophesy it, we, Father God, that you would just move, Father God and breathe upon these bones that they may live and Father, pour out that spirit of grace and supplication that they may, Father, recognize Yeshua, we pray for their salvation physically as well as spiritually in Yeshua's name, amen. Amen. Amen, Pastor Frank. Lord, we pray now, we come before you, Heavenly Father and we ask you for an outpouring of the Holy Spirit over your people, Lord God. May you feel them, Lord God. Father in heaven, we pray in the spirit of Zechariah 4.6 that they may understand that it's not by might, that it's not by power, but by the Holy Spirit, God, that their hearts will turn to you, God, that the victory will be one in which your people will become your holy people. They will turn to you, God. Lord, we know, we understand, Lord God, you're in control of everything. We know that you are using all circumstances in our lives and in their lives to turn them to you, God, Father in heaven and we know that this can only be made possible by the power of the Holy Spirit, God. We pray today that you will, only the Holy Spirit can write your desires in their hearts, Lord God, and you desire for them to become your holy people, all, Lord God.  So today we pray, Lord God, please, that you will fill in with the Holy Spirit, God, politicians, teachers, Lord God, the military, the Father in heaven, the reignant that is now in Israel, Lord God, your holy reignant, God, that they will be Father in heaven infused with a power from on high to turn to you, to fight, to believe, to persevere, God, and to preach the gospel. Strengthen them, strengthen them, Lord God, and let them see the victory that will come from you, Lord God, for you are coming back for a people that are led by the Spirit, that are infused with power from on high to accomplish amazing things, including the defeat of the enemy. In the name of Jesus we pray, amen. Father, it's so amazing and prophetic that the eyes of the entire world are on Israel in this hour. Father, nations are in the valley of decision, multitudes, Father, multitudes in the valley of decision as they behold what's happening to your covenant people in Israel. Father, thank you for waking up your church and raising up more watchmen. Father, that would stand before you in the gap on behalf of that land, that ancient land, that ancient people, the God of Abraham, Isaac, and Jacob, his land, his covenant land. Father, awaken your church. Thank you, Lord God. Wake up your church, Father, and raise up more intercessor, watchmen on the wall that will cry out day and night and remind you of your word and hold you to your word and take you at your word. Father, thank you for strengthening the intercessors all over the world, all over this nation. Father, that have it in their heart to stand for Israel, to pray over that nation, to pray for those people, to see your will done. Father, thank you for raising up more intercessors to stand in the gap in this hour in Jesus' name. Jesus, thank you, God. Thank you, Lord. Thank you, Lord. Father, we so thank you that you said that you would raise up the age-old foundations, that we would be the restores of the breach, some trust in chariots, some in horses, but we remember you. We remember your name, the name of Jesus today. And those age-old foundations we affirm and confess to the principalities and powers of the air, those age-old foundations that were established and once again emerging will not be destroyed at all, that you are Jesus, the builder of your church, the builder of your nation of Israel, the builder of your covenant people. And we pray in the name of Jesus Christ for the governments of the United States of America and the European Union particularly. We pray against the anti-Semitism and everything that would try to destroy. Lord, help them to see how foolish and how useful it is to try to fight against you, the king of the city of the great king, even our Lord Jesus Christ. We pray that you would raise up leaders in this nation who would stand boldly and say we cannot fight against. Lord, let them be as the old time in Egypt when they were dealing back and forth with Pharaoh's sorcerers and Moses when they finally came to the conclusion we cannot fight against this God. I pray that you would bring leaders in the United States of America and throughout Europe and the entire world, including the Arab world, that we cannot fight against this God. Lord, help them to see how futile it is that they cannot fight against the age-old foundations because you are raising them up and we pray that in the name of Jesus Christ. We pray for the conviction of sin, of righteousness and judgment on everyone who sees that they can in any way frustrate your purposes and frustrate your plans. And we thank you for those lives that everybody is saying have been destroyed, that they can never be the same. You are the repairer of the breach.  And we thank you for that and believe in you for that in the name of Jesus today. Hallelujah, Hallelujah. Father, we thank you so much for this moment that you are awakening your church, even in the midst of a war. There are people, Father, they don't even know what it means to connect with your Jewish people. They don't understand, Father, the scriptures. And so you're using this to awaken your church. And so God, I thank you God that through this, God, we can also pray for the innocent lives that have been taken, God, through this war. We pray for children, Father, and parents and families that have been made hostage and innocent blood that has been shed, Father, you're near to the brokenhearted. So we pray, Father, for every broken heart. I pray, Father, that even as you enlighten us as your people on this journey, God, that every local church will awaken that will evolve and say, I'm not even connected to the Jewish journey. I don't even know what the Torah is. I don't understand the Jewish Hanukkah. God, you're awakening us. You're giving us an understanding that we need to know. You told us to pray for the peace of Jerusalem. It's in scripture. And so, Father, as we learn your word and understand this journey, may we not miss this moment to be awakened as your people. So we continue to pray for the innocent, Father. We thank you that there will be answers, supernatural resources, people need counseling, they're traumatized. There's so much that has happened, Father, that has been shared. Like in Jacob, you changed Jacob's name to Israel and that is the church, way local church in America and around the world. In Jesus' name, hallelujah, amen. Amen, amen. Thank you, Father. Lord, as we are here at your altar, we lift up Israel and your holy people. And Lord, in this season of Hanukkah, we pray for a Hanukkah miracle. Lord, a miracle for your nation, for your holy people. In Jesus' name, Lord, fight their battle. Defeat their enemies, Lord. Truly, bite of the world through in Jesus' name. And you know, Catherine Coleman used to say that the Bible is more current than tomorrow morning's newspaper. And in Zephaniah chapter two, there's such a prophetic word that is so relevant for today. In verse four of Zephaniah two, it says, Gaza shall be forsaken. And with all the bombings going on, it is being forsaken right now. But then it says in verse seven, for the Lord their God, the God of Israel, will intervene for them and return their captives. And Lord, we stand on captive. The American captives, the Israeli captives will... Jesus wept over Jerusalem. He, the emotion, the heart of God, that is the heart of God for Jerusalem and for all people and for you. And we just wanna pray right now. We wanna pray that God's purposes will be accomplished in Jerusalem, but also in your own lives. Let's pray together. Father, in the name of Jesus, we thank you.  You're a God who has a heart and concern for his people, Lord, and I pray, Lord, that many will know Messiah in Jerusalem, Lord. That many will know Messiah in that region, Lord, that they will understand that you came and you lived and you died and you rose again. And we can have newness of life because of that. I pray for the gospel to flourish in that region, Lord. And I pray for many to come from near and far and come to know you as Savior and Lord. And we ask it in Jesus' name, amen, amen, amen. Yes! Let's continue to pray. Let's go back over to Amy. Wow, that was so powerful. And we just wanna say thank you. Thank you for those that are praying. Thank you for those watchmen on the wall. Thank you for those that have a heart for Israel. Thank you for those that are praying for Gaza and the Palestinians and the hostages. And we pray that God would wipe out, not people, but the wicked in Jesus' name. And I love the scripture in Jeremiah 31. It says, at that time declares the Lord, I will be their God, the God of all of the families of Israel and they will be my people. This is what the Lord says. The people who survived the sword will find favor in the wilderness. And I love this and I'll finish with this. I will come to give rest to Israel. So we just pray a peace and a rest over Israel. And I'm reminded just as we close this program today of the incredible story of Esther, where Haman is about to wipe out the entire Jewish race.  You cannot stand. You can sit down and live in the palace. You can have a good life. But don't think that if you're quiet, that deliverance will not come from some other place because it will. But who knows Esther, if you've been born for such a time as this. If ever it was the time for the body of Christ to rise up, it's now. It's the time to wake up. It's the time to be alert. It's the time to be prayed up.   Let's think about others. Let's think about the world. Let's think about the coming of Christ. Let's think about the body of Christ. Let's live these last days passionate about the King and the Kingdom and its people and the Jewish people. So we thank you today for joining us as we are praying for Israel during this time of Hanukkah. So we say to all of our Jewish family and friends, happy Hanukkah. And shalom. And we say to all of our Christian brothers and sisters, peace be to you and Merry Christmas. We'll see you again.