you today, some of the work we are doing at CSIRO around blockchain, also self-sovereign identities and verifiable credentialing. So I believe these kind of topics are very relevant to this audience. And I will start with a quick overview of what data 61 is CSIRO and the kind of research and innovation that we do on blockchain. So CSIRO is the Commonwealth Scientific and Industrial Research Organization. It's Australia's largest scientific research agency. And CSIRO data 61 is the data and digital business unit or kind of specialist arm of the agency focusing on computer science data-oriented research. So we are home to 1,100 people, more than a third of which are research students, PhD and master. And our core business is obviously research and it is specifically research in digital science and innovation and leading to new research as well as working across disciplines and sectors to apply technologies and drive impact. So that's the main goal. And the expertise that we have within data 61 includes AI, robotics, cybersecurity, and data analytics and modeling, etc. So there are a large number of teams involved in all aspects of these kind of topics. We also have extensive interactions and collaborations with universities and partners. So over 38 university partners and 31 government partners including all sorts of government agencies and 91 corporate partners as well. So we get involved in industry projects as well. We also host a few facilities that are cutting edge facilities including the mixed reality lab, the robotics innovation center and the AI for cyber enclave. So you can actually learn more about these. There are a few videos online on the website, on data 61 website that you can learn about these centers. And regarding blockchain, we have a dedicated team and part of this dedicated team at data 61 that consists of seven research scientists, three software engineers and a number of PhD students and master students. And we have we have also closed relationship with many universities, leading universities in Australia with which we collaborate on our research. So for example, we work with Sydney University on the Red Belly blockchain, if you are familiar with that. Also with Monash University on blockchain in the energy sector. Swinburne University has also a blockchain center with five research scientists and engineers. And we have a close relationship with them as well. And many more interactions with other Australian universities. We do projects with government and also different industries, most of which we cannot really mention publicly, especially for industry projects. But for the blockchain topic, our priority domains include fintech, energy and supply chain in agriculture, food, transportation and logistics. And I will show you an example later on, especially in the agriculture domain. For fintech, we have done projects with pretty much all the big four banks and also lots of government agencies, like the Australian Financial Security Authority, the ASIC Australian Securities and Investments Commission and the Australian Taxation Office. So around blockchain as well. So the approach we have for our work on blockchain R&D has four main components. And we try to balance our work across all these four. The first component is the core research activity, which has a focus on design principles around blockchain systems, their trustworthiness, the use of smart contracts and also a number of architectural considerations of blockchain platforms. I'll cover more details in the coming few slides. The second component basically fulfills our role in government and education. You may not know this, but CSIRO started back in 1916, so more than 100 years ago. And it was actually called the Advisory Council of Science and Industry. So that advisory role continues today. And we often contribute to government agencies in a variety of ways. We also contribute to education by publishing, obviously, research papers and also textbooks and training the blockchain workforce of tomorrow through our PhD programs as well. The third component is our involvement with the community of experts around the world. Our team is actively involved in a number of standardization efforts and also international technical committees, particularly around standards involving blockchain, obviously. And last but not least, we conduct projects and create innovative solutions to complex problems. And we do that through the application of original concepts and unconventional approaches to solving these kind of problems. This can take a form of patterns and tools that we publish or release. And we deploy these tools in large projects with either government agencies as well as industry partners. All right, so I'll go through these four components one by one and try to give you a few examples of what we do. So for our contribution in terms of assisting or providing assistance to the government agencies around blockchain, these are a few examples of what our team contributed in terms of principles and guidance for the adoption of blockchain technology. These are three reports that are available on the Data61 website. So I'll encourage you to have a look. The first report is on distributed ledgers and it explores these scenarios for the Australian economy over the coming decades. It helps understand what might plausibly happen across society and economy. So it's kind of an introduction to what can we do with distributed ledgers. And that's very helpful for government agencies as well as the industry in general. The second report is on the risks and opportunities for systems using blockchain and smart contracts. So this is a bit more technical from the title, you can guess that. And it focuses on the technical risks and opportunities. So it's very much useful for system architects to read these kind of reports. The last one is another report titled Blockchain 2030, a look at the future of blockchain in Australia. And this report explores what is the industry profile, skills, trends and future scenarios in Australia around blockchain adoption. So yeah, I'll encourage you to have a look. These are really good reads over the weekend. So next I'll give you a quick overview of what we do in terms of a contribution to education. So we do that by publishing textbooks, delivering courses and supervising students. So one textbook worth mentioning is the architecture for blockchain applications that provides a fantastic introduction to blockchain, how to design blockchain systems, the blockchain design patterns that I will talk about later on to achieve cost, performance, defendability, security, etc. And it also includes some industry case studies. We also have a course that is delivered at UNSW that builds actually on the textbook itself. So yeah, obviously we have a textbook, it's good to use it for delivering a course on blockchain. So as I said earlier, we are actively involved with the community of experts around the world on blockchain. So this includes taking roles such as program committee share or guest editors of some of the major international conferences and journals on blockchain. Our team is also involved as chair in the Australian Technical Committee for Blockchain Standards and we have been leading the Australian delegation of the ISO TC307 Blockchain Standards. So we try to always contribute to these kind of collaborative work on standardizing blockchain. So the research that we do at CSRO Data61 on blockchain, they cover a variety of aspects of blockchain. So including performance, scalability, the energy consumption, obviously, and data privacy, data transparency, all the kind of topics that are very critical for the success of a blockchain adoption. So pretty much what we try to achieve is find new ways to actually improve the way blockchain networks and blockchain system work. And I'll show you a few of the innovations that we have done to achieve that goal. So these are a few things that I wanted to share in these slides that are research output. The first one I want to talk about, and it's very well explained in the textbook that I showed earlier, is about blockchain patterns. And the goal is to systematically capture and organize knowledge on how to design blockchain-based applications. And these are in the form of a set of design patterns. So a design pattern is pretty much a reusable solution to problems that are commonly occurring within a given context. And when you are designing a software, this approach of relying on these design patterns considers the blockchain as part of a bigger information system, where patterns could assist to build a robust design of a large blockchain-based system. So some of the patterns are explicitly identified based on real-world blockchain-based applications that leverage blockchain's unique properties. Other design patterns are variants of existing design patterns applied in the context of blockchain-based applications and smart contracts. So these patterns can be helpful to software architects, developers, system administrators, and technical leads who need to design and develop and also monitor blockchain and distributed ledger-based projects. So we also include in this set of patterns some of the decision models that help developers and architects select the appropriate patterns for blockchain-based applications. So most of the presented patterns and decision models should be applicable in concrete use cases regardless of the blockchain framework and smart contract language that you use. So it's in the pretty much blockchain platform independent. All right, so a few other examples of research output that I will glimpse through very quickly. So we also investigate approaches to simulate large and complex blockchain networks. So as you know, it is expensive to run experiments on the blockchain and it's difficult to reproduce some types of attacks or exceptions that can happen within a highly concurrent system. So that's when simulations play a major role in the research that we conduct. So an example of this is research on security analysis, so blockchain security analysis. And the main objective is to identify all sorts of attacks, in particular, parasite attacks, double spending attacks, hybrid attacks, and this is only made possible using these kind of simulations. This is a kind of a list of publication records that we have in the team. So you can refer to our website to kind of get through this literature and enjoy reading it. Okay, so I got to the juicy stuff now. It's the kind of innovations that we have come up with. And I took just four examples. Actually, I would dive deeper into three examples. I'll start with F-Viewer. It's a real-time Ethereum monitor of visualization tool. Then I will talk about Loricit. It's a model-driven engineering tool that basically generates solidity code, generates smart contracts based on a business process that we define using a business process modeling language or modeling notation. And then I will talk about Macrokey. It's a self-surveying identity mobile app for Android and iOS that can, obviously, it's a self-surveying identity app and also able to interact with Hyperledge Fabric to interact with smart contracts, basically. And then iCertificate. I probably will never have enough time to dig into all four, but iCertificate is a smart blockchain-based certificate system. So it's very useful to create certificates for all sorts of purposes on the blockchain. Let's start with F-Viewer. So what F-Viewer is, it's basically a visualization tool that visualizes the recent history of the public Ethereum blockchain. It shows 24 of the most recent blocks on the blockchain. Maybe I will switch to a live view of F-Viewer. This way you can see how it looks like. So this is live in animation. So it shows 24 of the most recent blocks of the blockchain, so represented as the boxes here. And the current transaction pool represented in the form of circles. This is the pool of transactions that are currently in the pool. And all the observations are collected by a single full node, full blockchain node that we use as an observer. So first let's talk about the chain of blocks. The most recent block is on the top left, obviously. And the circles in the blocks inside the blocks here are included, basically are the transactions included in those blocks. Blocks that become uncles or folks are shown in red, which is not the case at the moment. And blocks in the main chain are green. So what we are looking at is all the blocks in the main chain. Regular links here between the blocks are green lines. And if there is a forks, if there are blocks that are uncle blocks, their links are red. So in each block, we also display the block number in the first line. And also the miner who created that block. The fuel gauge here, it's very small, so it's difficult to see, but each block has a fuel gauge. You can see that it can be empty or full or halfway through. That's basically, it shows how much gas was used by the transactions in that block relative to the block gas limit. The transaction pool that you have here shows all the transactions currently waiting to be included into a block. And when a new block is created, typically a number of transactions from the pool are added to it. So if you wait long enough, you'll see a new block showing up and a bunch of transactions going into the block. So yeah, a few additional information about this. The visualization is obviously not possible to accommodate the entire existing pool of transactions. It's too big. So what we see here is only the last 500 transactions, depending on your internet connection when you load this at fviewer.live. If you have a very poor internet connection, it will only show 50, but it can go up to 500. More than that would be kind of insane visualization. And basically, it's showing the most recent transactions. The ether value that you see here on the bottom left is the sum of the ether values of all transactions in the pool, not just the ones shown. So we show only 500, but it's a lot more than that. And then you have an extended view here that basically it groups the transactions in the pool based on the offered gas price. So you have the different gas prices here. They form different groups related to the transaction fee. So yeah, that's pretty much how it looks like. And that's a very useful tool for teaching blockchain as well as explaining to non-technical people what blockchain is, trying to visualize it. It's always difficult to explain what blockchain is to anyone. So it's very useful to have these kind of visualization tools to help assist with that. The other tool that I wanted to talk about is Loricit. So this is a model-driven engineering tool for blockchain-based business process execution and asset management. It's a mouthful, but simply put, it enables engineers and domain experts to focus on the business processes rather than writing solidity code and writing smart contracts. So typically, when you talk about smart contract, the number one person that is supposed to define that contract is a business person. So they are not familiar with coding or smart contracts. So it's very difficult. So that's the main objective of this tool. And what it does, given a business process, you can actually model the process using this notation. So it has a modeling tool built in. And the notation is called BPMN, business process model and notation. It's fairly standard in business process management in general. So most business people would be familiar with this kind of notation. So it's like a workflow where you define the different steps and the conditions on when things can be done and not done, et cetera. So pretty much what Loricit does is to automatically generate a smart contract to manage the business process on the blockchain. So what the user is able to achieve with this is to generate on the fly the smart contract of the model of the business process that they are building. It's very useful because you can actually tweak the business process and generate a new version of that smart contract. So Loricit supports fungible and non-fungible asset registries, escrow for conditional payments and asset swap, and Loricit's solidity and go-lang smart contracts are formally verified and they are well tested and production ready. So it's regardless of how you design your business process, it will always produce those quality smart contract. It also can help with the deployment of the smart contract and the monitoring of the smart contract. So it's all built in, which can reduce time to market and security risks, especially for a business person using these kind of tools. So we actually use this tool a lot in many of the projects we get involved in, where a smart contract has to be designed. So rather than coding the smart contract manually, we actually rely on this well tested and verified approach. So something went wrong with my slides. Let me go back to, I don't know, actually it's correct. I thought it went back to the beginning. All right, so the next tool I wanted to talk about is MacroKey. So MacroKey is a self-sovereign identity app and the slogan of this is your data, your terms. Obviously it's a self-sovereign identity app. You are supposed to be in control of your data and the way you interact with the blockchain, etc. And the key idea of MacroKey started a few years ago with key management issues around blockchain. You have certainly heard of cases where someone lost their private key and they lost, I don't know how many bitcoins, etc. So key management in blockchain is very, very important to solve. So obviously we can always blame the end user and say, you have to take care of your keys, but are there any really easy to use and reliable tools that we can have to manage our keys? And if those tools exist, obviously there are plenty of tools that can help you manage the keys. How easy are they to use in a day-to-day scenario of interacting with the blockchain? But also we try to think of this solution, MacroKey, not only from a blockchain perspective, but also from a normal web browsing perspective. You don't have to necessarily use your graphic identity just with blockchain applications. Could be also used with normal websites where you can authenticate on the website. So that's the main goal. So I'll go through a few details about what it does and how it works. So if I want to describe this app, it's many things into one. So it's a self-surveying identity app. So when you install it and create a profile, you basically create a key pair. It's your public key, private key. The private key is safely stored on the device, but then you can actually use that key to interact with the world. So it's an enabler of trust, because when you interact with the world, you can actually prove your ownership of that identity every time you interact with a website or with another person. And it's also a simpler way to authenticate because you are not involving passwords. It's a kind of a password less authentication, but also it's a server less authentication. So it's completely not relying on any third-party intermediary or server-based authentication. So when you authenticate using MacroKey, it's your device, your mobile phone that is interacting with whatever you are authenticating against. There is no MacroKey server, for example. The other aspect of MacroKey is that it allows you to store data on your device. So it's kind of a personal data vault and fully encrypted, obviously. And that's very important because as you interact with the world, you can collect certificates or credentials from different sources and keep them into your data vault on the device. It's also because of that, it can be used to prove your identity, prove your credentials to other parties.  You can basically sign blockchain transactions directly on your device. And that we have full support of Hyperlegia Fabric and the Ethereum Network. So these are the two blockchains that we support. Obviously, it can be extended to support a lot more, but that's the main focus for the different projects we've been conducting. So yeah, the way it works in terms of authentication, it's using a simple way. We built a Web SDK that basically integrates into any website. So if you have a website and you want to get the MacroKey users to authenticate against your website, all what you need to do is a single line of code into your website, similar to basically any, let's say, Google Analytics, when you want to integrate Google Analytics, you need to add one line of code, JavaScript code into your website. And that basically loads the SDK. So in our case, yeah, we have that SDK that allows any website to be kind of MacroKey ready. And the authentication is done through that SDK and shows a QR code that you need to scan with the app. So it's fairly straightforward authentication. And that allows a two-way communication between the device and your browser. And this way you can interact, collect data from the website or share data with the website. Obviously, with the user consent always as a centerpiece of this interaction. So the applications of this are, there are so many applications, but a few examples include, for example, logging in into your university website and collecting approval claim or a verifiable credential about your qualifications. You could actually then go to a job website where you can share that credential with the website to get better offers of employment, et cetera. So there are so many different scenarios. Here are like just three different scenarios like proof of qualification. The other one is proof of driver license status that can be useful when you rent a car or rent a truck online. You can provide that proof beforehand. That can help speed up any processes or even proof of insurance status. So if you are renting a car and then you can actually provide a proof coming from your insurance company that you basically are a safe driver because you did not have, you were not involved in any accident in the past two years, let's say. That verifiable credential can actually be provided by your insurance company beforehand. And you would have it on your phone that you can share anytime with other parties, including your car and your company, for example. So we applied MacroKey to a number of projects where MacroKey has been used for that purpose to basically interact with the blockchain and sign transactions. One early example, this is I think three years back. We used MacroKey to what was MacroKey at the time because it has evolved a lot since then to sign transactions submitted to the blockchain. And this was using the Ethereum network. And this was a work funded by the Department of Foreign Affairs and Trade. And the objective was to improve the important export product certificate sharing. So when you want to share a certificate about a particular product that you are exporting, the idea is to share that on the blockchain and obviously signing the transaction can be done by the individuals who are on the field actually registering the products about to be shipped overseas. So the use of a mobile device in that scenario is very important. And that's when we're getting this cryptographic service in your hand in the form of this app is very useful. Another example that another project that we conducted recently is in the agricultural industry. And so it's an external project with one of the world leading companies in the agricultural industry. And the blockchain that we used for this project is Hyperlegia Fabric. So the idea is to establish trust and reliability in picking up some compliance events. So I'll show you a quick demonstration of that in a moment. But the idea is that you have multiple parties involved. So you have the farmer, you have the transporter to transport the produce to different facilities like processing facilities, etc. So there is so much information to be collected from different parties. And having a blockchain solution is the best approach. Because in these kind of scenarios, if you have one centralized entity that is controlling everything, that can't work because there are different companies involved. It's too distributed for a centralized solution.  Now obviously in these kind of scenarios, you have mobility that is extremely important. Everyone is somewhere on the field registering how much of the produce has been planted, how must have been harvested, the time of harvest, etc. So trustability is extremely important for these kind of scenarios. And yeah, so it was a very interesting project to work on. I'll try to give you a quick overview of one portion of this. It's like a small demo. It's using an older version of macrokey, but the principle is exactly the same. So imagine you have a grower or a farm and then you have a processing facility and then you have the customer. So typically at the grower, you would have planted seeds of a particular plant and then harvest that produce a few months later. And then imagine that for each of these, let's say, boxes or sacks of whatever plant is being produced in that farm, you would have a QR code attached to it. Now it doesn't have to be QR code, it could be other things, barcode or RFIDs or anything like that. Anything that can identify something that you are shipping around. And the idea is that the grower would basically assign these different packages, let's call them, to a particular transporter. So you'd have the grower using macrokey and then simply scanning each of these packages using macrokey. So I'll scan the first one and then as you scan one, we call it a module. So you have a particular package that you want to assign to a particular transporter. So here I'm scanning multiple of these packages. And then once I bundle them all together, I can authenticate. And by authenticating, I get this form that is custom made for this particular purpose. And that basically allows me to, for example, declare these as harvested or assign them to a processing facility or to a transporter or etc. So there are many scenarios that we can use. And then once I pick what is the event I want to submit to the blockchain, that gets submitted. And then I can see here the details of the transaction being submitted to the blockchain. This happens directly from my device. So obviously in this scenario, you would have to be connected to the internet in order to do this. A more recent version of macrokey actually introduced some caching mechanism or kind of a queue. That once you submit the transaction to the blockchain, if there is no connectivity, especially on the field in the middle of nowhere, you are not guaranteed to have 4G, then that will remain pending in your phone until you get connectivity and then it's submitted to the blockchain. Now, for this project, it covered a very complex business process. So it's not just that that was one example of interaction. But then you can imagine that if the farmer allocated the three packages to one transporter, and then for some reason, the transporter actually delivered to the processing facility only two packages. Either they did a mistake when they picked up the packages, or they dropped one on the way to the processing facility, so anything can happen. And that's actually a compliance event. So if you have a compliance that the transporter was supposed to deliver the three packages, and that they only delivered two, that actually will be another. So the transporter will be scanning these QR codes and doing the same thing simply to report back to the blockchain that they have delivered two of these packages. That can trigger some compliance events. So one main component of this project was also to build a kind of a dashboard that showcases how blockchain can actually raise alarms when something went wrong with the process and how these alarms can be basically resolved once the other package that was missing is added to the is delivered to the processing facility. So yeah, this showcases how interacting with the blockchain can happen at various levels, not only directly from a website that is hosted somewhere, but also from mobile devices on the field. And the project involved not only macro key for on-device blockchain interactions, but also integration of existing systems and information systems from different processing facilities, the grower, etc. All right, so I'll talk with about also another project that we recently completed. This is the National Blockchain Pilot for Critical Mineral with Everledger. So Everledger is an Australian blockchain provider or platform. It is using Hyperledger as well. And this was one of two Australian government funded blockchain pilot projects that were one of them. This is one of the two. It was actually worth three million dollars that Everledger was selected for that. And we contributed to this through our collaboration with Everledger. And the objective of the entire project is to enable the traceability of critical mineral products in the whole supply chain for ESG compliance. And our role in this was to contribute with work on self-sovereign identity management in this particular project using macro key and also CSI on mining process provenance through simulations that we, this CSI, another CSI routine was providing as well. So that's all for today. I hope we have enough time for questions. So if you would like to contact us, please visit this website, research.csi.ru.au slash letter 61 slash pop chain. You'll find a bunch of information, a few details about what I talked about, the different tools that we have, and also contact details about the people that are involved in the different technologies that I talked about. Thank you. Any questions? Okay. Thanks, Admin for the very interesting presentation. There is one question in the chat that I just asked. It's been said CSI used to be a publicly funded. And what is the position on open sourcing tools and utilities like the ones you just presented now? Good question. Yeah. So some tools that we build, they are open source, some others. So in general at CSIRO, going open source has to be driven by different considerations. So when something is mature enough, it can be either going open source or it could be used as a separate entity to really achieve impact. So it's driven by what is the best strategy to maximize impact. If something going open source is the right choice, then we go open source, obviously. If some other technology is going open source is not going to bring the impact that we are hoping for, but actually getting it into a higher maturity level for a potential spin-off or anything like that, that's always something we can pursue as well. So there are many considerations that they can consider in this choice of whether going open source or not. But there are definitely many, many open source tools that are available through CSIRO. Okay. Okay. Great. So I'm just trying to see, looking into the question, how can we experience it? How can we experience the interface of MacroKey? Great. So MacroKey is not yet publicly available. So it's a mobile app. We have built the Android version. So it's completed. The iOS version is under development. It should be completed soon. And yeah, if you would like to kind of keep in touch and learn more about when we will release some version of MacroKey to the public, yeah, just shoot me an email and then I'll keep you in the loop. Okay. And then I think, so another question I have is, I was wondering if we can get some sandbox kind of things for the tools you've just demonstrated or some trial or kind of somehow, some ways that people can access the tools or is it like staying in touch with you would be the best way. So yeah, it's, there is no kind of one place where you can play with all the tools. So there is no setup like that, but definitely just reach out and then we can discuss what is exactly the use case scenario that you would like to use these tools for and then we go from there. Okay, great. So when you were talking about like storing logging information in the blockchain database and things like that, so I was just thinking what exactly is stored in the blockchain in terms of the information that you store initially and then pair logging or if there is like a faith login, what would be stored in the blockchain or like all these information related to each other and these kind of things, if you can just explain. So in relation, is it in relation to the use of MacroKey or another tool? Yeah. So MacroKey itself, when you create a profile, you can create a profile completely offline. So it's not actually your identity is not on the blockchain, there is no blockchain being used. So it's basically a simple key value, not key value, a private key public key that you generate on your own. So that's why it's self sovereign. And because of that, you are the only person in charge of that private key and it is in your own device. It's not being stored on the blockchain or somewhere else on the cloud, etc. Now when you authenticate against a website, obviously that website has to have the our web SDK. But then the authentication is a simple basically handshake that you are establishing between your device and your browser to authenticate. And the authentication itself is a cryptographic challenge that the website is asking you to sign. So if you have the private key, then you will be able to sign it and the website can verify that signature. So it's pretty much a classical challenge signature. But the key element here is that you are not relying on a third party. So if you think of authentication in general, when you talk about OAuth and all these kind of single sign on solutions that you see out there, everybody is using this. So from Microsoft Office or Google Systems, you always authenticate through a particular identity provider. So when you sign in using Google, for example, you are actually interacting with the Google service to sign in. So there is always a third party involved in your authentication. Now if that third party is down for whatever reason, an outage or any other reason, like being hacked, then you are not able to log in anywhere. So an outage of the Microsoft authentication services will actually make thousands of businesses stop working because they cannot log into their systems. With Macro key, it's completely distributed. So every user is authenticating using their own device and that interaction is not involving any third party service. So there is less risk for the users, more data privacy and security because the interaction is completely local to your network. So if the Wi-Fi is still working but the internet is down, any local web-based system that you are using can still authenticate and continue working with Macro key. So that's the key thing about self-surveying identities. It has to be truly self-surveying, not relying on a kind of cloud-based system. Even if these cloud systems, they always claim that they are fully encrypted, that they are having the best state-of-the-art security systems. But still, if you are relying on them, if there is an outage, you are basically not able to use your identity. And because of that, it's no longer self-surveying. Your question was about storing data on the blockchain. So in essence, when you create a macro key identity, you are not storing anything on any blockchain. Now, if you go and log in to a blockchain-based application and it happens that that application is using a hyperledger fabric network, then when you authenticate against that website, the website can actually store all the configuration details needed for your device to actually sign transactions on that particular hyperledger fabric. So all the network information, etc., are passed on to the app. So pretty much when you authenticate with the website, you establish this two-way communication between the website and your device. And then the website can store information into your device, into your macro key profile. And you can also provide information to the website. Let's say the website asks for your first name, your address, your date of birth, etc., at authentication. You have to approve that. So there is some user consent in the sharing of information. That's a key element as well. And then it's up to you every time you need to sign a transaction to save something to the blockchain. The app shows you a notification that asks you for approval. So nothing is saved without your explicit consent. Great. And the other question that we have is what happens if you lose your mobile then? Great question. I get this question a lot. So obviously, what happens if you lose your private key to interact with any blockchain? Obviously, if you lose your private key, the scenario is you go to your backup. You need the backup to recover. Obviously, any kind of crypto wallet, when you install a crypto wallet and create an identity or kind of a key on that crypto wallet, it will ask you to write down a passphrase on a piece of paper and save it safely somewhere. That process, we follow exactly that process as if macro key is a normal crypto wallet. It is actually a crypto wallet. It can play that role, but we are using it for not necessarily to make cryptocurrency transactions. That's not necessarily the purpose. It could be used for that, but it's more about smart contracts and interaction with smart contracts and interaction with websites in general to achieve many scenarios that are not possible through normal crypto wallets. So, yeah, if you lose your mobile device or basically get destroyed or whatever, you can actually install macro key on another device and then import your backup. Obviously, when you import the backup, you need to type in the passphrase, the full mnemonic passphrase that is typical of any crypto wallet here. And obviously, if you don't have any backup, just create a new identity and then recreate your credentials that you collected from other websites. So, you have to go and collect them one by one. Okay, there is another backup for that as well. Okay, so that's seven. I think we don't have any more questions in the chat in here. And thanks, Etni, for joining us. It was a very great presentation, very interesting tools. And we look forward to see these tools and play with them once they get available for public as well. And thanks for accepting our invite to join us. And anyone interested, yeah, send me an email or visit that website that is on the screen to get the contact details of the rest of the team. So, yeah, happy to help and provide access. Okay, thanks. And thanks everyone else for joining us today. If you haven't followed our Discord channel for Hyperledger, Sirleisure chapter, please follow us on our Meetup channel so that we will be notified for our next events. Thanks, everyone. Thanks, Etni. Thanks, bye. Thank you. Thank you very much. Thanks.


I would like to look at the actual goals of our team on non-conspiracy. I am currently working at Everslake in Romania. We are actually hiring one, if not two, hub, hub, and butter. And then you're also? Butter. All right. All right. My name is... I have a number of two projects. Remember... All right. We are... Everslake in Romania. We are hiring one, if not two programs. We are hiring... We have a lot of people here that made, I think, appropriate for hiring one for Everslake. Mr. G is hiring one. The bandwidth out there is wonderful. I am right now... I have a... Let's see here. A 10-year-old one. Give it a five-room. So, you've got plain bandwidth. Come on out. All right. First of all, those of you that don't know where to hire Everslake, we have World 6.4. World 6.4 is for esophagus. World 6.4 is for esophagus. World 6.4 is for esophagus. World 6.4 is for esophagus. You can find documentation online. There's also World 6.9. And World 6.9 is for esophagus. You can find models, supporting fight, for both, for any new set. We used to... We used to hard-hand up and down stuff because we sent the models all the way to a more fancy band for World 6. Right there, here's my card. Some of them out there right now. I have written out a feed. This up there is a 4-part card roll on print respectively. Some of them went out, and I didn't want to do that. So, my card... I'll tell you something. This is where you can see more stuff on World 6.5. First of all, there's a webcast coming up on Tuesday with a game for World 6. I will also be at Hobus for Spades in Copenhagen. Follow that, and that base game will be us for the weekend. After that, any options possible? How are we given them in-situations? We'll go through that. Obviously, we're not going to ask them. And DC, we'll go through this. So, that's how busy I'll be over here. Those of you with your left house out are all ready to download the model. This is where you look for the kernel 6-pressure within kernel 6. Now, at what time... was a meeting started by... probably started by either a label towards war and candy. That pearl 5 cannot be crossed by anything but pearl 5. Which is not entirely true. If pearl 5 could be crossed by pearl 5, then why is pearl 5 in DC? All being done by the macro from where I have seen the law of flavors. Pearl 6, I'll never hand it. I guess you could cross with a language, but you're so easy to cross with yourself. So, that's where this model goes. You want to download and play with yourself. You want to use Panda or be self-installed. I think it's a DC-installed keyword. I cannot be sponsored. Now, the question is, why would you want to do this model? Here is a sample test. A sample test. Pressure.format, why do I want to do one? Test to see if it is why do I want to do one? So, it's just taking a screen and returning a screen. Which, on the face of it, is really useful. If so, why does it take 1 hour and 66 seconds to run the test? This is on JPM, located back in the US, on part of the I Know Network. So, that's part of the supply. Most of it is the final I know as you can see by 23 simple I know. So, I assure you, it is very fast, as you can see here, 0.06 seconds. I mean, it's useful. A lot of used eyes pop out. It's the game of law, but it's actually going on. But, why would you take a screen and just secure it? There's no clue to that. Let's take a look briefly at what's actually going on. This is in the fill-in and profile of a written expression first, a very simple statement. My dollar I equal one. And, you try to break it out into pieces. You find out what the my keyword is. You find out the very thing to protect that. It will be equal sign. And, after the one there, that's enough. This is all in roll five. Everyone should probably get a full one. D slash x there. Let's add a space here. And, take it. And, add more space here. So, hold on a second. So, there's no real problem by parse this. But, we'll move into we'll move now into purl six. And, change it please. If you parse it in soft purl six. We haven't changed that much so far. After you slide here, you'll see the full year old of people to build. You'll find out the slash x to null file. Well, hopefully no double that. In purl six, you'll find out the you'll find out the close for build. And, you'll find out the yes. So, this is how you this is one way as when you move to how to write the code in purl five over to purl six. So, what we're doing here to win the code is we hold on this thing. But, we're using purl six inside this. Effectively using purl six. So, what's actually happening before is it's actually calling back to the power to do the work and determine the mash-up. With either process. Now, if you're going through and we make a priority if I try to compile this thing, there's some things that you don't need to worry about. You don't need to worry much about the wishes of your life. You don't need to worry about that because all your voice up here is number one. So, when I get the mash-up from these packages, this isn't quite correct as I understand. What we're trying to do is the very one here is pressurized. All of this is crazy. So, when I try to take this direction, press down, break it. Break down here, we just go back what I end up with. Looks like this.  We have an actual variable made here for the griddle. You have an injured ear here. And this is as close as to the inside of the problem. And this is just a problem. Now, we have this right here. And you want to return it and so forth. Say you want to create a grid. You want to get rid of the one-stage error. Or say you want to put a header here. Or say you want to use a lot of the simple on the left-hand side. What is the question? You can do that. Just more. So, how is it over? Let's think a little bit deeper on the grid here. We're going to start out by instead of using the format key, let's look at the built-in parts. The dot here, for those of you that don't know, like the Java and many other languages, the dot is the new flag. The new error. You can represent it. So, the dot here, the dot here, and I will throw in a little bit of a a little bit more from six times here with the dash. We finally have that add and I to use it. I'm not familiar with what most people do because I want to make sure it doesn't go away. As we all know, once you use feature in core, it never goes away. You don't know that to qualify. You have many features in profile that can't go away because they've been used for 25 years. While hitting the flag on the grid. So, what we're doing here is we're processing. We have got a data screen which is based, again, all comes in from Kyler inside the Kyler. I won't show you that because it's bound to change here over the next few years. Once we get a problem back we'll set up and we'll get the abstract syntax between it and which is what this model is to do. So, we first are saving current 8.8.3. And then we dump that out. We'll be getting our piece. This piece here, after saving is a very hopefully very straightforward simple way to do part of it. First of all, the current 8.8.3 is a document. If you remember when you died in cold or cold winter, well, honestly, you remember when you died in cold or cold or cold winter. You'll recognize that the current 3.8.3 is a document. So, this statement here is a document. So, we have a 3.8.3. This slide document is one of more statements than here. The statement, this is all for my internal human interfaces. This helps me a lot more with this project. And this slide statement, we have a very straightforward project for mine. This helps me instead of starting on here, over here. Zero is very logical. Over here. And we generate an online 5.9.2. Again, very handy. You have to go and trace the first thing. Because, by this time, this time, by this time, it gives an understanding of 3 states as complex as this. So, if there is a place based on a place somewhere within that, I have to either debug that through a wall or stack, or just go to the line of the interface. So, pass error tracing, pass debugging. And the routine that you hear reaches is maybe 3.5 also. Well, internally, what I'm doing, I'm trying to make sure that this becomes a core routine because I'm hoping that someone out there out of the room, or all of you here whatsoever, is someone mobile on top of this and I'm going to say the static interface where you build a stack file or you can use it to build a new written approach to this. So, by taking our statement here, you can bring it down into pieces and we still need pieces. So, internally as well, there is a lot of validation because right now, hopefully, there is a kind of step, but we can't change terms now. So, what I want to make sure of is that every piece of the portfolio counts. So, one of the steps I do is very intense validation. I'm sure that 0, 3, 2, the next token has to start at 0, 2. So, we have to pass the start with 3. So, the entire thing has to fall down. So, 5, 6, right there, we just say right there, we just say positive. So, I'm sorry, 6, 7, 7, 2, 8, 9, and so on until the last point. And white space is also preserved. So, if you want to say right and preview, if you want to go through and just take up my and equal sign, you do that. Sure. But, if you want to just return everything as it was, the module preserves all white space even through these hear dogs. Hear dogs are a very special case because the hear dog content has to go here, but the hear dog content has to go here, but it actually in real life code appears down here. So, I create a separate way to go down here that does nothing but open camps. So, that's the reason behind it. Now, let's take a look at this portion of this will be largely described why it is useful for e-mobiles in Perl 5 to go out and at least look at some of these other process offers. Now, as you felt by looking at the days of our years, all these are total six classes. We're not here that we have a variable class, which is as the case one single thing, a single content field, the word my. The entire segment, however, we use a list of multiple bare words and space and operators. So, we have essentially a word element which is either a bare word or a complex of bare word combination of bare words and listing as a room, which is okay, even if you do that as a inheritance or a future. And if you want to in Perl 5, you could just replace the class here with packet and use boots and add as a cap trial as a dollar content. You can do that really easily. So, you have a variable here with a single content and an operator here with a single content number. And over here, you have the saber which has a list of things. The question really comes here how do you kind of reconcile these? Because if you want to have just a single co-working element class over all these, well you have a three-year-old class element and its element is a element or is a element which is fun. The problem comes when you take these two attributes here and move them up into your parent class because of course you wouldn't have any specific classes across four. So, if you had a normal of a mythical element class we had a file and a content. When time comes to validate them, when time comes to run the estimate, the signature of is that your bare words do not contain one thing that your statement would contain a list of things. And the best way to do that is of course to have subtitles. But you always said you want a normal working class. So, how do you reconcile them? And when you add in things like a mythical to parent list. That gives you more context because you have parent list over here. So, you have a combination of the list of child and your content. So, how do you reconcile those? Well, again you can do this and curl by too. By using words. So, what we use here is rolls. Rolls, you get in boots you roll five and in roll six you get them free. They're essentially a place of a class. It's how I like to do it. So, I run here instead of having instead of having a whole bunch of classes and then having all the content inside the classes what I've done is I've taken the classes that we have here. Things listen. And where we have a trial I create a framework. So, a trial, so a segment as branches off it. Over here for the bare word, the bare word only has one thing. So, instead of having a conflict between a tree and a single point what I've done is created a naming board. So, that the bare word only have bare word does naming and the segment does searching. Now, I took all the we're starting so to figure out how to do we're starting to figure out so how the whole six best practices will be I find that if you're naming roles in classes naming roles in English if you use a name you use you use the adjective over here branching name name again it means very nicely class statement does branching or you can say class statement does branching and sort of falls off again. Now here is side name so right here the bare word only has a name right inside the operator only has a name and these are the only two ways that you can build a free so that there are no other bits of data going around and likewise if you want to go back to for a method call i.e method method parent list you can have it do a name or a name or the list you do the branching we have both common node and you branch as well so it's not so much a way to create a list for the class here as a way to help validate and make sure that your tree is consistent again tree because one of the things that we have come back to profile one simple thing if we have say a profile package we'll call it a factory package that does stuff just like here we have some d-y-u terms where we have w-x and w-n and we have the real view which is the what else happens isn't working in girl 5 there's a whole bunch of ways to come out of your code of course you can also use power signs as a term coming out that way or use your option the old people who like so the old people who blah blah blah but we all know that once we write the code suppose here we have down suppose here we are on indy volume we have a circuit down here so in order to comment on our d-value that we want to do before pushing we have comment out here and skip that bit right there and then comment down there well the old will say because in this case what you can do is take your d-value methods here dump text dump term d-pulses term put those each way old and add that to your class so now if we want to comment out of your d-value instead I find a two people are or a power sign you go into your class and comment out right there at one point so you move your d-value you can move any sort of foundation or matrix with one line instead of having to change packages and add roles and it wasn't and as a propose if you want to make sure that you can't see the old old class slide on your class front you use line because now classes and roles everything can be so now we have our method already like if you're like me and a car or a fin user you know the key word around the paragraph and you can erase it so it becomes great p you can move here to here and dump down past your code or select your entire line of old in one file without having to worry about okay did I put this up here is there more people down there is there validation stuff here I need to worry about put all slide one more past your way is hit away in our class in another world rather and comment out comment out and it's in one more in your code now you might after taking a look at this huge tree okay so how do you how do you get your output if I want to read how do I do that how do I take this tree get this three and how much work is you want to get out to get your text out well it is just that that is that is all I know that you need this is the entire method with all that data with all those methods all those objects going on this is all you need to turn your Perl 6 back from the data into your Perl 6 that's it I'm trying to look at this as simple as it be I'm showing you the code all it uses the advanced customers I use in the code are further expressions and if there is and given the way those are the most complex things I use in the code I call our show place a lot of stuff with indexed calls I put network to worry about that now I mention for code format so if you have this two string that returns the content returns the word my from a bearable or returns the list of all things in the code and by the way now you can kind of see why it is important to have roles and to separate tasks so that the bearable doesn't actually do this or by the statement you never heard because then your cross is free and you gotta told us cross is free is bad so if you want to write your role no matter if you want to say get rid of all my scripts that's it remove all my scripts in your code with less than a line code the bang till fill here is matching the type code 6 believe us and this is all that you need to write your role for if you want to work with space that's for me if you want to place by space to your own then you then return what they've earned how much by space followed by the operator followed by more fighters that's all you have to do to my role that's it so that's the real and back to pro fucking a little bit we've all been here we have a we have a call here that doesn't mean that's broken we need to find out what's going on and we need feedback hands up here how many people use data for this okay either you know or okay I'm also minority I bring out myself but so you would add so this was very good for sure use the number get these stuff get the big bad stuff get the number 5 everything comes to that no problem but the time comes when you want to commit the code get commit or use the r or commit and you forget to remove the print double model been there done that may not I know I know about you been there also over $3,000 $2,000 online and someone who's going to do that and wonder okay why do you have a dave duffer can't we actually call that their loan is something deeper we go like this no you just forgot to remove it after the debug well no fix it stay away if you need to debug say no take this that's it there's no need for using YAML there's no need for cracking models there's no need for call dives there's no need for YAML use and return the code just doesn't work the data stack we know to use dot curl and it will turn the curl it will turn a 30% of the curl that's it there is nothing above here use search now for the word dot pist or the word dot call if you want to cover and we know it's going to be fun it keeps it very very straightforward coming I'll loop this for you in curl 5 there's a bunch of ways to come in out of curl you can use downsides soft dodge blah blah blah blah you can use curl or curl 5 downsides you can do things this way in curl 5 get your family or you can use your curl 5 cut and hopefully you'll remember to have the blank lines there that you curl 5 curable put that into your dot list and with those curl dodge you'll see these people are inside there and they shouldn't that's a good thing to do if you say add them or clip them they don't have grow up and evolve you have pound markers they have a minute x coming out one or a minute or a minute x add 4 the problem though is that most of those actors haven't quite called to the way curl does for them in curl 5 curl 6 in C you have slash star star slash C vim and ex all know how to jump between the start and end of that one when there comes curl jumping from the evil side to another evil side to another evil side they get confused at least at least it does you can add highlighting be sure no problems you can add your highlight markers every month as a curl to go and page how the error was but really it's better to use the principles of curl and go with the effort when it comes out you can do it and you all know how you jump from the start of the marker to the end in vim and ex I think it's met a point met a dollar sign between them I don't know how it looks but in curl 6 we saw that you have the common marker here with a back kick and here come there down to there so here we are giving the address now to the C's do you want to balance things the program is next to the C to balance items like so and also we have a back kick there makes it very easier to go for a test say if you use this command you can comment out test wise if you use this comment if you want to know how easy to comment out all you do is back kick type wc return the number of lines that have the back kick so you know how many more tests to have test how I get the test wise sat down the curl 6 test wise like 27 plus files two or three odd tests and I'm now down to maybe putting this left so speaking of testing there's two ways to go about doing this or rather two ways to go about solving the problem like this either write a test week and you can have some stuff in there that is not necessarily things that are often only like say in my model I have a lot of stuff there that is validation or reader link but I do want someone to be able to do that in curl 5 what you do now is you clear the problem of writing say strict or author and have your own side there and it does stuff but the thing is a first couple things here point out here is obviously if walla-walla inline in your code just wait and solve the problem at least it will come out also you gotta remember and look right out for the test end and be able to look up what you did for the offer key button every time that you go through or to say ok it's always offered or always the other thing here is that this is actually over inside your form package so this is not inside this is not inside this is not where you saw your model and you want to keep a separation line between the already blank stuff and the rest of the world well the line gets a little bit working you gotta have this going on over here in your test and you have this going on so one thing we got this in front of rable you can see when you're outside that you don't really want keys so again this comes to the rescue with the constant of the dynamic rable so you'll see here this is a outside rable you get us a river rable you can saw your method but it's not clear to you if there's no line here so well there should be a way up there otherwise there's no wide r-star spectrum over there nothing like that this is over here in your code and this is over here in your test so what happens is 06 says alright r-star amazing with the star sum is a 9 variable and can you clarify so instead of 3 in the variable inside your package here and following up your namespace reducing percent of the to communicate information around you don't want your namespace apart because it will be a big delay and you must remember too that 06 is not compiled so if we have a way to see a little bit of that then code runs faster in 05 if you say if you've always got 10-star value in 06 you have this so it's not passing it's simply being as a click I shouldn't use the word script there apologize $90 r-star my point is there so this is over here and automatically the unfortunate program triggers the kidney bug so you out there as the user never need to know about this if you look there you might see the $90 r-star but you don't need to worry about that it won't impact you but another thing that I'm reconciling that I've seen a lot of at least 5-5 though that I keep updating and updating and evolving as I move more into 06 I will reach the point where I well I should say not click I move past the point where I dropped out the errors in my drill flag I've not gone over that and I survived when I saw 06 I don't use the errors in the drill flag I still do so I'm closing on the end here the last panel I see and this can be resolved in 05-24 right again in 05 I'm closing on the end here I'm sure we won't have to use that look for your number if you look out all entries okay okay let's go okay okay let's do that um I will bring I'll close down to my last bit here so I'll be out here the parallel we have here in 06 in 05 in 06 and in 05 we're now down to that so you're still having both you're still having to index and you're still having to index and you're still having to index and you're still having to index and I don't know if we're having those library still in 05 and again I have a I have a a lot of information we're still live from there so if we're going to do it we'll do it again


Hello and welcome to EGE 101. I'm Brandon Schwartz. I'll be teaching the course this semester. Very excited to have you in the class. I've taught somewhere north of 3000 students EGE 101 over the years and I'm excited to teach it to you.  So what we talk about in EGE 101 is energy in the environment. We talk about energy choices and their environmental impact. Sometimes it's things that you wouldn't think of right away. So for example, right now about 40% of the world's electricity comes from burning coal. And so we'll talk about why that is but you know it's worth asking yourself why in the world, how in the world do we burn coal to produce electricity. And as I said, we'll discuss that. There's lots of environmental impacts from any energy choice. And so we'll go over those pros and cons of different choices. But we'll start off with just an introduction about you know an overview of energy in the world today and where energy use is going in the 21st century. So, but for now, we'll just look at some of the course expectations. So, if you've seen the syllabus, then you'll know that we have several ways to give you feedback throughout the semester. The main one that you'll be thinking of probably is midterms. They are called midterm exams in the syllabus and they are exams. I prefer to think of them as really hard quizzes and the reason for that is you if you're imagining a traditional sit at a desk with a pencil and paper and take an exam it's not really like that and all of the midterms will be already questions multiple choice you'll take them through canvas, and I'll give you more information about that, you know, as the semester progresses but what you're looking at here as far as the class structure is the units and so you can kind of get a sense for, for, for how we've structured the class or the first thing we'll do is talk about introduction to energy, what energy is power efficiency, which will, you know, we'll define later. In midterm one, you'll notice it only covers two units. So the good news for you is that there's not a lot of material that you would need to study for in order to complete midterm one successfully. The second midterm covers the three fossil fuels and climate change as a group of as a common theme. And then midterm three covers nuclear energy, wind energy, solar energy and hydropower. So as you can see the midterms aren't cumulative meaning they only test you on content from each of those sections, but the final exam is cumulative. So by the time you get to the final exam you will need to understand the entire course. And as far as ways that we grade you that the first is on a weekly basis, every lesson. We have participation points scattered throughout and so as you look at the text and video for each lesson at some point you'll come to breaks where there'll be interactive content included that will prompt you with a question that you will then answer usually multiple true false if you get it right that's that's great if you get it wrong that's fine too because usually the very next slide in that interactive content will be an explanation for for what what you did wrong if the event you did get it wrong. You get unlimited attempts so you should get all 10% of the participation points available in this course. So one of your grade will be preclass activities which are going to be completed on canvas. And the idea behind these is to give you a really quick brief introduction to the content of the next week just a little bit in advance we'll talk about things that you've probably never even thought of before maybe maybe you've never had an opportunity to think much about wind energy but you've always wanted to so the questions in that preclass activity will just be thought provoking the questions on wind energy.  And you usually have two weeks to complete those and those six assignments are worth 30% of your grade so about five points for each one. Every midterms are worth a total of 30% and as I said you'll have 60 minutes to complete 40 multiple choice questions. It's not given at a specific time it's given on a specific day. You can see the dates for the midterms in your syllabus. Once you access the midterm, you'll have 60 minutes to complete it but you can access at any time throughout the day that is offered. And then of course there's one final exam which is similar in content to the midterms but just longer. Okay, so as far as the lessons form at every week you'll log into canvas you'll go to the module that we're doing that week or unit. There's 12 of them. There's no textbook required everything's on canvas. If we have any external readings or resources we will link to them in the canvas lesson. As I said there's 12 units, which is basically 12 weeks. If you look at orientation taking one week, 12 weeks of lessons that means you will probably have two weeks at the end of the semester that you will probably mostly spend doing final exam preparation and we might have some some live exam prep, if that's something that you expressed interest in. But as far as during the regular part of the semester each unit's got two or three lessons, you'll notice that these lessons are a mixture of text figures like like graphs, some example problems. Some short lectures similar to this video lecture here, and also some open source video so the idea is to give you a really good overview, using all of these different media types of each lessons content. Participation points are scattered throughout each lecture so you need to really make sure you view each page of each lesson in order to not miss any of those participation points. And then certainly if you have any questions, you know I am available through email at any time. So that's all that I wanted to talk about today. I'm really happy to have you in the course welcome, and we'll get started.


Do not. I repeat, do not. Wait, wait, hold on, hold on, hold on. Now we got that squared one. Do not try to trade options, stock, whatever if you're not going to be in front of the computer. Do not do that ever.  Do not place a trade. Forget about it, just forget about it. Let me tell you about the trade that I made today, guys. Boy, I broke one of my biggest, biggest, biggest rules today. But I do want to start out by saying it was a winning trade. It was a winning trade. It was a winning trade. It was a decent trade. But I had to work all day long at my part-time job, occasionally glance at the markets while I'm working. It's allowed. First of all, it's definitely allowed. I saw an opportunity. I saw that I could be getting a signal. And I did, I was at work. That wasn't so much the issue. The issue was I was literally about to clock out and I had to go run some very important errands on my hour lunch. And I knew this going into the trade. I knew it so well. It is extremely dumb, guys. It really, really is.  But my strategy definitely entails being in front of the computer and basically babysitting it. It does incredibly stupid on my parts because not only could I not watch it really, I could watch it on my phone, but I was driving. It just, everything about today's trade was bad except for the fact that it was a green train. And on top of that, I don't know the app really well. The Tasty Works app very well at all. In fact, I didn't know how to sell. I was up and I had to call up my representative while I was out on my errands at the bank and it just, you got, don't do it, guys.  With that being said, I was really smart about being dumb. What I mean by that is understanding that I wasn't able to watch the market, watch my trade like I usually do. I went a little bit further out and I made sure that I was in the money. By then I mean my expiration was next Friday, I believe, on the queues. I traded the queues today. So that's my trading tip of the day for Friday. Do not day trade if you're not in front of your computer screens, watching as that trade unfolds. If something were to happen, be sure that you're there. You have your, basically your plan and plan A, B, and C should something go wrong. Make sure that you have your phone numbers to your brokers on speed dial, basically.  So let me show you today's trade really quick. Here's my trade, guys. Obviously I traded the queues. I bought two of the 167.50 calls that expire in seven days. And I went with the queues because just to give me, to not give me that temptation to trade, spy three days out understanding that I couldn't watch the trade unfold. So in case something really bad happened, I wouldn't be losing a whole lot. That was my logic there anyways. So I bought two at 193 and I sold them both at 205. This actually was called in two Tasty Works representative and he actually executed my exit trade there. So, and here is the signal I got on the queues. Got it right here. I got in essentially at the start of this candle here. I had to endure a little bit of pain before it actually started going back up. And my original plan was to exit at 210. That was gonna give me my 10%. But I chickened out, of course, because I wasn't in front of my computer and I was the high there for quite a bit actually. Let me just check here at 1215, which is 10, no, in 1215, yeah. So let's see, I sold right here. 205, oh no, that wasn't the high there. Actually I was close to the high there for a little bit.  But that was my signal guys. There you have it folks. That was my trade for today. It was green, I'm happy about that. It was very stressful to say the least, but there you go, it was green. Don't forget to hit that subscribe button, hit that bell notification guys so you can get notified the moment that I upload a video and don't forget to like and share my video and comment down below. Comment down below what you thought about this video. Did you hate it? Did you love it? What did you make money on? What did you lose money on? Let's stay profitable guys, take care.


5 Tips on how to impress business clients as a business English teacher. Like it or not, ready or not, English is the global language of business. Globalization in business is widespread both in market globalization and production globalization. More importantly, more and more multinational companies are mandating English as the common corporate language, Airbus, Daimler Chrysler, Fast Retailing, Nokia, Renault, Samsung, SAP, Technicolor, and Microsoft in Beijing. Here are 5 Tips on how to impress business clients as a business English teacher. 1. Dress to impress. 2. Be professional. 3. Needs analysis. 4. Provide a course success report. 5. Distribute a course evaluation at the end of the course.


Okay, another big thing that we have done is a big thing because it's been around for quite a long time. We have improved the management of created users in course restores. So this is basically when you restore a course and it includes user data, now it's possible for Tenant Admin to import these kind of courses and have the users created within their Tenant. Previously there was this capability missing and this was possible only as a site admin. So as a Tenant admin, you use this as a work credit in the default Tenant which was not desirable. So now we have this capability that adds more granularity to this process. It's been around for a long time and finally we have improved this functionality. So next slide please. There are many other things we have done in this sprint and I just wanted to highlight some of them and as you can see, many of them were suggested by the advisory group. So I will not spend more time on this but all of these issues were important. As I said, just a small part of everything that we have done in this sprint. So next slide please. I think this is the last one. So from the discovery point of view, nothing to add to what I said in the goals. Only that we are very excited that we finally started with the accessibility of it and hopefully we can have more work place with this accessibility for 4.1 and 4.2.


Hey everyone, welcome back to SNES Drunk Place Final Fight and this time we are on the West Side where evidently there are many advertisements for the restaurant title, restaurant, or those windows. Are those supposed to be windows? I always thought they were posters, I just realized they might be windows with no customers in them. Well, why would there be customers at a restaurant where there's a lot of fights outside? Anyway, yeah, this is the game gets starts to get a little bit harder here.  When a game, when a beat them up bogs down like this with lots of people, with lots of people on the either side of the screen, fuck, did not want to die there. It really, the gameplay really needs to be slick in that you're able to flip between the left and the right very smoothly, very quickly. Final Fight does this very very well, as good as any beat them up on the Super Nintendo. Like the actual mechanics of getting everybody on one side of the screen is done very very well, as well as any beat them up I think in this game. That's why when people talk about like whoa, it's not the arcade port and blah blah blah it's like the game still plays fantastic so it doesn't have multiplayer so they change some of the names and so you can only have three bad guys on the screen at the same time. It's still, the mechanics are still there for a good game. And there's the sound of cracking somebody in the skull with a pipe, oh that never gets old.   I'm just going to keep getting up and just walking at him.  That's cool. That's going to be another 10 versions of me spawning later in this level anyway. Anyway, like the last episode I'm going to try while I'm playing this game or read this, read the uh what do you call it, the Super Nintendo Player's Guide notes about this game. And there have been some really interesting and amusing notes about this game so far. Like the Andore family fortune that they earned as a family circus over in Eastern Europe before they tragically got tied into the Mad Gear crime gang here in Metro City.  No, I don't know.  Okay, here we go. We've got G Andore and U Andore and if you're not careful you will get trapped and you will die just like I just did. You got to grab one of the weapons right away and I failed to do that and then just go to town on these motherfuckers. You know my brother and I when we first played this as kids we used to joke it's like oh it's Grandpa and Uncle Andore even though they look exactly like the other two Andores it's the same sprite just with different clothes. They actually are Grandpa and Uncle Andore that's exactly what they're named. And it says Uncle Andore resides on the west side when you come crashing into his home turf he'll be looking for a fight. This brawler is perfect at the Andore. This Andore body slam. It's funny. Like who would have thought I beat him up like this and put this much thought into this game. You know all you're doing is punching stuff. See this is what I'm talking about yeah being able to flip a guy on one side that's the key to doing well in these games is getting everybody on one side.   No feel me anyway what else can I say about these guys I'm interested in learning what this guide has to say about Jay and Tupi because those guys are really really annoying. Okay they're listed as fast fighters I can take care of this guy while reading. The speedy but weak faction of madgears is made up by two brothers in crime and that's one of them right there Jay. If you lay a hand on them these guys will go down the problem is that they're sometimes sneaky. They come in with a group of fighters and get their shots in when you're busy fighting the other guys. See it's good that the game has a good balance of bad guys like there's speedy guys there's big brutish guys there's strong guys. And then there's Edie here the boss Eddie I have no idea if he's part of the band that did that before I get to deep song from the early 90s.   What is her name Eddie and the somethings? Eddie and the somethings? I don't remember. Is that chick? That song? He was a butt head saw the video? Never mind.


Your Majesty and ladies and gentlemen, let me say a few words about the frank and very constructive meetings that I've just completed with His Majesty. We had wide-ranging discussions about the dangers and the opportunities we face in the Middle East. His Majesty was generous to share a perspective that he alone can bring to bear on these matters. His long and unique experience now assumes all the greater importance in this troubled area. We agree on much, on the necessity of making progress toward a just, lasting, and comprehensive Middle East peace, on the profound dangers which threaten the security of the region, and on the necessity to work in complementary ways to address these serious issues. We also discussed bilateral matters. The security and well-being of the Hashemite Kingdom of Jordan is a matter of historic and enduring concern to the United States. We agreed that reinforcing this friendship is a primary goal and discussed how our relations can be strengthened. We end this meeting on a note of optimism, realizing that today our friendship remains essential to the future of both our countries. Your Majesty, we've been more than delighted with this visit and to have you here. Mr. President, ladies and gentlemen, I would like to reiterate my feelings of very deep gratitude to you, sir, for the unique opportunity through which you enabled me to have the privilege and pleasure of meeting with you and visiting with friends in the United States of America at this critical juncture, critical time, which has a bearing and an effect on the future of our part of the world and on many common goals and interests that we share with you. I thank you, sir, for the opportunity to be with a friend whom I admire and respect now more than before. I value our friendship, and it has been a very moving experience for me to meet you, sir, and to have the chance to talk with you, frankly, openly, on all matters of mutual interest. I'll go back with impressions I will convey to my people and colleagues in the area. I can assure you that we stand together in our hopes for a better future, for a just and comprehensive peace in the Middle East, and from our vantage point for the freedom of the Arab people, the safeguarding of their identity, and for a better future for generations to come. Ever proud of the relations that exist between us, a deep-rooted friendship, our commitment to the same ideals and principles, and having had the chance to meet you, sir, I'm very, very proud to look into the future with hope and conviction that we'll work together and make our contribution for a better future and a better tomorrow.  We're proud to be your friends, sir, and rest assured that we will be on our way home shortly, realizing that this particular meeting at this particular time in comparison with all my previous visits to Washington has left me more reassured than any in the past and more confident of the future. Thank you very, very much.