What is going on ladies and gentlemen? It is a beautiful Thursday afternoon here in Miami, Florida and 1 30 p.m. Eastern Standard Time and Today we're gonna be talking about out coins So if you guys were here last week when we went live and we did our analysis on the different out coins One of the main ones that we spoke about was avalanche and since then avalanche has basically taken off so It was it was a crazy week for a vax. I think on the week it is up 45% on the week so it's currently sitting at about 38 dollars and we gave you guys We're when we were looking at it. It was at around 28 dollars or 29 dollars around there We spoke about a breakout above It was above about 30 dollars So I give you guys two options I give you guys 30 dollars or more more conservative approach was 32 dollars, which is where the Fibonacci level was If you guys took any of those You would have made a nice profit In a trade because it went up as high Got up as high as 42 dollars and 89 cents. So It was it was a it was a doozy as you like to say right So today, we're basically gonna be gonna be doing the same thing when I look at some of the top performing coins we're gonna go over them see where things are and Potentially where they can go right and we're gonna look for some Potential trades that we can take with within the next seven days basically Some trades that I'll be looking at some trade setups that I'll be watching to potentially take myself So that's pretty much what we will be doing I'm gonna Start out with the top coins in the market. So by market cap We'll go through the top coins. We'll see which are the best performing ones and Then after that, I'll pick out like five different ones probably from the market that are the best performing ones in the last seven days See if we find any type of trade setups there And then if you guys have any requests for any out coins that you want me to take a look at Then you could drop them in the comments And I will take a look at those as well Look at their charts and kind of analyze them see if there's any potential trade setups or how the outlook on it is So let's go ahead and dive right in. Let me swap my monitor to Let me switch over to my monitor. Here we go All right, so These are the top and me let me refresh it just to be sure but these are the top performing coins here Over the last seven days. Well, these are the top Let's look at the top performing coins first that that's just top market cap So the top performing coins in the top 100 market cap over the last seven days are these right here We have bunk up 75 percent. Remember bunk is a mean coin. So, you know, those get pretty wild Injective This one's up over 71 percent. So this is this is a good one to look at today We have bit torrent. This is up 68 percent Osmosis up 61 percent Woo Network up 53 percent and if we look at the within the top 10 we have avalanche 44 percent we have Cardano Cardinals and another one that we wanted that I want to take a look at today It's up 40 percent in the last weekend guys like just two weeks ago Cardano was trading around 30 cents It's at 63 cents now. So that's pretty wild there Any of the other top 10 top 25 we have polka dot up 17 percent Solana up 10 percent. So Solana slowed down a bit. It had a massive massive move over the last month or so And so on the top losers We have Terra Luna classic, of course down 13 percent Kava down 8 percent Thor chain down 8 percent Conflux down 7 and a half in Lido Down 7 percent. So Let's go ahead and start here with the Top 25 market cap. Let's take a look at the top performing coins Over the last seven days here So we got let's see B&B is up 8 percent Solana up 11 and a half percent Cardano up 40 percent. That's insane Avalanche up 45 percent. That's insane polka dot up 17 percent Cosmos up 15 percent that's another one we looked at last week and In these two here of 29 percent for internet computer and 47 percent for immutable All right, so so let's go ahead and start here I want to start with Ethereum even though it's down 2 percent over the last week The reason why is because Ethereum is the king of Outcoins, right? We know that Bitcoin is a king of crypto and Ethereum is the king of the outcoins Let's pull up our Let's pull this up here. Let's see how he theorems doing year-to-date. So you're today theorems up 91 percent Right in the last year. It's up 73 percent. We look at Bitcoin Bitcoin year-to-date. It's up 161 percent in the past 12 months 142 percent. So This is something that we see pretty often Where in the beginning Bitcoin outperforms Ethereum, right? That's almost always how these These bull markets begin the main mover the the the one to set it all off is Bitcoin It sets the stage for everything else basically so Then then comes Ethereum starts following and before you know it starts outperforming Bitcoin and and of course the outcoins Look at look at Solana up 638 percent year-to-date. That's wild So of course outcoins are always going to be a lot more volatile, right? So You you'll see that in in the price movement here. So Yeah, Solana looks like it's it's one of the biggest winners of this year as far as the top coins That we're looking at here. So that's pretty wild. Nothing else is even close to it right now And and like coin of course only up 3.3 percent on the year-to-date like coin is always a lagging lagging coin, so we usually expect a light coin to move post Bitcoin halving. So that's That's something that that we're gonna be looking at there probably later on what we won't see too much movement And we have Matic. It's only up 14 percent year-to-date This had to do with the SEC when when they started attacking a bunch of different cryptos and Matic was one of the ones that they attacked and It dropped significantly basically when that happened because it was mentioned in one of those things Arb and Aptos both of them were were basically came out very recently. So Arb is down Aptos is is still up though The lure this was another one that we liked RVF This one's been doing great. All right, so let's go ahead and jump into Ethereum and remember if you guys Won't have any requests on any out coins That you want me to look at drop it in the comments I'll be looking at those in a little bit We want to start first here with a couple of the top performing coins here So we're gonna start set things off with Ethereum. It's up about 91 92 percent year-to-date And and it hasn't been performing too bad. It's it's been a little it's been lagging behind a little bit, but it hasn't been too bad so We can see Where's the fib so I like I always like to start off with the Fibonacci We already see some levels here. We'll look at those but I wanted to Draw out the recent move the most recent move here. There we go Hmm. So so we can see here From the from October Which is the the recent bottom right the most recent bottom here It's it's basically had a massive move up to the upside it went all the way from about $1,500 all the way up to $2,400 right so we we just recently saw a pullback here and this was across all the market basically and we can see that it came exactly To this Fibonacci level here. This is why I like to pull up The the Fibonacci levels retracement levels because they give us a pretty good idea right About where things could pull back to so and and if looking at this right here This gave us the exact level of the pullback basically, which was 2200 If if it were to lose this level, then we could potentially see it go lower Maybe to back down to 2000 area, which was this big area right here This big cluster of price action So that feels like it would be a another big area there for For Ethereum, but 2200 has always played a big role in Ethereum And it looks like it played a big role here again on this retest here So this was this this might have been a pretty good entry there at 2200 Now it's gonna it looks like it's pushing back up Of course recently we got some bullish news across basically all the markets And that news was that Yesterday so we got two different things have that happened this week Yes, well on Tuesday we got the CPI data right the CPI report Which is basically the inflation data from the past month And inflation year over year, which is the main the core thing that main thing that people look at It went down from I think was 3.2 percent to 3.1 percent So year over year inflation has continued to slowly drop down And then yesterday We saw we got the Fed interest rate decision and they decided to pause it and They you know, not only did they decide to pause it, but in the report itself. They spoke about They I think it was 17 different members of the Fed that are that are on the board They they they're predicting basically three weight cuts in 2024 And then of course when Jerome Powell spoke he speaks 30 minutes after the report comes out He was basically speaking to that same You know sound right to that same Talking about that they believe that what they've done with interest rates that it's enough and That they're gonna they're not then they're probably most likely not going to be raising interest rates again Which is bullish overall for the market, so Now we're expecting cuts in 2024 and we could actually see that if we look back here on the monitor We can see that they're starting to To look at the cuts, right now. We're I think they're expecting you there's only a 18% Expectation of probability for a cut in January. I don't think we see it in January Maybe in March though in March. It's expecting the probability for a cut in March is 66% currently so that's that's really really big Hmm and and one thing that you have to know is that when there's a cut in interest rates that means Markets basically everything in the market starts to pump up starts to shoot up and that's because money is getting cheaper to Use and to borrow right so then people are borrowing more money if you're able to borrow more money You can invest more money, which means you can Push more things you can sell more things and This basically Boosts the economy right it pushes everything up. So when we get that first cut it's gonna be big And markets are going to try to price this in so you'll see markets starting to push up with the expectation for a Rate cuts and I expect to see that you know here next year so You can see in May they're expecting two cuts by then because This is 62% for 475 to 500 For 50 so they're expecting three cuts by June. I don't know if we're getting three cuts by June But I definitely expect some cuts Leading up to that like put potentially in March, which would be very bullish overall for markets And this is lining up with the Bitcoin halving.  We've been talking about this over the last few years That this rally was coming So you've had plenty of time to prepare for this You've had pretty much two years to prepare for this at this point because we hit all-time highs I believe in 2021 and around November 2021 If we look back on that Let's see Yep, November 2021 is when we hit those previous all-time highs and We're now in December of 2023. So you've literally you've had three years. I mean two years to prepare for this This massive massive run that's coming or at least over a year from the bottom here in June 2022 So plenty of time, right? So with all that said, let's look at Ethereum and see If there's a potential for a trade here in around the next week or so So currently we're Ethereum is sitting at 20 about 2300 For day trades, I think my magic number for me is 2200 We actually took some trades there at 2200 when we retested this level here This past week in the discord group My next level, I'm not sure 2300 I Don't it's kind of you see how it's kind of in the middle of nowhere. There's not really Anything that will Is giving us, you know, letting us know if it's could potentially go up or down So that's what you call the middle of nowhere, right? There's not really much to do there at 2300 As we approach 2400 we see that we run into this Kind of a resistance. It's just kind of the the previous high of this year So one trade setup that you can potentially use here is a breakout trade above this high here So that high was 2407 so it would basically be a breakout trade above 2407 so maybe you could place it at 2410 or something like that And and my expectation my target would probably be up here $2,500. So I think 2,500 is an next big level for Ethereum here and I'm definitely setting up a long position above 2,500 So those are the two well three set three setups that I'm looking here at that I'm watching for Ethereum break above the yearly high 2408 break above 2,500 any retest of 2,200 I am longing setting up long positions on all of those Now I'm not really looking to short anything here. I don't like to trade against a trend Especially with leverage. So I probably won't be looking at any shorts this week So that's just more or less what I'm looking at here in Ethereum. So next let's look at Which was the next best perform well, which was the best performing it looks like Avalanche was the best performer here. So let's go ahead and take a look at Avalanche. Let me take a sip of water real quick We got Carlos in the chat. What's up Carlos? Gaki was going on We got claws claws say got a quick question about the algo signals Hmm So the signals are for 30 minutes and 60 minutes, but I sometimes join later if the conditions are still the same Would you recommend that and how long does that work? So so he's asking about we if you guys don't know we have an algorithm That basically sends out trade signals in our discord now and he's asking about the bot Hmm so you're saying that sometimes you join later if conditions are still the same Yeah, so as long the the way that I see as long as the Targets haven't been hit then you can still jump in the trade even if it's your The entry is lower than what the bot with the bot signal, right? So let's say for example, if we're looking at Avalanche, right and we say the bot gives you a signal to enter here at $38 in 90 cents, right? if Let's say target one is $40 and Stop loss is at let's say is down here at $34. So if If target one hasn't been hit then I don't mind that like I I'm open I like to enter that as well and and Just you can use the same setup even if the price is lower. Let's say the price goes down to 35 36 dollars I would still enter that and that's actually better for you because you're getting a better risk to risk to reward Get you're getting a better risk Reward for your risk. I'm like getting stuck. You're getting a better reward for your risk So so I don't mind that at all as long as the targets haven't been hit once the targets are hit then the bot automatically is going to consider that trade as a The the trade is basically done like there's no more entries at that point. So it'll never signal a Stop loss at that point because it's considering that trade a win already. It's a success So that's how I would play it if there's a signal that was given, you know a few hours ago An hour ago, whatever That target hasn't been hit and stop loss hasn't been hit then you can say you can still take that trade So I don't mind that at all All right now jump in back. Let me see back. Here we go jump in back and I was on my face. I meant to show this chart by the way Claws, let me let me know if that helped it if that answered your question on that So All right, where were we? So we're looking at Avax avalanche. So on Avax Hmm, we spoke about this level here last week 32 $30 and I think we we were live on Friday. So we're alive during this candle right here We had a 15% move up on Friday, which is why we were looking at this at avalanche And we told you guys about this breakout right here and that breakout was very very successful If we just kind of take a look at Where that would have put us remember? I said $30 was was pretty much Where I would play the breakout That's a 42% move from that breakout. So if you use if you trade with leverage like me If you trade it, let's say with 10x leverage That's 400% profit if you caught it here at $30 sold at the top So even if you didn't sell at the top and say you sold right now Even if you sold right now, it's 280% 288% profit So very very profitable trade there guys And even if you instead of using the $30 you use the 32 At 32 you would have done still over 200% profit You'd be in right now if you use 10x leverage like I do with When you trade so great move there now for this week, let's see if there's any other Trading opportunities here for us So let's start with a top-down analysis Let's see what we got so So we know this level is a major level there at $32. That's one of the main levels that we We were watching that was a main breakout level for us And we've run up to about 42 almost $43 now looking back historically We can see we had kind of a similar thing here, right? So that's that's pretty interesting. It's kind of it looks like it's pretty much right around $43 Let's make this smaller Whoops, I didn't mean to make that All right So let me change the color here. I can't really There we go So it looks like we definitely have some resistance here at this level, and that's right around $43 44 and After that the next major major major hurdle for avalanche looks to be around here, which is around $56 So that's that's currently the biggest thing right now. Now next thing that we want to do now We want to since we're looking for a potential day trade or Short-term swing trade Let's zoom in to the weekly here Hmm, and now that now that we zoom into the weekly we can see that same look at this resistance here So we had look at this move here Where it was basically a massive massive move up It got to this resistance here, which was that 45 to $50 range and it got rejected and it kind of Consolidated here for for a few it looks like for a few months really Before you know, it actually ended up dropping and then took off even when it took off again with all this momentum It went up this this weekly candle is a hundred and thirty two percent by the way massive massive candle Even with that It still got rejected there and it still took another one to three weeks before it finally left that area and continued up Ended up setting a high of a hundred and forty seven dollars during November of that bull market So I definitely expect that To get not only hit but to get smashed In in the next year, right? So let's see is it so there's a possibility for rejection here consolidation here And this consolidation could go out can go either as low as back to thirty two dollars or Potentially back down here in that twenty dollar range so my first Instinct is I Will love to build an entry here at the thirty two dollar mark So I like that entry. I'd be you can see we hit it there went down as low as thirty one dollars and sixty cents So I love that entry third at thirty two for a long position My next one Would be above the recent high which is basically above this big resistance here So you could set up a potentially a breakout trade there above that level. I wouldn't mind that I also don't mind using the 40 levels since it's a big psychological number. It's a big whole number You can use that as a breakout as well with your first target being this resistance Which is basically forty four dollars um Yeah, that I saw so I don't mind that at all and That's basically the two trades that I'd be focused on this week I'll pull back to thirty two or a break above the this this high either break above this high or a break Above a forty dollars. You can use that that big whole number as well So yeah, that's pretty much what I'd be watching. I'm actually move this which is my alert To thirty two dollars in the event that we get thirty two dollars again there Because I definitely want to take that as it as a trade and I'm gonna move this alert up to The recent high So that's the recent high there and I'm I'm gonna use that alert there. I'm actually just take away This since I have the alert there. It's basically the same thing So I have two alerts set up here and that's that The recent high here and at the thirty two dollar range there that we spoke about so those are two setups that I will be Watching here and actually I'm gonna do the same for me theorem I must set up the alerts and this is the best way for you guys to trade these things self alerts That's gonna be the best way so that you're notified if the price does hit that range And then you could look at it and build a trade if you want to take a trade around that So first let's let's put one at the yearly high So I got to do is hit add alert here for ethereum crossing above that price So I'm gonna put above four hundred twenty four hundred, right? I want to I want to know once we cross twenty four hundred so that I'm I could potentially catch that trade and message just Ethereum crossing twenty four hundred. I'm gonna just put above 2400 So I'm very simple create that alert. Did you create it? Where is it? Yeah, just I don't know why it's set up like this Where can I? Whatever, we'll leave it how it is. Alright, so we have that one and then the next one remember was twenty two hundred So I'm not just do the same thing here set up an alert 22 open-ended Again, I'm just kind of do the same thing here. Just wanted to say ethereum crossing 22. That's fine. 2202 is fine perfect So we have two alerts set up there on ethereum. We have two alerts set up on avalanche here Next one. We're gonna look at is cardano So let's analyze this one and see what we can set up some alerts as well They're called crazy. This is we were literally two months ago We're sitting at 25 cents and Right now we're at 63 cents. So Almost a 2x in two months. So that's pretty wild guys All right, so let's let's look at let's start with the monthly and try to try to see where we can build a Potentially build a position here or build a trade Right, we're looking for big levels that have historically had effects on the price So we can see one big level right here. This is 70 around 70 cents Which coincidentally is right where this Fibonacci level is as well Which is a right around that 70 cent area? So right off the bat that peaks my interest And I like that level right so That's a level that I am willing to play For a trade So so right right off the rip guys, I'm gonna create an alert right here Of course the Fibonacci levels there, so it's not letting me put it I'm gonna just create it a little bit above it so I could set up the alert so crossing Is gonna be crossing 70. We're just gonna move it down here 88 crossing 70 Let's move this down to where we want it and even a little bit under it. That's perfect I like it So that's the first alert there because that's that's a trade setup that I'm potentially looking at To set up right Now let's now let's zoom in a bit because we know the bottom levels are down here We have we last week already drew that this level right here. This this was a good level right here So we actually spoke about this level look we drew this box. So this was the last week when we looked at it and This week this this candle is 69% guys that is crazy This is 69 is monthly. So last week. Where were we last week? Okay. So last week last week was a 50% move Yeah, so we're looking at a move either back down here or above this now another some more confluence We can see we have the 200 week moving average up here as well So those are two different things that we have here as resistance Right, so a breakout above that should be pretty strong for Cardano here So it's definitely I might actually move my alert Whoops, I moved the wrong thing. Let me see if I can grab it. No So it's not letting me grab it. It's it's basically forcing me to grab the Fibonacci level every time Oh, there we go. I moved it. So I'm gonna put the I'm gonna put this here at The 200 day moving out not 200 day 200 week moving average Because I do want to know a little bit before we get there So if I decide to set that trade up, I have a little bit of time to set it up. So We're gonna we're gonna do that Of course, the other level that we're looking at was down here And we're gonna set up an alert there as well because that's that's an area I want to know if we end up crossing and And It's pretty much down here now the levels down here. However 50 cent is Also, I consider a big level because it's a big hole number and you can see there's been a lot of price action They're at that level at 50 cents, right? So I'm gonna put the alert here at 50 cents and then I could either play that level or I Could set up trades down here for a long order if we get down here So setting up those two alerts there and those are basically the two setups that I'll be looking for in Cardano either a break a Breakdown here to this support level down here or a breakout up here Which could you know potentially lead the price up to the one dollar range, right? So that's the next big level for Cardano if we break above this. So that's What we should be watching here All right, so Let's see. What else what what else has been a top performer here recently We had Cardano avalanche. We just looked at those two. We have polka dots. So let's take a look at polka dot We didn't look at it last week and it's been performing pretty good hmm So to I think two weeks ago is when we spoke about this level right here and Guess what happened last week. We broke above that level. So we pointed this level out This is where I would have had my alert and we cross that level and look what happened when we broke above that level, right? And now Look at what's happening. We're getting close to this resistance up here, which is around eight dollars and Prices starting to slow down So right off the rip that tells us that's probably a big level and then if we start kind of zooming out a bit We can see that it indeed is in an important level, right? We we see it Here it played it as a support there. We see here a lot of price action here. We got rejected So it's a big level, right? so What do we do we place a an order there we place an alert there So, um, let me just set up the alert right there sure So now if the price crosses that The eight dollar range we're going to be alerted. So that's One set up there And then the next level that i'm going to be looking at that i'm interested in is back down here Right. So we broke above this and what usually happens after a breakout is a retest of that level You can see what happened here. We had a retest, but you know, just with things that were going on in the market It ended up retesting this as well So, um, i'm gonna add a level right about here Add an alert there And now so now we have two alerts set up We have the alert here on a breakout of a new high basically And we have an alert down here of this Previous resistance, which should now be a support level Um, and we're interested in those two levels if we're going to look to take any trades on polka dot a breakout above the eight dollar range or a Retest of the six dollar range. Those are the two levels that we're going to be watching in polka dot All right, so, um, let's see anything else in the top 25 that we want to look at Not really nothing really pops out um We can take a look at salana about 11. I know that's one that we've been talking about a little bit So let's let's take a look at it really quick salana Let me get out of uh, let's see. Let's go to Here so here here's where I drew my did my analysis last time And we can see We broke above this level So again, that that was the level that we spoke about you see this was a important level here So now we're looking for something similar. Where's that next important level? And looking back It tells us right like it's not it's not rocket science. I can't tell the future You know, I don't predict the future. I'm not an oracle. I just look for I just look at history and history tells us Where these important levels are So, um, what we're gonna do the same thing. We're just gonna set up an alert there That's at 80 dollars So I love, you know, you guys know, I love those big hole numbers So i'm setting up an alert there for salana if it crosses 80 dollars Right So that's one And you can see after that like There's there's not too much. So so let's let's draw some fibonacci lines here We don't we don't really have any any fibs here So i'm gonna draw one from the previous run And that should give us uh some levels here to look at So to make this a little darker color So a blue so that we know that's previous levels Hmm so you can see after this level here It looks like this level here is it's gonna be another important level for Salana and that's at a big hole number, of course, which is a hundred dollars Hundred dollars will will definitely be a big number here for salana To break above. So that's that's another good spot there. Um, if you guys are interested to create an alert I'm gonna add an alert there That's those are gonna be the two big levels for breakout trades So if you're looking for breakout trades now, if you're looking for pullbacks We can we can either look at this level that's that's already here This fibonacci level already painted one for us. This is right around that 56 50 Yeah, 56 dollar area um Another thing we can do to see if there's any other levels Is uh do a fibonacci Uh On this current run here, right? So we can either do it from the beginning of the year Which gives us pretty decent levels or the beginning of this current move Which also gives us some interesting levels. So Make these yellow because these are more recent actually Make it Pink so it's not the same color as these Um, so you can see that it pulled back to this exact fibonacci level, which is around 63 dollars Um, so the next pullback could be here, which is 56 Then we have this range right here around 47 48 dollars So those are all possible possibilities here um I think the level that i'm gonna highlight to the downside are gonna be these two here I think this is a nice little range here and you can see that that price Consolidated within that range for one two three four Weeks basically before I had that breakout. So I think this is a nice little support range here um right between these two so I would put a I'm gonna put an alert right here At which is 63 dollars Just set one up right there and now we have our our trade setups that we're watching right We're we're looking at uh two potential breakout trades to the upside and we have one pullback trade To the downside if you were to get it and for the pullback, you know, I don't mind entering anywhere there at 63 Or even as low as 56 at 55 area as well because that's another range here It's another support here. So I like that that entire area there All right, so now let's look at um We're gonna look at the top performing overall So I know I'm not gonna look at bonk because it's a meme coin um You know Meme coins are are are very unpredictable but um I mean I guess we can take a quick look at it bonk Let's see on spots Looks exactly like what a meme coin would look like Um started its run in october So like most other cryptos And uh, that's currently where it's sitting, right? So we have these femonacci levels and and again, it's these are a lot tougher. There's not much history on this right, so um, we can only look at femonacci levels And see potential moves back down to the downside. You can see today Well, this week it's up 35 percent last last week goes up 135 percent. So When things are so overextended like this, especially in a meme coin I I never recommend, you know jumping into one of these So i'm probably not looking to jump into anything, but if I was I'd probably be looking at at a pullback way down here That would be the level that I'd be looking at. Um Whoops Can I draw it's not letting me draw for some reason Doesn't want me to draw no No, I it really doesn't want me to draw these levels here for you guys Unfortunately, I don't know what's going on with The trading view here, but it really didn't like this coin that is that seems like a sign to me if I ever saw one So, um, yeah, so let's jump into the next one. I and j let's go to Binance Yeah, this is really tripping right now Like it's not even letting me look at this nothing's happening I I don't know. I don't know what which has happened Let's try it again I and j Binance. All right, there you go. That's working. All right, so Zoom out Right go to monthly Let's see how long have we been live for we've been live for 45 minutes All right, so after these, uh, I'm going to take some requests If you guys have any requests in uh, drop it in the comments and I will take a look I see uh, Fernandez said block x listed on maxi global so, uh Fernandez if you're still in here, let me know in the comments and I'll take a look at that one, uh, next If not, uh, then I'll I'll take another request from someone else So, uh starting out here let's pull out our Fibonacci Let's move it all the way from the bottom to the top And let's see what levels it gives us So this is this is always my starting point. This is how I like to start any analysis It just makes it makes life easier, right? And it gives you some levels to start off with so you you you can see I just pulled it up I just put from the beginning of this run to the top Boom, it gave me these lines now. I'm like, all right. So let's see what lines make sense here And let's see what patterns I might I might see Right. So now the next thing I'm seeing the first thing I'm seeing is okay. Look at all of this Um Consolidation and rejection below This level right here, which happened to also be a Fibonacci level Right. And then if we look back it's like, oh, look, it was also a level here It was a level here between all this it was A level here like so it's this is obviously an important level there So even without having this movement like this, I would have seen this Uh without without this move while we were consolidating here I would have been looking back at this and I would have been like, wow, this is an important level here So obviously this is a good breakout level there So Let's uh, let's take a look. Let's look for some potential setups. So The first thing I always look at is uh As a potential setup is above the recent highs, right above so it's the not only is it a the recent highs But it's the all-time high for for this project Right. So that's a potential breakout entry That you can they can play Right above that that recent high next let's go into the weekly And the weekly gives us a little bit more information that we can use to to look for trade opportunities, right? So now in the weekly I'm like, okay, where what I like to see a pullback to that we can potentially enter and it looks like down here Is an interesting level So that's potentially where I'd be looking for a pullback, right? We I know we have this level right here This is not a high probability level Up there because it's it's not a lot. It's not a big pullback at that point But it could play as a level, but I'm uh, I would rather play this level down here So this is gonna be the next level that I am doing because I like to play whole numbers. I'm gonna set the alert at 20 dollars instead Of all the way down there on that support. So I'm setting my alert right here 20 dollars All right, so we have our two alerts set up That's potentially what I look for If I was playing this if I was looking to play this a either a breakout long above the recent highs Which is it's all-time high or wait for a pullback down here and then this level gets interesting for me So that's how I'm gonna look at it for now Let's see. Um, what other coin here we had bit torrent Up 67 percent So let's see bit torrent All right bit torrent. Look at this candle this last week bit torrent went up 171 percent that's insane. So whenever there's something up that much you got to be careful Right That train has basically left the station already So you don't really want to be chasing that you want to be looking for a pullbacks basically So i'm setting up the Fibonacci levels the same way we've done every time You can see on the monthly it's up 170 Something percent. So yeah, it's pretty wild guys um But here on the weekly we can see that it's it got rejected up here and it it looks like it's printing This is known as a bearish pin bar So a bearish pin bar is when there's a big width to the upside and the a little body to the downside So that basically shows that there weren't enough buyers To keep pushing the price up. So there's the sellers are overwhelming the buyers at this point and push the price back down. So um Usually this means that we're going to see some downside for some downside You know potentially down here at uh at this Fibonacci level. This is where I start looking for a potential entry if not I I like this pocket right here. This is called the golden pocket between 61.8 and 78.60 So, um, there's the golden pocket down here But at the 50 level is where you can start at least paying attention to uh to this right here. So i'm gonna add an alert right there And we'll see how that How that goes I'm not really looking for for anything above it I'm only looking at this point for uh for potential pullbacks here on this coin So I'm gonna add that alert there and I'm gonna add another one down here And those are gonna be my two alerts if we get a pullback Back into this zone Then I'm gonna get interested in potentially Entering something uh to the upside. So those are the two that I'll be watching there Uh, so like at osmosis up 62 Well, I had a massive move down In 2022 well like everything else, right? They decided to uh release their project at the wrong time All right, so if we go from the bottom To the current top Again massive moves here 91 move Last week well last month and a night and a 76 percent move this month Let's go uh into the weekly see if we see anything else See if we see any stories here And um, I mean we can see, you know, there's there's a lot of resistance in this area We've got it got rejected a lot in this area so, um Yeah, I mean, I'm not I'm not too. I don't know too much. I'm not too familiar with this project So I'm personally never probably gonna trade this. Um But if I was I'd be looking for a pullback and kind of in the same range as the last one we just looked at kind of uh This level right here. Whoops. I didn't mean to grab that. I don't know why this is not letting me draw. There we go Look at this. What what is going on with with this, uh Look at where the Fibonacci level is That's crazy, right Trading view is tripping out today But uh, yeah either way. I'm not really looking to to uh do too much in that Um, all right, so we got a request here From mystery man. Hi sir. Can you please analyze? Gary usd t possibly 50 up breakout loading. Yeah, let's take a look at at that Gary usd So, um, I'm trying to see where the most of volume Would be cracking. Okay x maybe okay x All right, so we had so this was released This also was released in the wrong at the wrong time. They released that this during the bear market So, of course we had a massive massive, uh drop And now it looks like it might have bottomed out in september started to move up Let's um There's there's not a lot of historical data. So whenever there's not a lot of history. It is a little bit more difficult to kind of um Analyze but I will I will do my best. So let's start off with, uh A Fibonacci level there and let's see what it gives us. Let's go into the weekly where we can get a little bit more information And um, I mean the main things I'm seeing here Are this is obvious a big level here Here we go again. This is not letting me draw So for some reason Trading view is is not working. Look at this. It's not working right today. It's glitching out every time I try to draw it doesn't let me so you're just going to have to uh Imagine with me that I'm drawing a line here, but this is obviously an area of a lot of consolidation here We have what looks like the 50 week moving average up here, which is coinciding With this uh resistance that we've had that we have up here So, um, yeah, I I'd be looking at a potential breakout But the breakout wouldn't be at the recent high the breakout would probably be right here Where it was rejected a bunch of times and also where the 50 day moving averages So that's where I'd be looking for uh for a breakout there Um for pullbacks you you saw here that it moved up pulled all the way back to this level right here right and Moved up got rejected. I wouldn't be surprised if we got another pullback potentially to that uh to hear the 50 percent area or The 61.8 percent area That could be that would be a healthy another healthy pullback before a continuation up higher So that's potentially what we could see we might be able we might see something like that where it went up Pulled back went up pulled back and then goes up again So, um, I'd be interested in something Probably below this level is where I start to get interested in it, which is uh, 0.03622 Just about um all the way down to 0.3 basic zero 0.03 basically So that's that's the range that I'd be interested in a potential long here If you're looking to just trade it, um, again, you can build potential long there or you can Set up a breakout trade probably above this level here, which seems to be seven cents So above seven cents would be a breakout Trade area So hopefully that uh that helped If we have any other request Let me know in the comments right now. If not, we'll we'll go ahead and wrap things up Oh man, my voice starts going once uh Once we start once I start talking for so long All right guys, so it doesn't look like we have any other request Um So we're gonna we're gonna go ahead and wrap things up. I appreciate you guys Thank you everyone who who tuned in Make sure don't forget to like smash that like button on this video And don't forget to subscribe to the channel. We're doing a lot more stuff We have a lot of things in the works right now We got a lot of cool features coming out uh in our discord So if you're interested in that the link will be uh down below for that Um, and yeah, we'll be doing this every week So every week we're gonna be doing a bitcoin analysis live stream one day and the next day we'll be doing a outcoin analysis Uh, so that like that we can continue to stay on top of both the bitcoin Which is the overall market and to stay on top of the outcoins, which you know can outperform And in 2024 will outperform bitcoin overall. So we'll be uh We'll be watching both of those guys Appreciate you guys tuning in. I'll see you guys on the next one as always peace and love


Welcome everyone. This is the Jenkins Governance Board meeting. It's April 3rd, 2023. Thanks for being here. Topics on the agenda for today include the claim from BMC to get hub trust and safety, news, action items, several items there. Then I had put CDF topics and community activity. Are there any other topics that anyone wants to be sure we cover in this meeting today? Okay, then let's go ahead and get started. So first, two weeks ago when we last met, we received a note from, or we had Daniel Beck join us and share the work he was doing in handling a claim that had been filed to get hub trust and safety regarding private information that they said had been disclosed in a unwillingly disclosed in a repository of the Jenkins project. The claim was flawed at best, but we took action. You can see the actions taken in the entry from two weeks ago. Since that time, the claim has been rescinded, confirmed by GitHub that it's been rescinded, confirmed by BMC that it's been rescinded. The plugins that were distributed under an open source license have been restored to distribution. Those few plugins that were not under an open source license have not been restored because we don't distribute privately licensed plugins. Any questions, comments or concerns on that one? Okay, so next piece then is on the news. Jenkins releases are upcoming tomorrow. We've got a weekly, the day after it we've got an LTS. Chris Stern is the LTS release lead. As part of those weeklies, we've got a change of the PGP repository signing key for Debian and RPM packages. The Debian repositories seem to be the most impacted and are getting the most questions. Thanks to Alex for his work on helping to answer people's questions, resolve their concerns. We've announced it in multiple places and yes, we know we need to get better at doing this. The last time we did it was three years ago and we've not done this nearly well enough. We'll do a retrospective after we get through the work. Now we've got Oleg who added a note that he's changed affiliation. He now works for Wiremock and availability continues about the same. Any questions or comments on the news? Okay. And we may come back to Oleg's change of affiliation. He just joined us. So on the action items, the top several, no further progress since our meeting last week or two weeks ago, as far as I know, we've got EZCLA, the sub projects, Convergence and the Chinese Jenkins site. Oleg, did you want to give any comments on your change of affiliation? Congratulations. Well, I think actually nothing really changes for Jenkins except the fact that if you have any issues with Wiremock test automation, we have Jenkins here and there. You know, home to pink. Great. Thank you. Thanks very much. Yeah, but really for me, yeah, I was unable to work on Jenkins as much as I would like recently. But it's not really related to my employer, but to all the other stuff. So we'll see how it goes next. Thank you. And then the plan, a few talks about Jenkins finishing some beats around Jenkins file runner. And what else I plan? Yeah. One month ago, I gave a talk on open source road maps. And basically it was a retrospective on what went wrong with Jenkins public road map because personally, I believe that it didn't fly. So if someone is interested, maybe at the next governance meeting or I could do a recap, or maybe we could do it as synchronously. But yeah, maybe one of the action items if someone is interested is creating and you wrote them up using more convenient tools for the community members. Thanks. Okay. Okay, I think that's it. Great, thank you. So next, I see Daniel Beck has joined us. Daniel, we had just covered the claim from BMC to GitHub Trust and Safety. Thanks very much for your work on it. Is there anything that you wanted to note in addition to what's already been noted publicly? No. Okay, thanks. Thanks again for your effort on that. Thanks very much. So I still have an action item to archive the governance meeting notes. Gavin Mogan has politely declined. He's not ready to continue that effort. I'll carry it forward. I've got more work to do there. Basel, you had an update on the build monitor status. So the build monitor status plug-in, right? Yeah, there's not much to share but since I had brought this topic to the board earlier regarding Jan Mollick's request to maintain his link to his blog inside of the plug-in, I thought I'd give an update on this since it's been concluded now. And his repository has been transferred to the Jenkins GitHub organization. The build has been moved to Jenkins from GitHub Actions and the release process has been converted to our standard CD process. So this project is wrapped up and I was so pleasantly surprised to also see that some of our front-end contributors even improved the display of the plug-in website to display the older versions, the pre-CD versions of build monitor at the bottom of the list and sort the whole list correctly with the new versions at the top. So this effort has really been, has really fully been completed with everything from the build automation all the way to the display on the plug-in site. It now looks and feels like a full member of the Jenkins project with no, it's not otherwise visible as something that we transferred later on. So that's really all there is to say about build monitor. It's one of ours now. So that's it. Thanks very much. Thank you for taking that through to completion. Much appreciated. On the CDF topics, I had three items. Digisert, Signing Certificate Renewal Progress that I wanted to discuss. Then Project Presentation, April 12th and LFX Tools Working Group. Are there any other CDF topics Oleg that you wanted to add or to be sure that we included? Not really at the moment. So next week you will have a presentation on status of Jenkins, right Mark? April 12th. Yeah, is that next week? April 12th. Yeah, I think, I hope that's, yeah, 10 days. April 11th, maybe, because April 12th was really suspicious. Okay, yeah, so it's, I'll have to look at my calendar to be sure. Let me double check. It is, I show April. Yes, April 11th, that's correct. Yep, you're right. Yeah, basically I know that many other updates from the CDF at the moment. So there was a cycle of defining CDF and Jenkins hours for this year. So the announcements will go live, I believe, in a week or two, but otherwise no big news. Ah, see, and I thought that they were going to announce that at CDCon in May. Maybe at CDCon. Okay, so results provided to CDF. So announcement has not been made yet, right? Yeah, maybe it's internal announcement because, yeah, I'm in the outreach committee, so maybe there will be internal announcement first, announcement to participants, and then public announcement at CDCon, as you mentioned. It makes no sense. By the way, do you want to go in there? I will be there, and Alyssa Tong will be there. Okay, nice. And how about KubeCon? I will not be there. Anyone? Yeah, so I finally got the grant from the Linux Foundation to visit KubeCon. I will be there. I checked whether there would be any CDF events, apparently not, but yeah. There might be some Jenkins related agenda. Great, thank you. All right, so going back to the other CDF topic, so others are aware, we've, the Jenkins code signing certificate, the certificate we use to sign the war file and the MSI installer has expired. It expired March the 30th. The expiration of the signing on the war file is not a terribly big concern, but the MSI installer is a big deal. Most Windows users won't use an installer that's not signed. And so I sent a proposal to the board, to the release officer, the security officer, the info officer today asking, let's suspend distribution, got agreement from all of them. Yes, we should not build any more MSIs until we get the new code signing certificate. So what that means for users is they will install the old MSI and then they do an upgrade with the war file. Any questions there? Okay, other topic I had put on was the LFX tools working group. So what the LFX, the Linux Foundation tools working group is looking at a potential replacement or upgrade to supersede the DevStats facility that we've been using for a number of years. We use it to track participation and involvement at a course level in the Jenkins project. And so we're actively involved in those discussions and we'll continue to those discussions. Ultimately, Linux Foundation expects to retire DevStats and replace it with some new, this new thing. Any questions on that one? My understanding that we don't heavily use DevStats at the moment because, yeah, what concerns me that LFX Insights is not featured complete if you compare it with DevStats. So I wonder whether there would be any impact. There should be no impact on automation because what we had for automating community stats, it was quite weak and I don't think we use it anymore. But are there any other dependencies that we might have on DevStats? Yeah, I've continued to collect data from DevStats every month for quite a while and I've been using it to gauge how well or poorly we're doing. I'm doing it automatically or through scripts. No, manually, just once a month I collect them. It shouldn't be a big deal. Right. All right, so I think we've covered the CDF topics. Last topic on the agenda is... I had some questions about the key signing part if we still have time to talk about that. Sure, go ahead. There were some people complaining about the existing stable repository not being signed by apt until we do the next LTS release, which is coming up this week. And I wasn't clear if I think the action was, we told those people to wait. I'm not clear on whether that action was due to a lack of resources on our side or if that was because there was no technically feasible solution to the problem because I think both of those would be acceptable reasons to not do anything. But I'm not clear on which of the two was the case. Good question. Was that, because I don't know very much about this, but it seems to me that this wouldn't be an uncommon scenario for a key to expire and for existing old releases to be unavailable. So I'm not sure what the standard practice is, but I think it might be the case that you could re-sign older releases with a new key and publish that. I'm not too sure about this though, but if that's the common convention, then we may very well have been able, or we may still be able to do that. Of course, now with only two days left, it's probably not worth doing that from a time and effort perspective, but if we're gonna have this problem again going forward, that might be something to think about or I might just be wrong and there's just maybe no way to deal with this problem retroactively. But I was still a bit curious. Do you have any insight on whether that was possible or whether we just chose to do it because we didn't have the time and resources? Yeah, I think as far as I can tell from the comments by Michael Prokop, it is possible to sign old releases again with a new key without disrupting those things. So we could have done it. And it's also possible to sign packages with multiple keys so that, and between those two things, I think we could have made this process much, much smoother for the users than we did. The Debian process saying, hey, you're gonna be down for a week is really uncomfortable. That's painful for the users to say you can't install during this one week period. That's just terribly painful. Yeah, and from my point of view, there's really nothing wrong with us making that mistake or not having the time or the resources to do that. That's completely understandable from my point of view because nobody's perfect and nobody has infinite resources, et cetera. But I was a little bit confused about how that was communicated to users because I saw in many of these tickets, we just told them to wait another week. And then when they complained, there was just no response after that. So I think we could have done a better job of acknowledging from our side that it could have been done differently. And not necessarily being apologetic, but just, I don't think we acknowledged that as much as we could have. And I think users generally prefer when we're fully transparent with them about both our strengths and our weaknesses because at least that creates a complete understanding. Whereas if we're silent about it, then they could be confused about whether it's intentional or not. But that's my only comment is we could have been a lot more open about the fact that we just simply screwed up here. And it's fine to screw up, but I don't think we were very transparent about it. Right, good. Well, and I think that's a thing for that. That is a topic for inclusion in the retrospective of, hey, what should we do better next time in order to not have this cliff every three years? Is there a way to do it? So it's a much less painful experience for the users. Yeah, you're right. Any other concerns or comments from others? Alex, I know you were involved in those conversations. Are you okay with that as an acknowledgement that, hey, I know the infra team, we were surprised, right? It shouldn't have been a surprise. We knew about this. We've known about it for three years. When we set the key expiration, we knew it was going to expire. And yet we missed the opportunity to do it well before the .2 LTS. We should have done changes already in the .1 four weeks ago. And we didn't. So yeah, there are plenty of mistakes hiding in this one. Okay. Any other comments on the expired PGP key? How is this going to be handled in one, two, three, how many years? Yeah, so I don't know yet. We'll talk about it in the retrospective. One of the things that the Michael Procop mentioned was that if you sign with multiple keys and you create a separate package that supervises the keys, then you can do the upgrade much more smoothly. And I, but I need to learn a lot more about Debian packaging before I'm ready to say, ooh, that's how we should do it. So the answer right now is, I don't know what the best practice is. I only know that the way we did it this time was particularly poor. It was worse this time than when we did it three years ago. Did that answer your question, Daniel? Oh yeah, go ahead, Mark. Okay. Yeah, just a quick note on the communication thing. I've seen various tickets that complain that the stable packages are not, the stable pages are not updated on packaging and get.jankins.io, which is currently a limitation within the build cycle. Like we can't update the pages unless manually outside of releases because they are generated once the LTSRs takes place. And a few people pointed out that this is indeed a bad practice to not update documentation outside of releasing something. So there's possibly something we should consider changing in the future, or at least until the current GPG expires. Right, yeah, that certainly is another flaw, right? That flaw we could have hidden if we'd done this earlier, but it's still a flaw, absolutely. Good, okay. Any other insights or Daniel, did you have any further comment there? Yes, I'm less interested in the technique of how exactly it will be solved, but rather, if I understand the current problem correctly, it was that we discovered too late that the key is expiring. So the LTS release was already created. So there was no LTS release for which we can already use the new key to prevent the problem that happened. It did not happen as much with the weekly release because last week there was a weekly release, right? So I'm wondering, especially I think we have several keys on a semi-regular schedule that need rotating. Do we need some sort of calendar or other periodic warning system in infra without obviously, I mean, I'm not directly involved, but it seems like this is something that would be missing a calendar notification a month ago would probably have helped. Right, and that's in fact, exactly what the infra team uses. They have a calendar that has these kind of notifications on it, the early warning on this one was not early enough, right? And that was part of the problem is it, I don't recall if this one was the PGP key was not on calendar or was not early enough, the Digisert one was not early enough, right? So this signing, we probably needed to know six months ago that it was going to expire because attorneys had to be involved. And this one, knowing it six weeks of go would have been enough, but I think at best its warning was set to arise 30 days before expiry and not 60 or 90. So yeah, there is an alert system already in the infra team that they use a calendaring system that reminds them of these kinds of milestones. Yeah, six months sounds right to me because especially if you wanted to adopt the strategy you described earlier of signing an LTS release with two keys as a migration strategy, then that would need to be done for, because LTS releases are every four months or sorry, three months apart. So, and then doing the work to prepare for that would probably take around a month. So yeah, like four to six months sounds about right for how long we'd need to orchestrate this successfully. Exactly. And I think that's, and we may want to consider, hey, should we rotate every year even though the keys expire every three years? So that we've always got, there are all sorts of things like that that I think we will discuss in the retrospective and try to find a better path forward. The last time we did it three years ago we knife edge transitioned on a week when we did the weekly and the LTS within a day of each other. And that's the only reason we didn't get better complaints then, right? Because we did it on exactly that weekly plus LTS transition period. But that's still not a very palatable thing because it was still broken for a day, right? It's much more glaring when it's broken for a week but it was broken for a day even then. So there's gotta be a better way to do this. Anything else on either the Digisert key or the PGP key expiration? Okay, next topic I had then was this Artifactory bandwidth reduction progress project. So JFrog, our sponsor of Artifactory for the Jenkins project has asked us to reduce the bandwidth used by that server. The bandwidth that's using is enormous. Well, thanks to log files they provided we found a host at Alibaba that was downloading from 20 to 30 terabytes a month by itself. They have now banned that IP address and we're hoping that that's already a dramatic improvement. They've asked for further improvements and we may have to make use model changes in the Artifactory repository but we've made good progress thanks to that ban and the help of the Artifactory caching proxy. This is something that the infra team has created to provide cloud local caches of the artifacts instead of downloading them all from repo.jankenci.org. Any questions on the Artifactory bandwidth reduction project? Okay, so the next one is Google Summer of Code. We're delighted that we've got over 28 proposals already submitted to Google for Google Summer of Code 2023 in the Jenkins project. That's in fact, I think John Mark told me it was 38 because it's double the number we had last year and we haven't reached the endpoint yet. The endpoint is tomorrow when applications close. So we're delighted with the progress there. It's let's see 38 proposals. So, and we assume that there will be even more before we reach the closing of their time tomorrow. Any other topics that need to come before the board? Don't be surprised if you see me tinkering around with Launchable in the next few weeks. So I'll be making a lot of little changes here and there to try to get all the data flowing in. So you've probably seen me already doing that but if you haven't, there's gonna be a lot more of those changes coming. Thanks, yes. And so just for everyone's background, I Kosuke Kawaguchi has provided access to Launchable so that we can do some experiments. Basel started those. I've got this hope that we can find a way to reduce the cost of our infrastructure. Basel's got an even bigger picture view that he would like to find a way for us to get feedback much sooner to developers without having enormous costs or enormous time delays to get that feedback to them. Any other topics for... So Basel, did you want to talk anything at all about your work on prototype that you and Tim Jacome are doing or is that a separate story? I'm going to be writing a document that goes into all of this in a lot of detail because there's a lot of parts to it whether it's how to define test suites, how to define builds, how to define test sessions, flavors. There's a lot of concepts in Launchable and also what some of the benefits are. There are a lot of different use cases, some of which apply to us, some of which don't. The distinction can be fairly subtle. So I'm planning on writing a document that explains all of this. But to summarize it, I think we can benefit in three places. I think we can benefit in bomb builds to reduce cost. We can probably benefit in core builds to reduce the number of Windows tests that are running and also potentially to do ATH subsets as part of core builds. And I think we can also benefit in ATH itself just as we could in bomb by reducing costs there, although the costs are not as bad in ATH, but it's a similar structure. So those are some of the places that I see we could improve. But I'll have more in writing pretty soon about my current and every time I think I understand all of this Launchable stuff, a few days go by and I realized that I've misunderstood something and I have to do it over again. So it's been a learning process for me as well. But I think after reading the documentation, I thought I understood everything then I started implementing it and I realized that I didn't understand it at all. And now that I'm implementing it, I think I understand it, but I'm sure that in a week from now, I'll be going back and telling past Basil that he didn't understand it today. So, and I'm getting feedback from the Launchable support folks as well the whole time. So we should be getting pretty close to a working prototype, but having this all in writing should help explain the benefits as well as the costs and that could inform how we all interpret the results and ultimately whether we decide to productize this or not. Great, thank you. Thanks very much. Any other topics for today? All right, thanks everybody. Thank you very much for your time.


Andrea can, I think, hand posting back over to me so that I can continue to do what I need to do. And then Tucker and Betsy Ann, I don't know if you have a preference on who should go first in terms of walking us through the work that the Senate is moving towards the floor. But I'll welcome you to raise your hand if you have a sense of who wants to go first. Madam Chair, this is Betsy Ann. Can you hear me? I can hear you. Great. All right. I don't have a hand-raising capability, though, at this point. Okay. Well, you and Tucker both wait in at the same time. But if you're ready to go first, then we'll wait and have Tucker go second. Okay. All right. Thanks. For the record, Betsy Ann Rask, Legislative Council, looking at the, what's now listed as an H742 amendment, that draft 2.1. Apparently, we've been looking at the Senate this morning as well. They're currently meeting. And what I understand happened is that this language was actually instead placed on H681 on its own as a strike all to H681. And the Senate voted it out today. So all of this language, as I understand it, is coming your way, not on H742, but on its own as H681, if I got that number correct. But the Senate made two changes to the language, the elections language that you reviewed before. Section one, the legislative intent does not change. In section two, this is in regard to the voter signatures in the primary, general and local elections. Madam Chair, as you already indicated, the Senate ultimately did not recommend any further changes to this language, specifically the Senate did not move forward with prohibiting a person from submitting more than one candidate consent in the primary or general election. But as you did indicate, Madam Chair, Seneca Bob did discuss that this issue could be discussed further in the future, since candidate consents don't have to start to be filed for the state-level offices until May 14th. Okay, Betsy Ann, Jim Harrison has a question. Jim, go ahead. Yeah, Betsy Ann, do you have a way of bringing up the actual amendment? I'm afraid to switch screens because I will lose it all together and I don't know that I can split screen as easily because I'm not on an iPad. Are you looking at draft 2.1 that's labeled as an amendment to H742? Well, I was looking at it before, but right now I'm just looking at all of you folks. So Sarah had done something, but again, Sarah's on Zoom, but she had done something with sharing a document. I don't know if you have that capability or not. Oh, I'm sorry, I do not. Okay, Sarah, is it possible for you to do it? I'm afraid to, I'm going to lose everything if I try it. Yeah, let me see what I can do. I found the Senate calendar, it still has the language appearing as an amendment to H742, but I believe that this should be the correct language. And Betsy Ann, are you able to see what we're sharing on screen or are you on cell phone only? I'm cell phone only at this point. Okay, so I have in the Senate calendar proposal of amendment offered by Senators White, Bray Clarkson, Colomora, and Polina, and I'm assuming that this is the final language that they worked on last night, section one being legislative intent. So folks, if are you able to see what I'm sharing with you? Not if you're able to. Okay, I'm seeing a few knots. Good. So I will go ahead and scroll through, Betsy Ann, I'll scroll through as you are talking about what we're looking at. And hopefully that will be helpful for folks. If folks, if you're able to navigate away from your Zoom call, you can also go to the Senate calendar for today and find this language yourself if you would like to. Otherwise, I will scroll along with it. So Betsy Ann, I have section two in front of me right now. Perfect. All right. So no changes to that section two in regard to voter signatures and can it consent? I will move on to section three if that works for you, Madam Chair. Yes. All right. There were two changes in section three that the Senate Covops Committee ultimately proposed. The first change is in section three, subsection a, dealing with the ability of the Secretary of State to order or permit temporary elections procedures. And the question was what sort of involvement the governor should have in that order of permitting election procedures. So the original language that Senate Covops was considering was just to say that the Secretary of State is authorized in consultation with the governor to order permit these temporary election procedures. Instead, after hearing feedback from House Covops about Secretary of State and the governor working together in this, during this time, Senate Covops Committee ultimately proposed the language that you see here, which is that the Secretary of State is authorized in consultation and agreement with the governor to order or permit these temporary elections procedures so that the governor would need to agree with what the Secretary of State would order permit during the emergency time for the rest of 2020. Any questions on that, Committee? I don't see any hands raised, but I have a slightly different view now that I'm navigating a document instead of looking at all of your tiles. Warren Kitzmiller, go ahead. I very strongly agree with what the Secretary of State said the last time we were speaking. I mean, and agreement only invites impasse. And I think somebody has to be in charge of that decision. And I think it should be the Secretary of State who oversees elections, not the governor. That's nothing against Phil Scott at all. Those two offices can be at odds and then nothing happens. Yes. So this was a compromise workout because there was concern about wanting to make sure that when we get to the end of the balloting period that there could be no allegation that there was any partisan wrangling. And so the governor's people are willing to take on this role and we can continue to watch this and see if we are concerned that we don't like the way it's playing out. Anyone else want to talk about that change in section three? I see Jim Harrison. Go ahead, Jim. Yeah, hi. Sorry. You have to figure out how to scroll the mute and non-mute. The Secretary of State was from what I know personally and also in listening to the committee was involved in the collection of conversations and the director of elections, as I heard on the Senate GovOps committee last night agreed to the language which was suggested by the chair in the Senate. Okay. Any other questions on section three? All right. That's the end. Take it away. Thank you. And the other change here in this section three is adding this subsection B, which would provide that for any of the temporary elections procedure, the Secretary of State orders or permits under this section. The Secretary would be required to adopt any necessary corresponding procedures that ensure the public can monitor polling places and accounting of votes. This is just supplemental language to ensure that when an election procedure in the year 2020 would differ from current law that there would still be the ability of the public to monitor the polling places and accounting of votes as they consistent with how they normally would under current law. Great. Seeing no hands raised. Section four. Finally, there were no changes to section four. This is that Australian ballot authority for municipalities so that they can move toward Australian ballot more easily with just a vote of the legislative body instead of a vote of the whole municipality. And I have some reminders. Subsection B allows the Secretary of State to waive deadlines in statute or school district articles of agreement as necessary to allow that move to Australian ballot with the municipality needing to request it if the relevant provisions are set forth in the municipal charter or articles of agreement. No change there to that language that you originally saw from Seneca Vots. And that's the end of the elections provisions. Excellent. So shall we hand it over to open meeting law? Tucker? Tucker can unmute himself. Yes, I am here. Sorry, I was annotating the shared screen that was in front of me and getting used to this excellent new technology. So for those listening, Tucker Anderson, Legislative Council, I will start in section six. So, Tucker, hold on just a second. Warren, did you have a question before we begin? Yes, I'm hoping that Tucker can increase the volume. Oh, yeah. Very, very low. Thanks, Tucker, for speaking up. Is this an improvement? Yes. There may be some limitations with the age of the laptop that I am using, so I apologize. But thankfully, you will not hear my dog squeaking toys and my wife whistling for the dog to stop squeaking toys. I will start in section six and cover the changes that were made in Senate GovOps. The first change is going to be in subsection B. This is dealing with these emergency open meeting law provisions and the technology that must be used by a public body when they are meeting electronically. The first change is a small one that starts on line three, and this deals with telephone access to meetings. As you may recall, there is a piece in here that states that the public body shall allow the public to access meetings by telephone. Senate GovOps took some testimony and decided to add the following two words, whenever feasible. So, the public bodies shall allow the public to access the meeting by telephone whenever feasible. There was some recognition while it was snowing during yesterday's meeting that telephone access is not always guaranteed, and they did not want to have meetings closed because telephone access was not possible. The next change is in the last three lines, subsection B, as you are looking at it. This is an entirely new sentence. It was proposed by House GovOps and modified Senate GovOps. So, this new line reads, unless unusual circumstances make it impossible for them to do so, the legislative body of each municipality and each school board shall record its meetings held pursuant to this section. So, this was the recording requirement that was discussed just the other day. Senate GovOps determined that this should be applied to legislative bodies of municipalities and school boards, and that there should be an exception built in for when there are unusual circumstances that make it impossible to record the meeting. John Gannon has a question. So, Tucker, I mean, what does whenever feasible mean? I mean, does that mean, okay, the phone lines are down so therefore you can't use the phone or is it like the town manager in Colchester who needed to hire an additional IT person to do telephonic public meetings? The duty to allow telephone access is going to be dependent on the feasibility of providing that access. There was not a discussion about what the parameters of feasibility would be, but if you have the opportunity to provide telephone access, then there is this mandatory duty to do so. Okay, thank you. All right. If there are no other questions, we'll let Tucker continue. Go ahead, Tucker. We may move on to the next section. This was the Department of Fish and Wildlife Meetings language that you reviewed on Sunday. Senate GovOps made one change to this language, which was to state that the department shall hold not less than five meetings by electronic means. So the language that you proposed to Senate GovOps required the department to hold an adequate number of meetings. Senate GovOps determined it's a policy choice that they should set the minimum number of meetings that must be held and they set it at five. All right. Marcia, go ahead. But I'm going to unmute you right now if I can. Marcia, go ahead and unmute yourself, because I think you unmuted yourself and I remuted you while I was trying to unmute you. Okay, go ahead. Are we good? Yep. Okay. So is that for all the different types of meetings that they brought up, the deer and moose and antlerless, bird, etc.? As applied, this would be five meetings for all. Okay. So in total, five meetings that cover those subject areas. As you may recall, they were required by a combination of statute and rule to hold an annual meeting in each of the five regions over the next few months or summer for each of these subjects. So in total, by my count, that would have been a minimum of 15. And I don't want to speak for the commissioner, but if you go back to Sunday's discussion, I believe that testimony said that they do multiple meetings to make sure that they can get public involvement. So you may have been looking at, you know, three meetings for each of the five regions for each of these subjects, 40 or so meetings that would typically be held. Right. Yes. My understanding was that they had five for the deer and three for moose, etc. So I just wanted to confirm that this is five total for all types of wildlife. Confirmed. Thank you. Great. If there are no other questions, we'll let Tucker continue. Section eight, there is one change to the language governing these deadlines that are applicable to municipal corporations and regional planning commissions. And that was the suggestion from Representative Gannon that permit be added in each instance where a license is covered by these subsections. So you'll notice that permit has been added after license in each instance. That is all for that section. In section nine, this I believe is new to the committee. So I will take a bit more time to walk through what is happening here. Overall, this is operating as a moratorium on disconnections from public water systems and wastewater systems. Each of the subsections that I'll walk you through deals with a different type of system provider. And at the end, we'll deal with the division of enforcement. So in subsection a, this is covering municipal water and wastewater providers. And that not with standing clause at the beginning, not with standing 24 VSA chapter 129 is the generally applicable utility disconnect chapter for these municipal providers. So setting that aside, a municipality shall be prohibited from disconnecting a person from water or sewer services during a declared state of emergency due to COVID-19. Similarly, in subsection B, we are not withstanding any provision of law to the contrary. And stating that a person, which includes companies, businesses, corporations, person who is permitted as a public water system pursuant to 10 VSA chapter 56, which is the chapter that covers licensed public water system operators, and who provides another person water as part of the operation of that public water system shall be prohibited from disconnection during the state of emergency. We move on to subsection C. This is the same moratorium on disconnections applied to those utility providers that are regulated by the public utility commission. The public utility commission put out some guidance and a moratorium on disconnects from other forms of utilities. And this subsection C would extend this to those water system providers. Subsection D explains who's going to be responsible for any violation of this section. Subsections A and B will be enforced by the agency of natural resources. Subsection C will be enforced by the public utility commission. And that is that. Any questions? I don't see any hands raised. Great. All right. Jim Harrison raised a hand. Yes, Jim. Yeah. Not really a question, more of a process question. So the Senate, as I think I heard Betsy Ann say this morning, that this language has been added to H 681 as a strike all. And I assume is on its way back to the house for the floor session tomorrow. Is the expectation if we're in agreement with this that as a committee that the house will take it up and pass it tomorrow and it will be effective as soon as the governor signs it? That's our goal. Yes. Okay. No, that's good. I mean, I just obviously, especially on the open meeting requirements, there's been a lot of concern raised by towns. And I think somebody's got some loud stuff going on. They made the call to to segregate out the gov ops things from the UI and the healthcare provisions.  And it wasn't 100% clear whether they were accommodating enough of the concerns that that had come from the house side with respect to this language. And so that's why they made the decision to segregate this out in a different bill. But I think I believe that we have met enough of the concerns at this point that that we can give this the green light. Anybody else have any questions? All right, moving on Tucker, are you done with your section? Oh, is that the end of the bill? Chair, I am done. All right, look at that. All right, any questions committee? So, Mike, I'm going to consider that a raised hand. So why don't you unmute yourself and go ahead and share your thoughts. Let me see if I can. Okay. Okay, how's that? There we go. This is a process question as well. I raised a concern at, yes, Sunday's meeting. And I had Betsy drop an amendment. I realized there's a sense of expediency to get this done. And I'm not ready to push for that amendment right now. But I would like to discuss it a little bit and and perhaps withdraw it just so we have some sort of record that this is something we're considering or that we're mindful of it. Yep. So I'm going to go ahead and let you give us sort of your remind us again of your thought process. But one one legislative process statement about this issue. And that is that we do have until the middle of May to to move forward a separate piece of legislation if we find a way that we can move this forward, that the Senate can agree with. And in this abbreviated timeframe where we're trying to get this, you know, this emergency open meeting law and and Australian ballot stuff out into our communities, we didn't really have time to slow down and look at what we might do for for candidates filing for multiple offices. I will tell you all as a committee that I have heard from other House members who also have concerns about the the same thing that Mike has concerns about about the free for all of having you know, it's file for every office that there is simply because it's easy to do. So, Mike, I'm going to throw it back to you and then as folks have thoughts, please raise your hand and we'll have a committee discussion about this. Thank you and Betsy did drop an amendment and I wonder if she could put that up or if you just want me to explain this. Well, why don't you explain what the amendment did or if you would like to to phone a friend we can ask Betsy and to share as well. There's a number of different ways that we might that we might consider doing some sort of limitation on filing. If we could I don't want to muddy the waters more. I think you shared a little bit or shared the gist of my concern and if we could have Betsy just present that it might be the easiest way to put it out there.  Hello, it's Betsy Ann. Can you hear me? Yes, thank you. All right, thank you. House Go-Bop's members, I just re-forwarded to you the proposed amendment from Wickey. This is the amendment that you got in your email yesterday and so I just re-sent that. I don't know if you're able to pull it up. I'm sorry, I have technological limitations today with not being able to provide that document for you directly on Zoom, but I can explain what it would do. It would amend that section of the elections draft which is section two in regard to that voter signature elimination so that it would add in subsection B which starts out by saying in the year 2020 adding a new subdivision four that provides that a person shall be prohibited from having the person's name printed on the ballot for more than one office and either the primary or general election and then it would go on to say accordingly a person shall be prohibited from filing more than one consent of candidate form for either the primary or general because that's how you get your name printed on the ballot by filing a candidate consent and under this temporary election law language that's all that is required to get your name printed on the ballot filing a candidate consent since the voter signature requirement is lifted for these elections in 2020 but it would make explicit in the last sentence to say that however such a person may still win any office in the primary or general election as a write-in candidate just make it clear that a person could still run or win office as a write-in even though their name's not actually printed on the ballot. All right Mike anything else you want to say in the way of sparking conversation about limiting the number of candidates? Well it's a concern and as I said I don't want to stand in the way of the whole bill getting sidelined because of this it sounds like there is an intention to perhaps look at this further and I think alongside that I would hope that once we get past this piece we might look at establishing a study committee in general to look at these kind of considerations for elections and counting should something like this happen in the future again so we have have something in the green books ready to go that we don't have to reinvent the wheel. Thoughts committee? Jim unmute yourself there you go. Sorry I appreciate Mike's amendment I did listen into the Senate GovOps and I think as you mentioned before they indicated because of all the concerns and possible constitutional questions that maybe they could consider that later and if that's you know what we're going to do that would be fine with me as well. This year is very unique and on so many fronts but clearly I don't sure the public good is being served if each of us put our name on you know ten different offices that we might you know I tell my grandchildren this is the year I ran for governor some day so sounds good but it's not really practical so I like the sentiment of Mike's amendment and if there is an opportunity in the next month and a half to or month to consider it I would certainly like to do that as well. Great I appreciate you guys offering to work on that and and I would recommend that you go ahead and and continue to do some research into how to how to do that. I know that the Secretary of State in in our discussion and I think also in the Senate discussion had talked about being uncomfortable with with requiring for instance some sort of electronic list of signatures just because the town clerks would then need to verify them as being registered voters in that community or in that district but if you want to continue to work on this I would welcome you to do that. Any other committee members have thoughts about this issue of candidates filing for multiple offices? All right I don't see any names or hands popping up virtually. All right excellent well we have we've run into the end of our hour of a lot of committee time and oh Marsha go ahead. We had another piece of legislation that proposed legislation that we looked at on Sunday and that was about the extension of deadlines for municipalities. What's the status of that language? Did we see that Tucker or Betsy Ann? Madam Chair this is Tucker. We did see that that was the discussion about adding permits to the list of licenses programs and plans it would be extended for the municipalities. Okay thank you yes. Warren you're on unmute. Oh am I I'm sorry I didn't mean to be sitting there quietly. That's quite all right we're all attuned to hearing when people cough now that we're all a little paranoid about it. Any other questions about what we looked at for language today? Okay so feel free to raise your hand I'm just going to say a few sort of summarizing words here about what we're doing. We have there's there's a grand chart of when committees are allowed to when house committees are allowed to meet over the next couple of days and we have a few time slots that have been allotted to us tomorrow. I have not yet put together an agenda for those time slots and so I'll be working on that later on today but just so you know our agenda includes a meeting time tomorrow from 10 30 to 12 30 and or a meeting time from three o'clock to four o'clock. So just pencil those into your busy calendars and we may meet during one or both of those times and Thursday we are again allotted some zoom time from 2 15 to four and so please pencil that in as well and and we will we'll see if we can put together some agenda items for that. We sort of left off last week when we were last in person with with just getting the last few pre crossover bills out the door through the floor and all of that. We have not yet really jumped in in earnest with post crossover work although we had a few things around the police data collection and and use of force issues that we had anticipated doing post crossover on a Senate vehicle that has not yet arrived obviously. So what we do over the next couple of days is is still a little bit unclear since we're not yet able to officially vote bills out of out of committee in this virtual manner. Bob Hooper has a question. I may have missed it but did the actual crossover date come out? Well we pushed the pause button on the session last basically at the end of Thursday because all day Friday we were dealing with emergency response legislation and so I don't know what official negotiations the House and Senate leadership have had around what constitutes an extension of crossover but for right now we're going to consider that all of the things we intended to do before crossover are still able to be in play and and we will come back to them when we need to and in the manner that we need to. Any other questions? No questions. Excellent. All right well I want to thank all of the support folks who've been here to help hold our hand as we accomplish our very first Zoom meeting. Hi there's Andrea back. I think we can go ahead and turn off the live stream so I'm going to see if I can do that since technically I'm the host right.