 Thank you, Ming. By the way, good morning, DevCon too. Ah, nice. I think developer conferences are always a little bit more fun than business-oriented conferences, right? The participation from the audience is always fantastic. Excellent. So my name is Manu. I'm from Autonomous. We're in the business of incorporating companies, but I use the analogy of the Starship USS Enterprise blueprint that I have on the top there to describe what we're doing. So we're building the warp drive, right, in that schema that you see there. The warp drive is what's going to fuel innovation, production, and the Starship is basically the startups, organizations, and so on. This is really the final frontier in automation. I think over the years, we've automated a lot of things, whether it's self-driving cars or completely fully functional robots, but where we haven't innovated is in the area of law, corporate law, legal processes, the way companies, organizations are governed, asset management, and so on. And this is kind of sad, and that's what we're trying to address. So before I go into how we do what we do and our design pattern, it's important to understand first why the charter company. So the charter company, as I mentioned, is the underappreciated engine of innovation and production. We all build amazing things only because we are organized. Without that organization, I don't think we will achieve the things that Ethereum has achieved, for instance. And it's legal. So the way we designed our design pattern on the autonomous plan, everything that you do on our dashboard is completely legal. It's a mirror image of what happens in the real world. And honestly, I think it's the best use case for Ethereum smart contracts. I don't know why nobody else has done this before us, but I think it's the most straightforward use case that you can implement where you convert, in our case, we convert a certain section pertaining to corporate law into smart contracts, self-governing, self-executing, self-settling smart contracts. Hopefully, at some point, it will decentralize the courts and then lawyers become coders. That'll be interesting. So this is basically what we do. Now, there's been a lot of talk the last couple of days about security, especially yesterday, there was formal verification stuff. All that is amazing. I'm a technologist. I'm a developer. So I really appreciate the mathematics behind formal verification, but it's still complex stuff, right? It's not your average developer, average Joe developer that understands these things. So there's another tip I'm going to give developers, especially new developers. You don't have to design things from scratch. You don't have to create your own design patterns. You can seek inspiration from two locations. One is history, which is why I've got this timeline here, and the other one is nature. And you can learn lessons from there and design your smart contracts. And this is how we do things as well. And if you look at history and the blockchain and the chartered company evolution over time, it's sort of where we have arrived now with the blockchain chartered company as autonomous. So the first chartered company was somewhat in the 13th century. These were the traders, right? They went around the world. These were actually the chartered company itself. Then you had the Dutch East India Company. Then you had the Industrial Revolution. And since the Industrial Revolution until today, there has not been much innovation in the space of the corporation, right? A lot of the processes, policies are still the same until we came along, autonomous came along, and we put the company on the blockchain. We allow you to govern the company through a series of smart contracts, which I'll show you in a bit. Now what have we achieved? We have automated the corporate governance process. And why do we want to automate the corporate governance process? The cost of doing business today is so expensive because we have to hire additional compliance people now for new regulations. We've got policies that are more complex for us to comply to. So we try to reduce all of this friction. We try to save startups, especially money, and let them focus on the core building of the starship, right? So that's what we do. And it's not that we don't believe in the decentralized autonomous organization. We do. And if you see, we build everything towards a future of a decentralized autonomous organization. But what I believe, and if you see the headers there that I have, that last header shows you that for a truly decentralized autonomous organization, I think we need to go through some kind of socio-economic, political revolution before we're truly ready for an efficient decentralized autonomous organization. So basically what I'm trying to say here in summary is that when we design stuff, we go by the Secure by Design framework and the company, the corporation, the charter company, through its years of evolution has arrived at a certain state today and I think is Secure by Design. So we just convert the Secure by Design framework into a smart contract. How do we do this? Before I can even speak about the company smart contract, which is basically our main bread and butter, I want to talk about the identity smart contract. So again, going back to the energy of Star Trek, this is the dilithium crystals. I see a lot of blank faces. So I'm assuming you guys are not from the Star Trek generation. Okay. So dilithium crystal meaning that this is the fuel for everything else that we build and the central point of all interaction with the company smart contract. Now what is this? The identity in our case can be, it's probably slightly different from the U-Port guys or somebody else that's building an identity smart contract. We had to make this because we wanted it to work with our ultimate use case of the company smart contract. So in our case, the identity can be two things. First, persona, so a regular person, a natural individual. Second, a company, right? So it can be a collection of a company that's governed by a constitution, which is a collection of individuals. And it can also be a verification entity. So we said, you know, it's not enough for us to just allow the user to create an identity contract. We also need to verify this. And we don't want to do this in a central manner. We want to do this in a decentralized manner as well. And we said, okay, then we've got to create verification entities. But the way we've built them, so autonomous in this case is a verification entity. And we, as a result of you having to, if you decide to incorporate a company with us, you will also create your identity and we will then have to verify this identity. This identity can have a layered approach. So we do a proof of identity type KYC where we ask for your proof of address, your passport copy and so on. But this can easily be extended. So you can have a layered approach where a bank comes into play. Or you could have a government agency, for instance, verifying that a bank is allowed to do a specific type of KYC. And that's what you see at the bottom there on the left. And more importantly, this identity smart contract also has got identity information, right? So it's a collection of an encrypted identity file that is selectively shared. So by default, you can assume that it's shared with the public addresses of the verification entities. And it has the stamps of these verification entities. So the KYC stuff I talked about, it's all in a collection of stamps, if you would. And it routes calls. So if you go to the identity smart contract and you say, hey, get me the KYC of this identity with a specific bank, then it's going to route that call to that bank and get you the up-to-date KYC state. Should you wish not to use the localized stamp? The secure key recovery mechanism in place as well that we've attached to the identity. So basically, it's not enough. And a lot of things we design, right? We understand at the end of the day, people are using the system and people are flawed. Systems might be perfect, but people always lose their keys. And we've had many, many people losing their keys. Actually, as we speak, I think even my developers are still recovering some client's key, I'm sure. So we've come up with a very secure way in which you can store your key and retrieve it. So even the retrieval mechanism that we've put in place ensures that after you've recovered, you can still continue to use the keys because they've not been compromised in any way during the recovery process. That's also something that we did. And obviously, you need to be able to replace it. So in summary, I think we've identified or we've solved, at least for our use case, we've solved privacy, recovery and compromise of identity, right? And with this, you lay the foundation then to be able to sign documents, hold assets and do whatever it is that you need to do otherwise in the real world, in the digital world. Now, this here is the main blueprint. This is what we've been working very hard for the last one year. Actually, I wrote my first smart contract right about the same time when DEF CON 1 was going on. And today, we've got a whole suite of them. It's interesting. So central to all of this is the company smart contract and what is the company smart contract? Itself is an identity. It's an identity that's controlled by the stakeholders of the company. So these can be directors, these can be shareholders, there can be a corporate secretary involved in there and they all do this by way of legal documents. So there are preset legal documents in the real world which you use to enact any action in the company smart contract. Whether it's a transfer of an asset, you want to add directors, any corporate action that you have to do is by way of the proper legal document and process. So we've also replicated real world legal processes. So there can be a multi-step process, there can be 10 documents that you need, let's say in the case of a funding round, and they might have a certain sequence and that 10 documents will have to be executed in the correct sequence, otherwise it will not work. I think I'm running out of time probably, but let me just quickly go through what else we are trying to do. Okay, so before that, so that's what we do. So we've got a collection here that's got a complete trace of legal documents, identities, transactions, everything. But what is cool is those two purple circles that you see. One is the decentralized exchange. The company itself could become a decentralized exchange, which is pretty interesting. And you can also do that by way of a synthetic equity framework as well. And we've also designed this already. So this is my synthetic equity smart contract. In summary, I'm not going to go through it, but it is a way to replicate the payoff that you would otherwise have by holding real equity via smart contract. So that's basically what this does. So that is something that we've designed, we haven't implemented yet, and this is what I mean when I say we're working towards a completely decentralized autonomous organization at some point. These are things that you would need. And of course, the company is a decentralized exchange. This is a very interesting slide too. I'm not going to go into the details, but in one line, your company is a decentralized exchange now. So this is also very powerful working towards this. And the team, if I may, just before I get cut off here, I think the team Han, our CEO, is right there. And the team that's always working hard with me on the weekends. Guys, stand up and take a bow please. Ladies and gentlemen, these are the guys that give up their weekends for me. Thank you very much.