 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. And finally and most importantly, it allows you to interact with the blockchain. 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. And blockchain being a distributed technology is the perfect fit. 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.