Hello everyone, welcome to Options with Doug, streaming live daily on Bookmap Discord and the Bookmap YouTube channel at 1.30 p.m. Eastern Time. Before I get started, I need to go through the Disclosures. General Disclosure. I'll bookmap them in materials, information, and presentations are for educational purposes only and should not be considered specific, investment advice, nor recommendations. Disclosure, training futures, equities, and options involves substantial risk of loss and is not suitable for all investors. Past performance is not necessarily indicative of future results. Here's my contact information. The best way to get in touch with me is through Discord. My name on Discord is Doug P. Also on Bookmap Discord, there's an options-doug chat channel. That's a great place to post questions, comments, and content related to the topics of my channel and the topics of my presentation that I'll go through in just a moment. I'm also on X, formerly known as Twitter. My name there is at Doug Place. Here are the key tenets of my approach to trading. This is the basis of my approach to trading. I believe that options trades and market maker hedging activity are key drivers of the price of many stocks and futures, and certainly in the equity futures that I follow, the SP500 and the NASDAQ, as well as the large cap tech stocks. For the SP500, SPX is the underlying index, SPY is the ETF version of that index, and ES is derivative of SPX and SPY. When traders take positive delta position, buy and sell calls and puts in SPX and SPY, market makers take the opposite side of those trades, and they hedge their delta exposure with ES futures. For the NASDAQ 100, NDX is the underlying index, QQQ is the ETF version of that index, and NQ is a derivative of NDX. When traders buy and sell puts and calls in NDX and QQQ, market makers take the opposite side of those trades, and they hedge their delta exposure with NQ futures. The focus of my presentation today and the focus of the options-Doug Chat channel is options, order flow, the impact of options markets on stocks and futures, and the influence of market maker hedging flow on price action. I have a two-step process for trading in the first is planning, and I use positional analysis. I look at how traders and market makers are positioned to the options market and how those positions change from day to day to develop a thesis regarding the expected trading range and volatility for the day as well as the directional bias. And just note, on Monday, my directional bias was bearish based on the shifts in levels lower, and that's how the day resolved. In the yesterday, my thesis for the day was bullish based on the shifts higher in the spy and QQQ key daily levels, and that's how the day played out toward the end of the day as well. All right, the second step in my process is execution. I look at real-time order flow and book map and real-time market maker hedging flow and spot gamma hero to confirm my thesis and for setups. And when I talk about setups today, I will be focusing on an underlying asset. And setups in that asset can be taken any number of ways. For example, the SB500 setups can be taken with ES futures, spy shares, spy options, SPX options, or even ES options. Questions and comments are welcome, and I will be watching both the options-chatshug-chat channel and Discord, as well as the chat and YouTube for your questions and comments. Please feel free to post. I'll do my best to answer your questions. And hello, Suzette. Suzette, welcome. Glad you're here. Hello, Steven. Anirag, welcome. Glad you're here as well. And Slow Desiree says, spy call wall 50-20. Maybe we get there. Maybe we do. If the market likes what the drone pal has to say. In the FOMC meeting, which is coming up, announcement at 2 PM. So here's my agenda for today, Wednesday, March 20th. First of all, I want to go over news items, economic data, and events for today. First of all, there was a VIX expiration at 9.30 a.m. Easter time. And the big event of the week is the FOMC announcement at 2 PM and then the press conference at 2.30 PM. And the FOMC announcement is right in the middle of my webinar. I will stop whatever I'm doing, and we'll take a look at the live market at that time. We'll see what options traders are doing, as well as traders in the SV500 and NASDAQ. And before that, I'll take a look at my positional analysis for today. Then I'll review some setups from earlier today. And then I'll take a look at the live market. And that will probably be about 2 PM at the time of the announcement. And I forget to live market before that. If anybody has any stocks they want me to take a look at, please let me know, and I'll be glad to do that. All right, let's get started with positional analysis. Oh, let me just point out, this is the CME FedWatch tool. And according to this, so the current target rate, this is the current rate, is 525 to 550 basis points. All right, there's a question in Discord, mic off. No, I, OK, all right, that was something you were doing. All right, so let me just check. Yeah, my mic is working fine. All right, so this is the FedWatch tool. Current target rate, 525 to 550 basis points. There's a 99% chance that the Fed will leave that rate unchanged. And a 1% chance of a 25 basis point cut. All right, so the expectation for today is pretty much unanimous at no change. So really, what the market will be looking for is the change in the statement as well as the press conference. All right, so let's move on to positional analysis now. I'm going to start with the SB500. This is the SB500 futures and book map, ES futures, before I take a closer look at this chart. I do want to take a look at a larger time frame. And I'm going to take a look at the underlying index, again, which is SPX. This is the current rally began last year, October 30th. So far, SPX has rallied up about 1,080 points. So that's the current context of a very large rally in the SB500 SPX. Now let's take a look at a one-hour chart. So this is a 30-day one-hour chart. This is thinkorswim, just like the previous chart. Again, a 30-day one-hour chart. This is the top of that trend line, that green dash line, trend line, high for SPX, 5189. And SPX has been approaching that level today, not quite there. All right, let me point out some additional levels on this chart. Well, first of all, note that since reaching that high, SPX has been consolidating between around 5100 and that high of 5189. I've shown that by this light gray shading here. Consolidation after reaching that high. All right, let's take a look at the levels on this chart. First of all, the dash purple lines are showing the lower and upper weekly expected move. That's based on the options market. That's also based on the closing price for SPX last Friday. Those levels remain in place for the entire week. And then the dash blue lines are showing the lower and upper daily expected move. That's based on the closing price yesterday, also based on the options market. Those levels change every day. So note again, SPX is trading right up at the, was trading just slightly above the upper week they expect to move earlier today. And within the range of the lower and upper daily expected move. So again, both those levels are based on the options market. And I post those levels in Discord every day. I will post those in the evening the day before. So I posted the numbers that shown on this chart yesterday evening. All right, so the other levels on this chart are spot gamma levels. These are proprietary spot gamma levels that are based on gamma weighted open interest. These levels can and do change daily. No changes for SPX today. Let me point out the key daily levels. First of all, the put wall at 5,000. That's a strike where the largest net negative gamma that can be expected to act as support. The next level, and that's also the absolute gamma strike. So that's a strike where the largest absolute positive and negative gamma. Next level up is the volatility trigger VT. That is spot gamma's proprietary volatility flip level. Below that level, market makers position on the gamma curve is negative. In a negative gamma environment, market makers have to trade with price to hedge to their delta exposure that tends to enhance or increase volatility. Above that level, market makers position on the gamma curve is positive. In a positive gamma environment, market makers have to trade against price to hedge to their delta exposure. And that tends to subdue or decrease volatility. And Actin Bull, sorry about if I'm pronouncing your name incorrectly, ask in Discord, where do you get gamma levels that comes from spot gamma? And there may be other providers, but these are proprietary to spot gamma. And you'll just go to spotgamma.com and you can see the prices for subscriptions. I think spot gamma's well worth it. Hello Caesar, welcome glad you're here. All right, so the next level up is the call wall at 5,200. That's strike with the largest net positive gamma that can be expected to act as resistance. So if SPX continues to move up, that is the next level up. So that's the potential ceiling for price and the floor being at the put wall at 5,000. No, there were no shifts in levels for SPX today. All right, Caesar says my mic sounds like laptop or camera mic, not my usual mic. Is anybody else having a problem? It could be. I have a headset with a microphone. I don't know, maybe my headset microphone is not working. Hold on, let me try. All right, Gray says, sound is fine. Give me just a moment. All right, does that any better? All right, Stephen Teal says, sound has been great the whole time. Okay, let's move on. I'll look into getting a new headset. Maybe there is a problem. All right, so I'll have to do that later on. Okay, let's move on. All right, so let's take a quick look at and wrap up our view of SPX with a one minute chart. I'm looking at about two and a half days worth of data. Dark shaded portions are the regular trading hours. This is the move up that began yesterday up to the upper weekly expected move for today. Now it looks like SPX is making a series of lower highs, moving lower. All right, let's get to book map now. All right, book map, showing you yes, futures. I have my own cloud notes. So I'm showing SPX levels on this chart, spy levels, and also key levels for ES. In this range of the chart, there are no SPX levels. There are some spy levels in play. Here's the spy 515 absolute gamma strike. Here's the upper weekly expected move for ES. I do calculate that separately from the upper weekly expected move for SPX. That level did act as resistance earlier today. And again, ES making the series of lower highs, finding resistance at the spy 516 level. And now moving down again toward the 515 level. All right, for spy, there were a couple shifts in levels. The volatility trigger and put wall both shifted higher. So slightly bullish for spy. All right, so that is the SP500. Let's take a look at NASDAQ. This is the NQ futures and book map. Let me take a quick look at the underlying asset charts. First of all, this is QQQ resistance at the open at the 440 level. That is the absolute gamma strike. And then QQQ trading in a very narrow range between 439 and 438 volatility trigger. Also now making a series of lower highs. Again, 438 is the volatility trigger. That level did move lower from yesterday. And the call wall also moved lower from yesterday. So two levels move lower for QQQ, slightly bearish. And let's take a quick look at NDX. NDX trading just above the 18,000 level and note the call wall absolute gamma strike for NDX. Is it 17,900? All right, so here's this QQQ 440 level absolute gamma strike that acted as resistance before the cash open and just at the cash open. And then now NQ trading at a very narrow range between 438 and the 18,000 level and the NQ 18,300 level. All right, so again, I have my own cloud notes. All right, shifts and levels for the NASDAQ again, none in NDX and the volatility trigger and call wall shifted lower for QQQ. All right, let's wrap up our positional analysis by looking at gamma notional. This is market makers position on the gamma curve at the beginning of the day. For the SB500 and NASDAQ, this is what I'm focusing on. Note all these numbers did shift higher from yesterday. So SPX became more positive gamma notional for SPX. Again, in a positive gamma environment, market makers have to trade against price. Smart gamma assumes that in a positive gamma environment, traders are short calls, market makers are long calls. Hence the positive gamma and they have to trade against price. For spy, gamma notional is still negative. Same for QQQ and negative gamma environment. Spot gamma assumes that traders are long puts, market makers are short puts. Hence the negative gamma and they have to trade with price to edge their delta exposure. All right, so based on this, really today's an FOMC day and nothing much to do both the SB500 and NASDAQ trading in a very narrow range this morning, pretty much waiting for the FOMC. All right, so again, we know if the FOMC announcement, there's a 99% chance that rates will be unchanged. So the algos will be parsing the statement and then listening to the press conference that begins at 2.30 p.m. Easter time. Let's take a quick look at some setups from earlier today and not really much to see here. Again, price trading in a very narrow range, waiting for the FOMC announcement. So I'm gonna start with the SB500. I'm gonna take a look at what options traders have been doing today. This is the hero signal, hedging impact real-time options. So everything that we've looked at so far is based on static data. Spot gamma takes open interest data. They apply their algorithms to that data that come up with levels that I've shown on my chart, the key daily levels. Again, I'm looking at how those change from day to day to develop my thesis regarding the sentiment and how traders are positioned at the options market, what they expect. All right, so that's based on static data. Now let's move on to execution to real-time data. So again, this is the hero signal, hedging impact real-time options. This is available to spot gamma subscribers. What this chart is showing is price for SVX with a white line, and the purple line is the hero signal. Again, hedging impact real-time options. It's showing options trades a market maker hedging activity for a combined signal of SVX, SPY, XSP, and ES futures, all under one combined signal. So if you trade any form of the SB500, this is the signal that you wanna take a look at. A rising hero signal indicates traders are taking positive delta positions. They're buying calls and or selling puts. Market makers are taking the opposite side of those trades, and they're buying futures to hedge their delta exposure. A falling hero signal indicates traders are taking negative delta positions. That means they're buying puts and or selling calls. Market makers take the opposite side of those trades, and they have to sell futures to hedge their delta exposure. So let's focus on the long setup of the morning and then the short, long about 9.45, somewhere between 9.45 and 10 o'clock, then a short as the hero signal starts to move lower, right around 11.15. All right, so I'm gonna zoom in on this chart. So again, note how the hero signal really chops moving slightly lower, then reverses higher 9.45, 9.50. So let's go take a look at book map, go back to ES, zoom in, so notice how ES was making a series of higher lows. So here's that reversal higher in hero that started right around 9.45, 9.50. There were some large iceberg orders here. You can see that by the on-chart indicator, as well as the spike up in the light blue line on the sub-chart, or large traders use iceberg orders to hide their size. That's showing that 1,680 contracts were executed in 10 separate executions. If I zoomed in on that, that would show the separate executions. And note at this time, cumulative volume delta was slightly rising, and then as price moved up to the upper weekly expected move, there was a stop run up to that level that's shown by the rising yellow line in the sub-chart. These numbers are very small, but there was a stop run up to that upper weekly expected move. All right, let's go back and take a look at hero. So a move up, not the most clear here in the SB 500. All right, let's go back to hero. So here's that run up, that peak in hero. Hero starts to make a series of lower eyes that was right around 10.30, and continued to move lower. As traders were starting to take negative delta positions. So that's right at 10.30, right after that stop run up to the upper weekly expected move. Then again, SB 500 making a series of lower highs. Note in the sub-chart, cumulative volume delta, that show them of the dark blue line to magenta falling, so aggressive sellers. And you can just see the volume dots. The volume dots are showing market buy minus sell. Green dots indicate more buyers than sellers. Magenta dots indicate more sellers than buyers. So aggressive sellers really started to come in right at that sharp reversal lower. Let's take a quick look at NASDAQ and then we'll pause for the FOMC. NASDAQ, again, resistance at Kukuku 440, reversal lower at the cash open. Here in the sub-chart, this is showing a falling light blue line indicating large traders have been selling this move with iceberg orders. Also sell stop orders shown by the falling yellow line also have been moving lower. And cumulative volume delta was positive for a while now shifting back down. So all three lines of the sub-chart currently moving lower. As NASDAQ makes a series of lower highs. Let's take a look at HERO real quick. For HERO, I like to look at this Mag7 signal. This is the, let me just zoom out real quick. This is another combined signal. Showing options trades and market maker hedging activity for combined signal for the stocks known as the Magnificent Seven. That's Apple, Amazon, Google, Meta, Microsoft, Nvidia, Tesla. Note at 950, the HERO signal does move higher, kind of choppy, but does move higher. Peaks around 1030 and is now moving lower. The SB500, zoom in. All right, I've got less than a minute left. Quick look at NASDAQ. Traders taking positive delta positions. Price moves up, cumulative volume delta. 1030, they start taking negative delta positions. And NASDAQ makes a series of lower highs. As traders were taking negative delta positions. All right, I've got less than 30 seconds to FOMC. So we'll zoom in a bit here. So we'll watch this and then we'll take a look and see what options traders are doing. All right, initial reaction bullish up above highs of the day. We'll give this a minute or two and then we'll see what options traders are doing. Zoom in a bit more. Move these volume dots just a little bit. All right, so the Fed fund rate is unchanged as expected, 525 to 550 basis points. So now the Algos are parsing the statement. So buy-stop orders as well as aggressive buyers fuel that initial move higher. Buy-stop orders continue to fuel the move higher as well as aggressive buyers. ES above highs of the day. Remember that was right around the upper weekly expected move. Let's take a quick look. So again, upper weekly expected move was around the high of the day. All right, let's see what options traders are doing. All right, so Caesar says, Fed does not expect to cut rates until it has greater confidence. Inflation is moving sustainably to 2% target. Fed projections show 2024 policy rate view unchanged at 75 basis points of reductions. All right, so a sharp move higher. The SB 500, let's see what options traders are doing. Let's go to hero. I'm gonna zoom out on this chart. By the way, this is the preferred way for zooming in. Just I'm scrolling with my mouse wheel instead of changing the look back period. This is the way that Brett, the founder of, Brett Kachuba, the founder of SpotGamma Provers to do this. All right, so initial burst higher. Traders taking positive delta positions. I hope that SPX is approaching the 5,200 call wall.  Let's just take a quick look at a chart of SPX. Let's go to our one day chart here. One minute chart. Let me just check on that 5196 level. Give me just a moment. 5196, that's a combo one level. So combining SPX and SPY, gamma weighted open interest into one level converted to an equivalent SPX price here. All right, so that's a combo one level. It should show up on book map. Yeah, there it is. 5196 combo one level. Maybe acting as resistance. So the SB 500 testing that level again, that combo one level. Aggressive buyer still in charge. Note some large traders have been coming in buying with iceberg orders. All right, there's the 5,200 call wall. So right now SPX trading at all time highs, breaching the 5,200 call wall. Let's go back and take a look at hero see what options traders are doing. So they continue to take positive delta positions. I'm gonna shift to puts and calls to see what they're doing. All right, so not a lot of clarity there. They are buying calls. I'm gonna shift back to the total signal. Those lines were just too flat. All right, I'm shifting to the mag seven signal. Again, this is what I use for the NASDAQ. Gonna zoom in on the signal. So in this case, there's more clarity by shifting out, splitting outputs and calls. Traders are buying calls on the mag seven stocks back to total. All right, so we know they're buying calls on the mag seven stocks. Let's go back to the SP500. So traders definitely like what they hear. All right, Suzette, thank you very much for your kind words. Right now, options traders taking the foot off the gas. That is entirely to be expected at the 5,200 call wall. Major level of potential resistance. Doing its job, acting as resistance, note the aggressive sellers come in. As options traders take their foot off the gas and aggressive sellers start to sell ES. Wall has remained at 5,200 for quite some time. And again, so far that level doing its job acting as resistance. So if this continues, stay tuned till tomorrow. We'll see how the levels shift. If traders are taking long-term positions in higher levels that will show up in the shifts in levels for tomorrow. The SP500 and NASDAQ. I did not mention this earlier today. There were no SPX levels on the chart. Now here's this 5196 into 5,200 call wall. Note there is a difference in price between ES and SPX. Earlier today that difference that offset was about 63 points. Now it looks like it's closer to 62 points. So I'm showing the 5,200 call wall at ES 5,263. It maybe should be closer to 5,262 right now. But again, earlier today when I set these levels it was closer to 63. Note I do post the index relationships that I'm using for the SP500 and NASDAQ every day. I post those in Discord, right? So nothing going on in the morning but plenty of price action this afternoon in the SP500. Let's take a look at NASDAQ, right? So NASDAQ moves up to the NQ 18,400 level that's shown with red there. This 440 level, QQQ 440 level that acted as resistance earlier today acted as resistance again, now support. That just shows you how important the QQQ levels are for NASDAQ. And let's go back to hero, hero shifting higher for the SP500. Let's go back to mag seven. So the hero signal continues to move higher for the mag seven. Trader still buying calls for the mag seven stocks. Let's just take a quick look at some stocks. Let me take a look at one other thing. Let's take a look at NVIDIA. See what they're doing in NVIDIA. Right, for NVIDIA 900 is the call wall. That acted as resistance earlier today. That's the call wall, key gamma strike. NVIDIA did trade lower, note the flow alert. Now trading up just below that level. So this line right here, that's the 900 level. Call wall, key gamma strike. And traders continue to take positive delta positions in NVIDIA. Looks like they were in earlier before the FOMC taking positive delta positions. Then started aggressively buying, most likely buying calls. Let's go back to book map. We'll take a look at NVIDIA. All right, does anyone else have any stocks they want me to take a look at? Any other stocks, anyone have any other stocks they want me to take a look at? We'll zoom out to the full day. There it is, 900 key gamma strike. That's also the call wall. Price did move higher at the cash open, then move lower. NVIDIA made a series of lower highs, reversed. Now moving higher back up toward that 900 call wall key gamma strike. Let's go back to ES. Right now moving lower. Call wall did its job, acted as resistance. CVD starts to shift lower. Also now sell stop orders, fueling the move lower. Or at least my stop orders are no longer fueling and move higher. So both the CVD and the stop orders now trending lower. Light blue line showing iceberg orders has pretty much leveled off. So first leg up, now on the second leg, moving down. Let's go back and see what options traders are doing. Let's go back to the SV 500. Again, this line is 5,200 call wall. And this is entirely expected behavior. Traders start taking negative delta positions, taking profits at the call wall. Now price moving lower. That may be just the first test of 5,200. Let's go back to NASDAQ. All right, back down to the 440 level. Resistance, support. Let's check the MAG7 signal again. Call buyers have taken their foot off the gas. Krishna asked, would you be a buyer here with a liquidity below on ES? All right, so let's take a look at ES. All right, I would not be a buyer of ES as long as this hero signal is moving lower. To be a buyer, I wouldn't wanna see heroes starting to rise. Let's go take a look at book map. All right, so now NASDAQ is broken below the 440 level. Let's take a look at ES. All right, so what Krishna asked, would you be a buyer here with a liquidity below? What Krishna is talking about is all this liquidity. That's the heat map and book map showing history of the limit orders of the order book. It looks like there are a lot of buyers there. These limit orders below price or limit buy orders from around 52, 42 to 52, 45. A lot of buyers, and that could certainly act as support. It looks like traders may be front running that. Some iceberg orders coming in buying buy iceberg orders. Rising light blue line. All right, so just looking at order flow here, I would certainly consider a buy. Let's go back and take a look at hero. All right, so the hero signal now leveling off. Not a trade recommendation, but certainly looks like could be a potential buy. Let's check hero again. All right, so the hero signal is starting to level off. Looks like price may be stabilizing. All right, Krishna, thank you for pointing that out. Trend break. Aggressive buyers starting to come in. Hero signal leveling off. Liquidity in the order book. Passive orders, limit buy orders down below. Traders coming in and front running that liquidity. Knowing they have probably a potential support at that level. Let's check Nasdaq. Nasdaq did trade below the 440 level. Now maybe moving higher as well. Another trend break. Good long entry at 440. Let's go back and check hero. All right, so the hero signal did shift higher. Traders start taking positive delta positions again. To Nasdaq, back to hero. Check the mag seven signal. Moving slightly higher. Right now for the S&V 500, it looks like the hero signal is now. Looks like maybe just making a lower high. Let's go back to book mount. Go to ES. Let me do a sound check. How does my sound? How's my sound? I'm hearing a lot of buzzing in my headset. Is my sound still okay? All right, uncle says sounds fine. Thank you. Suzette and Ragh says good, it's fine. Thank you. Caesar says sounds the same, no change. All right, I've got about five minutes left. Thank you, Stephen says it's fine as well. All right, does anyone have any questions, anything they want me to take a look at? Please let me know and I'll be glad to do that. Check Nasdaq. All right, I would say at this point after the move up, reversal at the call wall, move down to the liquidity just above 516, right around the 52 to 5245 level. Now, ES is probably gonna consolidate the index, indices are probably gonna consolidate until the press conference. And Ragh says the liquidity we see today, we see below the current price in red is that limit buyers or sellers. That is limit buy orders. So below price, this is showing a history of the orders in the order book. Those are buy orders, limit buy orders. Always below price, limit buy orders. These are the current orders in the order book shown right here. And then this is history of the limit orders in the order book. So they started coming in right around 208, 210, something like that. They started coming into the order book and they so far remain in the order book. Let me check the questions and comments. All right, Caesar says, I've only been using book maps since December. So still not that much experience, but it feels like the last two weeks, I've been seeing way more of those large thick walls of buyers on ES take up three whole points. Do you feel that's a new phenomenon or just something I'm just noticing now? I don't know, it's not something that I don't have any stats really or anything. I don't think that happens all the time, but I don't know. I really don't have an answer for your question. I don't have a feel for how unusual that is. I don't think it's that unusual. And Rex says, but when buy orders are enacting, then there must be sellers also. Yeah, that is correct. So that's what the volume dots are showing. But these, so we're looking at passive orders and active market orders. And the heat map, again, these are passive orders. These are limit buy orders. They remain in the market, typically in a stock, they will remain at that level. They come in at the cash open, remain at that level until they're filled. So that's limit orders, passive orders. The volume dots are showing the aggressors. Green volume dots indicate they're more buyers than sellers. So there are buyers and there are sellers, but in this case, in this volume dot, they're more buyers than sellers. The buyers are more aggressive in this case. So here, looking at this liquidity, again, these are resting orders in the order book. They're still in there. They have not been filled. They have not been enacted. All right, so Krishna, good call on this. Trend break above liquidity. Aggressive buyers starting to come in, showing by the green volume dots. The hero signal was shifting higher. And he has moved back up to the 5,200 call wall, again, doing its job acting as resistance. So a quick move up, 10 minute move up from the upper weekly expected move to the 5,200 call wall. Let's check hero. Caesar, you're welcome. Maybe you can ask Bruce. I suggest you ask your question to Bruce. He may be able to give you a better answer than that. He watches ES more than I do. So ask Bruce about that as well. Let's take a last look at hero. All right, so hero moves up again, back up to the 5,200 call wall. And just in the last couple of minutes now, shifting lower. All right, start move lower at the 5,200 call wall. All right, let me do a quick check for questions. All right, Joan Powell has started speaking now. Press conference has begun. All right, I'm gonna wrap it up. At this point, let me just summarize real quickly. For the SB 500, the 5,200 call wall did a great job acting as resistance, supported at this high level of liquidity, right below the upper weekly expected move, acted as support for a move higher. Now maybe the 5,250 acting as support. All right, everyone, I wanna thank you very much for watching. Thanks for your question to comments. Enjoy your afternoon during the press conference and I will see you tomorrow. All right, thanks again, everyone. Have a great afternoon and I will see you tomorrow. Bye.


When Jones first launched the mountain twin, little did they realise the impact it would have. By integrating their free ride philosophy and technology into a more usable everyday style of board, they inadvertently created what could easily be described as the ultimate ride anything and ride everything at snowboard. So what is it that makes the mountain twin so good? Well the starting point must be the shape. Starting riders a traditional twin gives the board that balance of predictable ride that you only really get with more free style specific boards. But it's what Jones do to the nose and tail shape that really transforms away the mountain twin rides. By integrating their advanced blunt nose shape which extends the transition zones from the end of the effective edge into the nose and tail curves into both the tip and tail they unlock a level of performance in the power that is literally unheard of in this type of board. Now add to this the versatile camrock profile which blends rocker at the tip and tail with a poppy camber between the bindings and the mellow magnetraction side cut and not only do you get a board that has the balance of a free style board and the float of a free ride board but you also get one that clavs like it's on rails. So if you put this in simple terms you get a snowboard that does everything really well. Now obviously though there's more to the performance than just the shape, it's got to be made right and in this respect the mountain twin doesn't disappoint. Coming up the high-performance credentials is the top-spec wood core. This multi-density popular wood core is reinforced with bamboo stringers running tip to tail through the length to give a poppy and lively ride. This is then enhanced with a powerful trius clastructural layers which step up torsional response and showing that no matter how hard you push the mountain twin it's always going to be able to deliver whilst never ever feeling overly aggressive. Finally as you would expect from Jones they utilized a high-grade 7700 sintered base to give a super fast glide in all snow conditions.


Hey, listen, this is important and I didn't talk about it a ton, right? She's attacking the roll. Do it again. Do your rep. Watch how hard she attacks the roll. I know when we're drilling we're going slow, but she's gonna get bigger. Now when she gets ready to roll, she's rolling an attack, rolling an attack. She's got her feet in the mat. She's even punching it up on her shoulder to get it higher. Now higher his leg is, the more weight going towards his head. Do it again. Do it again. Yellow's tangled up there. The other one I saw was really smooth. So driving in, getting that elbow digging in, digging in, digging in, digging in. This is him going seatbelt too. Right there getting above the knee, getting under, just attacking the roll. Right there. Right there. Not bad at all, but you notice how the feet are in the mat. She's attacking from right to left. I think that's super important. That's not something we can just kind of get up under. And be like, alright, I'm rolling through. That guy pinches knees. We might get stuck on our back there. We're probably not going to get hit or give up near fall, but we want to attack right to left. Alright, so get up under that leg, whether they got seatbelt or not, attack rolling across. A little bit more. Go. Don't grab a splash.


So I'd be like, hey, this, this identified a bush right here at the end of that out there. As soon as you hear me fire at everybody. So no one is going to fire until I fire. So I'm all. Other than that, it's going to be myself. Same thing for like.


It's a pleasure to be here in beautiful Taiwan and such so nonetheless so let me introduce some of the aspects associated with our project. A lot of the way I present things is to give a lot of philosophy behind what we're doing, and I can always back it up with a lot of the details I tend to like my actions to talk more than my words. But this is one example in which I give you some philosophies on how we're doing and why I think the approach that we're doing is a valuable approach out there so let me first introduce our mission. So we're implementing a community built we are platform as comprehensive and can be curated at multiple levels so each of those words that start with C is exceedingly important for what we're doing so we're trying to build a community, and this essentially means you. And that community is not necessarily the OER community but it's the greater academic community and I'm fortunate in that I wear multiple hats so I'm the executive director and founder of the LibreTechs project, but I'm also a active chemistry professor so the OER content that we use I actively use in my classroom. And I'm also a co-chair of an OER project that's being formed in my campus at UC Davis that is pushing it to a very large community so I wear three different hats and that gives us a unique perspective I think than many other projects out there. We have OER platform, I'm going to just refer to that as free since we are, we know a lot more about OER we know that's not exactly the proper definition of that but let's just keep it at that for now. And they'd be curated and I don't know why the arrow doesn't go to curated. We basically follow a no gap left behind policy so we don't focus on content that is the lower divisional and the content that's only just the classes that have a certain amount of enrollment. So that we cover everything from start to finish depending upon what your context of that and we've used content on our site at graduate levels and even have some primary campuses that are using it. We follow a no tech left behind policy so any valid open source technology that we're able to capitalize on and integrate into our system. We do so gladly as long as it has a, at least some level of utility off it. Okay, this is, this is why it's changed I raised a couple words and moved around. So curated should be it's a living library. So that that would be the opposite of a dead library for example a link or a platform or repository of PDFs would be an example of a dead repository and it's important in order to be able to curate content because only our content like all academic content starts to age, then we need to have a mechanism to do that. So, what is the Libertex project. Well we're a construction platform provides the opportunity to build OER content. And we are a dissemination platform professional argue with the most popular dissemination platform on the net today. And we're a learning platform, which is a mechanism in order for students to capitalize on our content in order to learn effectively and also to be utilized by faculty off these things but we have a bigger picture out there so the term Libertex was originally designed in order to focus on OER open textbooks. We've expanded that scope because the concept of a textbook is changing rapidly, and it's much more than just a physical book that we used to give in the past. And we need other answering materials in order to focus on the textbook of the future. Now, so we have a core set of libraries about 13 libraries 1415 and when I look at focusing on different fields out there but we have ancillary components necessary in order to push this textbook of the future we have a homework infrastructure. We have a Jupyter notebook in order to embed executable code which is important for STEM based fields. We have Java server in order to host JavaScript server in order to host content or technology as it involves learning analytics infrastructure in order to push the learning platform. A bot server in order to be able to go through our platform because it is a curatable platform it gives us the ability in order to update our content to handle modern and emerging accessibility requirements. We have a learning management system, which I don't know why it's called TMS here, we have forums that facilitate communication of the community. And we actually have two flavors of homework system one formative and one summative and this formative summative one is based around implementing adaptive learning and culturally responsive pedagogy. And if anyone's interested I can certainly talk about that but that's not a focus of what they're just saying. And then off of what we're doing is that a we're nonprofit so we're not trying to make money off of this thing. We understand that some revenue is necessary for sustainability, but we all have day jobs because we're all in academics and most of us are faculty and use the content of this that means that we're very faculty centered in the way that we do things. And that does give a different perspective than projects that are more library and perspective a more publishing perspective or even just basically very commercialized in order to be able to gain the system in order to make a profit off of that. And these are two key aspects that I feel quite strongly is necessary in order to push both our project and I think the greater or your project or we are effort, not everyone agrees with that but that's our approach. Okay, so the Babson survey identified a range of different reasons why people don't use we are. One is the just the sheer number of we are out there. The difficulty in order to find we are the difficulty in order to catalog we are constructively, and then other ancillary materials in order to supplement that we are textbook, including the homework system and other support stuff. So the, the key point of building this Libreverse is to try to address all these issues within a single infrastructure that we have control over, and then we're able to push things forward so the way I view we are is through conflict theory so I'm a very much the glasses half full kind of guy. I feel that intrinsically, this is a competition between big publishers that have a lot of infrastructure established in order to, to, you know, profit and do everything which largely is a motivation for a lot of we are efforts but not all we are efforts. And fortunately in the last few years have been lots of small or even a medium size projects that have been funded across the globe. In order to be able to deal with us but the problem is that they don't have a centralized standard essentialized format, even communication is sometimes limited although this meeting as a one example mechanism or facilitate that. There's one mechanism and I feel in order to compete constructively with the big fish in the sea where everyone works together. Anyone who's been in academia for any period of time knows that that's never going to happen. Just because the very nature of how academics operate, or if you're outside academia have for profit entities operate. So our approach is to build a bigger fish is to take everything put it together into a central infrastructure warehouse of sorts. But I don't like using that term because we're far stronger than just a simple repository in order to be able to compete with the publisher and that means building all the components in order to build to support the textbook of the future. Let me skip over this and talk about just briefly some of the philosophy of what we're doing here. So we bring everything into or we build content, and we harvest content which is our term of taking existing OER and bringing into a platform capitalizing on the O and OER and the permissions to largely create a commons although other licenses do provide that support to and bring it into an infrastructure that's curatable and centrally localized and that's a bit of effort. But the key point is that when we want students to graduate in whatever respective institutions we want, we want the synergy of their learning to be manifested. In other words, we want them to understand how some concepts in some fields relate to other concepts in other fields. So the synergy of what they're learning, even though we teach in silos we want something much more comprehensive. And my argument is that if we want that to be instilled into our students, we need to give them the resource that reflects that synergy that connection so stop talking about building individual textbooks, and start talking about building text libraries interconnected on a college basis that are able to reflect it. You carve out certain sections for a silo because we still teach in classes, but you benefit from the, the massive network behind the infrastructure behind here. And that's essentially arguing that the textbooks reflect how we want our students to see the world. Now in constructing any sort of project, like what we're doing here we have several different approaches that can be constructed. One is a centralized approach and the other one is a decentralized approach. And you can have sort of mixtures of the two off of here and their benefits and detractions off of that centralized approach gives you high stability and high fidelity. It's effective sharing. It provides pooled resources, and it's very efficient way in order to operate. So that would be example of using essentially anything Google related that's a centralized off of that. One of those is it typically provides lack of local control, and that's local control from the base level all the way up to the top level, or to medium level that decentralized approach would be for example making software that you can then port on your individual campuses or individual computers, you can run and implement effectively provides flexibility. It has several cons it perpetuates why I refer to as a fragmented ecosystem. There are all these individual we are projects in various spots that don't talk to each other very well and results in inefficient progress moving forward in the general community because people are oftentimes replicating the wheel. Moreover, it hinders the ability to remix one of the key components of we are it requires independent resources. It's inefficient. Even though the code free and open source software may be free it's not free to implement. You still need servers you still need it and this idea that you own the pipeline from your server to your computer is largely not real either because you have to pay ISP and other things like that. So, there's a lot of issues that I feel that the fragmented ecosystem that's oftentimes pursued in terms of individualized efforts is necessary. And I want to be able to generate a platform and this is what the Libertex is doing in order to provide the positive components of the centralized platform, and the positive components that decentralized platform while neglect negating or at least reducing these red terms. So let me give you a little bit of an aspect on impact. If you are a chemist and you've Googled anything in chemistry it is physically, it's not physically it's virtually impossible to avoid a Google search of Libertex. And that applies to a great deal of other Google searches out there. So we're the most popular OER platform in the net today in terms of traffic. We've distributed 520 million. So over a half a billion page views since we started. You'll notice that COVID basically bumped us up by 100% growth in the last couple of months, which is not unreasonably expected and other projects have expressed or demonstrated several activities. So we're somewhere in the order of a million page views delivered per day. So the second percent of our traffic is in America. So the other 55% of our traffic is outside the side of America with India being our second largest and they're largely countries that have English as a native language or lingual fronk as a largely commonwealth countries out there and I can show you distribution of people are interested in that. So you'll notice here when I'm talking about impacts is I'm not talking about money. I have a pet peeve in terms of trying to quantify OER content and turn to money because I'm an educator. I don't care about the money perspective, the money perspective is only a problem because it adversely affects my mission as an instructor in the classroom, the students are not purchasing the book. Don't purchase the book then it has a detrimental effect on my educational mission. That is the only reason I care about money. The only reason I care about is how students use the resource, how it augments their educational mission, how may, for example, how many years or in this case here for millennia of confirmed students of reading, and the analytics behind the learning, not the analytics run the money. And that's my perspective but I think it's the valid perspective in terms of what OER is out there. So if you look at any of our libraries and this is an example of the chemistry library. But when you log in, actually when you log in, when you just look at it anonymously, you have two different categories. You have the stuff that's in the bookshelves and the stuff that's in the courses. This reflects this centralization, decentralization approach that we have here, where we have canonical content stored in our bookshelves, whether it's content we've constructed, content we harvested, and invariably whether it's constructed or harvested, we're constantly curating the content in order to move forward. And then we have the courses where individual campuses have individual hubs and individual hubs have individual courses and individual faculty to customize, remix and match and build whatever they want and have the control, the flexibility that they want outside or so. While it's centralized, we do not curate this content, the exception of running bots and cleaning things up in order to make sure that things follow a central standard. But we have the content in the bookshelves as the canonical repository of things. So we have somewhere in the order about 750 books that are in the bookshelves. I want to mention this very clearly. Actually, I'll be showing it in a moment here with a new slide. So I mentioned that the OER universe is fragmented. This is an example of that you can find content or links of content in the open textbook library. I need to make sure that I'm seeing chats in case I'm supposed to be going quickly. Thank you. So we have, you can find content, you find links to content in the open textbook library, which is largely a library guide. OER Commons, which is more of a refertory with some repository stuff, OpenStacks, why am I not moving here, Merlot, Open Sunny, Galileo, Open Oregon, NOBA, BC Campus, Ontario, Alberta, Hawaii, Sailor, Affordable Learning Solutions, and there's a whole slew of other content out there. So this is a need in order to centralize content. So what we are doing, or at least part of our thrusts off of here, is to take content and make it available in order to build effectively. And that building effectively is not just building from scratch, but to remix from existing content. So whenever you're building anything from scratch, you need to decide what your platform is off of there. So if you're building a house or something like that, you can build in Tinker Toys or Lego Babies, Lincoln Blocks, Duplos, Legos, Erector Sets. And you can, you can pop in various formats of websites, latech, PDFs, et cetera, if you want to make this analogy into the OER Engine. What we are doing is we're taking the content, oftentimes PDFs or other things, we rip them apart, bring them into our platform. In the database, you then can go in and edit, modify, curate, and move forward, whilst PDFs, for example, are a dead format that do not enable that. So we go through this effort so that the community doesn't have to worry about that. They can actually capitalize on it. So you come in, it's a Lego store, you can come in and you can pick and choose things effectively, and we build technology in order to enable that in order to build a book useful. We're basically assisting OER, we integrate into libraries, and then we spend a lot of effort standardizing existing formats. So the key point here is that when we harvest content, we're not just storing a PDF off of there, we're doing, going through a lot of effort to rip it apart, convert all equations into latech, make sure the format's all established, make sure it's easy in order to cut and paste, because anyone who's ever tried to cut and paste a PDF, for example, into a document understands the pain of going from one format to another format. We also have standardization of meta tags in order to be able to allow more powerful approaches off of that. So we have a handful of advanced features, visualization capabilities, embedding executable code via a Jupyter notebook system. I want to skip over the community thing. I just mentioned one last few comments here. So we have this greater Libreverse here. But its utility as a dissemination mechanism is only dictated by the dissemination tools that we have off of that. So we can disseminate into learning management systems into mobile phones, or we'll have an app that'll be coming out in a few months in order to do that, directly to LibreText. We have a LibreText in the box, which is a Raspberry Pi hotspot for developing countries. We can just basically get it and get the whole library that you have available. We have 300,000 pages of content out there or physical books. So any content that we have on our site, we have the ability and that's compiled to be able to let anyone purchase a physical book. So for my general chemistry book, normally $300 and now let students that they want to purchase it for $12 plus shipping, they can go about doing that, and that's perfectly fine. And you can see that right now of over 1200 books remixes and books. Essentially located is available for rapid on printing demand. We just basically take the money and hand it off to the printer we're not taking any money off of that that way we don't have to conflict with non commercial clauses on on the content. And it can be branded and dynamic for faculty instructors is an example of that general chemistry textbook that I'm going to be using next quarter out there. So this is a version of Libertex in a box. So this is a Raspberry Pi box costs about $45 and you can load it with the entire Libertex libraries, you can ship it off to developing country you can ship it off to submarine or the ocean could be in the, in the Andes. And as long as you have a Wi Fi enabled device you can then get access to all the content out there with a lot of the JavaScript capabilities that's available off of that. And mentioning again, we're implementing a community built OER platform is comprehensively curated at multiple levels. Hopefully you find us useful. And what we're doing with that I shouldn't mention where we got our support which is largely from federal agencies, both from the state of California from NSF from the Department of Education that's responsible in order to move our project forward, because what we believe is that OER is part of our educational mission, which means it's part of the mandate of our governments in order to support with that, I thank you for your attention.


Good afternoon coming close to the end of day three at the World Famous Mining Show in Toronto, Ontario We have the pleasure of being with Alf Stewart who's with searchlight resources Alf. Thank you for coming by you're welcome Peter Now you and I only met for the first time today But we seem to have a lot of friends in common one of them being Steve Wallace the CEO at searchlight. Yes So what are you doing with searchlight? I'm helping them raise money. Hey, it makes you everybody's best friend. That's right Searchlight has a variety of really interesting properties in the interest of disclosure I advise to searchlight from time to time because I like the CFO and I like to see eel The property I like best is what's called the Dudbridge property, but you have a different opinion. Yes, which is your favorite? My favorite is the English Bay property just outside of LaRanche Ontario or Quebec? LaRanche Saskatchewan. There you go Why do you like that one? Because it's a very very unique situation. It's Privately developed it's never been in the public market and it looks like a very strong gold system. Prior drilling There's 37 drill holes on the property 5,000 meters of drilling Of those 37 drill holes 20 have intersected gold along a consistent 400 meter long zone And with that conversation we didn't ask the risk because none of that was 43 one-to-one or QP'd right? That's correct We've had a conversation about this our first action on this property will be to have a competent person review all of those results and verify them Good searchlight trades on the venture exchange SCLT on the TSX ventures. I like Dudbridge because it was a Originally 43 one-to-one for uranium with a significant deposit, but Steven went back and looked at the old data There's also vanadium and cobalt there and to me That's a sexy property and that's also in North Saskatchewan a little bit further north Yes, what else is in the portfolio? There's another gold property near Flynn flan So Flynn flan is interesting because it's right on the border between Manitoba and Saskatchewan, right? We're on the Saskatchewan side and there's a property that we have an option We've earned a 51% interest in it and it has three former producers on it three former gold producers Wow And it's within driving distance of Flynn flan which is a major mining center in Canada And if I remember correctly, there's also a former mine on another one of the properties That can be reactivated right so the the main Mine on the property was developed in the 1980s. They did 1.5 kilometers of underground development and never produced gold Why not they went bankrupt? They borrowed money from a bank and that's not how you finance gold exploration What year was that? 1983 okay, so interest rates in the early 80s were running around 18 percent exactly and the gold price was $350 it's a tough way to make a living yes today looking at gold prices if we take the $350 historical gold price in US dollars convert it to Canadian dollars today That's about $900 in current gold prices, but the gold price today is $2,100 Canadian over twice the historical price when this property was developed Well, one of the advantages that Australian and Canadian properties have is their expenses are in local currency where the revenues in USD so it does create an extra layer of comfort there for investors. Yes So what's next you're going to raise money has that been announced in the public yet? The company has been attempting to raise money flow through at five cents for a few months. Stay tuned That's an excellent way to end this elf is wonderful to meet you hope to see you again Searchlight resources on the venture exchange day three at PDAC. I'm Peter Clossey. Thank you


Hey Tavesee and our Richardson here with Bill. We're doing a special version of T-shirt Tuesday to mark the Army Navy game, the football game of the year. Alright, this is the year we turn it all around, put Navy back on top, break the winning streak. Blackjack, seriously, we're trying to do a thing here. Come on, man. Blackjack, blackjack, settle down. Hey John, how are you man? Good to see you. I was on your Facebook page and I saw your T-shirt, it looked a little small, so I thought I'd get you one that was probably more appropriate. Beat Navy. Alright, thanks a lot. We'll work that into the rotation. That's just rude. Mark, I'm sorry, here, why don't you take this one, you can get your own Facebook thing, go and work out. Beat Army, I don't know if I can have this one, but I tell you what, blackjack looks like blackjack needs a T-shirt right now. He does. Blackjack, why don't you take that T-shirt. This happens every year. Oh, f*****g no. Like every time. Every single time. You can't control them.


Hello everyone, the topic of this part is best practice for accelerated image distribution using Dragonfly. There are two speakers. I'm Wen Boqi, working as a maintainer for Dragonfly at Ant Group. I'm my partner, Yi Yang Huang from BatDance, who is also a maintainer for Dragonfly. First, let's introduce the Dragonfly project and some other research and development dates in the past year. Dragonfly is an open-source, P2P-based file system and image acceleration system. It's hosted by cloud-native computing foundation as an incubating lab project. It's designed to improve the physical and speed of large-scale file distribution. It's used on the fields of the application distribution, touch distribution, log distribution, and image distribution. At this stage, Dragonfly has a habit based on Dragonfly 1. On the basis of maintaining the capabilities of Dragonfly 1, Dragonfly has been upgraded in major features, such as system architecture design, product capabilities. Dragonfly has been selected and put into production used by many internet companies. Since its open-source in 2017 and InterSensef in October 2018, in 2020, Sensef TOC voted to accept Dragonfly as a Sensef incubating project. Dragonfly has developed the next version through Production Protects, which is observed the advantage of Dragonfly 1 and met a lot of optimizations for non-properms. Now that Dragonfly has been released more than 270 times, the project has active commits for a long time. We can refer to the first picture, which is the commit date for the past year. Dragonfly maintainers come from different companies, include Ant Group, Alibaba, Baddance, Baidu Group, GitLab. Listeners who are interested in the project can join in the community through the link below and discuss the future development of the project with us. Some listeners may not know much about the Dragonfly project. I will introduce the architectures of the Dragonfly project and the rules of each service. First, Dragonfly consists of four services, including manager, scheduler, set peer, and peer. The manager in the project can be used as a manager service. The scheduler in the project can be used as a scheduler service. The DFD men in the project can be used as a peer service and all set peer service. We introduce each service. First of all, the manager service, which is a management service, is used to manage the relationship between multi-clusters. A P2P cluster includes a scheduler cluster, a set peer cluster, and multi-peers. Multi-P2P cluster are managed by the manager. At the same time, the manager also provides a dynamic configure management, such as controlling the load of peer and set peer. The manager can also become a certificate issuing CA service, issuing leaf certificates to scheduler, set peer, and peer. It also provides a front-end console, which is easy for users to manage P2P clusters. It also provides user-related features, such as use mode, management, and RbAC. Also provides open API, such as pre-hate API, to be coded by other services. Of course, the main feature of the manager is to manage the capability of the cluster. It can remove inactive service drives from the cluster. Scheduler is a very important service in John Fly. Its main feature is to select the candidate download parents for download peer. When the peer download is failed, control the peer to back-to-sons download task. Of course, the scheduler is still very completed. It will build a deck of peers, and in the scheduling, it will go through filter and evaluator to select candidate parents. Set peer can be triggered by the scheduler to download back-to-sons and dive the resource into PCs, which can be used as the root node of the cluster resource. And it also has the feature of peer. Urally set peer in the cluster provides high performance machine and high quarterly network environment. Which downloading task for the first time, they can back-to-sons download the resource at the faster speed. Peer is the client in P2P network. It can be downloaded and uploaded. It will start a DevGate daemon to distribution. It gets the parents by exchanging information with the scheduler. The DevGate daemon and DevDaemon extensions DevGate, Dev Store, and DevCache command line choose a CSS architecture. For example, DevGate will download files with command line and DevGate will call the JPC API of daemon to download files. The above picture shows a download precise. First, peer will assign the most matching scheduler address from the manager. Then peer adjusts the task with scheduler, and peer will build stream with scheduler. If the task is downloaded for the first time, the scheduler will trigger the set peer to download back-to-sons. The scheduler returns the candidate parents to the peer. Then peer will download pieces from parents, and build the piece into a completed file. Users can deploy the set peer in a place where the network environment of the source is better, so as to ensure that first time back-to-sons is as fast as possible. Of course, we can see that John Fly can support different types of protocols for P2P transmission. Firstly, John Fly can support object storage, such as AWS Google Cloud Storage, Azure Blobs, Aluminum OSS. Object storage is also a common solution for storing machine learning modules, so John Fly can also provide service for inference modules, and accelerate the process of pulling modules. John Fly also provides acceleration for container images. John Fly supports many clients, including Docker, ContinuD, CIO, OR, AS. John Fly also supports the HTTP protocol, and the HDFS protocol. This supports for the HTTP protocols, expands John Fly's range of use. John Fly and Netus load for both lazy load container images, and download with P2P technology. We will provide users with a set of container image acceleration solutions based on Hubble and John Fly. First, we will build the image, then upload it to the Hubble, and then download the container image through container D. When downloading the layer of the image, it will be accelerated through the John Fly P2P network. In this way, users have an image acceleration solution based on P2P technology. Netus acceleration framework implements content addressable file system that can accelerate the container image startup by lazy loading. It has supported the creation of millions of accelerated image containers daily. Currently, its containers come from Ant Group, Alibaba Cloud, and BatDance. Netus has many features include an image can be fetched on demand in chunks for lazy load, lazy pulling to both container startup, deeply integrated with Netus kernel's ERFS and FS catch, enabling internal support for image acceleration. From build time to runtime, Netus covers container ecosystems, such as Docker, container D, podman, buildkit, node control. Faster build speed than OSI-V1 gzip or GSTD format, as well as the ability to directly accelerate OSI-V1 image. The ability to deduplicate data at the trunk level between local and server-side reduce storage waste of over 50% caused by incremental builds. We will provide users with a set of container image acceleration solutions based on hardware, John Fly, and Netus. This is a more perfect solution. First, we will build the image into a Netus image, then upload it to the hub and then download the image through Netus's snapshotter, which of course is a lazy load. When downloading the data of our file, it will be accelerated through the John Fly PDP network. In this way, users have an image acceleration solution that can be used on demand and in joint PDP acceleration. That's the performance of a single machine image download after the integration of Netus, mirror mode, and John Fly PDP. That's the running version commands using images in different languages. For example, the startup commander user to run a pattern image is a pattern version. The test will perform on the same machine due to the influence of the network environment of the machine itself. Actually, download time is not important, but the ratio of the increase in the download time in different scenarios is very important. Tess has different scenarios, including OSR V1, use the container D to pull the image directly, Netus codeboot, use the container D to pull the image through Netus snapshotter and doesn't hit any catch. Netus and John Fly codeboot use the container D to pull the image through John Fly and Netus snapshotter, transfer the traffic to John Fly PDP based on Netus mirror mode and no catch hits. Hit John Fly remote peer catch, use John Fly to pull the image through Netus snapshotter, transfer the traffic to John Fly PDP based on Netus mirror mode, and hit the remote peer catch. Hit John Fly local peer catch, use the container D to pull the image through Netus snapshotter, transfer the traffic to John Fly PDP based on Netus mirror mode, and hit the local peer catch. Hit Netus catch, use the container D to pull the image through Netus snapshotter, transfer the traffic to John Fly PDP based on Netus mirror mode, and hit the Netus local catch. Test results show Netus mirror mode and John Fly PDP integration. Use the Netus download image to compare the outside WeE mode, it can effectively reduce the image download time. The codeboot of Netus and Netus and John Fly are basically closed. All hits to John Fly catch are better than Netus only. The most important thing is that if very large Kubernetes clusters use Netus to pull images, the download of each image layer will be generated as many range requests as needed. The QPS of the source of the registry is too high, cause the QPS of the registry to be relatively high. John Fly can effectively reduce the number of requests and download traffic for back to source registry. In the best case, John Fly can make the same task back to source download one only once. John Fly also has very very good practice in machine learning. Inference energy include test floor serving, turtle server, and torch server. They will download modules from object storage. John Fly supports different types of object storage protocols. Allowing it to support the effervescence energy to download modules through P2P technology. This provides the object storage from reaching bandwidth limitations and download modules slowly. It can accelerate the download speed of modules and reduce the bandwidth on the object storage. Many companies are currently using John Fly to accelerate their download modules in the inference energy. Hello everyone, my name is Huang Yi Yang. I'm a software engineer from Bidance. I will introduce best practice using John Fly in Bidance Cloud Service Volcano Engine. Before start, let me have a short introduce about products of Volcano Engine. John Fly will be used for them. Container registry CR is a product of Bidance Cloud Service Volcano Engine, which provides secure and highly available container image hosting services to facilitate users to manage the entire lifecycle of container images. Volcano Engine Kubernetes Engine VKE provides high performance Kubernetes container cluster management services centered on containers through deep integration of next generation cloud-native technologies, helping users quickly build containerized applications. Volcano Engine Container Instance, VCE is a service and containerized computing service. Currently, VCE can seamlessly integrate the container service VKE to provide Kubernetes orchestration capabilities, with VCE users can focus on building the application itself without purchasing and managing infrastructure such as underlying cloud service and only pay for the resource consumed by the actual running of the container. In Volcano Engine, users use CR to store and manage their images. There are some limits in two scenarios. First, in a VKE Kubernetes cluster, the number of clients is increasing. The image used by application may reach GB level. Second, if an image is converted to Nordic format, the number of requests will increase by an order of magnitude. Therefore, the concurrency or pool is limited by the bandwidth and QPS in the end. We did some research about P2P projects in community. There are two production available P2P projects, General Fly and Kraken. Here is the comparison about them. They are both high available. Continuity support, HTTPS artifact registry support, and production available. But Dragonfly has some advantages. Its community is more active and has more users. It is used by Ungroup, Intel, Baidu, DD, Kwaishou, and many other companies. Kraken is used by Uber and NetEase. Most importantly, Dragonfly is Nordic-competible. The architecture complexity of Dragonfly is less than Kraken. So, Dragonfly is a better option and we choose to use it. How to deploy Dragonfly in Volcano Engine? We need to consider three points. How to deploy in VKE? How to serve for VCI? And how to serve for Nordic? In the Volcano Engine, VKE and VCI pool images through CR. The product feature of VKE is Kubernetes nodes deployed in ECS. So, it is very suitable to deploy DfDamon on each node, making full use of bandwidth of each node, and then making full use of P2P capabilities. The product feature of VCI is that there are some version nodes with sufficient resource at the bottom level, and the upper level services are carried by ports. So, it is impossible to deploy DfDamon on each node, like VKE. So, several DfDamons are deployed as caches in the formal deployment to take advantage of the caching capabilities. The VKE or VCI client may pool the Nordic converted image. In this scenario, DfDamon needs to be used as a cache. If using too many DfDamons as a cache, it will cause scheduling pressure for scheduler. Here is our architecture with Dragonfly. The resource in the Volcano Engine belongs to the main account. The P2P control components, scheduler and manager are isolated at the level of the main account. Each main account has a set of P2P control components. The control play implements the P2P manager controller, which all P2P control components are managed. The P2P control components is deployed on the VPC, on the control play on the CR side. They will be posed to the user cluster through LB. In the VKE cluster, DfDamon is deployed as Damonset. It is deployed on each node. In the VCI, DfDamon is deployed as deployment. Continuity on ECS access DfDamon through local JS. By deploying a controller component in the user cluster based on the private zone, a certain domain with class IDs generated in the user cluster. And the controller will select DfDamon port include port in VKE VCI according to certain rules. An A record will add to this domain. By visiting this domain, client can access DfDamon. Node is Damon on ECS access DfDamon through the certain domain. Image service clients and Node is Damon on VCI access DfDamon through the certain domain. Here is our benchmark data. The environment, CR bandwidth, 10G bits, the ECS 4CAG. With local SSD, the bandwidth is 6G bits. The test image is engines and TensorFlow. The version of Dragonfly is 2.8. The core tau DfDamon limit is 2C6G. We deploy scheduler and manager to replicas. The request is 1C2G. The limit is 4CAG. Here is engines port creation to container start benchmark data. And here is TensorFlow port creation to container start benchmark data. In a scenario of large-scale image pooling, using jengfly and jengfly with notice scenarios can save more than 90% of the container startup time.  Here is pooling engines image peak bandwidth comparison with using jengfly or not. And here is pooling TensorFlow image peak bandwidth comparison by using jengfly or not. Here is pooling engines image back source traffic comparison by using jengfly or not. Here is pooling TensorFlow image back source traffic comparison by using jengfly or not. In large-scale scenarios, the number of images pulled by jengfly back source is rare. In OCI scenario, all images pulled must back source. Therefore, the peak and back source traffic of using jengfly is much less than that of OCI scenarios. By using jengfly, the number of concurrency increase, the back source peak bandwidth and traffic will not increase significantly. Finally, thanks. I hope more developers can pay attention to jengfly and the nettles. Interested developers can scan the QR code to join our GitHub group or join our select channel or follow our Twitter. We will release some version information and feature upgrade information. Thank you.