So, yes, welcome to this week's CMT markets charting analysis webinar. Got the risk warning on the screen here. We'll just zoom through that. Any questions at any stage? Best way to just send it through the chat window. You can do it to all publicly, or you can just send it privately straight to me, either way it works. And then I can address those as we're going along or just cover them at the end. Quite a busy week ahead of us, actually. There's a few things going on. We've got a fair bit of Chinese economic data coming out. Obviously, China's been one of the major headwinds and it's slowing economy this year. Those concerns seem to have abated in the past few weeks, but this is quite a flush of data, including the GDP report this week. So that could change things. It's unlikely to because China's currency has become more stable. Obviously, we have the offshore rate. It's not as liquid. It's a bit harder to trade than some of the major currencies, but the default is the dollar C and H pair here. And you can see that after depreciating rapidly, it's kind of come back in line and it's at the lowest levels this year at the moment. It was those currency concerns that were biggest concern about markets and it was the slowing growth type dynamic that kind of exacerbated that, but not by itself. China's economy's been slowing for a while, so there's nothing new this year. It was this sudden ramp up in dollar C and H and dollar C and Y, the onshore rate that really got people worried. That's pulled back largely because of dollar weakness and so those concerns are off the table at the moment. And that dollar weakness has helped a lot of things. Obviously, all prices still very much a factor. We're back up above 40 in Brent. This week we are a bit less in the way of central banks. We've got the Bank of England on Thursday, so Cable looking a bit hairy today despite a lack of economic data really driving things. The political situation is actually playing into Cable more than it normally would. When I say Cable, I'm talking about the bridge bank against the dollar obviously. And it's the beginning of US earnings season, so we saw a bit of a pullback last week in US stocks, one of the biggest pullback since we put in a low in February. We'll have a look at the S&P and the Dow, Gengen II or our versions of them obviously. And we'll see what the dynamic is there. The US market's been pretty solid given the fact their expectations have been paired right back in terms of how much US companies are going to earn on aggregate. So today we've got Alcoa reporting, that's a sort of unofficial kickoff of US markets. But earnings expect to drop about 8% year over year. But nonetheless, we're at multi-month highs, highest this year in US stocks. I'll pull up the old, since I've talked about that, I'll pull up the S&P at the moment. Still that's a weekly chart. We can see that we're still inside our range and we're at the top of the range. Again, a lot of that because of the weakness in the dollar because of a bit more dovish Fed policy, only looking at probably two rate hikes this year whose consensus. And these lower interest rates are basically what a lot of these market gains are built off. So that's been positive for markets and obviously a week of dollars being positive. Commodities as well and oil was the big worry at the start of the year too. So as I mentioned in the update here, on the weekly chart we've had, it's kind of better when you're looking at Harami patterns, it's easier trade if the inside bar is small and the first bar is long. Now the first bar is quite long here but the second bar is also pretty long. It's basically kind of matched the first week, closed off the lower bit, but a pretty similar trading range. But nonetheless that's a Harami pattern basically shows that we've sort of stalled basically these two peaks from December and we're coming into the top of this trading range which I've just kind of used these two major peaks here. It's the final top and these two, three troughs down here to the bottom of it and we're running into the top so the closer we get into this declining trend line and then this area up here, the bigger the risk is that we eventually roll over and that could have already begun to happen down here but it doesn't seem to have been the catalyst yet. There may be, as I said, there's quite a few things going on this week, not least of which happens on Sunday where we've got the non-OPEC producer meeting talking about a possible freeze in oil production mainly with Saudi Arabia and Russia. If that kind of fizzles out and doesn't do anything that could mean there's a roll over in oil prices and stocks and oil have been pretty well linked this year and so that could be the trigger for us rolling over here. I've got this little line here which doesn't mean much on the weekly chart but say if we are looking for a breakdown of this inside bar, kind of inside bar more like a Harami pattern. Harami, by the way, just looks at the Japanese candlesticks, just look at the body, the candlesticks. So this body fits inside this body whereas when you're looking at traditional Western bar charts you're actually paying attention to the highs and lows so this obviously made a higher high so not actually an inside bar. If we got down to the daily chart, here we can see if we hold this low from Thursday, if we hold higher today, that will be a swing low with two high candles on either side. So then one trigger we can look, this is the weekly low marked by this candlestick. So I dropped through this rising trend line and this low here could be the first sign of a possible breakdown which triggers the end of this strong uptrend that we've been in since February. The Dow Jones looks pretty similar. The equivalent trend line has arguably been broken although you can kind of mess it around a bit and change it here and it's less broken. But here's the top of the trading range again and here's the peak up here which we haven't quite got to. Here's an equivalent sort of trend line here so it's just if we're looking for the market to break down what's going to tell us it's happening. You can see this trend line holding up quite well. If we go down to an hourly chart it'll be a lot more clear cut. So we're heading into a big long-term resistance area and we've got a trend line supporting us. If we break down below it, of course it could be a false break and you get knocked out of the trade but pretty favorable risk to reward if we do reverse this long trend that we've had because we've come pretty much straight up. So you'd imagine in the case of the US-30 here this was support didn't act as much resistance but a little bit. We've got a bit of a pullback here then broke the 200-day moving average and went up right up to the trend line. So you can imagine we might actually get back down to this 200-day moving average and this old support and resistance and support again but if a pivot around basically around sort of 17,000 mark-ish. So something to look out for there but obviously for the moment we're just looking at hypotheticals here. The trend is still higher but you can see here we've got a bit of a double top in the RSI and Menton's already rolled over and so potentially depending on how these different events take place this week we could be looking at a little interim top in the market. Let's switch over to UK stocks this week. Sorry, it's next. Been an incredibly tight range in the FTSE 100. Basically between the sort of 6070 and sort of 6200 to 210 is pretty well defined in the market. You know, it's plain as day to see. It's this tight range here. As of today we just hit that 200-day moving average which could be a trigger for a few people to sell. To me the bias here is probably the fact that we haven't been able to push sustainably above the 200-day this seems to me more likely to resolve to the downside but maybe not right down to retesting the lows. Maybe just down to 5900. Maybe retesting this broken declining trend line here which looks a bit better on this. I'll say it doesn't actually look better there but you can see it's basically these peaks through here that I think I've lost a bit there. Using these peaks here you can see a false break, false break but then it works again, works again. So maybe a retest of this line to then push higher. At the end of the day we're not in a very trendy environment in stocks at the moment. So if you've caught a breakout trade and just sort of riding the trend higher obviously wouldn't be the case in the FTSE at the moment. I think you've got to just be aware of the fact that it's not likely to run that far. Since we bottomed in August you can pretty much say that we've been in a choppy trading range with no real nicely defined trends. This was the best we got in terms of a downtrend but it was incredibly choppy, incredibly wavy. It took a long time. If you'd sold the break down here it would have taken a hell of a long time just to get you down here. European stocks looking distinctly weaker particularly than those in the US. Just looking at the Germany 30. Here you'll see that it's a bit of a kind of use of you almost say matching the indicator to where the price is reversed here but you will find that sometimes when you put in a low and then you push higher then you try and get through that low again. That's basically a false break down there so actually the true low is this original one. So then if you take that up to a similar thing at the top use that as the peak and then this was really just a false break at the top of the top and then we've got kind of a triple top in the end and rolled over. Then we find ourselves down at this 50% retracement mark here and just above the previous swing low for March. So basically failed to break above this 9,900 level several failed attempts and we eventually rolled over which is what I sort of suspect might happen in the 5100 where we basically haven't been able to break higher and you resolve down and then you push up a bit. Not a massive amount in terms of notable UK earnings except probably the front and center will be just on Wednesday. We've got results from Tesco's and a couple of other retailers scattered around on Wednesday and I think Thursday too. Devinum's also reporting but just like today it's going to be the miners that really kind of dictate the state of play. That obviously rests a lot on the oil and metals prices and also the banks. Banks are doing well today but they had a bit of a rough week last week kind of following suit with what's happening in Europe. The fact that the ECB in their minutes seemed to sort of apply that more rate cuts into the negative was a possibility if inflation doesn't pick up and so that's a worry for banking profits because they just can't... Obviously if interest rates are 10% and they're charging us 10% and they're paying 5%, they're making 5% if interest rates are half a percent and they're charging us 1%, that half a percent is not as good as that 5%. In very simplistic terms it's just not a great time for banks and negative interest rates makes it even harder. They're being charged while they're actually not charging us for the time being at least on our deposits. Obviously the big one last week if we switch over to currencies was the Yen. I hope some of you are in the Dolly Yen trade because we've been pointing out for a while in my last week's snapshot video I pointed back to our video from a month prior which talked when we were up at about 117.50 talking about 116 being the big level and then down from there a possibility of 105 and so from 117.50 we're down one big handle from there. We're at 108 now so let's have a look at that chart of Dolly Yen. At the end of the day if you're not on board yet there's probably some more room to go on this but realistically when you decline eight of the last nine days and you take out 900 to 1,000 pips obviously we saw worth here so if you take this as a kind of bare flag with the pole, the flag and another pole then we've got a bit more room probably down to about 106 but still they've been trained as a bit old at this point so I would say that maybe just this quite strong reversal that we had on Friday suggests that there's still a fair bit of selling momentum we haven't quite followed through on it today though obviously putting in a kind of little minor double bottom on the short term short jump chart but this is the weekly chart that we've been referring to for a while the 116 and the big breakdown level basically a head and shoulders pattern with a nicely retested trend line and obviously if you sold at the broken trend line that's just textbook and if you held it down to here and even if you hold it down to the 105 that's down to this support that literally is a textbook trade I think if we can close the week back up with 110 and then also to some extent just 111 which had been holding up the price in that consolidation that we were looking at on the daily chart then you probably don't want to be as aggressively short but for the time being the trend is well down it has a little bit further to go but you're going to have to be careful because there's going to be some short covering rallies the big fundamental point is will and if so when will the Bank of Japan intervene directly in the currency market and actually start selling yen, buying dollars and pushing this currency pair higher my sense is that there'd be unwise to do so at this point I mentioned this in the morning comment which I'll be doing this week instead of Michael Houston that I tend to think that the Bank of Japan are comfortable with the they've mentioned specifically they're comfortable with the exchange rate above 100 and I think with this kind of momentum against them at this point they would risk losing face if they intervened and it failed so they have a bigger chance of success if for example not so much you and I but big traders jump on board shortest dolly yen pair around here so if they're short down at 108 and then we get down to below 105 and then there's a big squeeze 300 pips higher there's suddenly those people short at 108 they're offside the people at 116 short from 116 they're still sitting pretty at this point and if we have the short squeeze from here from 116 even took us back up to 113 those people short at 116 they're not going to be flooding out to the market they're able to hold on they're sitting strong at a higher position so you need from the Bank of Japan sort of trading dynamic perspective if that's a word if that's a sentence is to wait for a bigger drop so you're able to squeeze those weaker hands when you do intervene you know you need the price to drop further more people to get in short at lower prices to be able to squeeze those extra people and really create a big price and even scare everyone else out of the market as well I don't think that would work at this point but you know see what happens it couldn't happen this week I mentioned the note in the first few days of this week it's not really happened today but maybe tomorrow, Wednesday if we get a big push down below 105 then they may be tempted to get drawn in just because of the speed of the descent the British pound has been the other big loser so Euro sterling being the big gainer it's dropping off quite hard today if you'd been following my chart forum posts and my Twitter posts I'm using this level and it's actually working out a tree at the moment and you can kind of see why so here was the low back in July of 2010 and then that corresponded nicely with the top of this consolidation here in September 2014 and we came up to that level and we have that kind of pivot point and we also have the 61.8% retracement of this entire decline in that same area and there's also the it's also not far above 80 the round number so we'll push them right into 80 now but this was around 81 just above there is this particular pivot level so 81.50 I believe there's if you connect I don't like it because I feel like the trends already extoller should away from here but there's a trend line down through these highs as well was it these two maybe that did also point to a resistance around this sort of 81.50 we've not got there this 61.8 has worked pretty nicely for the time being we may still get to the 81.50 for maybe the final top if these people getting short now get squeezed out of the market with another little push higher but here you can see quite a big drop down in your pound today and it's mostly sterling strength you can see the same thing happening in pound dollar maybe just as there was a bit of political risk last week Cameron was in a fair bit of trouble looks like he's going to get through the storm as of this week introducing some new plans to crack down on the wealthy using tax havens you might have a bit of a rough ride in this Wednesday's parliamentary questions but looks like he's going to be okay and probably won't dense the Brexit the sort of remain campaign too badly and the only reason I mentioned that is because politics only really matters when it's felt that it could impact where the Britain stays in the Eurozone in Europe so in the European Union so this is a good trend and if I just shift this little line up here this is some fairly clear cut resistance down at 79.30ish so look for a pullback into the area and if we do have some sort of reversal candlestick in that vicinity depending on your trading strategy whether you're waiting for a reversal candlestick or short term momentum change or whatever the case may be that could be the area to get involved if we get right down to 78.40 again near these lows at the end of March my feeling is that probably that's this rise done for the time being and we move back into a more sort of sideways choppy market but as mentioned sterling one of the big movers today up 120 pips and that's just this support level working fairly well depending on the tightness of your stop this is an example where okay you bought at two previous obvious supports if you had your stop under 140 which is the sort of round number support even better if you'd bought down or just pure the round number wouldn't have been such a solid case for doing so you can see this rising RSA trend line backed up by that pretty obvious horizontal support has worked out nicely so if you had your stop down here you'd be well into two times risk on your reward back up here and this line that I've got and just pertains back to a super long-term support over there but we're range bound at the moment I think there's probably a good chance we'll push up to 144 again but to obviously say it's been a big move higher but I suspect it does continue up to 140 just because that's the nature of the trend at the moment it's just a less it could of course it can always happen but there's just less chance of a sort of pullback trade working where you know we're here we pull down and then maybe we're back about 50% at this point so here we are perfectly at 50 pretty much let's drop the time down a bit in my experience we may get a bit of a drop from this area because it's half of that decline but what's the context? that decline is just within a trading range so that's the bottom of the range this is the top of the range up here near 144, 50, 145 so why would you sell the we're not in a downtrend where you're selling a 50% retracement expecting the downtrend to continue of course it could but it's much more likely we just pushed to the top of the range again so a lower probability trade in my mind I'll try and remember saying that for next week's webinar and see if that proved true or not so I'm mumbling on a bit this webinar so coming to the end of it we're just going to cover some commodities if there were any kind of questions then feel free to let me know and I can always expand the length of the webinar a bit crude not doing much today but you know we basically came off today's highs because you can see a fairly clear cut the August lows have worked as support three times they've worked as resistance once and they appear to be working again and to my mind not much likelihood of pushing much beyond 42 this week ahead of those Doha meetings on Sunday unless something gets leaked unless some sort of freeze is pre-announced which is possible but I suspect probably this week we're just going to get a mile drop back and all prices down to around the 40 level on Brent because there's not really much else to drive it even if we've got another big draw in weekly inventories from the US still how aggressively long would you realistically want to be before you know the result of those meetings between Saudi Arabia and Russia because that's a game changer you know if anything you know you basically use a bit of chart positioning to take an uneducated guess on what they actually end up doing in that meeting you know you can go short right in this kind of vicinity just with the hope that they don't agree on anything and all prices drop again on the idea of oversupply or you could wait for a pullback back down to maybe 38 or so if we can get that load this week on the hope that actually they do agree something and so you're selling resistance or buying a support before a fundamental event that maybe works out your way or maybe it doesn't but if to be buying up here you're obviously buying right before major resistance which is generally not a great idea we do have too much time but I did want to kind of touch on silver and copper which I don't normally do so gold is up big today let's just quickly look at it it's basically running your right into 1250 at the moment finding some resistance from 1250 we had a big reversal from 1250 on the 24th and Feb seems to be kind of in that reversing from that same area at the moment struggling to get through it above that we've got this quite big reversal from 11th to Feb that 11th Feb top in gold wasn't quite the top we had a few false breaks above it that matches the bottom in most global equities so gold trying to push below push part beyond that sort of risk-off peak which goes a bit counter to most of the equity markets being well away from it their respective equivalent lows so even if we peak here or if we do manage to push up to 1260 still a bit of a risk of a very choppy looking head and shoulders pattern that could eventually break with about 1200ish being the or maybe 1210 being the neckline bit choppy really to really call that at this point silver was a bit more interesting just because I've scrolled out my daily chart a fair bit here because we have this trend line where we had a false break went all the way down and successfully tested the 200-day moving average got a false break through it held it, didn't go as low as the previous low down here and we pushed right back up to this trend line again so don't get too distracted by the trend line but the trend line seems to be working where it's pausing where we are at the moment the 200-day moving average as well and holding above that previous low bit of evidence suggests some underlying strength in silver but still the caveat is that we're in a range bound market with about 1480 I would say that low that we just put in is the bottom of the range and it's 1595 to 16 being the top of the range so really to be very confident that it's breaking out to an uptrend you don't want a nice solid close above 16 but obviously that's a lot later in the game than we are at the moment this would be much better entry price down here if we can get a close above the trend line it's just not as certain of a directional move equally in copper we also had a kind of downsloping trend line which was pretty well defined and we've dropped right down to retest it here and it's also the 61.8% retracement of that pickup of the lows so not a huge reaction on the first test doesn't bode well nonetheless we've got these lows down here so maybe a confluence of Fibonacci previous lows and broken trend line support could be enough to trigger a rebound in the price of copper maybe Hibiki and I in the RSI we're pretty oversold if we can come out of the oversold territory maybe a bit of confirmation of those technical support levels okay that's it for this week's analysis this week's webinar much appreciated the signing in I hope that was helpful and good luck with trading this week and see you in the same time next week thanks very much just a lot of signing out


good morning another day is here they just keep rolling around the corner don't they it's gonna be a good day got my breakfast i met my loading appointment there's a crane loading up those two cylinder things right there gonna oh why am i eating hair why was that no i'm gonna get this stuff on the trailer we're gonna tie it down we're gonna fly it we're gonna tag it it's supposed to be a little bit oversized we're gonna take it to wisconsin let's see where's it going in wisconsin i know this grand rapids oh so i'm right grand rapids it is going to know what's coming from winnipeg going to wisconsin rapids wisconsin how far away is that from here let's find figure this out go go google me google me hey what i said grand rapids grand rapids grand rapids wisconsin rapids wisconsin rapids no not grand or oh come on grand wisconsin rapids no how about just wisconsin rapids choose start location how about my location that google's being difficult this morning can you ever do this to you oh it's a thousand kilometers with 600 miles full day's drive oh yeah so we'll be unloading tomorrow morning i think i'm taking both of those looks like it's going to be a really easy load to tie down no idea what it is looking at my info i've got on my computer here says that it's two filter vessels with feed chambers 3800 pounds each light load doesn't really matter to me what it is i'll pull it well this is disappointing this is only day two of having these lights on there and there's already moisture in there you're gonna be kidding me you see that that's disappointing to see on the second day after installing them but i remember there being an option to get rid of that there's a seal in the back a little plug you can unplug you turn your lights on i think they said for half an hour to an hour or something i'll have to look at the instructions again you you sort of unseal the chamber i guess and then you let it all evaporate out of there so there is a way to get that moisture out of the light at least there's there's a way there's supposed to be a way i guess we'll find out when we actually get to the shop i'll give it a few more days to see what happens but uh i really wasn't expecting moisture to get inside there so quickly those are supposed to be sealed units right i think maybe it's the weather i don't know i'll see what i can do and uh i'll keep you updated on the lights the lights were $179 canadian so pretty cheap 180 bucks it's probably what 150 bucks american for all four got them on amazon and they're really bright the dot proved really bright uh that i really like them i just uh i hope that moisture inside the bulb is not going to be an issue i'm just glad that they sort of offered a way to get rid of that just if it works so when i get back to the shop uh in a couple of days here i'll pull out those instructions i'll show you how it works and i'll give it a shot see if that'll see if that'll work i don't want to do that every week though that's the thing it's only been a day um maybe it's just the weather it's been really it's been kind of warm and then it got colder and then warm and then colder maybe that's why ready to go button down flagged and tagged my oversize load size crooked oh no you gotta fix that no this side can't move that's that the license plate better pretty close and i say they were 6800 pounds each they're 3,800 pounds each i don't remember what i said if i said it right the first time now i've told you twice 3,800 pounds each it's going to wisconsin rapids i gotta figure out if there's a delivery appointment they're probably going to need to unload me with a crane well this thing just turned out to be a big parachute the wind is coming from directly almost directly in front of me i'm coming over there and it is catching every single molecule of it up to 20 psi just steady said this is going to be a ooh it's going to be a high fuel day we use lots of fuel until we get on die 94 we start headed that way towards minneapolis hopefully the windows sort of be a little bit more at our back then straight south right now just what at the border straight dollar bills so i'm in grand forks north dakota the sun's gone down and i can't move after dark with an oversize load so i'm at a pretty good spot i'm in the front row here or near the front right by the flying jay and this is where we're going to be sleeping tonight we had a few delays on our trip today so i wasn't able to make it further than this i was hoping to because once i get into minnesota i can uh i can keep going into the night if i have the edges of my load uh lighted up properly right for an oversize load according to my permits and in wisconsin it's the same thing but north dakota no oversize loads at night not on my permit anyways so we had some delays here we got held up and uh the sun disappeared on us like it always seems to be doing lately disappears way earlier than we want it to and ran out of daylight hours so this is where we're staying for tonight until the sun comes up so vlog got cut a little bit short but my day got cut short as well this is why you know oversize loads are nice uh they do pay better obviously because it's a bigger load more responsibility right but at the same time it's kind of frustrating when you're in north dakota and the permit doesn't allow you to drive at night even though it's north dakota and everything is wide open there's nobody here the roads are super big and wide four lane divided freeways but that's the way it is so we can't change that i just talked about it on the internet maybe they'll change it trying to get my bunk heater to work properly again tonight i'm having issues with it again i think i'm gonna need to run it through another cycle uh for a few hours on high with straight kerosene one more time to see if that'll work because it worked pretty good and it worked for a couple of days now it's going back down to sputtering and not wanting to not wanting to heat my truck it's kind of annoying because it's acting different this week than it did last week now it heats up and it runs for about an hour or two so you forget about it you're all nice and warm and comfortable and then all snitches silently just shuts off without telling you just stops working and you don't notice it until you're like suddenly you're like why am i getting so cold i've got no kidding the bunk heater's turned off who knows how long that's been off for so i'm probably still gonna have to bring it in i have an appointment excuse me oh i do have an appointment to get it done i was just hoping to be able to fix it myself and not have to bring it into them we'll see we'll do another round of kerosene and see if that does anything is what it is it saves me a lot of money so it's worth it to get it fixed costs a lot of money to idle your trucks through the night uh with the cost of fuel especially and the wear and tear on your engine oh it's it's expensive to expensive to idland it's turning itself back on now now you want to eat make up your mind it had turned off there for a while no i think it's turning itself back on i have no idea what's going on i'm too tired for this i'll see you tomorrow we're gonna be driving from here hopefully and get all the way into wisconsin maybe even get delivered tomorrow afternoon yet but uh we got held up a little bit now we'll see what happens tomorrow so tune in don't forget to subscribe and make new videos every day be safe out there on the roads please we're all trying to get home to our families just take the extra time deep breath believe me i'm just as frustrated as you are at the drivers out there we all just we all just got to get home don't do anything crazy okay keep your stick on the ice which is canadian for pay attention be ready for anything


As we embark on our new financial year coming up as today will be our first vote on our budget where once again we're investing heavily internally at the city. We're investing in our employees, we're investing in technology, we're investing in training. We'll continue to do that as we get ready to embark on Finley Park starting as we're making investments in Greenview Park and Maze Park, Hampton Park and Owens Field. Finally getting those fields that people have been asking for and being able to do it but also investing in citywide art projects, neighborhood art projects, little libraries, doing things to improve the quality of life of both our citizens and our employees and we're so excited to share that with all the visitors who are going to be coming to see the great things being done in our community.


It's gonna be a 1959 Super Fracture, Rikki Otto of Corbin, Carol. Dude! Oh, there we go. Rookie stars of 2023. Dude, that's not Jeffery. There we go. Mr. Jeffery H with the 59 Super Fracture. Otto, it's Corbin. That's one of the bigger ones I think we pulled. That is beautiful, man. I love that design. Congrats, dude. Sajae sick one there. Congrats. That's awesome. Shady always guesses the Corbin Super. That's true. That is true, Shady. Does not count, unfortunately. There you go. Jeffery nice one. The two one-on-ones were the two Rikki of the Years. Yeah, that was also Joe asked earlier, like a couple minutes ago, if we take Corbin or if we take Gunner. That's pretty funny. Got them both. There we go. Jeffery sick hit there on the 59 Super.


Welcome, everyone. My name is Piotr Pawłowski. I'm from Poland. I live in Kraków and I'm currently studying at AGH University of Science and Technology. My project was to extend Hyperledger Iroha queries with optional arguments. My mentor was Mr Grzegorz Baziór and we used Hyperledger Iroha 1.1.2. Iroha is an open source blockchain coming from Hyperledger Greenhouse. It differs because it uses no native cryptocurrency and it's not open. It's basically a permissioned blockchain so you have to have necessary permissions to join it or to access some data, especially making some transactions or querying, you have to have necessary permissions. That's how it differs from other public blockchains. Iroha queries, so get account transactions and get account transactions are giving us all the transactions of specified user. So, in the first one we get all the transactions and in the second one we get only this regarding some asset, the asset we specify. There is also pending transactions, so in this query we can get all transactions that are still not accepted, so they are not saved in blockchain. And my main task was to modify these queries so we can query for transactions in given time range and in given height range. But there is a small difference in get pending transactions because these transactions are not yet saved. We can only query for time range because they are not given height in blockchain. So, in order to achieve all these tasks I have to get known with Iroha codebase. I was quite new to blockchain so I have to acknowledge myself with, generally speaking, blockchain architecture, how it works internally, what technology is being used and all the technical things. I also have to learn protobufs because we need to make a new protobuf message, send it to Iroha, then it was validated and then executed on the database used there. We also have to provide tests, documentations and examples in client libraries. There are actually quite a few of them. Okay, and deliverables are mainly the same as on previous screen. What is worth mentioning that Java Strip library and Java library was quite new to me so I have to learn a lot to modify these libraries. But yeah, everything went well. We accomplished mostly all the tasks specified before, so queries were extended with these arguments, time and height range. Client libraries were modified and provided in examples so now everyone can see how it works and how to use it. We modified the documentation on the official docs site of Iroha. And additionally, this was not planned at the beginning. We added these queries to Barrow integration. I also managed to add some new comments to Barrow. They were not integrated before but some other mentee tried to do it. He did not manage to finish it on time so I made it as an additional work. It was quite a developing experience. So now we can use almost all Iroha comments in smart contracts because Barrow is an integration into Iroha that enables us to use the smart contracts written in solidity. Are you hearing me properly because I hear something in my... Yes, we hear you. What is still not done is that Iroha iOS library is not provided with extended queries. But there are some news from Iroha Core Team that they are already working on it and it will be provided in next release. So probably in a few days. If you are curious about my work and want to see results physically, you can go either to the wiki page where everything is written and you can see it there. Or you can go to GitHub and see the pull requests with code. There are quite a few of them. Yeah, I also gained some insights into working with open source community. Iroha open source community is not a big one but it's really a living organism and everyone here is engaged and working really hard to do his job the best way. Yeah, you don't have to be afraid to ask for help. It was great to have a mentor who was always there waiting to say some good word. And also it was a great opportunity to develop both social and programming skills because you have to make many new contacts with people all around the globe. So you have really to have the soft skills. I think that's all from me. I want to say a big thank you to my mentor Mr. Grzegorz who is with us today. He was really helpful and showed me some directions in which now I can develop. Also I wanted to thank the Iroha community. All of them developers and the people from community organization. They were also a big help and I appreciate them. Thank you so much. It's great to see all the accomplishments. So such a short period of time and your mentor has been, even though this is the first year that he's mentoring but he's actually mentor multiple mentees and done a great job. I really appreciate Grzegorz's contribution. Do you have anything to add. Yes, I can say that Piotr was working really hard and really good. He managed to make basics functionalities faster. He also made much more and also it's not everybody can do everything in that many technologies in that short time but Piotr touched lots of technologies during those free those. Thank you Piotr. Okay, you are welcome. Thank you.


All right. Good morning, good evening, good afternoon, wherever you are. My name is Jason Shepard. I am the VP of Ecosystem at a startup called Zedita. We actually have a project within LF Edge under the Linux Foundation umbrella. Our goal is to build the Android of the IoT Edge, and I'll talk about that as we go within that project. And then I'm also a board member for LF Edge, which, like Cloud Native Compute Foundation, is a collection of complementary projects. And our whole goal as an overall organization is to harmonize across these open source projects, you know, necessarily different focus areas across this edge continuum. And I'd also highlight to stay tuned for an Edge white paper that's coming out soon from that community that we participated in with the community, and so it really helps to clarify things. So we'll actually do a little start by doing a little preview of that from that white paper.  No, it's a continuum. And so we're going to see, you know, the spectrum of compute across the landscape from sort of the constrained devices that live in the physical world, you know, where people are in operations and processes and vehicles and you name it machines, to, of course, centralized data centers in the cloud. So this diagram is from the LF Edge white paper. And it really kind of talks through what this continuum looks like. And, you know, it introduces concepts that are absolute inherent technical tradeoffs, inherent logistical tradeoffs, versus using these loaded terms as I call them, which is very common in the industry today. And this is why there's so much confusion about Edge computing. Today, the, you know, you've got people saying, oh, it's near Edge and far Edge. That's a common explanation in the telco world. It's thin and thick compute. So kind of like a gateway versus like a server on-prem. And, you know, that's fine. We're always better off to have very clear terms. And of course, this is just, you know, language and whatnot. And what matters is that technology is in the outcomes that we're delivering for, and customers, and enabling for open source collaboration for those foundations. But it helps to get on the same page. And so this continuum, if you look at the right side, you've got the centralized data centers in the cloud, you know, massively scalable. You know, for the big public clouds, there's tens, and you call it hundreds of those kind of resource pools. You've got the internet Edge, and then you're seeing more and more compute moving left into, to be closer to the devices and users that need those resources. You know, we define Edge computing as moving compute both as close, or as close as both necessary and feasible to the resources that need it. In a perfect world, we put everything in the cloud, and you get the benefits of centralization and the scale factor and all that. But there's a variety of factors of why we're seeing a need for more and more compute closer to the physical world. You've got, you know, certainly regional Edge providers that are providing, you know, CBN networks, content delivery networks, and even the clouds are moving on the other side of the internet Edge to run data centers here to get a hop closer. We're seeing telcos, wire line operators, service providers in general, creating more compute, you know, literally a modular data center at the bottom of a cell tower to feed up stuff. And to users, like, you know, online video streaming is an example of that, so that we reduce the latency and congestion on the upstream networks. So you just see the spectrum and we'll get into kind of the user edge in a second. But at a top level, the service provider Edge and the user Edge are the big categories that we have. And you notice that there's a bleed here with this angled line. If I'm a service provider and I run equipment on-prem, like in the form of customer premise equipment, CPE equipment, then it bleeds into the user edge. And I push that last mile network boundary even further into the on-prem scenario. And if I'm a user, you know, enterprise or, you know, in this case, if I'm an enterprise end user and I run a private data center up here on the right, then I'm basically bleeding into that right side. And the important delineator between these buckets on top is this last mile network. This is your cell connection, you know, satellite, if you're out in the oil well or mine somewhere, you know, out in the ocean, it could be wired connectivity, et cetera. The reason why, as a community, we define this as a top-level delineation in the taxonomy is that there are certain things you just will never do over a wider network, even if your network is super reliable and super fast, like, you know, say it's a 5G network.  Anything that's latency-critical will always be done, you know, locally. Anything that's latency-sensitive, you tend to want to push upstream to take more advantage of the economies of scale from these other edges. So the paper that will come out next week goes through great detail in how this breaks down, but the reason why I'm running through it makes it really clear where Eve plays, you know, what we're doing. Once I get to the user edge, now I'm on the other side of the last mile network, everything just continues to get more and more complex, more and more custom software, more choices for protocols and hardware and OS and, you know, form factor types and unique certifications and everything. It's pretty standardized infrastructure on the right. Not that it's trivial, you know, there's a lot of great innovation. Of course, Kubernetes has taken the world by storm on the right and it's kind of moving more and more left, including into on-prem data centers. So that first tier, sub-tier under the user edge, these are data centers that have been on-prem for a long time.   You're limited by power and cooling and all that. Not going to be as scalable as the kind of the nearly infinite scalable in the centralized cloud, especially with the public clouds, but it's still, you know, good level compute on-prem on this side of the last mile network. So your latency issues are less of a variable, you know, of course, 5G, there's a lot of great things that are going to happen there. Big difference, though, between this and the other edges is that it's still in a physically secure data center. I'm locked up, you know, whether I'm in a traditional data center or in a micro data center, these are secure locations. The next tier over what we've called the smart device edge in this taxonomy, this includes both IoT type devices, you know, gateways or even a server on a factory floor or out in an oil rig somewhere. Headless IoT components. And then you, of course, have PCs and smartphones and client devices in general and tablets, whatever. PCs and smartphones, very well-established ecosystem. Of course, we've got Android and iOS in the smartphone world. You know, these devices in the smart device edge, anything, whether it's IoT or client side, two characteristics that make it the smart device edge. Number one, I am outside of a physically secure data center. I could be in a closet, so semi-secure. I could be just sitting, you know, out in the wild in your pocket. You know, in the case of a phone on a IoT gateway sitting, you know, in a building somewhere, like in the closet or, you know, out in the open. They're physically accessible. So now you have to have unique security needs that you're not necessarily considering around, you know, the data center. You have, you need to have like a zero trust model to where you trust nobody. So you start to, you know, build trust relationships with various different entities. The scale factor is getting bigger. You need to have things that run autonomously, regardless of whether they're connected to the Internet or not. You know, you could have a gateway and an oil rig or some sort of server on an oil rig that you lose this connection for days, if not a week. And it needs to run autonomously while it's, and then whenever it can phone back home the central controller, it gets any updates it needs to have. So just different needs, you know, at this smart device edge and, you know, IoT components tend to be upload-centric. I'm getting data from the physical world. I'm doing some preprocessing here at this edge and I'm moving it up for further processing upstream. And then client devices, you know, like phones and TVs and PCs, they tend to be download-centric. I'm downloading content. You know, of course, if I'm doing cloud-based gaming, I'm kind of, I need latency that's low either way. So, you know, it's just outside of a physically secure data center but still capable of running apps and abstraction like virtualization or containerization. Once I get to the lower side of the smart device edge, I get into the constrained device edge. Now, this is basically, I'm out in the wild, I'm microcontroller-based and I'm so constrained that I can't run apps anymore. I'm doing embedded software. You know, this is over-the-air update tools that are almost custom for every piece of silicon.  You've got folks, you know, like, founders.io that's doing that in the open source sense and there's a lot of, you know, cool stuff happening but it's really, really messy here. But if that smart device edge, and of course on the further ones up, you can create abstraction with a small tax. You can create abstraction with things more platform-independent. So, you know, I know this is a lot of setup but really important stuff and again, the paper gets into great detail. So think of Project EVE that we'll switch focus to, you know, this is, you know, do for the IoT edge as part of that smart device edge, what Android did for the mobile component of that smart device edge. Very fragmented. You need to be able to support all of these different technologies. We want to create within this project, a universal abstraction engine for this type of edge compute hardware. I'm not going to say it's just a gateway. It could be a gateway, it could be a server, it could be a hub, a router, any kind of hardware that's capable of supporting, you know, an abstraction layer. And then, of course, on top of that, you run apps in the form of VMs and containers. You can think of this spectrum as 256 megs of memory or so, you know, that's what we aspire to. Below that, you're starting to get so constrained to embed it, and devices over here could have kilobytes of memory, you know, for sure. 256 megs on a single node of memory, you know, give or take maybe 512, up to a small server cluster. Now we have, you know, Kubernetes is coming from down here, down this way. There's great work happening with K3S out in the market. As a project, we started with the kind of sweet spot of the IoT component of the smart device edge, you know, Project EVE, and we're bridging up to the Kubernetes space. Now, very important, too, is to not look at it as Kubernetes, you know, is going to carte blanche, just get dropped on these more constrained devices outside of a physical data center. What we'll see is a subset of the key capabilities that make it attractive, like clustering and stuff like that, but you're not necessarily going to see a one-for-one relationship. There are just different needs across this continuum, and it's about finding the right balance. And so, again, check out the white paper. It's really, really good read, and it really breaks this down into inherent trade-offs that you can't change versus using loaded terms.  I mean, it's fine, and we talk about that. We kind of map those terms. So, near and far, if you've ever seen the Sesame Street, you know, with Grover, and he does like near and far, you know, I kind of joke that these loaded terms are just confusing and whatnot. So, anyway, so that's where we play. We play at the IoT component of the smart device edge. You do for IoT what Android did for mobile. So, a big part of LF Edge, this community of projects, I think we're up to nine projects, you know, now. And a big part of this is all about how do I create various different levels of abstraction within the landscape? You know, obviously open source, in general, is about a shared technology investment. You know, we've partnered with Linux Foundation for a long time on various things. We've helped with a team at a project called Edge X Foundry started with it, which is also now within LF Edge. You know, it just hit five million downloads, and we started with a blank sheet of paper in 2015. And that's just an example of the power of open source. Of course, Kubernetes has taken the war by storm. It's just super awesome stuff there, and we look forward to bridging, you know, Eve to that story with the right considerations. LF Edge as a whole is a collection of projects that are all about shared technology investment, minimize for end users, developers, et cetera. You know, the undifferentiated heavy lifting that's happening out in the market today. So we can all focus on value. You know, drive interoperability, drive these various different layers of abstraction. I'll talk about how this is important to get to the real-time potential. Just because you can build stuff on your own doesn't mean you should. You need to be part of a bigger open ecosystem, and you need to be able to have choice in this market. And so these are principles for IoT Edge Scale. I want to abstract all these different layers of technology and services and smarts, your domain knowledge from the underlying infrastructure.  You don't do that. But in, you know, the IoT wave that came from 2014-ish, you know, till now and continues to go, but now we're talking Edge and, of course, AI and 5G and all these different tool sets. You know, of course, it's about customer outcomes first and foremost, but what we saw in the market, you know, even when I've been looking at this for five years, I've been doing this for a while, initially what happens in any new market is it's people that have built, like, a platform of some sort and attached it to some sort of domain knowledge gets that initial traction. I know more than you'd ever need to know about cold chain, you know, grocery store monitoring or monitoring wellheads out in the wild or whatever. And they built technology for the sake of just getting to data and providing an outcome for a customer, but they didn't really need to. What they need is domain knowledge and necessarily unique hardware and software applied to consistent infrastructure. And so as things evolve in IoT and Edge and digital transformation in general, what we need is a roster of pure play solutions that plug into more of a consistent infrastructure. Imagine, you know, if one company owned the Internet, you know, probably wouldn't have worked out the same as the massive innovation that's happened since the Internet really came alive. So you want tools that are running on top of consistent infrastructure. Of course, Eve is about providing that for the IoT Edge, as explained in that previous slide. In the end, the winners will be those that leverage, you know, shared technology investment for the base. Open source is becoming rapidly, the has become, I'd say, the way to drive, you know, de facto standards in the industry compared to traditional standards bodies, you know, interoperability, all that kind of stuff that LF Edge is working on. The winners will be people with the best services, the best algorithms, the best, you know, necessarily unique hardware and apps, domain knowledge, not the 100th person this week to reinvent the middle. That is not valuable. And so this is a big part of LF Edge. And so the second key principle is that you want to untether, you know, not have a hard coupling between your data and any backend service that says cloud services here, but it could just as well be on-prem system. If you take control of your data, the moment it's created in the physical world, and all data pretty much originates from people or devices in the physical world, if I decouple that from any given backend service, the moment it's created, and this is the point of EdgeX Foundry, of course, there's Fledge with an LF Edge and there's a lot of other projects. You know, Eve is about that rule number one, kind of abstracting infrastructure from the apps. If you make that uncoupling the moment it's created, then all permutations along that continuum from Edge to cloud work. You can choose to pump all your data to one public cloud. Great, they're doing awesome stuff. If that's not right for you, or inevitably you're going to need a multi-tenant Edge where you send data to multiple clouds from your data source. You maybe have different parts suppliers heading the same factory floor. You've got a service provider coming in to work with you in your building automation sense. All permutations work and you don't get locked in at that point. So this is an abstraction, you know, with some of the projects with an LF Edge that we're creating both interoperability for this and that abstraction to prevent lock-in.  Use something that's abstracted like, you know, Gmail or something like that, you know, any kind of abstracted emails. So you feel like you can make a switch on the internet if you need to, but just, you know, decoupling that Edge from the cloud. The first one's decoupling layers in the stack. This one's decoupling the Edge from any given cloud and then all permutations work. The last one is about this notion of how you architect for cloud native. So cloud native is more about how you build and deploy software, not where it's run, you know. So cloud native doesn't mean it only happens in the cloud. You know, we talk about this in the paper from the LF Edge community again, look for it next week, but with the taxonomy, you want to extend this notion of these principles. So platform independent software, you can run on any hardware, whether it's ARM or X86 based and various different capabilities across that spectrum. So of course, you know, what Eve is about creating that abstraction for that. I want to plan on continuous integration, you know, and delivery. So CI CD, you know, I need to recognize the technical trade-offs, you know, that I elaborated on in detail on that first slide, you know, more and more constrained hardware the closer I get to the physical world. I've got time critical applications. If you need, if you're time critical and you need, you know, a real-time operating system and it's embedded, you're not going to necessarily be running, you know, modularized apps on top, but you could be running next to something that is where you consolidate on common infrastructure. So we're seeing, you know, a trend there where you see kind of like soft PLCs programmable logic controllers running next to analytics apps, but that's going to transform over time. You'll see this sort of physical to virtual split between the operations technology environments, you know, that have been running for a long time, but not connected to the back end. And you, of course, the IT services that do things around the business and, you know, kind of keep things running, you know, from a data security standpoint. There is a definite evolution happening today between OT and IT operations technology and information technology. It's not to say either group does, you know, only does what, you know, one thing versus the other, but there are different needs. If there is a issue from a security standpoint or just downtime in general, there's immediate loss of production and could even be, you know, safety issue in the OT world. Meanwhile, in the IT world, if there's immediate, if there's a loss or a hack, you can, generally speaking, just shut down the IT network and sorry you can't get to, you know, your email or whatever. So you have to recognize these trade-offs. Most, many OT folks that have been running factories for a long time or any kind of process in the physical world, you know, the catch-22 of industrial IT is to connect those systems in a very segmented way. You're not going to connect your controllers right up to the cloud. You'll have network-layered layers on top, but you punch through these different systems to get data to back-end solutions, whether they're on-prem or in the cloud, and you also recognize the fact that someone might not be ready for continuous delivery of software to the factory floor, you're above those control systems today, but if you architect for it today, you're ready when you have to as people start to innovate around you. So we think it's really important to invest in solutions to kind of leverage these principles across the board. And again, LF Edge as an open-source organization, the umbrella within Linux Foundation, you know, it's driving towards this. You know, us as a private company and other companies within the landscape are working on these types of things. You know, we think that it's super important to have, like, this open ecosystem. And so that's just the basics.  So, you know, the market is just a crazy number of platforms and everyone's trying to build these silos. And great, you know, we want to start small. Let's not get crazy here. But long-term, the real potential in digital transformation is this notion of interconnecting ecosystems. You know, I've been blogging about this for a long time. You know, of course, I believe in Open. I've been working in EdgeX Foundry with a bunch of great people in the open-source community for a long time. And of course, part of the reason I joined Zdita is because this notion of, you know, another layer below, you know, like an EdgeX or a Fledge of abstraction. If you want to get to the real potential, and this is B to X to X, whether it's B to B to C, B to B, whatever, across heterogeneous ecosystems, I'm connecting between, you know, supply chain, you know, in a grocery store and the end user in their house. I want to bring insurance services into the home, like Snapshot for the home, like they do for your car. I want to do, you know, retailers. I want to enable retailers to come into the home, you know, to kind of get on a level playing field across the board. You know, any of these things, you know, businesses, you know, across the supply chain, I have multiple stakeholders. If you really want to scale this, you have to have an open foundation across all of these different, you know, forums. And for that, you must have, you know, this kind of openness and trust factor. So LF Edge is building this. There's some new efforts, trust over IP foundation with Linux foundation. I helped launch, kind of pre-launch, a project called Alvarium that we're going to be working on this stuff. You know, this is about creating competence and data as it flows across heterogeneous networks where you can kind of really develop new business models over time. granted, let's start with a small use case and whether it's IoT or otherwise apply some AI model or whatever, get started. But don't forget about the real potential because when you're cutting costs, there's a lower limit to how far you can go. When you're making new money across all of these different domains, the sky is the limit. So super important to be thinking today about how you architect. And again, like I said, imagine if just a couple of companies if not one on the internet, it would not work. We need to make it democratized and build trust in through collaboration and to do trust. Of course, there's root of trust at the hardware level which Eve builds in. We've got a bunch of different capabilities that we'll talk about. But then you've also got things like, of course, ledger technologies, renewable storage, confidential computing. There's all kinds of trust insertion technologies that you can use. And that's what Project Overium and some other initiatives at Trust Over IP Foundation is about kind of vetting. And it's just about industry collaboration on that base, building that trust foundation. And then let's go figure out how we make money around those interconnected ecosystems. So super important to be thinking about this, even if you want to start small. I joke, Holy Grail of Digital is selling stuff to strangers. I've written about this at length, you online. We've got to scale the Grail. Start small and scale the Grail is one of my taglines. So very important to think about long term. Okay, so I've already kind of explained what Eve is a bit, but again, think of Project Eve as due for that IoT edge, what Android did for mobile. So we want to make it easy to orchestrate these devices. We want to provide a security layer so it's bare metal, that lowest layer. This is all about distributed hardware out in the field. It's outside of a physically secured data center. I don't necessarily own the network. I can't trust that I have a firewall. So I need a zero trust model. I have a distributed firewall capability where I can tell, say, this app can only talk to that cloud and this app can only talk to that app on that box, et cetera. I need to support both virtual machines and containers and we're exploring stuff with the Unicernals, but lots of legacy stuff out there that's running still on older flavors of windows, maybe a SCADA system, a point of sale app in a retail store. I need to be able to kind of run that stuff. This is not about dumping all your existing capital expenses or expenditures, but all the modern stuff, it's not like you wouldn't use VMs too, but most many things now are in containers and then of course Kubernetes has taken the world by storm. So you need to be able to run existing apps and VMs. You need to run containers. You need to be able to have those security elements and we'll talk through that in more detail.  So Eva's that lower level abstraction layer and then you choose the applications you want to run on top and the clouds you want to connect to, you choose the hardware that you run on, whether it's ARM or X86 based. And ultimately Eva's really just as much as like an Edge X, it's about those open APIs that are shaped through that open source collaboration and those APIs work with the controller of your choice. And as a data, we have our own controller. We welcome anybody to go build one. We have a simple open source controller in the market or in the project and we're actually collaborating with some other projects within LF Edge that are somewhat competitive on the back end, but we're all better off if we focus on creating that universal foundation that helps to abstract the complexity and help with vendor lock-in. So there's a page called Eva on Market at the project site. You just type in project B of LF Edge. You'll find it. And it lists what hardware we're supporting. We're working with a bunch of different hardware providers out there. And then of course, as more and more controllers get added, that'll be there. But the point here is that that open API between whatever controller, whether it's on-prem or in the cloud and project B is that lower level abstraction layer sitting on top of whatever hardware you choose is that that open API is the insurance policy that you are not going to get locked into a particular controller. And then parallel to that orchestration plane, you choose the apps and clouds that you want. Eve, from the project standpoint, in our own personal company, we believe it's very important to not try to be in the data path. You're in control of your data. And of course, you want to abstract that as close to the edge as possible. So all permutations work. So that's kind of like, what is project Eve? Again, do for IoT what Android did for mobile. Layers of abstraction, support VMs and containers make it very easy to deploy. So as you get outside of data centers and you have less IT skillsets, people that are used to working with servers and virtualization and all that, you need to make it very easy to onboard devices. So literally with Eve, as you put it out there, you could install it on a box. You ship it to a location along with some sensors. The person who installs it, connects to the network, scans the QR code, and then it logs it onto the controller or whatever choice that you're using. And Eve doesn't do some of those value add. We think that's where the community comes into play. The value add of the apps and all that. That's the zero-touch easy button. But Eve has the hooks to enable that stuff, which is super important when you have a variety of skillsets out in the field that are doing field repair and upgrades and deploying new services. ARM x86, we support various different co-processors. So if you're using GPUs, FBGAs, TPUs, very important here is that there's a lot of tools out there that are coming from various different providers and you just want to have something that has a universal story so that you're not locked into any given choice. And again, I mentioned that we're striving to make it with a meaningful app running on top, down to a single node with 256 megs of memory. We're comfortable at a gig today, maybe 512, and it of course depends on what you're running on top. Raspberry Pi 4 comes with these eight gigs of memory, so things are changing. We know some people that want to run lighter memory, but there's a tax that you pay for the abstraction, which is super valuable because it simplifies things. And of course, we need to have the concept of a failover. There's a blue and green partition, so as you're updating something, it runs autonomously with the current setup. And only after you've proven that it's running after a certain amount of time, that it'll switch over and there's also multiple copies of e-burning on a given box. So it's all about uptime, which is super important in the OT world. And really it's like this IoT edge needs a standardized foundation, of course Android in the open source sense, for orchestration. It's flexible, open and agnostic. One stack that you need that takes into all the accounts that are those challenges that we talked about at length in that first slide, but done for the IoT edge. And so that's what Eve's about, and we've been seeing good growth in the community. So just to make sure that it's clear on these architectural approaches. So if you take Eve on the left, then we'll compare it to some various different choices. So proprietary bare metal, there's a number of solutions out there, good solutions, but when it's bare metal, you get benefits because you're tightly coupled to the hardware around security. You can tie into root of trust, you can tie into stuff around measure boot, and out of station, and kind of grounds up security functions. You're sitting between the OSs and the apps, whether they're VMs or containerized, and the hardware so you can literally turn on and off ports and do distributive firewall type stuff. So it's great, but the proprietary versions cause lock-in to that person's controller, that company's controller. And so if that's fine for you, cool, in this world, because of all the reasons mentioned before, it's really important to have those abstraction points. Most of the solutions out there commercially or even open source tend to kind of fall into the camp of modern, we support containers or we only support VMs. Generally there's much more container focus in the open source world these days with Kubernetes and beyond, just Docker and the like. And then of course there's data center solutions out there that are proprietary that are great offers, but they're just not built for the IoT edge. The constrained nature of it, this idea that I don't have physical security, I don't have network security, I don't have a pipe. Most IT data center solutions pre-suppose that you have a constant connection to your controller. In the IoT edge or even the constrained device edges, the smart device edge and the constrained device edge, you quite likely do not have a constant connection. So you need to have what we call an eventual consistency model. So you set the state that you want in the controller, whether it's on-prem or in the back end, that communicates with Eve, and even able device phones home. It says, what am I supposed to have? What versions of everything? You work to get up to date. It does it in a separate partition. And then once you've checked everything, then it switches over. And if it doesn't succeed in that update, it keeps running the way it was because you have to focus on uptime. So anyway, there's some unique things for the IoT edge and, of course, I think that openness really matters. And then you've got an agent-based solution. So the bottom right. So this is another approach that we see commonly out there in the market. So this is an agent that connects to the controller that has APIs. And if it's open source, you could have an open API or you could have a close if it's proprietary. It just depends. But that agent then communicates through the OS into the hardware. And the challenge with this is that if you have an agent without deep integration into that OS and hardening of that OS, you might have security gaps. You don't get those benefits of the bare metal foundation like Eve has or even the proprietary ones have in terms of security and networking functions. If you don't do that integration between the agent and the OS, you could likely break that device out in the field. And that's bad news if you're out in the middle of nowhere and you're rolling a truck out there to update that device. You just spent $1,000 to roll that truck out. We have customers in the commercial sense that are doing wind turbines. You could spend $150,000 to $100,000 to get it for the day to get a helicopter out there and all the logistics associated with that. So you do not want to break devices out in the field. These solutions tend to only support containers. If it's an OS, if it's an abstraction layer, of course you've got solutions out there that support VMs, proprietary locks people in. But I would actually say that an agent-based solution could run on Eve by leveraging the APIs that are brought up through Eve. And if you do tight integration between that agent and the OS, well, guess what? You just built Project Eve. And so that's why we think this is the best blend for kind of enabling edge computing at the IoT edge. Completely open API, vendor neutral governance through the Linux Foundation. We think that's important. There's open source all over the place. But if you don't have that neutral governance, you cannot build trust because of the necessary transparency. Again, we support both containers and VMs. You can't break the device during updates because it's at that lowest level and it's optimized for this constrained hardware outside of a physically secured data center. Gateways, servers or otherwise. So that's why we think as a project community, we're building up the right approach. It's not to say there's not other good solutions out there, but we just think this is the way to go and kind of do for IoT edge what Android did for mobile, as I keep mentioning. So in terms of use cases, we've got a variety of different ways to do it. These are kind of more of the horizontal use cases. It's certainly applicable in many markets, manufacturing, industrial, oil and gas, energy, retail, healthcare, you name it. We've seen folks from all walks of life working with it. Workload consolidation. So this is basically, I take a compute resource. Could be a gateway or server or otherwise. Small cluster as mentioned. But in the case, call it an IoT gateway. I'm running Eve on top. I ship Eve out. I provision it. I've got my choice of controller in the back end or on-prem, just a remote controller. And I want to lift and shift legacy applications. So if I'm in a manufacturing world, I might have like a legacy Windows application that has to run in a VM. And I don't have to reinvent it, but I can just put it on the same workloads as maybe next to it. I'm running one of the clouds, the Edge solution for one of the clouds or I'm running an Edge X foundry connected to my choice of back end. I'm running Fledge or whatever, other projects within LF Edge. Pushing AI models down. So I'm like kind of, you know, this hybrid workload. So that's kind of one use case, helps you reuse existing investments while investing in kind of modern new cloud-native apps alongside of Eve's the common base. We've seen a number of people using Eve in another model where it's less about running apps and it's more about secure data access. I mean, I literally use Eve as a base for an appliance that then does secure network proxy. And I'm pulling data out of machines or wind turbines out in the wild and pumping that to whatever, you know, we're just, we would just as a project be that lower level abstraction and then you use your choice of controller. What's not shown here is whatever the back end is, but again, Eve is not in the data path. We're not trying to get the data to, you know, our controller or open source or otherwise. It's about the orchestration and then you choose where it goes. And the last one, Edge security analytics. So this is similar to the first one, but I'm not in-band with the data per se. I'm out of band. So maybe I have a box that has a span port. I'm sniffing traffic. Maybe I'm putting a intrusion to technical system or some sort of, you know, active, you know, AI based ML based threat analytics. I'm monitoring traffic. I'm triggering events of something, you know, fishy's going on, but I'm not in the data path. And again, you know, Eve and whatever controller you use provides that universal abstraction layer. So this is about gaining visibility about what's happening on your network. And so, you know, we see all kinds of different use cases and of course different markets and whatnot, but these are sort of the patterns that we see, the deployment patterns that we see. So we've got all these features in there. You know, I've been mentioning a lot of them. It's that root of trust element tied to TPM. If you don't have TPM available, we can virtualize that through Eve. You know, it provides that, you know, the distributed firewall capability and those open APIs for managing the container objects or the Edge compute objects, whether they're containers or VMs. Lots of detail online, you know, about the project. You welcome to go to the Wiki and dig in, download the code to go to town. And this roadmap is also online, but just the name of the game for the project as a community and we run regular TSCs, there's a link I think at the end of this, is to continue to build out that framework. You may always strive to reduce the footprint. I mentioned 256, you know, is kind of the lower extreme of megs and memories that we're seeing, you know, we're a little higher than that today, but you know, we've got all these extra features, you know, and of course, if you don't need VM support for legacy, you can actually, we've modularized that hypervisor so you can actually use your choice, not only your choice of hypervisor, but also, you know, not use that if it's only meeting containers. We're not trying to reinvent anything. You know, we've adopted recently container D as sort of like the, which is the most popular runtime for containers. We've adopted that. You know, certainly we work with Docker and as I mentioned, we're starting to evolve into support for Kubernetes by bridging to the great work happening in K3S, but we're not going to do it carte blanche. We're going to do it in a way that makes sense for the IoT edge and especially makes sense in the case of having to write security elements underneath because these are devices that are not in a physically secure area and so you have unique considerations. You know, I mentioned the modular hypervisor support. Initially, we were opinionated on Zen hypervisor as a community. We've had folks out in the landscape asking about KBM, so we modularized it and made KBM support. There's an open source hypervisor effort that Intel has been leading the development of in the community building around this real-time hypervisor called Acorn. Very lightweight and that can help supply, support mixed criticality workloads. So, you know, the mixture of time critical and more time sensitive workloads. And then we're just always looking at new ways of creating kind of north, south, east, west communication capabilities between different edge nodes, edges to cloud, but in this case, edge-to-edge data flow. So that's like between different compute nodes at the same tier. So, all about starting where customers are at today. They need to be able to support legacy and then also containers, but then also at the same time evolving to not reinvent stuff, take from various upstream and downstream projects but create kind of that one-stop shop, the one stack that you need to pre-install on hardware and ship it out, and then you take advantage of an open ecosystem of value add. And so that's, you know, we think it's super important for all the reasons I've been mentioning. Of course, you know, you can't, nobody, you're not anyone if you don't have Raspberry Pi support. So, Stefano from Xilinx, there's some blogs that we're going to be doing about this, but in some others, you help build this image for the Raspberry Pi 4. So you can get that today. I think in here, if you just search online, you'll find it, you know, but basically you can get Eve running on Raspberry 4. You can go work with the controller of choice. There's some controllers coming that will be, you kind of come with dev kits and stuff, but now you take your pick, you know, build your own controller if you'd like. There's a very simple controller today, as I mentioned, but yeah, this is good for kind of tinkering and start to kind of build the solution with your choice of value add around, you know, a very low cost point of entry. Definitely check that out. And again, thanks to Adam and the community, Stefano and the community for contributing that support. So we actually talked about this on a webinar that you should be able to find, you know, online recently about Eve. So anyway, it's a really cool there and there's lots of other hardware from companies like Adantek and Lanner and Supermicro and, you know, OnLogic, Dell, you name it, HPE, you know, all on that even market page. So just take a look and, you know, get involved if it makes sense. So we'd love to have you. Speaking of kind of involvement, as a community, we've grown to almost 50 unique contributors. I mean, literally the last time I updated this, it was 40 and that was a couple months ago. You know, I mentioned Xilinx, Stefano Xilinx and some others were doing great work on the Zen stuff, you know, related to the Raspberry Pi. We're working with Intel around Acorn and there's other providers that are making contributions. Of course, you know, Zedita, you know, as a company, we contributed Eve. We have a commercial controller, but at the same time, like I've said before, we firmly believe that it's best for the community, for the overall market to have a completely open foundation. That's what we put it into Linux foundation versus open source it on our own. And then that allows a community to transparently develop that.  So we've seen Eve deployed in various different use cases. So, you know, wind turbines, as I mentioned, that secure proxy is with an example there. We've seen people exploring it and leveraging it in hospitals. So say I'm a medical imaging manufacturer, a machine manufacturer. I've got these imaging machines I put into hospitals as a service for my customers, but I don't own the network that they're sitting on. I'm in the room where the patients are. I'm not in the data center. I'm trying to do medical imaging to deploy analytics models for those machines, but I don't know what the network looks like. So I need distributed firewall. I need zero trust model in general. So we see that in manufacturing plants. We've seen people use Eve, not only to do workload consolidation, but also just to securely create a segmented network to get data into some sort of cloud application. And so these network overlays over the process, you know, at all costs protect the process, but I need to pull data out to get to some other system for further analytics and just visibility in general. And because of the distributed firewall capabilities and all that lower level functionality because of the bare metal foundation, I'm able to do that. And then, of course, in oil and gas, you know, you've got wells out in the middle of, you know, remote locations and people are using it to deploy AI models to run predictive maintenance. We've got folks, you know, the wind turbine folks are using models to listen for flaws and, you know, potential issues with those turbines. And it's really about collaborating with various other projects as we go. So hopefully this demo works. This is actually Sarah from the Zadita team. This was at a conference where we were presenting with other LF Edge projects. And so hopefully this video works in terms of audio, but you're kind of a quick demo. I'm going to start with some part of the Fledge project within LF Edge and just kind of showing how Eve comes together as that orchestration layer. Hi, I'm attached to a small, a big box running project-based software. On top of that software, it virtualizes the hardware network and application layer. We have a small application that's translating the sensor data and then sending it in real time to apply servers so I can see any maintenance data. I can get vibration information, information about temperature or humidity, things like that that might tell me the general health of my wind turbine. It's very easy for me to know in real time. And also, with this box, Eve very easily has other applications beyond my application running my wind turbine with sensor information. I'm going to go into the interface, go into my catalog, and from here I could choose an application such as Edge X Foundry and very easily be able to deploy that out to my box as well. Okay, I saw in the chat that you guys didn't see the video. I'm watching it here, but that video was online. Of course, Sarah is talking about okay, so maybe it is working not sure if some folks had an issue, but that video is online and Sarah is really talking about a use case, but the Eve component in that is providing that abstraction layer. Okay, so you saw a picture of Sarah and her talking. Anyway, so that's kind of, we decided not to try to do a live demo over this platform, but anyway, check it out. Get involved. Hold on. There's a lot of links here.  All of the technical steering committee meetings are open. Of course, the value of the Linux Foundation in general is the governance that they provide, all those extra services, but then we work as a community. Of course, we'd love folks to join LF Edge as a member, but it's a technical meritocracy, so you just get involved and the best way to vote is with code. All the Wikis and stuff are here. With that, I don't know if there's any questions, and we I think we'll kind of move to any questions as you guys have it after I kind of summarize. The summary, we talked at length about how the IoT Edge is unique. There is no single edge. It's a continuum very, very unique and it's not the same as the data center. You want similar principles, but they're necessarily different tools because of the diversity of hardware and software and protocols and the resource constraints that need to be autonomous in operation. You've got different degrees of latency. Is it critical or sensitive? Too many people say real time. Real time to a building's operator is 15 minutes usually. Real time to an airbag? A little faster. The security elements, I talked at length about the scale factor. Tens of massive public clouds, eventually trillions of extreme devices in the smart device edge is somewhere in between. It's an exponential scale. Really important to think about the scale factor, think about all these constraints. We're talking 256 memory single note up to a small cluster, but we'll do Kubernetes right and we've got lots of stuff spinning up around that thing. If you'd like to help bridge Kubernetes to Eve, get involved. Lots of cool stuff happening now, but again, we'll do it in the right way. Super important to have an open architecture. Yes, you can go build it on your own. I need to decide if I'm going to build on my own or not. If you build a silo, you miss out on the party, which is going to be this V to X to X, interconnected ecosystem play. This is about everything connected, maintained privacy. But if you build trust and you set privacy terms that you're okay with, the ultimate goal is to start interconnecting different use cases and building new infrastructure. I'm going to start off this snowball effect in the broader market. Imagine if the internet wasn't open and you don't have to go crazy with it. Put the right tools in today and architect today from grounds up. Start small and then scale over time. And then of course, Eve is really built to be that for the IoT edge. So outside of physically secure data center, still capable of running apps, headless, Linux space typically, but also I need to support Windows. That's a very well established ecosystem. So this is about doing that for the IoT edge. So with that, I don't know, again, if there's any questions, I think that we're probably running out of time here. Sorry about the video. And then there's also go check out the LF edge YouTube channel. There's a variety of different demos of the projects and we've just got a lot of good content there. So we appreciate the work that the Linux Foundation team does for us as a community. So, yeah. And I see May talked about the link for the video. So if there's any questions, I think that doesn't look like we have any additional questions must have explained it perfectly. But yeah, reach out and get involved in the community. If you have any other questions, you can always go there. I'll try to get on the slack after this. I'll have back to back meetings. But from there, it's definitely look look for you guys in the community and would love to collaborate within the project. All right. Thank you.