Hello it's Missy, thank you for watching! For today's video I wanted to share some more hairstyles using hair scarves. Make sure to like and subscribe, click that notification bell as always then you'll never miss any future videos and let's get started! For the first hairstyle, start by dividing off the top section of hair, beginning above both of the ears. Bring this hair to the back of the head and tie it off using a clear elastic band. Now take your hair scarf and tuck it through the elastic band, then pull it through the elastic so the scarf is centered at the back of the head.  Then divide off a similar sized section on the left side and bring this towards the back of the head as well. Take a clear elastic band and tie the two sections together underneath the crown section but sitting on top of the rest of the hair as well as the scarf. Now take the ends of the scarf and tie them over the elastic band at the back of the head. So cross the left side over the right, then loop the left side up and around the right side, pulling the ends in opposite directions to tighten the scarf against the head. Now divide off two new sections of hair from both the right and left side of the head. Use a clear elastic band to tie these two sections together over the top of the rest of the hair and the hair scarf as well. Now tie the scarf over the elastic band, so take the two ends and cross the left side over the right, pulling the ends in opposite directions to tighten the scarf over the elastic. Now take the last section of hair at the nape of the neck and use another elastic band. Tie the two sections together at the back of the head. Then take the ends of the hair scarf and knot them once more over this last elastic. Cross the left side over the right, then flip the ends up and through the middle, then pull the ends in opposite directions so it tightens over the elastic. For the next hairstyle, begin by dividing off a section of hair for the ponytail. You'll want to leave some hair out around the nape of the neck to create the knotted portion of the hairstyle. So starting at the ears, divide off a section going down towards the back of the head, then use a clear elastic band and tie off this top section of hair to create a low ponytail. Now take your hair scarf and slide this through the elastic band and then pull the scarf through so it's centered in the elastic band underneath the ponytail. Now with the hair left down at the nape of the neck, divide this into two equal sections so there's a left side and a right side. Use these two sections to create a knot on top of the ponytail. So cross the left side over the right, then tuck the right side up and through the gap, pulling the hair in opposite directions to tighten it over the ponytail. Then wrap the two ends back around the ponytail on opposite sides, combining them back together underneath. Then use a clear elastic band to tie the two sections together at the base of the ponytail underneath the rest of the hair. For the next hairstyle, begin by pinning the crown section first. Trace lines with your fingers along the sides of the top of the head, meeting at the back of the head to divide off this top crown section. Slightly twist the section together and then pin it in place using some bobby pins. Now divide off a small section of hair on the left side next to the crown section underneath it and create a twist with this section of hair. So twist the section upwards and then gently pull on the bottom side of the twist. So part of the hair will slide out of the twist, making it look fuller. Then lay the twist under the crown section and pin it in place with bobby pins. Now divide off a new section of hair on the right side of the head and create another twisted section. So twist the hair upwards, bringing it around the back of the head so it meets at the other twist. Then tuck it underneath the left twist. So pull the right twist underneath the left and then pin it in place with a couple bobby pins. Now twist and pin one more section of hair from the left side of the head and pin this underneath the previous two twists. So divide off a section of hair from the left side of the head and twist this hair upwards. Then go back and carefully pull on the bottom side of the twist to make it look a lot wider and more full. Then lay it underneath the other two twists and pin it against the head using some more bobby pins. Now create the ponytail portion of the hairstyle. So combine the remaining hair together and tie it into a low ponytail. Now you're going to create a topsy tail with this ponytail. So carefully pull the elastic down slightly and then create a gap in the hair right above the elastic. Then flip the ponytail up and through this gap so the two side sections end up becoming twisted. Then gently pull on the two sides to make the twists look bigger. You want to pull on small sections of hair and not on the entire section, just little pieces to kind of pull them up and out of the elastic and this will make the twists look a little bit bigger. Then as a last step cover the elastic band. So divide off a small section of hair from the ponytail. Wrap this around the elastic band and then pin it against the wrapped piece using a bobby pin on the underside of the hair. For the next hairstyle begin by dividing off a section of hair at the top of the head. You'll be using this section for the braid so you can make this as large or small as you would like. Trace a line beginning at the corners of the forehead not too large of a section and once this is clipped up take the remaining hair and create the ponytail. So combine all of the hair together and tie it off using a hair band placing the ponytail where you want it to end up sitting. Now let down the hair from the crown and create the braid. Divide this section into three equal pieces and cross the side strands over the middle strand alternating between the right and the left side strands. So cross the left side over the middle then cross the right side over the middle and once the braid reaches the ponytail wrap two sections of the braid around the left side and one section around the right side so it looks like the hair is going around the hair band. Then combine the three sections of the braid back together underneath the ponytail and use a clear elastic band to tie the hair together so it stays wrapped around the ponytail. Now go back over the braid and widen it a little bit. So just carefully pull on the edges of the loops so the hair slides slightly out of the elastic band and the braid gets wider and flatter. Then you can go back over the crown of the head and pinch and pull on small sections to add some volume and texture to the hairstyle. I think this ponytail is so fun because it looks like the whole thing is braided but it's really just done in two sections. So I hope you give it a try and let me know which of these hairstyles you like the best down below in the comments. Thank you so much for watching. I hope you enjoyed today's video. Be sure to let me know in the comment section which of the hairstyles was your favorite. I love knowing which one is the favorite so that I can film more of those in the future. Be sure to like and subscribe if you haven't already and click that notification bell then you'll never miss any future uploads and I will see you next time.


Boom Some money geeks of V here welcome to another video guys. So in today's video, we are going to talk about CC IV charge a capital This is a company that we've covered here on the channel. I've given you guys my perspective I do own a lot of the shares and finally this company is making a debut on that You're new to Casimbo on the Nasdaq. So that's what I'm going to talk about today Give you guys my game plan But before we get started guys, we are new to the channel We talked about how to earn money how to save money how to invest and build wealth So that's something that interests you go ahead and hit that subscribe button and the notification bell So you don't miss out on new content. So it comes with Chelsea capital This is the Lexus of Tesla in my personal opinion There's so many good things about this company that I like in the direction they're going and some of the investors I kind of like that direction. So I have a lot of shares. So just so you guys know But again, if you are just looking for an alternative and you didn't get into Tesla You want something that you can buy Now it's cheap and hopefully write it up to the next five ten years and enjoy that that growth Then this would be a really good EV for you to go into the thing I like about them is that they are not rushing to the market Like I've seen other EV companies that will go out there and put their face and don't even have a product to show For so these guys are doing the opposite They're taking the time and actually making sure that they have something that they can go to market with so again If you are not in the stock do some research before you jump in So the reason why I'm actually doing this video today is because lucy has been trading under the ticket symbol cciv which is a spark and finally Their merger or their combination is over. So just to give you guys some context last Thursday, they actually voted to combine the two Companies so cciv which is just a capital and lucy models And so they didn't get enough vote and so they had to again I joined that vote and vote on Friday To complete it and after friday 99% of the shareholders had voted that they won that combination to go through So if you get up a monday morning, you're gonna see that the ticket symbol is going to switch from cciv To lcid that would be the new ticket symbol that trading on monday So if you see that new ticket symbol, don't be scared. Don't be confused. That's where it's going to be That's the new ticket symbol and it will be trading on the nasdaq. So again from a perspective of a game plan We've seen it over and over here on the channel with other sparks that there's usually what I call a post-spark Slum so if we just go over here and take a look at what happened to this stock when before they even announced that they were gonna go public You can see here cciv There was some rumor that they were going to take lucy public somewhere down here And then finally when that message came look at what happened to the stock it went up to as high as $58 So if you look them from there, they made the announcement And guess what happened? It just took a beating back in february and see this thing dropped down from that 58 down to 27 It went as low as $17 and some change And I kept telling you guys that keep buying keep putting money into this Company because when this thing bounces you're gonna see some really good returns So see it got down to that 17 squeezed back up to 26 and went as high as 28 Just in in june and then sitting somewhere at 24 20 25 So again to me, this is a great opportunity For for these stocks.   So again, just just a quick recap here guys As like I said, what these things start trading is going to be trading under their new ticket symbol l c i d And you're going to see it Nothing is going to change as far as your your your share sizes. Everything's going to be the same The name now is going to be lucid group So it's not going to be just lucid multi lucid group incorporation So that'll be the new name that they're going to be trading under and there's one thing I want to bring it up to you guys here There is a Saudi Arabia investor that owns about 60 percent of this company And i'm thinking I think it's a good thing for the company because if there is a Saudi Arabia investor And this person wants to push this vehicle in Saudi Arabia. These guys have money They would buy these The cars like crazy They would buy the lucid dream the lucid and they'll buy they'll buy gravity All the products that it's going to come they're going to push it out there In Saudi Arabia and push and actually increase the sales which by definition is going to translate to profitability So to me that is something that you should definitely Keep an eye on so i'm excited about the move. I don't know about you guys But again, if you are just looking to get into the stock be careful Don't jump in wait for that pullback even though the current price at which this thing is trading is not terrible But be certain that you're buying the really bottom. So wait for it. Wait for that post merger What I call pullback that pulls merger slum and then you can ride it all the way So that would be my perspective here So guys if if you have any questions, definitely don't hesitate again I'm an investor in this particular company huge I'm not talking like 100 200. I'm talking about 3000 doing three and four thousand shares total It's a matter for about 4500 shares. So, I mean, I'm I'm big here and my average is under 20 Which is to me is is excellent. So I'm going to hold these Long-term, I mean at some point I might offload a little bit and diversify. I'm putting in something else But for now, um, I'm just sitting there holding tight to see where this goes So let me know in the comment section what you think if you're new to the channel guys We took about how to earn money how to save money how to invest and build wealth If that's something that interests you go ahead and hit that subscribe button and your notification bell So you don't miss out on new content. Also, if you're looking to get started with investing guys We both have their promotion where if you sign up and deposit a hundred dollars, you get free stocks No cost to you. I'll put the links in the description below and as always guys Do your due diligence.


I'm Shane Berg, Assistant Deputy Minister and Chief Forester for the Province of British Columbia. The Office of BC's Chief Forester is home to global thought leaders in forest carbon modelling, climatic projections about our future forest ecosystems, and in research that spans forest carbon dynamics from seed to forest product. British Columbia's forests and ecosystems have become known throughout the world. For the quality of timber they produce, and their vast expanse and natural beauty. As we face continued challenges in our fight against climate change, BC's forests play a pivotal role in helping ecosystems adapt and become more resilient. For National Forest Week 2022, I would like to celebrate the unique role that our forests play in helping to find solutions to one of our most challenging natural resource problems today, our changing climate. The extreme wildfires, heat waves and flooding of the past several years were disorienting for British Columbians. We have a lot of work to do on bolstering our communities and ecosystems for the impacts of climate change. Reorienting ourselves with a strong foundation of climate data is an important part of this adaptation response. There is a large and diverse portfolio of activities that can help cut greenhouse gas emissions. Forest conservation and sustainable forest management can play an important role in this. At the same time, we also need to reduce the degradation of more sensitive ecosystems and restore forest health while continuing to enhance our use of wood and bioproducts to displace carbon-intensive and non-renewable resources such as gas, concrete and plastics. The Office of the Chief Forester is leaving the Climate X project to develop new data on climate extremes, drought and fire weather. The focus is on increasing the spatial detail of these indices by a factor of 10. This will vastly improve our understanding of how climate extremes are changing in BC's rugged landscapes. Ultimately, it will help us reduce climate risks to BC's people and ecosystems. Forest-rich northern regions like BC face a challenge in finding ways to increase the sustainable harvest of wood fiber and simultaneously reduce the environmental footprint. The mixing of traditional knowledge and rapidly adapting forest industry, all looking at the landscape with a climate change lens, is a pivotal moment for BC. Research and debate are important, and we must rely on a community of bold forest managers and practitioners who are willing to trial new ideas. Through active and innovative ecosystem management, BC's forests and the people who care for them are contributing to solutions to a changing climate. The Ministry of Forest is working to ensure that forest managers understand the trade-offs and benefits of managing forests for multiple values, including carbon storage and climate adaptation. Through our expanding research and knowledge, we have come a long way in discovering the relationship between carbon and forests. Forests that are managed sustainably and those that are conserved from harvesting activity both contribute to offsetting the effects of climate change. I'd like to recognize and thank the forest professionals, practitioners and land stewards working today to help manage BC's forests, to help mitigate the effects of a changing climate and to keep them healthy and resilient for now and for the future.


My name is Grant Ingersoll, and I'm the Chief Technology Officer here at the Wikimedia Foundation. The fact that we as a project in a community support over 300 human languages, as somebody who's written multilingual software is just mind-boggling. Nobody else does that. Nobody. Any of the big tech, nobody supports, I believe, in somebody's citation needed, but somebody can fact-check me there, but I don't believe anybody else supports as many languages at the scale that we do, so maybe that's my caveat on citation. And that's really just a true testament to all the folks involved working on this for 20 years who said, you know what, we're going to do this for everybody, not just English or not just French. But when I think about the way the product and the tech department work together to serve the movement, I mean, I think, you know, there's a lot that goes into it. There's some of the obvious things, right, in that we run something like, I don't know, 2,400 servers spread out across four going on five data centers around the globe, perhaps even more in the near future. We support something like, I want to say around 2 million plus lines of code, right? We do things, everything ranging from, you know, installing those servers into the data center because, you know, as I mentioned earlier, one of the key things we want to do is be independent of some of the, we want to maintain our independence, so that means running our own servers. We want all of our software to be open source in line with the open knowledge movement. And so we use only open source in production. And that requires a good deal of engineering work to make sure it all runs as seamlessly as possible for our sites. We also support an entire, what we call, Wikimedia Cloud offering, which basically allows anybody in the world to show up and say, hey, I want to do Wikimedia things or Wikimedia things, technically, and we will host that code and help them secure that code and run that code such that there's just absolutely amazing feature underneath the hood here of a bunch of bots and tools that people in the community have written that run on that cloud platform that then help keep the site up and running or a bit more effective. A little fun fact is something like 30% of all edits are actually done by bots written by community members running on that cloud services. So that gives a little bit of a taste of how that budget is spent. We also do research. We are continuously adding features and functionality. We are working with our communities on issues ranging from, hey, how do I make sure I can have great discussions on our reply to pages or our talk pages? Sorry. All the way through to how do we make sure we have effective tools for dealing with trust and safety situations because the world is incredibly complex and we need to make sure we need to do what best we can to support our community's safety. All the way through to how do we make sure we have these sites secured for those who do computer science. There's an old joke that there are two hard things in computer science. The first is naming things and the second is writing caching. But we actually made some really significant improvements in the way we do caching such that we are way more efficient at delivering content around the globe and keeping it fresh. And that freshness then directly translates to our readers and editors having a much better experience at the end of the day, right? Like, you know, if a Maradona dies or Kobe Bryant dies and you want to read about it, you don't want to read the outdated news from 30 seconds ago. You want to read the outdated news from two seconds ago. So the first thing I'm really excited about is what we are calling global site performance, namely, you can think of it as we want to make sure that no matter where you are in the world, you have, and I'm going to hedge here a little bit, but you have roughly the same experience as someone who lives, say, near one of our main data centers, right? Like, which is located in Washington, D.C. in the United States. Or if you're in Europe near Amsterdam, which is where one of our main caching centers is. And so we want to make sure that if you're no matter where you are, you have roughly that same experience. The second thing, you know, I talked to, I've talked some about, you know, we want to make sure the site is secure and reliable. We know that the landscape around the security of our sites is ever changing due to legal frameworks changing. And so in order to make sure we can truly withstand outages across any of our sites, we want to make sure that we have offsite backups from which we can restore, right? So we spend a lot of time just trying to make sure that if something, you know, if something bad happens, knock on wood, it doesn't. But if something truly bad happens, we can deal with it. So there is some disaster planning scenarios that we just work through and run through. Gory details are all underneath the hood. I don't want to bore our listeners with it. And then last, I'd be remiss if I didn't highlight, you know, I think one of the things this project has a real opportunity to do or these projects have a real opportunity to do on the software front is to modernize some of our software practices and tooling. We are working to establish what I would call a better welcome map, right? I think one of the things we've under-invested in, and it's almost sad to say because we are a site built on documentation, some of our software documentation, et cetera, could use some more love, if you will, right? So we're making some investments in documentation. We're also making investments in how do we make sure our content and our code bases are more inclusive, more welcoming of people? Because at the end of the day, you know, again, we want to make sure we're reaching everybody around the world and that's going to require developers around the world as well. Some continued focus on the resilience of our sites. We are continuing work around helping or doing research on, I believe what the community calls knowledge gaps, this notion that, you know, one wiki might have information about a particular person or a particular subject and another wiki doesn't, or it's missing information on a particular category. So trying to help through suggestions and editors fill in some of those gaps. We are continuing work on adding additional hardware capacity. So we are bringing up a second caching center in Europe. Fun little fact is 50% plus of all traffic to Wikipedia goes through our European data center, which is currently in Amsterdam. That is a single point of failure if you want to get into tech talk. And it also means that most of our traffic from Africa and the Middle East and Russia and the like goes through in all likelihood that data center, which isn't always a great performance experience. So for both resilience reasons and for performance reasons, we're adding a second data center or caching center and that should better serve traffic to Europe, Middle East and Africa with where it's located. So I'm excited about that as well.


Thank you very much, John, appreciate it. And are you going to do it? Tommy, I'm just going to go ahead and take it off here. Everyone, thanks for doing the hyper ledger Denver meetup group today. Really appreciate your attendance here. Today we have the pleasure of having Tommy Cook see from Simba chain, who's joining us. And he's a military veteran from the Marines with 30 years of experience in the it field. And he's also an AWS cloud professional. An AI champion trainer. And he's really been working in, you know, blockchain and leading the training for Simba chain for a number of years. And they've done a lot of great innovative work. And they have some great contracts in place. So I'm going to turn it over to Tommy just to talk a little bit more about his background and the background of Simba chain and what we're going to go through today regarding rapid deployment using Simba quick start. So Tommy, over to you. Awesome. Thank you so much, John. And thanks for inviting me to come and talk to your group today. So to probably give you guys an idea of really where Simba is layered in on any architect stack. You probably need to just kind of maybe even take a look at maybe the progression of the technology and, and how the technology has taken form. And generally speaking, when I, when I think about this concept, you know, and I, sorry, I was teaching another class this morning, but when I think about this concept, I always think about somewhere here, it's right there. The three P's, right? People processes and platform, right? And so what we at Simba chain are, our focus is, is that we want to focus in on the process and, and, and define structures for data that, that is going to be relatively standardized for maybe what the data governance should be. What data points do we need to collect about this transaction? Because our concept is, is that the internet is changing, right? The internet is changing from an internet of information to an internet of value. And that value is going to be stored based on our ability to capture that process and capture it accurately, whether that be through an ERC 20 standard as a utility, or if that be like a 721 more of a validation and a claim, right? And so, so we can start to look at the ability to create different types of architectures. And so with that, we want to stay as platform, agnostic as possible, give you the ability as the professional to define what your workflow processes should look like, and the data points that you're going to be using, and then just leverage the strengths of your people, right? Give them the tools that they need in order to be successful, right? And so we're concentrated on outcomes. And that's what we want to do is we want to create the appropriate outcomes. And so with that, at Simba, and thanks for the great introduction, just a quick introduction. I've been working in IT for a really long time, and I was teaching PeopleSoft. I taught PeopleSoft for over 20 years. And when I saw blockchain, I dropped everything and ran to this technology. And if you've ever worked in an ERP type environment, you probably understand that there's massive amounts of data that you have to trust somebody of holding it. And maybe that's inside of the hospital, and you don't necessarily trust that particular hospital network or that clinic, but they're reporting their data. And so Hyperledger is a really great adoption here because it's more of a private blockchain. It's leveraging the technology. It's leveraging your ability to define your consensus mechanisms and define how you're going to have that chain off-chain data, but still allowing you the opportunity to not necessarily make it publicly available like an Ethereum public chain. And so we like to give the users that opportunity to make that choice. They want to use an EVM on a Hyperledger fabric with borough, and that's what we try to do. But ultimately what we're looking at is we're trying to adopt these characteristics, right? These features and characteristics that we just don't have in our current workflow. We don't have decentralization and distributed data. We don't have immutability in anything, really, unless it's on a blockchain. We don't have cryptographic primitives built into our workflows. It's something that's bolted on later, but it's not something that's built in. And with the blockchain, with the appropriate smart contracts, we can start to bake that into our code. And I like to say, with the right structuring, we can start to bake the security in instead of taking it off. And that gives us the ability to start to also look to the actors, right? And their level of pseudo anonymity, autonomy in the workflows to be self-governed, and then have transparency in those transactions, and not really trust anyone. Just trust that the transactions are stateful and represent the state of the assets. And so with that, the big problem that we run into is if we have to learn how to write chain code in Hyperledger, that becomes somewhat of a lift. If we have to learn Solidity or Viper or IPFS, that's somewhat of a lift. And we want to make the functional user powerful still, but also give them the tools that allows them to communicate well with the developers, and also give the developers the tools that they need in order to unlock the value that might be already inside of their network, right? So how do they look to their data lake and figure out how to create data stores and things like that, right? So we kind of try to give them that tooling as well. But we try to remove all these barriers. We don't want to have rigid infrastructures and expensive proof of concepts. We want to be able to iterate, figure out if something works and if it doesn't, then try something different. And so we do that through our REST-based APIs that we generate. If you've ever used Hyperledger's sandbox that they used to have, I forgot what it was called, but that is very similar to that, right? And so we'll generate those REST-based APIs. You can still hit those REST-based APIs, see if it works for your workflows or not. And if it doesn't, then you can just change the iteration and re-mock it up. And so a lot of times we'll call that fail fast, but basically we're just reiterating to find the solution that works.  Not Einstein, the guy that did the electricity. Gosh, why am I drawing a blank? Anyway, it's his money. Yeah, Tesla. Tesla created electricity. Who was the other guy? The guy that stole his invention? Edison. Edison, yes, the Edison man. Thank you very much, John. I don't know why I was drawing a blank on Edison, but yeah, Edison definitely would just re-iterate, right? If something didn't work, he would fail fast and try something different. So that's kind of what we're doing on our front end. We're creating the REST-based APIs that can be built into any existing infrastructure, see if that blockchain data point would create value. And if it doesn't, then try something different, right? So with that, you know, when we think of our storage, that's our ledger. Our consensus mechanism is in essence our network and gossip and whisper protocols are what we use there. And then the smart contract is, of course, our compute or execution environment. And so when we comparatively look to that, compared to what we have today in Web 2, Web 2 is still the Internet of Information, but what we've done is we've siloed power. And so by siloing that power, we've created the ability to even de-platform presidents of nation states, right? And we've seen that happen. And so what we need to do with Web 3 is we need to create more of a semantic web where it's an Internet of Value and not necessarily an Internet of Information. So now we know we can do secure communications. So in those secure communications, can we exchange datasets that represent value? And that's going to be extremely disruptive, I think. And that's where the Internet of Value comes into play. And so that disruption is all occurring here on the back end, right? We're just moving our database away so that we're not using that crud infrastructure. We're getting rid of the update and delete functionality. And we're moving to a dataset where we define structure and then we define content. Structure is defined probably more in like a smart contract infrastructure, maybe even in a YAML file that could define what Kubernetes clusters that you need to have, what code base you need to be running. And that is ephemeral, right? It just always uses that same structural state. But the context of the data and the assets that are being used within that structure, that needs to be immutable, right? And so how do we create that? Well, that's the immutable ledger. That's the blockchain. And so the blockchain is going to have immutable ledger of state to track value. And then we can also have structure that is defining the ephemeral context of the transactions that need to go through that structure. And if we look at it this way, I come from a PeopleSoft background, but I think of it from like ERP, it's kind of the same thing that we did with ERP. We would just look at workflows and we'd say, okay, what data points do we need to keep track of here? What has value? Where are we going to keep track of it? What's the relationships involved? And then we could start creating these ERD diagrams and really creating an infrastructure that shows you the relationships of data. But what if that relationship of data could be bundled and then packaged and verified and then used to provide value, right? Provide value to who? The user, right? So the user doesn't contribute their data to the infrastructure. The user just contributes their data as part of the utility of the infrastructure and then they own their data as a signed owner, right? And so now they have a wallet that represents all of their military record or a wallet that represents their education or a wallet that represents their medical records. And we're starting to see that slowly get adopted with Anthem and UnitedHealthcare and so on and so forth. So the important thing is is we're giving ownership of data back to the user.  We just talked about Edison, so let's go back to Edison again. Let's think about the electrical revolution. We used Morse codes about 50 years before the Chicago World's Fair and are close to it. So electricity, even though it was available and highly available, I mean, it was adopted, but it just didn't create mass adoption until you could light up your living room, right? The same thing applies to blockchain. Blockchain's been around for a long time. The technology's around in Bitcoin and hash cash and things like that that we've meshed together, but we haven't unlocked the ability to actually see that light bulb moment that's just going to kick off that we call it the fourth industrial revolution or Web3. But in essence, it's going to be that spark that generates a lot of interest and wants people to start using the tech. We're seeing that in DeFi, but when we start to see that the same data points that we're using for finance can be used in order to track value that we consider value as humans, we're going to be able to unlock a whole lot, a whole new asset class that I think that is going to be available and it's just going to create a whole new revolution. So with that being said... Let me ask you one question before you move on from that because I think Tim brought up a great point. Is he had asked about... You talked about structure and state and what he was asking about was about speed and I think... Transactional performance. So maybe you can just touch base on that before we move on to the next stage here. Yeah, let's talk about that real quick. So transaction throughput is all scalability. So scalability... We call it the tri limit in blockchain. You got decentralization, security and scalability and transaction throughput or scalability. And so you pick two. And so with that being said, if you are using Hyperledger, then you don't necessarily have decentralization. So you can start to get those TPSs and things like that. So it really just depends on how you define your consensus mechanisms that you want to use in your network. We'll define how quickly you can push those transactions through. We also have an integration with consensus quorum, which in essence, depending on the size of your node, you can kind of size that to infinitely. So for TPS, but now you have chosen, decentralization is not going to be part of your model. So therefore you have massive scalability. So again, when you look at that tri lemma, that's really where you make those decision points. But we, we had some of the changes provided is the tooling and, you know, you can pick what path you want to take based on that. Does that help? Yeah, okay. Yeah, no, that's great, Tommy. I just want to make sure that, you know, some of these questions as they go along, I'd rather just weigh in on them. So go ahead, move on to your next stage, but thanks for addressing that. Uh-huh. So what we try to do is we just want to make it simple. We do want to make it like, like the question that just came in, we want to still make it scalable, but I'm not talking about scalable from a transaction standpoint. I'm talking about scalable from, um, you can build your solution one time and it's portable, right? Uh, because it's an EVM smart contract and that EVM smart contract, uh, has integrations with multiple, uh, blockchains that are built on top, including hyper ledger and, uh, uh, we have several integrations. So, so we'll look at those when we do the demo here in just a second. So what we do though, is what we try to try to define is define a method for you to bring in input data, define the data points like I had mentioned before, that you think is going to provide value. The value that it provides, you know, it's just metadata, metadata, creating the good keyword today, metaverse, right? We're all hearing that, but we're just trying to bring that data in, defining those data points, knowing the province where the data comes from, and then that data can get bundled and then provide either utility or functionality. And then that in essence is unlocking a lot of this Mary of, of the data points digitally with the asset that exists in the real world and which in essence creates a metaverse, right? If you're not familiar with this concept, I mean, think of the first time if you've ever played Pokemon go, or if you've ever seen that concept, that's probably the first time any of us ever really dealt with a metaverse, right? We had a, a screen in front of us, but when we were looking at the screen, it represented something digitally that was supposed to be in the real world that really wasn't there. But if I've interacted with it with the screen, I could get it from the real world. Kind of weird, huh? Well, that's, that's an, that's a metaverse, right? You're, you're marrying the real world with the digital world. And you're, you're making that leap.   I couldn't get online unless I was at the squadron, right? So, you know, now just get our pocket. We're communicating over the internet. So it's no longer a destination point is just ubiquitous. It's just there and available. So that's in essence, what we're doing is we're, we're making this digital data just there and available. And you can just, you can easily verify it, whether it be knowing where your, your stake came from or whether it be verifying that you're over a certain age when you walk into an, a drinking establishment. So, so there's all kinds of things that we can do with this, but we're looking at this as what we call off-chain data. And then we're using our smart contract to designer to generate these APIs so that you can generate these smart contracts. And then you can also subscribe to them. So you can have a web hook or an SMS text or an email notification based on the state change that occurred with that asset. And then you, we also can, we can subscribe based on those subscriptions. We can build a caching model that will allow you then to generate, you know, dashboards and things like that about certain data points that you're keeping an eye on. And we have SDKs for Firebase, for, for VB, IOS.  Anyway, so, so that's kind of our model. And then basically with this model is it allows you to kind of generate this smart contract that's going to be your inputs from whatever these separate data points are, right? So these separate actors that are reporting data points, they're just bringing it in through your smart contract. And then you're defining them as assets and transactions through relationships. Once you've done that, then you can deploy this, like I said, on pretty much any blockchain as long as it understands EVM model. And of course, we use borough for that on fabric. And then with that, then we generate the API for you to be able to hit those data endpoints. But kind of the beauty of our SEPT tool, and we won't look at that today. We're going to only be looking at our Quickstart tool, which is only kind of the functional side. But if you look at the technical side, because it seems like some of you might have been technical users, especially in our first, first during the conversation. But you guys will really love this because we're giving you a GraphQL, we're giving you Neo4j, all the tools that you're going to need to basically look at your data lake and then start to build your data storage, right? To start to find out, okay, where do I have leakage? You know, when you start to do your top-down model in GraphQL, we can run it through those models and start to find problems that you have. And you're doing that all internally with our tools before you start to expose it to the REST API that you had built previously, right? So basically what you're doing is, is you're using these tools to kind of do your own Kafka, right? You're matchmaking. You're matchmaking. What do they want? What do I have internally? And once you're doing that, once you can kind of match make that and marry that relationship, now you're able to really start to unlock the value of some of your data lakes, right? And so I think that that's where a lot of enterprises get stuck on this, is they just don't understand where the value is coming from. Well, it's coming from the data that you just afraid to let anybody have access to you because you just, it's metadata, but you're just afraid of letting, letting it be validated and owned. So if we can package it in such a way, maybe we can unlock the value. So with that, you know, again, this kind of just talking about the graph model, and we, you know, it will query existing REST-based endpoints, generate the ABI for it, and then we can use that, you know, to kind of match up data points and stuff like that. So all kinds of fun stuff that you can do here on the back end. And then our smart contract designer, I'm just going to go ahead and bust out of here, and we're going to go ahead and start our demo. And I want to show you how this tool works. So, and all of you that are here today, you can go out to app.SymbaChain.com. And Riley Faye is another representative. You'll see her there in the chat window. She's another representative from Symba. She's here to kind of support me. But she is, she is definitely somebody that would be able to help you get started on a project, on some kind of an idea.  People just don't understand it, right? And so they just shy away from it. But a lot of times because of the simplicity of our tool, we get a lot of traction in the educational institutions. And of course, Riley can help you with that. If that's an idea you have. But basically what this tool does is once you get logged in and create your account, there's kind of three distinct areas. There's an area for your wallet, there's an area for your smart contract, and there's an area for your API. That's it. Okay, so as, as developers, you probably understand that if you're not a developer, or if you're just a functional user, let me explain. Your wallet is where you're keeping your identity for signing transactions, right? So anytime that you have to sign a transaction, you're going to see that the wallet is going to be signed. So basically, the wallet has the keys that sign those transactions. So inside of the head and shoulders area, you will see your blockchain wallet section, and we have three different walls. Well, the remote wallet is our hyper ledger borough standard. Right. And so I've went ahead and created the hyper ledger borough. And these conform to the hyper ledger borough wallet. And we also, of course, have, we have five standard for Bitcoin. And then we have the Ethereum wallet, which is the Ethereum standard for wallet. So we have those three different wallet standards that you can use just to generate your wallet for generating the smart contracts. Right. And the cool thing is if you're using like Ethereum, we also provide links to faucets and stuff like that with, with hyper ledger. Don't have to worry about any of that. We're just generating the identity and creating the keys. Right. So you'll be able to use these keys. And then to sign transactions. So if I wanted to generate another wallet, I just put in my name, John's wallet. And create it. And there we go. Now John has a wall. There we go. So, and then a very simple again, but powerful and powerful how, because now if I come over here to my solidity area, and since we're using borough, we can go ahead and we can create a smart contract that will just be solidity compatible and then just deploy it on borough. So I'll show you that here, but basically, as I mentioned before, we're concentrating on assets and state changes. So an asset is something that has value. So, you know, my car, maybe so car. And then what kind of things do you going to have about the car? Well, you're going to have maybe a string, which will be maybe the Venn number. The Venn, you know, the color, maybe. And notice that one of the things that we try to do here is even though this is a functional user tool, we try to teach the users like data minimization and good structuring of data. So I educate the users on what a boolean is, on what a string is, an address of course just means that it's a calling smart contractor coming from a particular EOS account, that type of thing. So the integers, we have unsigned and signed integers. I briefly just talk about, you know, using an integer for anything that would have a negative value unsigned for anything that only has positive values and then also date and times. And then bytes would of course be anything where you're doing machine to machine communication. So if you don't need to have any kind of human interaction, just passing data. Last time we can just do that through byte and get the get the attention done without any ambiguity. So anyway, so that teaches good data minimization just by instructing the user on what these data types are. And then they get to define their tuples or the key value pairs for not only the asset, but also for the transaction. So if you make a car sale, right, then you're just selling. So the with the sale date, what kinds of things are going to be important to be maintaining state on an immutable ledger? Well, maybe we need to know the buyer, buyer, right? So maybe the buyer ID, maybe the sale time. Date time. So we can start to think about all this data. And then notice here, I have this thing. This is off change storage. Well, off change storage is really amazing because what that does is it just takes the inputs, runs it through shot 256. And then puts the, the digest on chain. So the bundle hash is just the digest the, the 256 bit hash of whatever the inputs were. And then you can use that to validate state of whatever the, the claim is. So, you know, when we think optimistic rollup, you know, we're being optimistic that what's being rolled up and put on chain is valid and they're not lying about it. Well, this is basically what an optimistic role of it's right. We're not running it through any zero knowledge proofs or anything. We're just doing optimistic declarations. So this gets you kind of in that direction, right? Most things will be ZK starts it at some point, but optimistic is probably the first step to get there. And so this is, this gives us the ability to kind of create that functionality. Anyway, so that's that. And then once we've done this, then we just create a relationship and say, Hey, okay. Well, the car is going to have a sale. And then there's that and said behind the scenes, you know, it's just generating this really generic code.  It's a very rough structure of what that input should look like. So think of it like this, you know, sandwich complexity. We're just generating the input tuples. And then we'll put the complexity in the, in the smart contracts that we're going to be calling after that. So, so that's kind of the, the model that we look to here. And so at that point, let me go ahead and actually, let's go back to this here. So at that point, you know, this is kind of what this does for us, right? It's pretty powerful, but it's a tool for that functional user to be able to put their intentions in place of what metadata points that they want to put on chain in order to unlock value from the data. That's it. That's all they're doing. And so how could I make that more complicated? Well, let's go look at our smart contracts and see if we can find one that's maybe a little more smart, a little more complicated and see what that looks like. So here we have this one. It's called our coffee tutorial. And if you can imagine, um, tracking coffee from the producer or the farm, all the way through the co-op to the sheller, to the batch, to the roaster, to the warehouse. Um, and then to your cup, right? And so we're keeping track of this and putting in those data points, right? Like, so I can just come in here. I can see the data points, the two roaster data points from roaster data points, the observations, the measurements that are being occurred, any off chain data, you know, and we're generating all of this logic. If I come over here and I look, I'm generating all this logic and as a business professional, I'm probably going to know that supply chain flow better than any developer that I talked to. So I have the ability to structure what I want and hand off to my developer, not just a, just a set of functional requirements, but I'm actually giving them a proof of concept that is REST based endpoints that they can hit and look at the data points that I'm looking for. And, and so, I mean, this is incredibly powerful, you know, I mean, even though, you know, it seems pretty simple, you know, you're giving that business professional the ability to unlock their intentions and, and, and provide the handoff to the technical team that defines those intentions much more granularly than ever before. And so with that, we now have the ability to just generate a REST based API on top of it, because here's the thing. I don't want to just hand that off to the developer and now the developers got to look through this, this code and figure out what's going on. I want the user to play with it. I want them to go through that Einstein. I keep picking on Einstein, man. I wanted to go, go through Edison. There we go. I want them to go through that Edison workflow and see if this works or not. If it doesn't, then let's know really, really fast. Let's, let's fail fast. We've heard that, hear that a lot, but let's figure out what works and what doesn't. And if it doesn't work, then we'll just try a different iteration, try different data points in order to collect what we need from a business professional. Once we figure that out, then we're ready to go talk to the tech team, but let's not, let's not be so quick to move to hardcore development until we have a relatively good idea of what our intentions are. Right. And that's what we're trying to do here.  And then we're going to just do this on burrow. And what about the off chain data? Because remember we said we're going to have those rollups that we're going to be optimistic about, put that data on chain. Well, if that's going to be off chain traditionally with this tool, we just put it on IPFS. And if we decide to use our full tool set, we can put it in any blob store, right? It can be an Azure, it can be an S3, because remember it's just that s, it's just that house of the inputs, right? Whatever the data point is, that binary large object input, we just run it through a hash, put the digest on chain. That's it. And so as long as you have a URI to that, to that data, data set, you can, you can access it, right? And that's what we get with IPFS. So anyway, that's all we're doing here. And then we have our smart contracts. So we say, okay, well, what logic do you want to do? Do you want to do the card? Do you want to do the coffee? What do you want to do? Well, we'll do the coffee. And okay, cool. So what kind of API do you want to create? Well, I'm going to create Riley's API. So, and I bet you there's a rack. She does these demos all the time. So I'm not going to do a Riley. We'll do a Tommy, Tommy. We'll do a bunch of funny numbers after it. So, Tommy, bunch of funny numbers after it. There we go. So, um, so that makes our unique endpoint created out here at this secure endpoint inside of Simba that is exposing your smart contract logic. Okay. That's it. We got to go ahead and sign it with, we'll sign it with John's wallet. John can deploy this out on fabric. It's going to post it, deploy it, finish it up. And that's it. It's out there. Now here. You'll notice. What we have now is it's out here on hyper ledger burrow. It's got IPFS is my off chain data. If I look at my app info. It shows, you know, all this raw information. And then if I want to manage somebody's ability to hit those endpoints, I can come in here and generate API keys. So, you know, um, if there's a data provider, um, Dave data. So Dave's the data provider. Uh, and, uh, and so then we also maybe we have another consumer. Uh, so, uh, Connie, the consumer. Uh, and so now we got Dave and Connie in here. And so we could just then somehow securely give Connie and Dave their API keys. Then when Dave needs to access the app. He just puts that in his host header. Okay. Well, Dave doesn't have do that. Well, okay. That's okay. No big deal. Um, if he didn't know how to do that in his host header, then he can just come in here and look and play with our swagger tool and it'll show them. It's pretty simple. We just come in here and it's, if you've ever used a simple API tool, it's swagger, but we just say, okay, well, here's, here's Dave's key. Just come in here, put it in here. And then we can just give him a little lesson on how to do post setters and gatters on all those, those methods that we've exposed. Right. So, you know, if you just do a, a getter on a batch code, there's not anything in there right now, but the cool thing about this is when we use this tool, of course it's going to go ahead and format all of our curl requests. So whenever we have a form or, um, you know, something in our form that's going to be requesting data from the blockchain, it's going to have to send this curl request out to this endpoint and retrieve the data. Well, this is doing it for us. It's just generating that curl request for us. And then we can just integrate this with our components or anything else that we want to do. So, you know, this is what we're going to do right now. Um, So we try to give us the, you know, the front end tools for developing kind of that front end structure and integrating it with your existing infrastructure.  So he, he doesn't know how to do that yet. So what else do we get? Well, we also give him a simple method call, right? So, you know, we know that the smart contract. Uh, has been exposed, you know, and it's got exposed for setters and gatters. So here's just all the setters for all those methods that we created in the logic. And then I can just come in, put in my data points and then call it. And then I can, then I'll see the, you know, all the, the raw logic over here. So I see, you know, the, the transaction blooms, the, the receipts and all that kind of fun stuff. The important thing to remember though, is that is that what we're trying to do is we're trying to give. The ability to use this tool, API rest-based API tool, easy to use the ability to interact with components, simple setters and gatters, most friend and developers know how to do that. And so, you know, if you got a people soft, let's just pick on people soft for a minute. And I need to report all the supply chain logistics information, um, uh, from my, from my, um, SCM product for my, so my supply chain management product. Uh, and I need to report all of that for this particular business unit that happens to be this clinic that I think I have some nefarious actors over there. I can start to track that better and put it on a blockchain, right? So those nefarious actors can't change the data. If it does, it'll, it'll show up and I can start to, start to do things and build infrastructures around this. And so, so you can, you know, if you already have the infrastructure like SAP or people soft or something like that, and you just need to have a REST based endpoint to do a setter and a getter against, then this is a pretty cool tool to start structuring that up. Right. So, especially when you start thinking about the enterprise capabilities of hyper ledger and then, you know, the ability for this to generate those REST based APIs and do quick iterations of, of tools building. I think the combination of those three things, um, you can probably do a lot of, a lot of help for an enterprise and helping them find out what data points that they have internally about their customers that customers might want to have ownership of and provide value and even utility for our system. So when we start thinking about rewards points and we start thinking about, um, democratizing capital product, uh, uh, purchases, um, you know, those are two easy areas of, of focus, you know, so let's just kind of talk about that. Um, you know, capital purchases, you know, when we start to think about CAPEX versus OPEX, one of the reasons that we don't make these, you know, purchase of the big car or whatever is because, uh, because it's too much of a, of an expense for that object. Right. Well, I'll give a great, a great story and we'll open it up for questions. Um, first time I ever rented a bicycle. I rented a bicycle in Okinawa, Japan, and I was in the Marine Corps and, um, I was 1992. And I had a secret clearance and I gave Hawk, the guy that owned the, the bicycle replace, uh, my father's address, my address, my social security number, my unit, my MOS, uh, all the information that he felt comfortable that he needed in order to rent me a United States Marine bicycle in Okinawa, Japan. He was a Japanese national. I probably violated national security because I gave him more information than he needed with smart contracts, data minimization, data blinding mechanisms. And we're all probably familiar with that. We can start to define mechanisms, you know, one way door mechanisms and all these kinds of things that we can do with cryptography that I can do that same interaction and mitigate his risk as well as mine. By the time I left Japan, I could go into Hawk's building and take any bike I wanted. He'd say, pay me when you get back. I didn't have to show him anything because it was all about building trust. What do blockchains do? They mitigate trust, right? What is a big barrier for business transactions is trust and blockchains help us to do that. I'll give you a great example. We've all seen the Lime Scooters setting around the cities. Well, that Lime Scooter does the same thing that Hawk did for me. It provides transportation to anybody that wants to use it. And all I have to do is provide my information to their smart contract through their application and mitigate the risk. If I own that data and I could do that in a blinded way, I could create a decentralized platform that would allow me to get that same resource, mitigate their risk, and also mine. And I don't have all of those pain points. I don't have Hawk keeping my personal information in his file folder that somebody could break in and steal it. Not that he was a bad actor, but I don't necessarily trust his security, right? So when we start thinking about data and we start thinking about how to protect data, it's going to be new ways. And blockchains are just a tool. And they're a tool to get there. So I'm going to open that up for questions. And hopefully you guys enjoyed the lecture and hopefully you enjoyed my demo and leave it to you guys. Yeah, no, that was a great demo. Tommy and we have some questions coming through. One of the things I'm going to ask you about first, before we jump in the questions is you have this great easy to use tool. And you talked about your outreach to the educational community. Is there any way for the attendees on the call here to get access to that tool just in a demo mode so they can go ahead and learn about Simba chain and try that out. Absolutely. 100%. And as a matter of fact, I will put the link in the chat window for you. This is at Simba chain.com. And you can actually use this tool for free. The only limit is that we'll limit to you to the number of transactions and the number of smart contracts that you can create. You'll need to get one of our subscription models. If you want to get something a little more enterprise related, but if you just want to get started and just start mocking some stuff up, you can certainly use our free version. And if you do decide you want to maybe put this into your curriculum and start to educate. We even have high school students that were able to build solutions out of this. And we have some pretty cool stories on our, on our website where some high school students were able to leverage this technology and build some really cool stuff with NFTs and things like that. So, so anyway. But yeah, you can certainly get started with that link in the chat window. And Riley will certainly help you with the, with any questions that you might have as far as sales and stuff. Yeah. Yeah, go ahead. Riley, jump on in. I was just going to say also put in a link to a tutorial we have where you can, it walks you through how to set up a free account and build an application. Perfect. Yeah. And I know that, you know, Simon chain really has a nice interface and easy to use. And it's a good introduction demo for people who just want to see how the platform works. So one question we had in here, Tommy was. Yeah. So one of the things that I wanted to ask is. Louisa asked about giving an asset to a new wallet. I know you went through some of the transactional stuff, but maybe you can just kind of address her question around this. And Louisa, if you want to ask her question directly, feel free to come off mute. Yeah, I think I understand the question. We, from our wallet interface, it's, it's generally just web three standard. So if you wanted to attach a wallet interface for the front side of the wallet, if you wanted to attach that in our set tool, we don't have that in this quick start. So the quick start is just a web three hot wallet. It doesn't really have ownership mechanisms and transfer mechanisms, other than just the keys and having ownership of the keys. Right. But there's no built in wallet functionality with this tool, other than just key management. That's it. So if you were to build an application that was going to transfer assets, then you could import the asset into the, the, you know, the import, the very first smart contract, and then you could have a second smart contract that would be responsible for that transfer. And so you could just, like I said, build it in that sandwich model. As long as you define who the, who what all the state changes needed to be for the transfer of the asset. So that's it. Hopefully that makes sense. Yeah, that's great. The other question we have is from Mike. He wants to know, you know, if they're in 2.0 is moving to proof of stake. And I know we talked a lot about hyper ledger borough today, but is that going to have any effect on your service offerings going forward? Yeah, you know, we're, we're keeping a close eye on, on really the EVM. That's what we watch closely. And when the EVM has standards that change, we can form to that. With the consensus mechanism. That really is just how do we come to that conclusion mechanism? So, you know, when I, when I usually compare proof of stake versus proof of work, you know, proof of work is like everybody's playing bingo proof of stake is everybody is trying to build a road together. You know, proof of stake is we're trying to see who can, who's the best and who can win the, who can win the random game of chance. And proof of work is let's trust that everybody's going to work in a combined effort, but verify that there's no bad actors by looking at everybody else's work. And so I kind of call that the trust, but verify or maybe the Ronald Reagan model, but it doesn't really change the mechanisms. When I, when I said earlier, it doesn't really change the way the EVM works. So as long as we still kind of look at the EVM and the logic of the EVM, we should be fine. It's an abstract at a different level. So when they change the consensus mechanism, it just means that we're going to have to change state quicker. No big deal. We can do that. So I think it'll be fine. Yeah. Okay, perfect. Another question we have is from Alex.  He's got two million records a month. So he wants to know how that will process through Simba chain. If he wants to run it on Simba chain. And Alex, feel free to come off mute if you want to add to that question. Yeah, yeah. So that's a pretty cool question because, because I'll just answer that as more of a cloud architect. And not necessarily a blockchain architect. So what I would do is if you're, if you're processing those transactions, that would be internal. I would be, I would do that. And that would be in my optimistic rollup. And really I would just look at velocity and how I would need to handle the velocity of those transactions. So I would do that with things like, you know, as an AWS guy, I would be used like DynamoDB and those types of things to, to track state. But then, you know, once we have that signature of that state and we want to report it, whatever, whatever that interval needs to be and whatever those data points need to be, that's what you're going to be reporting through your smart contract. So, so since you have one actor, that one actor is only reporting the, that state information based on the velocity that they need to have that recording. And so I would really probably want to look more at the transaction model and what's being recorded, what the velocity is of it, you know, because like, like for instance, when we do things for like race cars, I mean, like, Holy cow, I got to record all these things like right now. And it's like 10,000 data points that are coming in in two seconds. Or if I'm, you know, recording information about, you know, a dam and the velocity of water and the quality of water that's going through that dam, that's a little bit different data point is a little bit different velocity, right. So again, it really, I would silo it down into wherever your data stores are. And then look at the data points that need to be reported and then figure out what the velocity of those need to be. And I would guess that's probably not at that same level of two million per second or whatever you have. Yeah. Okay. And then the Vika has a question about, I know you guys have had a lot of success in the military. I want to talk a little bit about what successes you've had in the healthcare space. I wish we had more. But I will say that I've had some success in some training. We personally at Simba chain, we've worked on a few initiatives, but we don't have anything publicly available from a healthcare sense standpoint, but I will say that if you go to the blockchain training alliance, which is one of the leaders in providing blockchain certifications, they have a three day course on blockchain healthcare and I authored that course. So I identified various different areas within healthcare, things like owning your own medical data, things like tracking and tracing the actual health, health equipment, which is under what's called CFR part 11. I look at HIPAA and GDPR regulations and how we can conform to those regulations and still have the right to be forgotten and still maintain some of that data on a blockchain. So we look at a lot of standards within healthcare. There is a plethora of pain points. I'm of the opinion that at some point in your life, there will be a piece of data that will be more important than any other data that you have. And that's your healthcare data. And the fact that you don't have full visibility into all of that information and have a full portfolio of that data and readily available for you to manage. I think that's a travesty. And I hope that we can fix that problem. And I really feel like that there's a lot of opportunities there. So if you have some ideas, we are certainly open to have those discussions with you. And we'd love to talk to you about it. Perfect. And then James has a great question here for you. He's talking about different data cadences and they all need to fit in the same ledger. And James, if you want to come off mute and ask your question, that'd be great. So basically, I think he's looking at James. Yeah. So, um, when I did work with the state of Colorado underneath for the blockchain work, we realized the telecom infrastructure. So the white quote, quote, global wifi is not as strong as it needs to be. And actually I've even seen this in oil and gas. So we know that there's variable data cadences and they still have to either fit retroactively or sequentially into the chain. How do you rectify that problem? That's probably a little bit outside the scope of my, of my capabilities. Honestly, I'm not a, I'm not a wifi guy. Um, but it sounds like basically what it sounds like is just having bit creep basically in, in, in your inputs. Um, is that accurate? I don't know. I'm one of the sales people. Uh, I come from a technical and sales standpoint. But when you're, when you're looking at it, I mean, you look at what IBM and what they've done, when they've taken, it's almost, they almost did an RFID when they moved a yogurt throughout Turkey, like Turkey to Egypt or something like that. So I mean, you're going to, you're going to be in places where you're not getting connection.  But even, and you may record it, but then you have to do it retroactively because when you're looking at the hyper ledger, the sequential, the sequential nature and the date and the time post, when it comes down to the data mark is incredibly important. Yeah. So it's not going to be a good example of one that we kind of work with, with this. Um, there's a, there's a thing called beef chain. It's in Wyoming. Um, and so basically. Yeah. Yeah. Yeah. So, you know, Tyler. Yeah. So anyway, they're no longer, they're no longer really around, are they? They're kind of struggling. Uh, I talked to Tyler about it last, what we were there, what a month ago with Riley, uh, in Wyoming. Yeah. Yeah. It seems like, I mean, they're, uh, they're, they're doing different things and they're making, they're, I think they're probably making more of an ADA, uh, or Cardano approach with it. But yeah. Um, but anyway, the point is is that they're doing the same similar concept. They're, they were collecting through the IRD device that was in the cow, right? They would collect the identity and then that identity would interface with the feed trough and, and then feed the cow basically, uh, whatever that identity should have, right? So they're, they're portions for that day. Um, and so what they've been able to do is, is if they have certain data points, like for instance, um, the collection of how many steps that, that cow has taken. Well, that can't be collected in that IRD device, right? That IRD device can only collect like the location that it is in, within that field. So it depends on the IOT and all. Yeah. I mean, if they have. Create a local bridge basically is what we have. Right. Right. So we just, we were basically doing a local collection bridge, which is going to be your proxy collection. And a lot of times we'll do that either in, like in this case, we'll do it in the, in, in, in the, in the barn or in the, you know, in the feature off area, it'll have that wifi, uh, collection point that's then collecting all that data from those individual IRD readers from each one of the cattle that are in the, in the field. Um, but, but then, uh, we don't manage the, um, you know, the individual devices, uh, in the field. We just manage them locally from that collection device, that proxy. And then from that proxy, you can use things like Laura Wan, right? So with Laura Wan, um, you can just report state, right? So if, if you don't have to report the entire dataset and you only have to report the hash, then you can just send the digest up as through Laura Wan. And it's a very small data packet. And so even though you're sending it through satellite and it doesn't necessarily have to be 5g, it can even be low, low bandwidth. There's a lot, there's a lot of 2g out there. Yeah. Yeah. I know the food industry. So. Yep. I, you're close. You're close. What you're saying? Yeah, I was trying. Yeah. You probably know better than I do. So I was trying to explain your own industry. Yeah. Because just like for an example, they're going to, there's other IoT devices that actually measure a cow's temperature. So like for an example, people don't buy, some people don't buy beef in the summertime, especially if you're looking at the rate planes, because of the temperature variances. And the reason I'm bringing up tear temperature variances.  And when you're looking at there's beef chain, which is trying to do certified cows versus general feed, feed yards where there's more money in it. When you're looking at those temperature variances, you want to get ahead of them quickly. And if there's even that lag, that could mean a difference between. Yeah. Yeah. Yeah. Incredible probability and losing everything too. Yeah. So yeah, I mean, that's kind of where it needs to be because you have to, sometimes I have to have that granular level quickly and be able to create a data mark throughout. And I think, you know, honestly, like a lot of that stuff could be, like I said, it could be optimistic, right? So we could pray, we could create those rules. And as long as that's just part of your, part of your governance, then you could just, you know, you could put that into like an AWS quick start or something. You know, that quick start could be what you would launch and buy the devices and then, you know, you have a smart farm or whatever. Okay. So what I want to tell you is we're coming up at the top of the hour here. Tommy, if you're okay taking a few more questions, I'd like to go ahead and extend beyond. But one question I want to ask. Yeah, I can probably take one more question, but I do have another appointment that starts in like, it starts at five after. So I got about a five minute break. Okay. I'm just going to jump right into. Chen has a question here that I think is highly relevant to everyone on the call. So he teaches a blockchain class at Purdue Northwest. Is it okay for him to have each student sign up for a free account and work through the tutorials as class assignments? That's his question. I'm going to punt to my co co worker who can probably address that better than I. So I appreciate your time today guys and have a great afternoon. Thank you so much, Tommy. Take care. Yeah, this is awesome. Yeah. Yeah. So to answer your question, Chen, you can definitely use the free version of our tool. However, it will limit the students on how many transactions they'll be able to make and how many applications they'll be able to make as well. So a lot of universities have been leaning towards our pro version. And usually for the education sector, we do have different discounts based on the needs of the university itself. And then also how many students are going to be using the tool. That's a great question though. Okay, everyone. Well, I really appreciate your time this morning and. Riley, did you post your email in the chat in case anyone has any follow up questions? Yes, I am going to right now. That would be perfect. After she up there. Rather already got it done. Okay. Thanks everyone for joining today. And I hope you have a wonderful rest of your day. And we look forward to having you join the next webinar that we host. Thanks. Thank you guys so much. Thank you, John. Yep. Have a great day. You as well. Bye.


Welcome to the Chavoygan County Historical Museum and our 2019 Holiday Memories exhibit, subtitled, Season's Greetings. We're so pleased to be able to offer every year, this step back in time, to the days of the H.C. Prangie Company and the decorated mechanical window displays of years past. Every year, visitors are greeted when they come down our main staircase to a scene that is right out of a window display. We've tried to recreate one of the large display windows that have been down at the Prangie's Company. This year, we feature Santa and Mrs. Claus having their photograph taken by an elf and in fact, our visitors can even help to take that photograph. We ask them to push the button, count to three, and there it goes. And it's so quick, it's like a Polaroid. This would be typical of a space that would have been seen at Prangie's during the 50s, 60s and into the 1970s with displays of various animation and occasionally an extra product that might be the hot toy of the season. This year, it's sock monkeys, getting into their typical mischief. Every year, the museum has a slightly different display. This setup is one that we now use in alternating years. It's the most recent set of animation that came here to the historical museum. Prangie started with window displays at the holidays, most likely shortly after they built their new building in 1923. The four-story building featured a number of really fantastic display opportunities in the front windows with at least 21 plate glass windows on both 8th Street and on Wisconsin. Over the years, they would slowly transition from having primarily Christmas merchandise to including bits and pieces of animation in their displays. The only time this took a break was during World War II, when energy conservation and additional materials went to the war effort as opposed to creating new displays. What we see here is a gift wrapping machine. The idea is that once the elves had made the different products for Santa, they would send it through this machine and it would be gift wrapped and ready to be placed under the tree. Of course, every once in a while, one of the elves got into a little mischief and tried to see if they too could be gift wrapped. Looks like that gift wrapping idea for an elf didn't work out so well and has jammed up the conveyor belt. Hopefully the elves can slide on over and fix it and get things working again. In Halloween World War II, H.C. Pringies continued the tradition of the animated mechanical window displays and in fact, in many ways, that became the primary attraction of their holiday windows. For the 50s, the 1950s and the 1960s, every year there was a new display, sometimes that had just been the year or two before, out on the east coast at the likes of Macy's or down in Chicago at Marshall Fields. These animated window displays would travel from store to store and often times after they appeared at the Pringies in Sheboygan, they might move on to the Green Bay, the Sturgeon Bay or the Appleton store to spread the holiday cheer. This tradition did continue through the 1970s even as additional attractions were added inside of the store, including Bruce the Spruce and an enchanted forest that visitors would walk through when they went to see Santa. Following the fire in the 1980s and the rebuilding of the Pringies store, the focus really became internal even though they continued to have small displays in street side windows. Interestingly enough, this setup came to the Yonkers store in 1996, following being purchased the HC Pringies in downtown became a Yonkers. The corporate headquarters had had this display for a couple of years in their flagship store in Des Moines, Iowa, but it wasn't the attraction they hoped it would be and store managers here advocated for it to come to Sheboygan because the tradition of the animation was strong in this area. It remained at the store until it closed in 2013. The museum began celebrating the tradition of the mechanical window displays of Pringies in 2001. Over the years we were able to acquire animation not only from the former store when it was under the Yonkers in Boston store ownership, but also from a private collector with support from many of the members of the historical society. We also are able to do this display every year thanks to the generous support of volunteers who have done everything from making all of the sock monkeys that we see this year as part of the display to helping with the mechanics and making sure things stay operating, decorating the Taylor House, decorating the main exhibit and helping to assemble the displays. Most of them are even kind enough to come back and help us tear them down, which is awesome. Every year the displays are slightly different. So they're up only for a limited time and they'll never look exactly the same again. This nativity is also original to the H.C. Prangie Company. From research we've uncovered that it appeared in 1939 and memories that have been shared with us indicate that every year right before Christmas the main window would be switched out to this display. The pieces are made out of plaster and several years ago underwent extensive restoration thanks to the support of Dan Merkel and his family. Many of them needed cleaning and several needed repairs, both structural and surface repairs to their paint, understandable after so many years of annual use. We love having it in this window because it harkens back to those days of standing out in front of the store, watching and seeing the displays. Of course the bonus here is that it's warm inside, it's not snowing or raining, and the wind isn't nipping at your nose. The display here at the museum is about more than just the animation, even though that's a key part. We're always excited to have additional decorations, particularly these community trees, that are done by various groups and organizations throughout the area. One of the trees this year was decorated by SCADA, the Sheboygan County Area Retired Teachers Association. Here you see that they've decorated their tree with all kinds of school supplies, which following the holiday memories season will be donated to area schools for use in their classrooms. Another tree was decorated by BSA Troops 6000 and 1. Their feature ornament is pine cones that have googly eyes and happy faces, harkening to their theme, making memories with nature. Interestingly enough, this is the first Scouts BSA troop of girls here in Sheboygan. The troop consists of 6th, 7th and 8th grade ladies, and they have had a fantastic first six months. This tree, decorated by Cub Scout Pack 3858, is celebrating making memories with the Pinewood Derby, an event that's been part of Cub Scouts since 1953. In addition to featuring Pinewood Derby badges and little cars, the tree also has on necker shift slides that members of the pack who are in 2nd, 3rd and 4th grade will wear come February when they race their Pinewood cars. Students in grades 9 through 12 from Central High School created the ornaments on this tree that we have on display. It celebrates the 12 days of Christmas, in addition to having some hand-designed geometric snowflakes. The students use 3D printing, laser cutting and AutoCAD to help create their ornaments, giving back to the community and having pride in this tree and the school. Students from Bethlehem Lutheran School used a common greeting to create their season's greetings tree. They used their hands, a popular way of expressing a hello, to create the various ornaments on this tree. Ornaments were made by students in 5K, 1st, 2nd and 4th grade. Here we have a tree that's been decorated by students at St. John the Baptist Catholic School. Children in 3rd graders created many of the old-fashioned ornaments hanging on the tree. It also features some beeswax ornaments made by Margie Seifert, who volunteers here pretty regularly at the museum and also is the great-grandmother of one of the school's 3rd graders. We see things from ornaments with music notes to trees made out of hand-tied strips of fabric. And mittens, highly decorated. Members of Sheboygan County's Wise Wizards 4-H group created a season's greetings tree with the theme, Go More Green. The club decided to have a green tree and utilized recycled media to create ornaments, popcorn strands and also was able to reuse ornaments from previous years when they've had a tree here on display at the museum. They also painted the inside of a clear ornament to create a new display as well. This tree, decorated by 3rd graders at Usberg Christian School, celebrates Christmas around the world with a variety of greetings in other languages. The 3rd graders help decorate these ornaments with their grandparents on Grandparents Day during school. During the holiday season, the museum also decorates the Taylor House and the log cabin to go along with the theme. This year we've carried the season's greetings theme right on through and in the Taylor House all the decorations center around Christmas greetings and holiday cards that are sent for the last 50 years. In fact, most of these cards have been donated to the Historical Museum specifically for the purposes of this exhibit and a large number of them were given to us by Henry and Eleanor Young who had been keeping their greetings for a number of years. Each different area will have a different set of greeting cards to remind us of all the various ways that we wish each other well during the holidays. These buildings wouldn't be possible without the help of our volunteers and particularly here in the Taylor House. We're grateful to members of the Ivy League Garden Club and Lakeshore Garden Club. It is their efforts that make sure that this home is beautifully decorated year after year. They are amazing when they come in and can put up these decorations in a few short hours. Hey everybody, it's your favorite tree, Bruce the Spruce. We are hoping to see all of you here at the museum in 2019 for our season's greeting holiday memory event. Please come in and say hi to me. I got some special jokes for you. You can see all our elves working hard in their workshop and you can visit with our pal Santa Claus up until Christmas Eve. Hope to see you all this holiday season. Have fun and see you soon.


How's Waddle been? They've used him at kick and punt, but mostly kick and have they kind of alternated guys at punt return and how's he been as far as a returner? Yeah, you know, I think he's trying to find his way a little bit. He's obviously a dynamic player, whether on special teams or on offense. And I just remember, you know, watching over him in college and him being dynamic with his hands in the ball.  So we've got to do a great job against him. On Sunday, I wondered, do you tell guys to sort of, you know, err on the side of caution in those kind of situations when it comes to return and punt or kick in terms of fair catches? No, you know, we still want our guys to be aggressive, but, you know, they got to understand the situation that they're in. And we'll obviously practice for the worst case scenario with weather, whether it's a wet ball drill here today and yesterday. So we'll get them prepared for it. And if it happens to be bad weather, our guys, you know, it won't be a big deal for them. But if they do have great weather, great. If not, we still want to stay aggressive as much as we possibly can. There's a missed kick. How much do you try to talk to Randy and kind of find out what's happening in game and that sort of thing? Or do you kind of leave that to him to know what he did wrong and to correct it himself? Yeah, I think the biggest thing for me is I let him gather his thoughts. I'm not one of those coaches that are going to go up to him right away and be like, well, what just happened? What did you do wrong and things like that? One, they probably don't want to talk to me anyways because they're upset. But, you know, I kind of let them go and then James will come over there and talk to him. And then if I need to go over there and say something to him, most of my coaching is when I go over there is telling him like, listen, we've got to move on to the next kick. That's done and over with. What do we need to do to make corrections for you to make this next kick? But we got to forget about it and go on. That's my big coaching point. We can't dwell on missed kicks. We got to just move on to the next one. What have they done at Pup Return of Lake? Has Holland been doing a lot of their, have they alternated those guys or have they kind of gone to Holland? Yeah, well, even last week they had another guy, Tommy Lee Lewis, I believe, who went back there and did some things for them. And then Holland came in, I believe, like the last six. But it has been Holland been back there and going over film from him when he was at Oregon. Dynamic Returner did a great job. You know, last week it was more fair catches for him, but he's another guy if he gets his hands on the ball, we'll be able to get upfield, make some guys miss. So, you know, we're going to prepare for three guys back there.  You see guys like David Long, Monty Rice, they always talk about how special teams help translate to them being a part of the defense. How do you approach that? Do you kind of like coach them to be able to carry over to having a bigger impact on defense? For sure. I think when we first get him, obviously Coach Rable does a great job. You know, he dealt with that when he was a player, where he played on special teams at the beginning of his career. And then when he obviously moved on to New England, had a bigger role on defense. So it's great to have Mike being able there to tell them about his experience. But we tell him right away when there are rookies that you got to play on special teams. And the more you do on special teams, the more you get noticed, the more you'll get noticed defensively and things like that. Because I tell the guys all the time, I want you to start on defense too, trust me. Like, that would be great for our team. But for right now, we got to focus in on special teams and doing your job and do it the best that you possibly can. And if you do have that opportunity to play on defense, you take advantage of it. So we just try to tell them it's going to help them out in the long run with special teams. But it will also help the defensive coaches notice them too when they make plays in space. What's happening again for your group for the most part this year? Yeah, I would say good. Not great. Because I still think we're leaving plays out there in space. I think that's one of our big things to do these past couple of weeks is make plays in space. So we're really trying to work on our gunners especially, kind of coming to balance a little bit, not hopping, not falling off the diving board, just getting big and trying to make those tackles in space. So we can always improve on tackling each and every single week.


Yesterday, I went through this amazing experience with you. It was a collective experience. And then I saw your relationship with the meditators who were the volunteers in this incredible course that we did. And there was something that connected you. Now, I've heard stories about this. I've heard that as Jesus walked in, he spread this love and we always wondered, how could you just spread love? I saw that yesterday. But I saw tears in their eyes. We could explain that. But I saw tears in your eyes because I saw a two-way relationship. So let's just keep with this idea of a Guru and tell me, what is this two-way? Because I saw you, like a devotee. You were like them. When you went to them, it was not just their emotion, it was yours. See, here you are using the word devotee. I don't know whether they're devoted or not. My life is devoted to them. That's for sure. My whole life is devoted to every human being on this planet, every creature on this planet. So devotion is just a deeper love affair. When I say a deeper love affair, generally these days, at least people are understanding a love affair is some kind of a transaction of give and take. Devotion is a deeper love affair of just absolutely giving. Whether take is there or not just doesn't matter and it doesn't occur in your mind. So for me, my love affair is just with everything that I set my eyes upon. Whether it's a man, woman, child, animate, inanimate, it doesn't matter. Whatever I set my eyes upon, I'm in a deep embrace with that. So for me to come to tears, I don't even have to look at a human being. If I look at a cloud, I'll come to tears. If I look at a tree, I come to tears. For close my eyes, I'll come to tears. So tears is not even about love. If you tell me I'm in love with people, I wouldn't feel that's a great thing. I feel you're lowering the whole thing. I'm not in love because love is still a kind of a transaction. This is a certain dimension of inclusiveness. Actually in my experience, there is nobody else in this planet, nobody else in this existence. It's just me. In my experience, I don't see myself and somebody else, I just see myself. So this is not even devotion, this is not even love. This is just inclusiveness. And this is not my idea, this is not my philosophy. This is the way existence is.  If you, your own species for that matter, if you do not constipate your consciousness with that kind of limitations, the existence is all inclusive. Well, science can prove it to you today, isn't it? The more people see you, even from a distance, there's a sudden outboring of love, complete outboring of love. So let's talk about love. This is one kind of a love. Is a, what happens? Is there something, is it a release? That could be one thing with the CU and their own stresses and emotional release. On the other hand, is there some kind of energy that you're transmitting to them? Is that energy possible only in a loving relationship? Even between you and the people or between people themselves, what is that energy called love? And then let's relate it to man and woman because that's a love most of us know. Love or hate, whichever you like it, but let's talk about love. There is no such thing as an energy that is love. Life is a certain energy.  The many parts of this life energy is finding expression as thought, as body, physical action, emotion, and there are other dimensions of course, energy action. If you can perform only physical activity in your life, the span and the scope of that activity is very limited.  If you make a movie, if it all physical, it's one way. There is a certain intellect involved in it, it's another way. There's a certain emotion involved in it, it's another way, isn't it so? So that's so with life also. So these are different levels of intensity. Physical is at one level of intensity. Intellectual is another level of intensity. Emotion is a different level of intensity. Generally people are looking down upon emotion as something less than intellect, which is a very wrong thing they're doing, which I think slowly people are realizing they're talking about emotional intelligence now. Because emotion is capable of being of a higher intensity than intellect in many ways. Intellect has a certain coolness, intellect has a certain penetration, but emotion can just embrace everything. Intellect can know pieces of life, emotion can know the wholeness of life.  But what a devotee knows in terms of life's experience and what he knows in terms of perception of life, in its totality, an intellectual person will never touch that.  So right now what's happening here when people are around me is neither intellect nor emotion nor body. It's another dimension which is just pure reverberation of energy. If I reverberate in a certain way, some people will roll their eyeballs upward and simply sit there. Some people will cry, some people will laugh, some people feel that they realize so many things being there in that space. This is their expression of it. This is like if I give you electric connection, somebody makes light out of it, somebody makes sound out of it, somebody makes coolness out of it, somebody makes heat out of it. Different gadgets are making different things out of the same electricity. So my thing is just to exude that energy. Somebody makes love out of it, somebody makes alertness out of it, somebody makes awareness out of it, somebody makes meditativeness out of it. That's left to that individual depending upon his level of evolution and his receptivity as to how he is. So am I creating a love energy? There's no such thing as love energy. There's just life energy. There is only life energy. Love is just one expression of life. Intellect is another expression of life. Physical action another expression of life. Awareness another expression of life. So life can find million forms of expression but people energizing one over the other is a huge mistake. All of them are needed. Love without the needed awareness and balance is going to be horribly burdensome. So what you're referring to as love is basic... basically the sweetness of your emotion. You sit here and you could feel about love. You could feel love about somebody who is not even here. So it's got nothing to do with anybody. Once a human being becomes more and more aware of his own nature, he understands to experience love, to experience blissfulness, to experience ecstasy, even to experience orgasmic ways of life, you don't need anybody actually.    Most people still believe that their experiences are being shaped by people and situations around them but that's not true. Human experiences are 100% self-created, 100%.