Namaskar! I am Dr. Juri Hazarika from Bhupen Hazarika School of Mass Communication of Krishnakanta Hondiko State Open University. I welcome you all to the program on Master of Arts in Mass Communication and Journalism. And today we are going to discuss the first paper of semester one of this program. So this first course is named as Concept of Communication. And now we are going to discuss the unit number one of this course. The unit number one is named as Concept of Communication. And after the discussions that we will hold in this particular unit, in particular session, you will be able to define the term communication, outline the process of communication and explain the seven C's of communication. So this is the first unit of the course as I have already said. And here we will try to introduce you to the basic concept of communication and how the process of communication takes place between the human beings. So all of us we know that communication is a very simple term and it transcends each and every walk of human life. And that's why it is considered as very important for the existence, very existence of the daily lives of the human beings. So this term, the communication term has been derived from the Latin roots, Communus and Communicare.  So it is something from which the concept of communication has been derived from and that's how we can understand that communication means to share any knowledge, any feelings, any ideas or information. So in the case of face to face communication, when two human beings are conversing face to face, it is merely an exchange of information. It is not merely an exchange of information, but it also includes, you know, the gestures, the expression, the facial expressions, the gestures of the hands and eyes, the language, the kind of language that is used, okay, the kind of tones, whether the tone is often, whether the tone displays anger or kindness or love. So these all things together comes into the entire process of communication and which makes the communication process successful. And, you know, the impact of this particular communication, that is, that falls on both the parties, both the communicators, that who are conversing or taking part in that communication process. And the, you know, the behavior, the personality of the persons involved in the communication process also affects the entire communication system. And vice versa, the communication system may in turn affect the behavior and personality of the persons that are taking part in the communication process. So if we move to the definition part, then communication is a very simply, we can say that it is an all-encompassing activity and it has a far-reaching, you know, importance or influence or impact on the humanity, over humanity, over human beings, okay. So in a way, we can say that it is very important and it is a driving force for the humankind anywhere in the world. Because this is a simple act of sharing and exchanging information. You know, it is important to understand the views, the feelings and interests of the fellow human beings and it in turn, you know, affects the attitudes and status of mind and the way of living in almost every part of the world. Now the communication process, it happens two ways. So first, we have to know the mental status of somebody else and the second, if we are interested in getting across our status of mind to someone, we will rely on the process of communication, okay. It is merely the sharing and receiving of the kind of feelings or information that an individual wants to share with another. So if we try to look at some of the communication definitions that has been shared over the years by different communication experts, we can see that William Schramm, William Schramm, he said that communication is sharing of experiences on the basis of commonness. Again, by commonness, he is implying the attributes, the behavioral patterns, the kind of personality that the communicators, the persons who are involved in the communication that they possess, okay. So this is just the sharing of experiences.  Again, here we are talking about, you know, the mental status, understanding the mental status of one person by another through the communication process. Then again, in 1961, Legans, he mentioned that within codes, a process by which two or more people exchange ideas, facts, feelings or impression in such a way that in such ways that each gains a common understanding of meaning, intent and use of messages, okay. So through this process, if one exchanges the ideas and feelings and, you know, whatever one wants to pass on, so there will be a, you know, it comes towards the common understanding of derivation of meaning, derivation of the intent and then in the next step, the usage of the messages that has been passed on, okay. So overall, we can say that communication is the mother of existence for human beings. Now, let us see how the communication process takes place, okay. So in our daily life, we are always making use of communication, we are communicating all the time. So if we try to understand in the technicalities of the process, we can understand that there is a person who always, you know, start the process of the communication, you know, the proceedings. So that person is described as, is termed as the sender of the messages. The word sender comes here, so we have to understand that the sender implies the person who sends the message, okay, the person who, you know, initiates the process of communication. Then on the other end of the communication process is the receiver, the person who, you know, receives the communication message, okay. For example, here we can take one example that the sender wakes up in the morning and, you know, asks another person staying in the house for a glass of water. So the sender would form a suitable sentence. The sender would form a sentence, for example, can you please give me a glass of water or kindly hand me a glass of water. So that is the message. So that particular sentence that the sender has formed in his mind and said to the other person that is the message, okay. So the other person will hear the message, hear the sentence and will try to understand, okay. Will try to understand the meaning of the sentence. So that person is the receiver, okay. The receiver will try to decode the message, okay. So these terms decode and encoding, these are important in the communication process. And based on that, the other person, if he or she understands the message and thinks of handing over a glass of water to the sender, then that person will act in that way, okay. So the act of the person or the answer of the person, the receiver is termed as the feedback, okay, the response. Then now we can come to the aspect of channel. So channel is basically the carrier of the information or the carrier of the message that we want to send to the other party, okay. So the channel may come across as the language that we use, okay. If one is, if the sender is forming a sentence in English or SMEs or Hindi or any other language, that please hand over me a glass of water. So that the language, okay, the body language, the gestures that the receiver might use to ask for a glass of water, all these can be described under the term channel. So let's talk about the words that I have already said, the encoding. That means, encoding means forming the message, okay. As I have given in the example, the sender has formed the message as can you hand over me a glass of water. So that is encoding, okay, forming the sentence, forming the message. That term can be simply understood as encoding and the opposite is decoding. That means, you know, hearing and trying to, you know, understand the message that has been given by the sender that is decoding. The receiver does the job of decoding by trying to understand, trying to deciphering the message that has been given, okay. So these are the important terms that we have to keep in mind while trying to understand the process of communication. Then again, there is another important term, that important concept we can say that we need to know that comes most of the time in the communication studies. That is the word noise, okay. So noise basically refers to the various types of disturbances, the hindrances that might take place in a communication process, that might hinder the process of a successful communication process. So these disturbances, they may cause distortions in the smooth flow of the communication process. They may hamper the proper understanding of the messages or the informations that are being exchanged between the communicators. So there are different kinds of noise, the physical noise, mental noise, psychological noises. So we will come to that in the later part of the course. So here you just need to know this term and its basic meaning that anything that disrupts the communication process during its, you know, process or during its understanding, these all are clubbed under the term called noise, okay. Now let us see the need for communication. So we already have discussed again and again that there is the basic need of communication for the existence of the environments, the physical, biological or social. So it is always important to communicate through communication only, you know, the human beings living in the social structure will be able to understand their concerns, their needs, their plans, you know, for that purpose. We can always understand the importance or need of communication for the society to have a smooth process. So communication between the different stakeholders of the society can lead to, you know, different new opportunities, okay. It can lead to the evolution of different new ideas, okay. So it has a hand in the man's evolution, you can say. So communication facilitates the flow of information and understanding between different people and different groups and which is very important for the, you know, better understanding, better functionality of a society. So communication does, you know, helps people in understanding better, you know, removing misunderstandings and creating a clarity of thoughts and clarity of expressions. So it also educates people, okay. So the sharing of knowledge and information process cannot function without the existence of communication.  It helps people to express emotion ideas and help to understand, you know, that these emotions and thoughts can, of one individual can be understood by the other. So, you know, communication, it acts as a base for any action, base for any activity, any process that emerges in the ideas in the, in the, in a society and it leads the society to take action on a particular topic or a particular issue, okay. So if we come to human communication, so we have already discussed that it has been a part of the human society, the communication has been a part of the human society since time immemorial. So communication enables humans and other life forms to interact with each other and share information. So from the very beginning of the human society there has been examples of communication taking place between different individuals, okay. So human beings, they communicate in a rich and sophisticated way. We know that we have different, we have developed language, we have developed codes. So we have different means to communicate, which is not seen in other animals. So we can say that human beings, they communicate in a sophisticated manner as compared to other species. So human communication takes place through the use of sound, vision and physical contact, okay. So sound, when we say sound, it includes speech, it includes language, okay, the sounds that we make, okay. So it'll speech and language, they form a major part of the sound. And when we say there are vocalizations, okay, when we say sound there is the clapping of hands. If we encourage somebody, we do the, you know, we clap our hands. So it is one kind of communication, like we are encouraging, we are appreciating, isn't it? There is food tapping. So there are different other sounds that are made by the human beings to express their feelings to, you know, to communicate something. So when we come to vision, vision, when we say vision, we are talking about, you know, the sight, the things that we can see. So it includes the facial expressions. If somebody is angry, you can understand by looking at the facial expressions, right. And different eye contacts, different gestures, okay. People make gestures with their eyes, with their mouth, with hands, and the body language, whether the person is offended or, you know, welcoming. So this kind of, if somebody extends the hands to, you know, you know, shake hands with you. So these are body languages that will imply something that will imply the communication, imply the messages that will bring forth the messages from one person to another. Then there is the physical contact. The physical contact includes, you know, hugging somebody, patting somebody on the back saying, yes, you have done a good job, right, handshakes when you meet somebody for the first time. These are simple, you know, formal physical contact between two persons that, you know, shows the feelings or the kind of messages that they want to share with each other. So all these three parts, you know, these are the part of the human communication, sound, vision, and physical contact. Human communication is the product of a combination of all these things. Okay, so there are body postures, gestures that we have already discussed, then physical proximity between the communicators, okay, the kind of gap, the kind of distance that two individuals keep between them, keep between them while communicating. This also gives a message. If you are conversing with somebody very close to you, the physical proximity between the two persons would be less than, you know, when somebody, two strangers are talking between themselves. So these are all, you know, the messages that can, that the symbolisms, the kind of, you know, what you can say, the things that we see in our day-to-day life, if you decode them, if you try to understand them, you will be able to understand the communication process, the technicalities of the communication process in a better way. Okay, so an important factor in the nature of relationship among the individuals, the communicators, and how will they know each other, okay. So these all forms, these all are the base for all the gestures and body postures that one might take or, you know, take into consideration while conversing with another person. Now let us discuss the different, you know, seven C's of communication, which is very important and which has been basically formed as a guideline for the choice of content and style of presentation. And this has been given by, you know, Francis J. Bergin. So let us discuss them and try to understand them one by one. The first being credibility. When we say credibility, we are talking about trust or belief, okay. So the climate of trust or belief has to be mostly formed by the communicator, the communicator, the sender has to establish one's credibility, that I am a person you can trust or the things that I'm saying are trustworthy or, you know, I'm speaking the truth. So it is a process, it is a, you know, over the years, over the over time period, the sender can form a, you know, establish one's credibility so that the messages that the sender sends or gives can be taken into full trust by the receivers. So credibility, it forms a very important part in the communication process. If the receivers do not have the full trust on the sender, then the message that has been given, it will have another kind of implication on the receiver, okay. The sender might be sending a message with something, some objectives in one's mind, but if there is no credibility of the sender, then that the objectives of the sender might not be fulfilled in connection with the receivers. So credibility that C is very important in the communication process, that is one. The second is the context. So when we say context, we are basically referring to the environment in which the communicator is sending one's message, okay. The context, the environment, the area, okay, the situation, the base upon which the communication process is taking place, basically the setting. So it is very important to know the setting, to know the base, the context, because of which the communication process is taking place. For this is necessary for the communication to be successful, okay. So if we are talking, for example, if we are talking about, you know, the political situation of the country, then we have to understand the context, okay. We have to understand what kind of government is there, what happened ten years back, what was the, what is going to happen, what is the expectation, we have to understand the kind of the kind of people that are living in the country, okay. So if we take one example, this can be one to understand the term context in the communication process. The third is the content, okay. The content basically means the content of the message, okay. When one message is sent by the receiver, what all things are there, okay, in that particular message, what are things are included in the message that is the content. For example, here in this situation, when I am teaching you about the concept of communication, the content of this message, as a sender, the content of my message is about this particular course, about the concepts that are included in the communication, in mass communication. So this is the content, okay. So it also determines the audience, okay. So this content is for the audience, only the audience, the people who have taken admission in the master degree course of mass communication, isn't it? It is not for political science students or sociology students. So this is the content, so it will determine the audience as well. So the next C is the clarity. Clarity means how easily the message is understood, how clear it is, okay, and how the things have been planned, how they have been planned in the message so that it can be easily understood by the receivers. So clarity is very important and while forming a message, one has to take into account the audience, the receiver, okay, whether they will be able to understand or not, okay. Keeping that in mind, a message needs to be formulated so that it has clarity and it will be easier to understand by the people, by the audience, by your receivers. So that is very important. Clarity is important in a while forming a message. The next is continuity and consistency. Continuity basically means since communication is a process that is unending, so you have to understand the phases, you have to give the message in a phased way, in a continuous process, okay. For example, when we are making these videos for you, we will go unit wise. First you have to understand the unit one, then there will be continuity. The continuity will go to the unit number two, then three, then four. So in that way, the process of understanding, the process of communication will be easier. You will be able to understand the things that we will learn in unit one, it will have a continuity in unit two, right. So in that way, the communication process also should have a continuity, it should go from one step to another. Then consistency, there should be a, you know, consistency, that means the messages should not be repeated, okay. It should be consistent, right. So there, something out of the blue should not come in between a particular message, then it will lose its context, it will lose the meaning and there will be no clarity, okay. The next is the channels, channel that we have already discussed. Channel basically means the medium or media through which the people will communicate. So the choice of a suitable channel for the receiver is very important.  For example, in this particular context, I have chosen the language English to converse with you as a channel to send the message, send my message to you, okay. So because I have, you know, through experience or through understanding, I have chosen this language because I am confident that a person who has taken admission in the master degree course will be able to understand this basic English language, isn't it. So in that way, you have to decide and so that this particular channel will be suitable for my receivers. Here, another channel that we can talk about is that we have taken the channel, the media form that is the YouTube or a technical, you know, platform to send the message to you. Then again, we have decided this because we were confident that the learners, our learners will be able to access this particular video through YouTube, so it will be a suitable channel for us. So in that way, this is just an example. In that way, in every communication process, in every context, you have to be, you know, you have to choose the channel with a proper understanding of your audience, of your receiver. Only then, your communication process will be successful. The objectives of your communication will be successful only in that case. Okay. Now let's, you know, talk about the last sea of seven seas, that is the capacity of the audience. Capacity here means the ability of the audience, of the receivers to receive the message and to absorb the message, to understand the message. Okay. Whenever a sender, you know, forms a message that the sender needs to understand, to keep in mind the abilities and habits and, you know, the nature of its receivers, whether my receiver will be understand, will be able to understand my message. Okay. So keeping that in mind, we have to form our message. Okay. Keeping in mind whom we are going to address. For example, if you are talking in your home, if you are conversing with your family members, the kind of language that you will use will be totally different from, you know, from the language that you might be using in your office or in your workplace. So in that way, you have to, in a different context, you have to keep in mind the capacity of the audience. The way you will be conversing with a, you know, what you can say, a rickshaw puller. Okay. You will be conversing in a different way than somebody may be in a, you know, if you are talking with a higher ranking official in a workplace, maybe. So you will be, you will be speaking in a different manner. You will be putting different words to your messages. So in that way, you have to understand, you have to form your communication process. Okay. So communication must take into account the capability of the audience. Okay. The most effective it is when, you know, they are, they require the least effort on the part of the recipient to understand the message. Okay. So this will include the factors of availability, habit, reading availability and the receiver's knowledge based upon that the sender has to form a message. Okay. So this is what we have discussed in this first unit. So if we try to go back what, what all things we have discussed, we discussed that communication is a mutually understandable activity. It is an exchange of information between one person with one's fellow human beings with the use of different methods. Right.  So this process essentially involves different elements or components that we have discussed, a sender, a receiver, a channel, or a vehicle for movement of the message or the information. Then feedback we discussed that is the response to the communication we discussed about noise or the disturbances that might interfere, you know, from a technical or human problems point of view, which might, you know, put hindrances in understanding the message. Then similarly, we would also like to perceive something only with those aspects with which we feel comfortable and we are familiar. Okay. So we actually communicate something even by not responding to the sender's messages. Okay. When if we not respond to somebody's message, somebody's, you know, communication, that is also one kind of feedback. Okay. So human beings, we communicate in a very rich and sophisticated way other as compared to other species on the planet. Then we discussed the different seas, the seven seas of communication, which are very essential elements for a successful communication process to take place. So these are the things that you need to understand in the unit number one of this particular course. So in the next video, we will be discussing the next unit, the unit number two of this particular course. Thank you.


Hey guys, Brian here from Free Salon Education here and I've got my lovely model, Christina. She came in today and I'm really excited because she actually is mostly virgin hair. It's really long. It's a great texture and all she's got is highlights from last year. So she was a perfect, perfect candidate for me to go in, do a really great balayage. We talked about wanting to keep it natural but still giving it a really nice pop and really get a nice blonde in there that's just going to make it head turning blonde. So I'm really excited we're going to go through today, do some really great hand painting. I'm going to be working with cream lights because I wanted to make sure I use something that was nice and gentle on her hair because while I want to give her a really great pop I want to make sure that I don't trash the quality of the hair either. So here we go. Alright so to get started as you can see I've got her sectioned off just back to front and we're going in with the cream lights here. The key to making sure that you get a nice seamless balayage, the start, your first key actually I guess I should say is going to be that you want to make sure that you're using a lightener that's got the strength to lift but the consistency to glide over the hair. Some of you may or may not know balayage is actually French for sweeping so keeping that word in mind as you're working can help to make sure that you're gliding over the hair with a good sweeping motion. So cream lights is really good for that because I know that it's going to give me the lift that I want and it's going to brighten her up but it's just going to glide through the hair as I'm brushing on those nice wide sections. Make sure as you're working that you elevate that hair straight out from the head. I've got her parted from hairline to hairline with a little bit of a semi-triangle shape to her hair so that as I lift that up it's flat on top so that as I am applying that to the section it's going to go on nice and smooth but then when I let go it's going to have that hair from underneath sort of make the section buckle a little bit like you saw just there so that it's not going to press too hard against the hair underneath and it's not going to cause any weird bleed marks. I wanted her hair to have a nice seamless transition from her natural into the lightened ends so as you can see I'm doing triangle sections that are really just framing the outside because what that's going to do at the end is that's going to work out through all the hair and just really give it no harsh lines of demarcation and just that nice seamless gradation that I'm looking for. The saran wrap that I'm using in between is actually a really cool perforated saran wrap that I got from the sunlight company they make a whole bunch of balayage tools and different things that just help make our job that much easier the paddle is also from them as well just holds on to my product for me making sure that I can work cleanly and quickly so I've got the back of her head done as you move into the front I always want to make sure that it not only looks good when her hair is down but it's also going to work when she pulls her hair up so that's why I always make sure that the hair around the face that hairline I paint that a little bit closer than I might throughout the rest because if she throws her hair into a ponytail I also want her to enjoy her highlights enjoy that balayage so we're working that down I make sure that I don't just have those two lines that I'm creating framing the section just ram together I want them to come together on their own sort of throw a force perspective kind of technique when applying it that's why I'm holding the hair down further towards the ends of the section because I want this painted line and the painted line on the backside of this section to just seamlessly come together and when they collide at my fingertips is where it's going to be blonde through the ends Matt goes in and does a really great cut to to work with these nice long layers that's why I made sure that I I had the line come together a little higher up than I think I was planning on just because I knew that some of these ends were going to get cut off as you get up towards the top of the head you want to make sure that you're still getting a good elevation I had her tilt her head back just a tiny little bit so that I wasn't pressing any of the hair underneath working on the section framing technique like I'm doing with the the application of the cream lights is also going to make sure that I'm giving her more of a highlighted effect rather than just an all-over-blonding obviously if you wanted to use Bally as to create something that looked a little bit more like she was just entirely blonde you could do that as well but this is just going to make sure that you know she's got a nice grow out we work with her natural to have it become a part of the color itself her her nice gradation color story what's cool with Bally as is as you look through this saran wrap you can kind of see where your highlights are going to live so if there's any areas that you feel you're looking a little too dark then you can go in and always of course add more working into my last section here the small side of the part just making sure that it's quick sweeping motions I started the mid shaft of the hair sweep down and work up towards the scalp rather than starting at the scalp because sometimes there might be a little too much product on your brush or you know you just haven't gotten your rhythm yet and then before you know it you got a big blonde blob right by their face so what's good is if you apply it to the mid shaft then you can smooth it out moving downwards and smooth it out moving upwards which will also make your highlight you know get a little bit finer so that you don't have to have large streaks near the face if that's not the look you're going for as I get close to the part I tend to work in slightly smaller sections because that is the hair that should have the most dimension because in a sun lightened effect that's the hair that sees the sun the most so it makes sense making sure we get those ends nice and saturated I like to always make sure that there's two good hard highlights right at the part on the face line it just adds a really cool look to it to make sure that she always sees and enjoys her balayage herself get one last piece of that saran wrap to make sure everything stays nice and protected and there you go hey guys this is Matt Beck from free salon education comm here with our model Christina who Brian just colored using the cream light so I'm really excited to not cut too much of this off because we want to see all the highlights that he did so what we're going to do is keep the hair long but what I want to do is add a nice kind of face frame feel to Christina's hair she's a really low density of hair so what I want to do is keep the fullness I'm not gonna do a lot of elevating throughout the haircut we're gonna use a razor the Donald Scott carving comb it's gonna make the haircut really quick we're actually gonna work off of three basic sections throughout the hair so we started off right at the high point or the mid part of the crown and we section diagonal forward down to the ear on both sides you can see that and then what I'm gonna do is I'm just gonna cut my basic line in the back I'm gonna use a heavier stroke with the carving comb so I'm gonna comb his hair down you can see how long it is and really the focus of the haircut is gonna be the face frame so you guys look at right here how long this is she's got one piece that I think used to be part of a bang and then the rest is just really long and hanging so what we want to do is bring some life into that and how we're gonna do it you can see how long this is and how it shortens her face up a bit so and to be able to kind of elongate her face we're gonna add that layer and movement right around this area and that will kind of shrink the gap in between her the length of her hair and where the chin line starts I guess so we're gonna start in the back you can see this hair has been on her head for a really long time so we're gonna remove just about a good two inches off of the base that'll make a nice strong base for her and we'll leave that highlighting because you can see where the gradation starts right around here and gets lightest at this point so I just want to remove just a couple inches with the carving comb a carving comb makes it really simple so as we tilt it down I'm gonna take a nice vertical section just combing everything very consistent in the back and we're gonna work one length at this point so even though we're gonna do a layering haircut because I've taken that section at mid crown forward all of these layers are gonna fall or some of these layers are gonna fall over top of this haircut so we're still going to have that that that movement in there even though we're cutting one length in the back alright so once we get I want to see that couple inches there and I'm just gonna go through I like to use the carving comb as like a kind of like I'm drawing with a pencil so we're gonna work from one side to the other keeping that tension this will give us a nice soft broken line you can also go straight in with the carving comb if you want as well whatever is most comfortable for you in this part of I find my guideline there and I'm gonna work just cut some of that so nothing real exciting here we're just doing a quick trim the excitement is gonna happen right in the front that hair is jumping off of her head it's wanted to leave her head for a while so very exciting the same thing combing the hair down keeping my body straight with the head my shoulders parallel to the section and that's cleaning up the back so we don't have to do much more in the back we could do a little bit dry if we feel like we want to break it up a bit but the most part you won't have to she's got that lower density of hair alright so now Christina likes to work off of a center part so and that's how we're gonna do the blow dry and the finish on this haircut so we're gonna cut it with the center part if she liked it more on the left side or right side then we would just part it there do the same exact steps for the haircut and we're gonna work in a forward angle so I'm gonna take now diagonal back sections I can take a little bit thicker sections because Christina has that lower density of hair so we're basically gonna do this in two two passes so we got our first one which is gonna be our guideline on the hair forward keep in the elevation low if I go too high I remove too much weight I want to keep it nice and heavy around the face but just create that nice face frame panel out which is the rest of that whole section if they have a higher density of hair thicker hair I would elevate more and I would do less hair in my hands but without I can see my guide under there and I'm just gonna work I'm sliding my hand out as I carve through you can see we're keeping all of that length in there more pass the tie in the bottom now we have a full face frame nice long hair alright so moving on to the opposite side the only thing that we're gonna change about this technique is we always want to be moving our tool in the same direction so even if I was cutting with scissors I would want to cut from the top to the bottom just like we did on the opposite side so I'm gonna work the hair out and then I'm gonna start working the carving comb from the top three inches section back and all that hair forward last bit now if I see a little bit extra length on the corner then I'll just pull the rest of the hair over and keep going until that length is gone you never know each side of the haircut might be a little bit different based on her previous cutting or non-cutting for a long time all right and then I'm just gonna work around check the back and a lot of people are always asking how do you create that V sectioning with the haircut well that's how you do it pull everything forward you cut it and when it falls back it goes short the long that way longest in the center we did our trim and now it's she's gonna have a beautiful layered haircut to go with her highlighted hair so hope you guys enjoyed this technique we're gonna blow it dry and then we'll sum it up all at the end thanks for watching just finished her haircut as you can see we gave a nice little just a face frame to lighten up her hair a little bit so that we get a little bit of movement around the face and we went in did lots and lots of balayage this is this is the final result of everything we'll spin her around after we processed it till we got it to a nice light level that I was happy with we went in with a picado demi 10a just so that I could get just a little bit of overall that very nice pale cool hug to the color that I just wanted to make sure just made everything even more seamless so we gave her a fun little style just to really show off all that nice layer and texture that Matt put in there hope you guys enjoyed this video thank you very much go check us out at free salon education.com thanks


Now, the Rural Vocational Skills Program of the Federal Ministry of Humanitarian Affairs and Poverty Alleviation, Farida Mosajaro has imparted 500 women on vocational skills in the Dhammo state. The women who were equipped with various skills on carpet making, makeup, bags, and shampoo among others were drawn from Mubi in the state. The program manager noted that the aim of the training needs to empower women who are the custodian of the home with necessary skills so as to become self-reliant. To have Mr. President as the President of Nigeria may God bless him and be with him. I am my boss lady, Mr. Dr. Betah Edu, the Minister of Material Affairs and Poverty Alleviation. It's Ruinu Hope, yes, as our President, what is always saying, Ruinu Hope is for better Nigeria. Ruinu Hope for better Nigeria, so we pray all over to be Ruinu Hope for better Nigeria. A member representing Mubi North constituents in the Dhammo State House of Assembly, Johanna Mosajaro, lowered the initiative of Farida and urged the beneficiaries to use the knowledge acquired for the purpose intended. The rate of employment has been at a very diminishing level all through but with such particular programs every individual, every person we have around here get to do one or two things for himself, really cater for himself. So it is really decreasing the rate of unemployment in our community. So beneficiaries of the trade and appreciated hard year for Rida, President Tindu and Dr. Betah Edu for empowering them. On the effort of His Excellency Ahmed Bola Thiribu, the President of the Federal Republic of Nigeria, for creating the Ministry of Humanitarian Affairs and Poverty Alleviation to enhance the standard of living of a common man. I learned a hard work that will help our beneficiaries. I as a housewife before I don't have any work or job to do but now I have learned something to do. Thank you so much. News updates.


Hello everyone, welcome back to another Adobe Premiere Pro tutorial guys, this one, we're in Adobe Premiere Pro 2020, it just released a couple days ago guys and this one I'm going to show you how to relight dark footage.  Here we go guys, we're going to do this in like three minutes, it's going to be amazing. All right guys, the first step here is you'll see I've got some video footage, I've pre-selected, I downloaded it from Pexels video because they have free footage because I just want to show you the technique. So what you guys can, if you're following along, just load up any old footage and drag and drop it in. Next step, drop it into your timeline, boom, we're in business. Now, when you look at this here, I'm just going to make it a little bigger, when I hit play, you're going to notice that this is, yeah, this is a little bit dark. It's not perfect, right, it's darker than you'd probably like, it's not lit perfectly unless it's like the 19th century and you're in Victorian England and you're doing a Jack the Ripper video, but whatever, you're not. So here we go. The way to relight this and brighten it is very, very simple, but not a lot of people know this trick. What you want to do is you want to go to your effects. For me, I'm in effects up here at the top and then effects is over here on the right side for me. If you don't see this, if your workspace is different, you can always go to window, drop it down and then make sure that effects is selected and there's a check mark beside it. Next, go to effects and just type in light, actually, and when I type that in, you're going to see that it loads up lighting effects and if you didn't see this, you go to video effects, you go to adjust and then you go to lighting effects, drag and drop this onto your video or your sequence and boom, you get this weird looking light and this is not what you're going for. Don't panic, I got you. The next step, guys, is you want to go over here to your effect controls, wherever those might be. If they're not open for you, you can just go down here to window and make sure there's a check mark beside effect controls. They are up on the top left for me, so I'm going to go click on lighting effects and you're going to see this little blue outline here, which is not what we want and then this is the key step, is you want to click on light one, click the little chevron or the triangle, whatever you want to call it, the angle bracket and then select light type, but from light type, go switch from spotlight to directional and when you do that presto, we've got brand new lighting. This is synthetic lighting and it works great. I'm going to turn the lighting effect off. This is the original. This is the new lighting. Now this could be all you need to do. Again, we can go a little further down the rabbit hole, but this is the pivotal step, switch light type to directional. Now you're going to notice here that it comes in at an intensity of 30 degrees. This can be up or decreased or increased depending on what you're looking for. If you're a forensic video editor, you can jack this all the way up to like 100 and you can maybe see things in a video that you would never be able to see without doing that. So anyways, I'm going to go, let's take this up to about 40 or 50. Let's go to 50, just for the effects. So again, now this is completely differently lit. I'll hit spacebar and you'll see that, you know, it's a hell of a lot brighter and you see a lot more stuff. It's not perfect, right? But it's pretty damn good and this is probably all you need to do. There are a few more little things here. I will show you that can have an effect. One of them, of course, is the light color. If you are in doing some color correction or you're doing like, you know, a nighttime scene or a horror movie, for example, and you want the light to have like a blueish tinge to it for the video, you can just click on the color of the light, head over to blue and then let's take a dark or blue maybe and let's just see what that looks like. Boom! You've got a brand new blue tinge to your light. So again, there's so many different things here. You guys can season this to your taste. Let's try that one. Okay, that's got a nice blueish tinge.  This is how you do it. Also, if you just want to light a section of your scene. So let's say maybe just, you just want to, maybe a square, like a component. You can let's say you want it to do like the bottom half and then the top half. Maybe not so much. You can do something like this, right? So you could do this if you really wanted to. Let's see here. Something like that, right? So I'm going to got the bottom half kind of lit and then the top half is not lit and I'm just going to back this up a bit to like 50% and then click off and let's see what happens. Right? So you can see here how much of a difference it makes, right? So again, I wouldn't do this for like a regular shot. I just want to show you the difference between the lighting. So masking and relighting components of a scene or components of a video or of a couple shots is another thing you can do. Guys, that's really all there is to it for relighting. I hope you enjoyed this tutorial. I'm going to switch the lighting back to white and I'm going to get rid of the mask. I'll feather the mask, sure, and then I'll get rid of it. What do you think? Yeah. You know what? That's a pretty cool look. Right? It covers actually that's actually something I should show you. That's a good point. I jacked the feathering up huge on this thing and then you'll see here that like I kind of relit the bottom half, but I left the top half dark. You can do this and you can do vice versa if you want the sky to be brighter, but you want like the street, for example, or whatever's on the ground to be darker. Again, guys, you can do this as you see fit, but these are the techniques, guys, that relight footage using just Premiere Pro and no external lights. Hope you liked this tutorial. I got a ton more stuff coming up. Stay tuned.


This is stock number 9526. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. Remember we are the guys with the trucks on 41. Today we are checking out this super clean 2015 Ford F250 crew cab long box. This vehicle has the 6.2 liter V8 motor. From this HD video you will be able to tell that. For the age of miles on this truck it is in really nice condition. Nice clear headlamps, red ruby tint coat is the color. We shoot all of our videos in 1080p so if you have HD capabilities on your computer tablet or smartphone device turn them on now because it's like you're right here looking at the truck with me. Handcooked Dynapro tires these are LT 275 65 R18s and they have just about half the tread left maybe just a hair under. Didn't see any dents or dings on that fender. Has the factory fog lights. Grille is in really nice condition. Didn't see any chrome peeling or anything like that. The hood is in really nice condition. I didn't see any dents or dings on that. Passengers side rim is in really nice condition as well.  How reflective and mirror like that paint is. We take these HD videos so if you are far away or even if you're close by and just can not make the trip down but you're still interested in purchasing the truck. You can still see the truck hear the truck and hopefully get a really good idea of the overall quality and condition of the vehicle before you even get here. I didn't see any dents or dings down this side of the vehicle. Lower rockers look really good. Has the factory chrome step bars that are in really nice condition. This back rim is an excellent condition as well. And the back tires have just as much tread as those front tires. Frame and underbody is very nice. Very little to no corrosion. Once again those rockers look really good as well. As we come around to the back of the truck you can see that it has the reverse sensors, the full towing package which includes a receiver hitch, four pin and seven pin wiring. Tailgates in pretty nice condition as well. Does have a backup camera locking tailgate. This one comes with a bed rug. That's in pretty nice condition. Didn't see any dents or dings on that rear bumper. And as we go down this side of the truck just as clean as that passenger side. Once again I didn't see any dents or dings down this side of the vehicle. It has the power scope mirrors. Driver side door code entry. We do have the code for that. Inside the King Ranch package gives you the deep dark brown chocolate leather interior. There are no rips. There are no tears on these seats.  Both these seats are heated and cooled. We have factory King Ranch floor mats throughout. Power windows, power locks and power mirrors. You got a memory driver's seat. These power scope mirrors, they power fold in. They also power fold out. They also telescope out and in. Has the auto headlamps, the power pedals. And this one does come with the Sony sound system. As we hop inside the vehicle here you can see that this one has 95,950 miles. It has the leather wrapped dark brown leather wrapped steering wheel. Cruise controls and Bluetooth and audio controls on that side. Cruise controls on this side. This one comes with the Ford MyTouch radio which has the climate control in there as well. This one has the backup camera. So you can do all your heated seats, cooled seats right there as well. Dual climate control. Turn dial four-wheel drive. Stability control. Has the factory tow command brake controller. 110 volt, 150 watt plug-in and the Microsoft sync system. Up here you have the home link buttons for your garage door security systems and lightings. The power sliding rear window. You can see that the ceiling is in really nice condition. Side curtain airbags. Pass in their seat is very clean as well. No rips or tears on that. And we have the factory floor mat on that side as well. I don't know if I show you. That's where the backup camera is. And this truck has 95,950 miles. We'll take a quick look at the back seats and then we will check out under the hood. So the back seats are just as clean as those front seats. There are no rips, there are no tears back here. It does come with the power sliding rear window with the built-in rear defrost. These seats fold up and there is a lockable storage compartment underneath here that locks with the ignition key. Factory floor mats and carpeting is very clean back here as well. And it does have a 110, 150 watt plug-in back here as well as in the front. Behind the seats you have the factory subwoofer and the latch tether anchors. And you can see the backs of these seats are in really nice condition as well. Very nice truck inside and out considering it does have 95,000 miles on it. Is it perfect? No. But is it a nice truck for 95,000 miles? Absolutely. Under the hood we have the 6.2 liter V8 motor. Engine bay is very clean runs very smooth. This truck has been fully safe and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off. And it is 100% ready to go mechanically. And to see more pictures of this truck or one of our other 400 new and used cars, trucks, SUVs, minivans, Wranglers, half tons, three quarter tons, one tons. You name it we got it.  Videos of every single used vehicle that we have all at summitauto.com. If you want to just check out our used inventory you can go to truckson41.com. It takes you right to our used inventory page. Take a look check us out and if you want to make this truck ears give us a call right now<PHONE_NUMBER>. Ask for one of our sales associates to make this truck ears. Today once again that number is<PHONE_NUMBER>. Thanks again for checking out the video. If you want to check out more go to youtube.com slash summit auto. Remember to like subscribe and share on this video and all the videos you see there. In fact in a second you will see a link to subscribe to our YouTube channel on your left. A link to more heavy-duty truck videos like this one on your right and if you have not been to our website on the bottom link to this truck on our website click those check us out and we really look forward to helping with this super clean 2015 Ford F-250 crew cab long box King Ranch. Thanks again.


It's it's amazing to me every time I meet with and and and with most of the nonprofits that I meet with I meet with most of their departments I meet with the executive team I meet with their different departments and it's amazing. To me, how often the things that they really care about come off their tongues really quickly they know they know what's important, but then they turn to me and they say but I don't know I don't know how to get to that information. I don't know, you know, I know that if I could measure this thing, I could improve the way that we're serving our clients whether we're pushing things forward. So they know what they are the challenge is I don't know where that information is and I don't know how to unlock it. And so, obviously that's why they come to us to say what what is that we need to do what is that strategy do we need to put in place to bring that information together so that now that we know and so you know we spent a lot of time with them outlining okay here are the things that are important to this group, and then of course the executive team has their own initiatives and things that are important generally they roll up pretty pretty clearly there there's not usually any surprises at the executive level that the, you know departments aren't aware of, but if we can help them put that process in place it's really generally getting access to the information making sure that it's accurate that it's accessible that it's actionable. If we can accomplish those three things then generally they feel like I'm much more empowered than I was before.


Okay, let's get this off. We have a group of people here, and I'm sure more will join in. Welcome to the fourth of these 4844 implementers call. We have a ton of spec stuff today as always on the agenda. And then hopefully we can get to some updates on DevNet 3 on the large block test that we wanted to do. And then Terrence had a couple of PRs that he's put up that he wanted to get feedback on, if not on this call, at least async, so we can go over those quickly. And maybe I guess to kick us off, and Gar, you gave some updates on a couple of your PRs in the agenda yesterday. Do you want to just take a minute quickly to sort of walk us through where those three are at? Sure, yeah, yeah. There are always like a few of these small ones. Also just to check my microphone works well this time around. Yeah, great, great, great. So basically, I think it's four, but one of the PRs didn't have a status change. That's the one where we just discussed whether or not you have the minimum price. So the three were actually something happened. First, the kind of throughput reduction PR is merged.  The understanding of course is that once we collect metrics, it could be that we end up setting like a slightly different throughput for bringing this to mainnet, but I think as a kind of default, this makes more sense now. And then the second one is the pre-compiler, the pre-compiler return values. That one is still not merged just because I had like some concerns last call around the formatting of the return values. And I looked at it a little bit more into this and it turns out indeed that there's some precedent with existing pre-compiles that handle this differently. So there's this VN128 pairing check pre-compile, for example, where the return value is padded. Also it doesn't return explicitly return a successful and instead of failing if the pairing fails. So I've reached out to the Solidity team just to basically get their take on whether or not it makes a difference and whether or not it's worth basically following precedent here. It's a small change, but I think for this given that like all the test is like it doesn't really, like nothing depends on this, right? So I'd rather wanna get it right and merge the thing that we can actually bring to mainnet and not have to change it later on. So there's this one is still pending waiting for clarification there. And then the last one, that's one that I had forgotten last week was the mempool situation with not automatically broadcasting block transactions. I did, I opened a PR that adds a dependency on Marius's EIP 5793, which is the ETH 68 transaction type announcement. But I do have one question. So maybe if we could briefly discuss this here. So the way the EIP works is that it only adds the transaction type and the size of the transaction to the announcement message, but it itself is not like does not prescribe whether or not clients still broadcast these transactions. So this change itself basically just says in your announcement message, you have to include this information, but then basically whether or not clients still auto-broadcast these transactions by default or choose to no longer auto-broadcast over certain thresholds, that's up to clients. For now, I basically also kind of worded this way and just give it as a recommendation to stop auto-broadcasting. I was just wondering if people feel strongly that we should basically have the A requirement required behavior for clients for block transactions. So this did not just have it as a recommendation, but a extra requirement. I don't know if anyone has opinions on this. Otherwise, I think having it just, yeah, the recommendation makes sense to me, but... Yeah, and I guess maybe once we do this like blob spam test, if we see something break at the mem pool level or gossip level, then maybe we wanna make it more than a recommendation. Yeah. Marius doesn't look like he's here, but I'm just referencing back to the execution layer workshop at DevCon. And I think the key thing we were trying to mitigate here was DOS risk of the execution layer and basically giving execution layer more optionality in whether they were gonna take in blobs or not or large transactions or not. And so I can imagine Marius saying that it actually is really important for it to be a requirement rather than a recommendation. But I think we probably need someone like him or Peter to really weigh in on that, of how strongly they feel. Well, I'm not sure that helps because if someone's trying to DOS the network, they're not gonna follow that anyway, right? They're gonna broadcast blobs like mad. Yeah, but if it's a requirement, not a recommendation, I think the idea was basically you could terminate the connection, the peer connection. Yeah, you can just stop remaining. So they can broadcast blobs as much as they want as long as they're connected to the peers. But if every peer drops them, right? Yeah, but anyway, yeah, I guess we can revisit it. It seems to me like you could drop them anyway, right? Regardless of you've noticed some spamming and dropped them rather than you noticed. Otherwise, how do you tell that they're actually broadcasting something? Right, yeah. Yeah, I suppose though, if everyone's required to request rather than, yeah, I suppose so. Yeah, maybe that does help. All right, sorry. Could somebody articulate the concern in like concrete kind of conditions that we're looking to violate from this? I guess that has been still a bit abstract for us. What are we trying to find? What does break mean? So I guess if nodes are just unable to process the blocks or get put offline because of the increased bandwidth requirements of getting a bunch of blobs that are either invalid or, yeah. Are there's concerns written somewhere we can point to or can somebody own? I suspect if they're somewhere already, they would be in that EIP Ansgar link too, but let me check it real quick. Well, it's basically just the existing mempool issues section in the EIP. It's a really small section, but the idea is just that it's not only bandwidth, it's also compute given how expensive the block verification are. The idea is just that you want to have some mechanism to throttle. Ideally, you could also do that in an existing world with peer scoring, but the execution plans just don't have a concept of peer scoring. So by the time they would basically validate blocks and see that they, for example, they're invalid block transactions in there, they just don't keep track of which peer this came from. And so that would mean a complete re-architecture taking of the mempool to be able to handle this. So instead, if you do it with announcements, then all of a sudden you have explicit control over a, okay, I only pull block transactions from this peer once every so and so many seconds or something. And then you don't respond. Sorry, Ansgar, even more answer, zooming out, I guess my point is that the stress test that we're doing is not testing blobs, it's just called data transactions. And I think I heard that the concern is not just bandwidth, it's also compute because of the KSG verification cost in the mempool. And that's something that we'll be testing with this stress test. Is it, does everybody in this group understand that this is the case or have we been, have we not? So I think the stress test actually tests something different. We have two different concerns that we have the concerns about the size of the actual assembled blocks. And then we have the mempool and those are completely separate. And so what we are testing with that stress test is at the size of blocks because that is consensus critical, right? Everyone has to download these blocks and so they might be kicked from the network. The mempool side of things is somewhat more forgiving because if you make a very constrained bandwidth situation you don't have to actually run a mempool, you don't have to propagate all these transactions. But on the compute side, for example, it's much more problematic because on a block verification the compute is really negligible because you do one check for the entire assembled blocks but for the block transactions you have to do one check for transactions. There might be hundreds of transactions coming in. So it's basically, it's much more of a compute issue there. So it's again, like those are just like the stress that we're doing is just for the block propagation that's separate from mempool. On this one, I feel like we probably need someone, we probably need Marius to weigh in here because he was the person who had a strong opinion on it. And given he's not here, do we wanna push this async and ask for his feedback on the PR? Yeah, I think that makes sense. And I think the test also like, yeah, the test, even just on the bandwidth side is really valuable, right? Yeah. I'm good, we'll get it done this week. I'm writing this today, we'll try to run it on girly by the end of the day, might start doing more coordinated tests over the week. So, we'll give you a chance. Cool. Also, just in terms of philosophy, very briefly, I think it's important to point out that mempool concerns are a little bit less of an issue because we can always launch the CRP with a mempool that is very restrictive and maybe a little bit less efficient in propagating transactions, but doesn't actually break nodes and then make propagation performance better in the long run, whereas block propagation really has to work, right? Because the entire network breaks down if it doesn't work. So mempool is more forgiving. Okay. Okay, so those were your three, Ansgar, and you said there was a fourth one, sorry, that, yeah, you said there was a fourth one that you hadn't gotten merged or given an update on. Oh, the minimum cost, okay. So just no update there. Exactly. Okay, perfect. Okay. So next up, what was this one? Oh, okay, Danny can't make it, unfortunately, but he was reviewing the spec yesterday and highlighted this issue where I think two calls ago, we decided to not verify the blobs as we are propagating them. And Danny was saying that there's a way in which just means any node on the network might be able to propagate an invalid blob, which is not something you would like. I know Mofi, the two of you were chatting about this yesterday. Do you have a quick update on where things are out there? Yeah, I think it's, we sort of like figured out that it is a concern. The options we have is to either use reliance signature verification to deter invalid site person being lost it or rely on the KCG commitments. And based on the contract, I'm leaning towards using signature verification as Danny proposed in the PR. Yeah, open the feedback there from anyone else that has it with you. So we were looking at the times it takes to do the KCG verification versus signature verification. And I think the difference for 256 kilobyte blobs is like two milliseconds. And I think that's probably not significant enough to warrant the signature just because the signature requires the changes to the beacon API and the validated client. And like it'd be nice to avoid those changes if we don't have to. But yeah, I mean, if we end up going with bigger blob sizes, it would be okay to add later too. So sort of my two senses like maybe not, maybe we shouldn't prematurely optimize for this because we also could do things like figure out KCG verification of the blob in parallel with other aspects of gossip verification. Yeah. So you're saying it's like almost because the blobs are not that big now. It's not the end of the world if you're not doing the signature check. Is that correct? Yeah, so we do need something and it's either we need to do the KCG verification or the signature check and the KCG verification is more substantially slower the bigger blobs are. Right, okay. If we're targeting relatively small blob sizes, it might not warrant signatures yet. If, you know, things are going well and we're like, we actually have a lot of headroom, I think it'd be okay to like add signatures later because signatures like it impacts the scope of work by requiring changes to the beacon API and validate our clients. So... Right, right. I guess I'm curious if other client teams do any other client teams on the CSI have thoughts on that? Yeah, I agree. It feels like a premature optimization. Okay. Is this worth, I guess, bringing up on the CL call Thursday or should we just comment on this issue and try to resolve it async in the next couple of days? I mean, I think it's still worth bringing up again, but yeah, I'll reply on the issue. Awesome, yeah. If you wanna share that on the issue, yeah, that'd be great. And then, yeah, we can follow up on it on Thursday's call. Sweet. Okay, so next one after that, I just wanted to follow up, I guess, on this rebase PR. I know we've been working on this a lot and there's comments on it from yesterday and today, but yeah, anyone have anything they want to share, bring up on this or... And just to reiterate the point of the rebase PR, the point of it is to make it easy for client devs that are already working on withdrawals to add 444 on top of that. There's a clause in the spec in the PR to make it easy to disable withdrawals just for testing. And I think Danny brought up a comment of like, if that's like, what are the other ways of doing it? And the approach we went with is to simply know up withdrawal sensitive functions, such that there are no withdrawals in the big block and the withdrawal route is whatever the route is like an entity should be. So that's kind of like where we're going with testing. This lets us avoid introducing withdrawals in the EL so that we can test EIP 444 on ELs that haven't quite fully implemented withdrawals on as soon as possible. And also it lets us avoid any bugs in EL or the CL that to be sure that it's a withdrawal. Okay. So I guess, yeah, we can just keep following up on the PR there, but it doesn't seem like there's anything urgent to decide here. Okay. I guess, yeah, the next thing I wanted to make sure we covered was just definitely three. So last week, all of the, or I guess, yeah, 16 teams said they were trying to get, yeah, get this implemented so that we could launch a DevNet on around November 30th, which is two weeks from now. So yeah, I'm curious to hear about just the different implementations, how things are going, if people think this is still possible or if there's any issues that seem to block this. I can give an update on some of the work I've been doing. So I've got DevNet V3, I've got Aragon is in prism updated to most of the new spec. The pending issues are the PR we just discussed, some of the Capella rebasing as well as I think we still made a couple beacon, the sidecars with the beacon blocks and the consensus layer. So those are pretty close. Those are in great shape. I've also been spending some time pulling out some of the remaining KZG code, mostly from the execution layer into what I hope is a clean library. That's in the crypto slash KZG package within geth. Even though it's in geth, I'm using it both for the consensus layer as well as the execution layer, KZG related or EIP4844 related functions. So all the go clients can hopefully share that. Likely that stuff will move into the go KZG or some similar external library, but for now we're trying to get it right there. Once it's ready then we can then think about moving it out. And I think there's some little bit of discussions like should it contain version hash related functions or should it just be KZG? So there's some discussions around the edges. But anyway, I think it's in pretty good shape for people to start using on it if you're writing in go anyway. And I'll be starting to integrate that in Aragon this week. Nice, pretty cool. Any updates from NetherMind? Yeah, so we are integrating everything like in master branch. No new guest calculations still there. And probably we have no bundle. We won in point being added. But everything goes quite smooth. I hope we will join with everything needed. The difficulty, actually the main difficulty was to repeat all the binary layer of encodings, new encodings we have in this EIP. I mean SSZ encoding. Well, what else, different hash algorithm and like a bit different layout for transaction encoding is this, what, slow submit. But in overall, it's okay. The main problem I see now is we still have no same outputs as go KZG library for CKZG library because as far as I know implementations a bit different in terms of like getting some internal hashes because it is based on different like a binary layout like that. So that's why it's hard to synchronize with guest and the other government implementations now. And we just skip verification for now. But I hope we will find, we will like wait for update from go library and we will have some tests for both libraries with the same inputs and hope to get the same outputs. That's the only issue which is not resolved for now. Got it. And who is working on these like harmonizing these libraries? I know, yeah, I noticed a bunch of people working on them but yeah, is this just something that we're tracking or I don't know, yeah, Kev, yeah. I started with test factors but I don't think we've started integrating any of them. I can definitely speak with LXC offline to sort of interrupt the go KZG with the CKZG wrapper that he's using. Okay, nice. Would that library I have in Geth be a solution to this? Yeah, so I'd basically just make sure that that is interoperable with whatever LXC is using. I had a question about the CKZG library. So like are we expecting like all the bindings for different languages to be hosted on the CKZG repository? It's like who would be responsible for maintaining the different language bindings? Like being the CKZG repo or like for Rush, like maybe as a Sigma prime, we can have it in our own repository like the bindings for Rush, something like that. So just wondering what other language bindings we're thinking of. Yeah, so right now the go and the CKZG stuff is pretty separate. And even the go KZG stuff is somewhat scattered about. So I think the short answer is no, we don't have a good story for that yet. Whether we should consult, I'm not sure we should consult, we need to consolidate it all on one. We just need to make sure that they all work together, right, work the same. But maybe people have other view. Yeah, we were discussing this today actually, because we are starting working on the Java binding and we were asking ourselves if we want to have a separate repo for the Java binding or try to initially stick everything in the current binding directory in the library. And I think if it is the idea, I would prefer the second if actually the end state will be having everything in the same repo. What do you think? Yeah, makes sense, but like another question I had was like, in the end, like maintenance of the CKZG library itself, will it be done by the year? Like, so like whoever maintains that library would also have to maintain binding for different languages. So like that might be hard or not, like I'm not sure about that as well. Well, the solution will be, it will be maintained by several groups. Maybe someone are more CC and crypto oriented, but maybe the bindings inside the directory will be mostly maintained by different groups of people and I don't know if this is the something that makes sense. Yeah, makes sense to me. Like I made a draft PR for the Rust bindings today to the CKZG, Dan Cradd's folk of the CKZG library. So like that was our intention, like at least from Sigma Prime, that we would want to get the Rust bindings merged into that repository and like anytime, like in terms of maintenance of the bindings itself, we could help with like reviewing PRs and stuff like that My understanding from the latest conversation in the telegram group is that Ramana is going to maintain the kind of core crypto and C libraries. And then that, just like you guys are suggesting, we're going to have kind of separate people maintain the bindings, but all in one place. Yeah, I just wanted to clarify what I added in the comment was, I think if it's just bindings for the CKZG library then it probably doesn't make sense in the same package. Go KZG, however, it's not a wrapper around KZG, CKZG it's its own thing. So that probably belongs, should be remain separate. Yeah, so Rust have a completely different implementations and not simply a wrapper, am I right? I think there are like multiple, like pure Rust implementations also around, but yeah, like I was talking specifically about the bindings to CKZG. Okay. And there's also a comment in the chat about like working on common test vectors. Is that something anyone is working on or wants to work on? And we don't, yeah, I guess we don't have to do this now, but I know in the past, like for say BLS, we would fuzz all the libraries against each other pretty extensively. So that seemed like something that it's probably valuable to do as well, but yeah, it doesn't have to happen now. Okay, and I guess, yeah, I'm curious to hear. So this was mostly for folks on the EL side with regards to participation in the DevNet. On the CL side, we have Prism, Lighthouse and Loadstar, say they would participate. Anyone from those team wanna give a quick update on where things are at? So for Lighthouse, we're still planning to participate in the next DevNet. Right now I'm working on the peer to peer portion of things and Pawan is working on integrating the REST bindings for KZG that he just finished with it. And yeah, I think we're on pace to get there, so. Nice. For Prism, oh, Tim is, yeah, I'll, I guess, speak for the Prism team and the stuff I'm working on. So the work is basically incorporating all the, the for-for-for rebase on top of Capella. We are basically going ahead with what I have in the PR for the rebase targeted data soon it gets merged. And also working on adding like the logic for the rebase on the IP4.04 on Capella. It's still going just a lot of development and refactoring work going on. Nice. Loadstar? Yeah. Loadstar I think is on track to be included in this DevNet. We now have Lyon from Loadstar on this call who might want to be giving updates in the future as I try to hand this back to ChainSafe. I think it's looking good. And we now have Loadstar integrated into our interrupt testing repo with only the first of our test suites running against it. But it's using the updated gossip topic and the chain advances and that all works. It doesn't actually save the blobs yet but most of the foundation is there. Sweet. And I guess anyone else think they might join the testnet or still those six teams? Well, small update from Tegu. We are working contemporary with progressing with Capella and for it for four. Actually Capella is definitely far ahead with the works compared to the works for the 4844. So we are progressing in parallel, strictly and pushing things directly on master. So things are progressing but I don't think I'm gonna change the idea that we are able to join the DevNet so far. I don't think the next one will be the one for us. Sounds good. Happy to hear about the progress. Anyone else wanna give an update? This is Andrew from Ethereum.js.  I don't think I've got a mostly done local implementation and I'm still testing it. I'm still trying to get it to work against the local version of the DevNet just from the interoperable. So until I feel like we're able to actually trade blocks and serialize and de-serialize transactions, there's no point in me trying to go to a public DevNet at this point. But I am plugging away at that. At some point it would be nice to understand the current status of the actual EIP. It feels pretty out of date in terms of like the pre-compile spec doesn't match up to what y'all are talking about right now. And so I'm just trying to under, we can talk about that later offline. It's not important. I don't wanna take too much time just to submit the definite questions about that. At some point I've talked to Kev a little bit, but could you some clarity on a couple of things? Yeah, the pre-compile is probably the bit where there's the most, like just like we were talking, there's the most potential changes. But aside from that, it should be pretty fixed. Okay. All right, well then I'm gonna look at it again. I thought there were a couple of places that I went astray. And Andrew, feel free to reach out to me. I'm trying to keep on top of all these things to keep up. Yeah, it will help out. No, that's cool. I appreciate it. I was still just trying to get all the code in place to even start testing it within a while. So, I agree. So, but maybe in December, that's probably the earliest I think with travel plans around Thanksgiving, I'm not gonna have a lot of time to work on it and get ready for DevNet 3. All good? Yeah, thanks for the update. Anyone else wanna share any development updates? Okay. If not, moving on. The next thing I want to chat about was this large block spam test. George's posted an update on the agenda about the way they're thinking about doing this and given that we're probably gonna run a test net run in the next week or so. I'm curious to just hear feedback from folks here about like, is there anything that we're missing or that we should be looking at or do you think basically George's approach is broken in some way so that, you know, once we start running them, if we can get that feedback, or before we start running the test if we can have that feedback, that's great. And then otherwise we'll probably run this on test nets a few times and share results here before we move to main net. But yeah, maybe George, I think like a minute to just explain sort of how you're thinking about approaching this and then see if there's any feedback, thoughts, comments on it. Sure. I'm walking, so it might be a bit noisy. TLDR, my understanding is that we want to create sustained load for some time and we're gonna do it in chunks of some size, which we want to be parameter, which we want to parameter. Default base case, we're gonna do 128 kilobytes, but possibly we wanna try out bigger one to know when that would be useful, but it's also like one of those tests as well. And it's generally low cost to just make the tool generic over whatever transaction shape we want. So my idea is that we'll just make a general load test that for cold data transactions and it's gonna be able to submit either part to C. I'll end it on maybe for a builder, two by thousand, 128 kilobytes. Nothing's hoped for me to do any metrics gathering and I assume that either somebody will be watching or that they could make false analysis. Curious for any thoughts, reactions. If there's no feedback, I guess one thing that's probably worth emphasizing is right now we have a prism branch, which is specially configured to track a bit more metrics than they usually do. So we'll be obviously looking at on-chain metrics and we can run some other clients as well. But if any other client team thinks it's like trivial for them to add some extra metrics and monitoring, it might be worth just looking at what prism did and that would help kind of send it to check the data across more than one client. I don't have the branch real handy, but I'll try and find it and post it in the chat here and we can have it in the notes. But yeah, worst case, we'll just have the on-chain data and this prism that's specially configured. Yeah, oh, I found the branch. So I'll just post this here. Yeah, and I guess once we get the results from this first one, we can come back and discuss them here and see if there's anything we want to tweak before going to Mainnet. Anything else on the spam test? If not, parents had two PRs he wanted to discuss. He's not here to do so. The first one was adding this block in sidecar retrieval by route. I think it just, it got approved this morning. So I don't know if there's anything more to discuss on this. Well, something related that isn't quite this PR but is the by range request, like the counterpart for this request, whether to keep it as a separate block and blob request or combine them into a single request. I'm interested in discussing that at all. I think for Lighthouse generally, whether or not we have the requests together or separate, we're probably going to treat them as if they're a single request, even if they're specced out separately just because it makes handling things like attributing faults to peers a lot simpler. So we would generally have a slight preference for just combining the requests, but it's also not a huge deal if it's a pain for other teams. So I was just interested about other teams are thinking about this. Yeah, we're having this discussion on GitHub and I come up actually with the same reasoning about that. The only thing that we were internally discussing a couple of days ago about having a separate call is for, let's say, archive nodes that for some reason they imagine that you want to have a node that wants to suddenly start getting archive blobs and start searching for nodes that provides blobs for a deeper history. And then this node would like to start filling up the archival blobs for the very deep past. So in these use cases where you want to have those kind of nodes having a separate method definitely makes sense because in that case you have to download the blocks another time, but a part of these archival nodes, I think we think that having the coupled version is simpler. Yeah, it's an interesting point and out of archival nodes. Just to clarify, they are still decoupled. And if you're requesting sidecars that are not recent, we do have like an API to request a response to RPC to get those in a decoupled manner. It's not what you do on your own. Is that the concern for archival nodes or something else? Yeah, I was thinking that having the coupled version actually does not assume that we will have also the dedicated sidecar method. But if you think that we will have both of them, the coupled and decoupled version, this definitely, yeah, solves the issue. But I don't think it was at least intended in the first place to have them both might be right. Yeah, we only use both during gossip so that nodes can easily have like the blocks and its requirements of sidecar all in one message. It makes it easy as Sean mentioned to attribute any problems in the message to a different peer and also avoids weird race conditions where you get a blob but not the sidecar and vice versa and you're waiting for one or the other. But there is a fallback to request like a specific blob given its root or by a range request, similar to how it for begin blocks it works. Okay, yeah, so having them also having the option to have these dedicated sidecar method, yeah, it definitely works. Yeah. Hope you just so I understand like this PR that Sean shared is the remove blob sidecar by range. Are you saying that we wouldn't remove the blob sidecar by range or are you saying that there's another method that's not blob sidecar by range that would serve a similar purpose of this like blob retrieval? Oh, I understand you could. So Sean has just proposed the blob sidecar by root. We could use that instead, plus I'm missing on the use space where that would be sufficient. Oh, I mean, so I was suggesting rather than like having a block sidecar by range request, we have a block sidecar with signed block and sidecar by range request. Essentially just saying like if we're cut, like I feel like we're converging and coupling these two things everywhere. So in the one place that I don't think we have them coupled yet, which is the by range requests, should we? And I think for us like whether or not we do, we're gonna handle them as if they're coupled. So it's not a huge deal if it's spec'd out to suggest they should be coupled, but it would be nice if all the client teams are gonna handle them seriously or similarly. So was just curious about like what other client teams were planning with these by range requests. Yeah, like so I am interested how the prism implementation works right now. Do you guys like hash blobs and blobs separately? And then as a by range request for blocks or blobs completes, like pick off processing at that point, or are you just like making both requests at once? If either request fails, both fail. And then once both complete, you just start processing. Yeah, I can't really speak to present, but the way we had it working for the first two couple deaf knocks is to do the lotter, request the blobs, block, request the blobs, site cars, and if either of them fails, then it just short circuits the other. Yeah, so this is I think what we would implement if the requests are separate, but it's more or less the same as just having a single request, just like a bit corkier.  But yeah, that's all. And it's generally what I was curious about. Cause I think if all clients are gonna implement something similar to that, we should think about just having a couple requests there as well. Yeah. Well, at least for Prism, they do try to like avoid parallel downloads because it makes like attribution and to your scoring a bit wonky. Like for example, in the case where you make few requests, you get the box and the site car and one of them is invalid. Ideally, you don't want to keep communicating with the other peer, especially given like, if we go like with one megabyte size blocks of logs, we don't want to keep making that request. So, I imagine a lot of clients would make a request to get the block, ensure that that's valid before proceeding to get the site car in the decoupled case. But if it were coupled, then we can adjust like our peer scoring parameters to take advantage of the fact and make a single request. That would just be easier. But either way, I don't think it'd be that useful, at least not without crazy workarounds to make two requests at the same time. Try to like explain how it wasn't there. Yeah. So we can keep talking about offline, I guess. But that's definitely, it'd be nice to have some clarity around that relatively soon. And if we're getting too close to the, I don't know, DevNet, and we're not sure, we can go with separate requests. But yeah. Mofi, can we at least pick a solution for the DevNet, even if it's not well thought through? Yeah, I think the current solution, which is what the current spec is right now, will work for the DevNet. We still do need the ByRoot, but other than that, yeah, work works half right now, but we should work. Yeah, so maintaining the range separates and having the coupled ByRoot, this is the current solution, right? So yeah, also considering also what I was discussing before, with regard of the potential Blob's archival nodes, definitely have sense to maintain them separate. And in Tegu, we were also thinking about, in any case, having kind of simulated couple version of it. So you talk always to the same peer and you ask for Blob's and Blob's, and if they match, okay, but if something goes wrong, you can easily peer score, yeah, downscore the peer you're talking to, yep. I just wanna make sure I get this for the notes. Can someone reiterate what the decision we just made is? I think leaving ByRange as it is for the next DevNet, right? And then I'm in open to discussion in the future. We're not gonna merge this, yeah, the 3087 PR, that's removed Blob's sidecar by range. I believe so, to be honest, I link that more for the discussion on the PR. I haven't looked at the PR itself. There isn't a PR, it's just a discussion. It's just an issue right now, but yeah. Okay, so we're not gonna, do anything on that, okay. Is there anything else that we are gonna do or are not gonna do for the DevNet? All right, let's check the DevNet doc, but ByRoot is still something that you want for the DevNet, which is the 3089 ad block inside car retrieval by root. Yeah. And do we have a clear next step on that? Oh, I think it's approved at this point. So we just need to merge it. Yeah, that's pretty much done. Let's go there, ByRange. And the other thing was Brian's PR to, or issues, we decided to flip and we want a signature verification commitments to deter invalid long-sighted car dream gossip. I think we kicked the decision to do this for next week. I think that's probably something we want to have for the DevNet, but hopefully by next week we'll have like a decision on what we wanna do and then update the doc. Yeah. Oh, go ahead. Oh, I was just gonna say, looking back on my notes, it looks like we had a recommendation to proceed with just the KZG commitment rather than the signature, but maybe we haven't formally decided that. Right, we do KZG and we just confirmed this on the call Thursday with the other CL teams, but yeah, generate events. I think we agreed to. Yeah. So end of next week, we should know for sure. End of this week, sorry, we should know for sure what we're doing. And do we have a PR open for that one? The spec? No, there is no PR, that's actually a good point. We just have the issue from Danny, but it might be worth opening a PR before Thursday's call with the KZG and then discussing, yeah. Does anyone here want to own that? I can make a PR, sorry, just so we're clear, like the PR would be to add the KZG verification as a gossip condition, right? Correct, yeah. Okay, cool. And then on the CL call, we can discuss that PR and if for some reason, you know, people think we should do full signatures, then like we can always change it, but I think it's at least we can come to the call with like something more concrete to propose, yeah. Cool. Yeah, thanks. And I think that was everything from today. Just if we have two minutes left, there were a couple action items from last time. So we discussed like end scars at the beginning. George and Kev had this one around discussing the KZG interfaces and how the handle asserts that this happened. We have two non-blocking issues. For the crypto, so there's 3093, we're waiting for a reply. This doesn't block clients. There's 3097, which is the interface for the pre-compile. We agreed on a bytes array interface, but there's a bit of discussion around whether the version hash code should be in the crypto, but that's also non-blocking. Okay, thanks. And then Mofi merging the PR, yeah, we're basing for it for foreign Capello. We're getting close there. Mofi open, oh, yeah. Open and merge PR string to in withdrawal fields on engine API specs at VIP444, did that happen? Oh yeah, the execution APIs. I don't believe that's been merged yet. Are there PR strings? Yeah, there is, let me click that in. Nice, thank you. And then Terence had three of them, but he's not here. And I think basically the two last ones, yeah, the two last ones are the, sorry, so the two issues you pointed today, one is adding the block sidecar and retrieval by route. So I believe this is the first action item he had. And then this second one was ancestor blob availability check. And I think this was the second one, if that's correct. And yeah, that seems... Yeah, this is more associated to a spec change requiring to be more specific about what should do a validator in terms of start testing the head with regard of having all the blobs already downloaded. Yeah, this has been a discussion that started on Discord by me and then became an issue here, but then blended with all these other things around the by range methods. But I think we were converging to the option to say avoid block import. Completely if there's no blob downloaded and verified. Got it. Is there anything, we're just a bit over time, is there anything people feel we are missing you're having, yeah. I just linked one on the, which I think is the 3090 for the beacon block. I think that's in Alex Stokes's core at this point. Oh yeah, one of Alex's on the call. Yeah, he is. Yeah, this was just like deprecating the beacon block also. Correct, okay. Yeah, I was gonna make one edit, Danny wanted a clarification, but I was gonna do that right after this call and then that shouldn't be merged. Anything else, anyone feel like we should have touched on but haven't? Yeah, so I'd like to come back to this test vectors question, which we shortly discussed at the chat. And at least in my opinion, it looks like it would be really great to have these test vectors, something like we have now for a consensus layer that the theorem foundation is maintaining. And so for these at the proper level for the library interface, because looking at the chats, I see that there are a lot of edge cases where people are trying to cover and discover it. And there are multiple implementations, multiple wrappers and detailed test suit for the wrapper level will be really useful, especially if it covers those new discovered edge cases. So I don't know if there are some resources available that somebody could take care of. So that cover is working on that, but I don't know, does he have enough time to develop the full suit and follow all the details? I can add in the edge cases that we discussed. It's mainly basically going to all of the wrappers and passing the JSON and adding the tests into them. I'd have to reach out to maybe Alexey and the others, the stuff like C-sharp. Okay, so you feel comfortable to try to take care of that? Yeah, just making the test vectors is fine. Okay, that's cool, thanks. By the way, for the seal site that we will provide the basic test vectors in the spec test in the next release. And I am keen to merge the Rebest PR as soon as possible. We will talk Danny to agree with it. And once it's done, then I have a test generator PR, which is based on Moffitt's PR. So we will provide the test vectors later. Oh, and by the way, in the CL test vectors, we use the minimal trusted setup configuration. So the format is described in this PR. So just in case, if you have time at CL clients, can take a look if you agree with the format and if there are any issues, we could change it before the next release. Yep. Okay, anything else before we wrap up? Okay, well, thanks everyone. See most of you on the CL call this Thursday. Otherwise, yeah, talk to you next week on this call. Bye. Bye. Thank you.