 So the idea of grid is to bring your computer closer to your operating system. We always wanted to have a computer like always present to have a computer using our computer. So as much as you have DNS services, Windows servers and your computer, it's like from the operating system you can access to your computer. So we'd like to have this fourth year. So our interpretation of this design it and then we could develop grid as it is. This is how we should just turn on the computer. It should be just as simple as this. So yeah guys, this is grid. Right, and that's multi. So here it starts with a menu application and then if you just click on the switch, it starts to get ready. If you don't have it downloaded, you can download and connect using the live plan. So if you click it, you go straight to the marketing page. Here you've got links to our presentation. Using the apps version list, you can upgrade download just for the click. Just follow these and switches version for it. Here you can use this form to configure a node and that results in a series of flags related to that. You've got some sensible info and even some cool stuff like presets for a minimize. So here you can just edit your flags to go beyond what we provide now. So just copy, edit, do whatever you want. Just start to just flip it just like that. Just follow your face and then you take you straight to the terminal with the regular output. We also provide some node information so you can have sync status. And of course, when I was testing, you could get one here. So one aspect that I agree to highlight is how great can serve as an Ethereum app store for the tooling and launch by as well. So app stores, what do they usually do? They help with app discovery and securely installing something. Just like your phone app store. So here we help users finding Ethereum nodes and tools and apps. We'll talk more about this later. And we handle all the installation of it, find integrity, security, co-signing, and launchpad, which is how easy it is to configure it and zero friction to run. So, you know, the ecosystem has, you know, 10 folder and at least a number of clients. So we have like this in 2015 and then 2019 and then, you know, the rest, you know, is just increasing a lot. So here now this is what you get out of the box with grid. And we call these plugins, which could be either Ethereum nodes, you know, clients, or even like IPFS, this storage tool. So, plugins. From there, we can define lots of feuds that they are all defined in a single file. So we can have things like this, which is not bundled in a gap by default, but we can just, you know, provide this preset. So, what does gap loading have? We've got the release speed. So we pull downloads directly from the gas source, and now we're ready to deploy the package manager. We put the default flags, we put some sensible defaults. The communication protocol, it is all defined on the plugin itself. So the grid doesn't have anything hard coded for gathering the plugins, which is good for extensibility because we can integrate it with, you know, virtually any other client. So it's for documentation related apps. So this all goes in a single file. And as such, we can have several others, including yours. So what are grid apps? So these are self-magnified applications that run offline. They are unpacked and verified using our own packaging system. And, you know, anyone can view those apps and anyone can use it. So we'll talk about this in detail later. So grid can be really useful for onboarding developers in a different approach. So several developers start today using gateways, you know, some other tools. They're like, you know, on the flag of standing for using real nodes for development. You can just start a local developer chain on your computer and then start developers with it. So, yeah, your nodes are not for miners. Developers can also use them. So you should just do this one. And as well, as you know, we can have things like this helpful about it. So we can start a beacon with it. Then we can start, you know, a small fluster validator. Speaking of some shards on it. And then we can have lots of others. Then we can just swap the beacon and then, you know, keep signing, keep profiting. So, yeah, grid can help 2.0 make me 2.0 more inclusive, providing tools. UI tools for everyone. Shortening the feedback loop of these developments. Hopefully, speaking of iterations. Of course, we are already talking with some core developers on this part. And compare across implementations, which is really important for this stage of the project. And using grid apps to manage state, water, validators and beacon nodes. So, under the hood and that in this hood. So, as we learned, grid already comes with a bunch of clients out of the box. And there's many more clients that will probably be integrated in the future. Think of it as decentralized package manager. All these different clients already have their own lease management. They all have their own formats that they provide. Some have Dockerfired, some provide binaries, maybe not all platforms. Some need to run a script before they can be started. This was the first challenge for us to have this kind of communication with the client providers. How we can define good standards. The other big challenge for us, of course, they all have different hosting. So, we need to talk to a bunch of backends. And these are probably the most prominent and relevant backends. But they are all very centralized. And maybe in the future, someone decides, hey, I want to pass my binaries and IPFS. Or maybe something we don't know yet. And we wanted to not restrict grid. We wanted to allow all these projects to keep their lease management strategy. And we would adopt to it. And we needed to engineer grid in a way so that it's flexible for the future. And this brought us very quickly to the big challenge, which is security. How can we make sure that if we don't know the origin, or if we don't know the connection between the project and the origin, how can we make sure that the clients, that the users, that they are legit, that they're safe. And we came up with our own package signing scene. We have package format, specification, reference implementation, the CLI tool, and an EIP draft. And this all goes under the name of theme sign packages. And I will briefly describe why we are at this point reinventing the wheel and not just using package signing that is out there. So package signing is a critical piece of grid. And it has basically just two steps. Like you sign a package, you verify a package. In traditional code signing, usually you want to have a hardware device that stores it by the fees for your certificate. And these devices are usually purchased as a description and you pay up to $1,500 per year. This is difficult for open source because not everyone has these funds. Open to everyone. For if you sign packages, you can use your existing hardware devices that store your private fees such as your network. But you don't even need to pay something. You can also use to sign metamask to sign packages now. And then for the verifications there, sign packages have really nice properties such as authentication, integrity, and reputation. And you get the same Ethereum sign packages. But this is not all that goes into it. If you do the authentication step and you want to know who is the author of the package, I don't know it, you usually validate it against an identity or a certificate. And this is also part of the signup process. Before you can get the device, you need to register with a certificate authority. They issue the certificate and they do some background checks on you and you need to provide them with a lot of data. And this data is part of the package information. For if you sign packages, if you do the verifications there, you get an Ethereum address back, a public address. And this is cool for two main reasons. One is you can immediately send money to the address to be the author of the package. So now we can incentivize developers to actually sign packages and receive donations for this. It's not just that they have to do more work, they have to benefit from it. That's the main big step. The other thing is you can define your identity. So you can use some of these cool emerging identity contracts to just specify relevant information that's needed to make sure that people can trust you. And you can provide information such as your guitar handler instead of your company's address or your own personal phone number. We thought that this was really cool and we didn't just want to use it for the binary management, but we also started to sign our own software updates with it. Our user interface we packaged the web UI independently of the binary so that the updates get smaller. We signed these updates to make sure that it's secure. Then we thought, hey, maybe we can also use other applications like remix. So we made a test and actually uploaded remix to IPFS and downloaded it and started it in-grid. And this brought us to the next evolution, which is good apps. We thought that if we can in a secure way guarantee that these applications can be loaded, we can also extend it to applications that are not just provided by ethium foundation teams, but also other developers. And this is ethium apps, grid apps. Okay. So, grid is two main parts, right? The first are plugins, the second are apps. So what's inside an app and what does an app do? So an app can have a related client, an associated client, a package URL, client settings, and local URL input. So what does that mean? If an app depends and relies on, let's say, a graphical, that's the new graphical, new things for, again, we have an app for this. And it's specified on it that it requires GAT to be started. And it has the address in part of it and, of course, some settings around it. So it's like a manifest file to define how should that little piece of functionality should behave. But, you know, this all goes into a single file and this is graphical in it. So here we have, on the apps section of grid, you can click launch. And then if GAT is not started, it will prompt you saying, okay, the application graphical requires to start with those flags and then press OK to all this time. So now it works with the specific clients, but it can also work with client types. So it can be storage types. Okay, so we need to run this app with a storage client so you can just, you know, start your own favorite storage app, such as IPFS, Swarm. So a set package application that runs live, you've probably read this slide before. So we're mentioning that grid apps are not dapps. So the idea here is to provide lower level access to those clients. So you can have dashboards, you can have monitoring systems. You can even connect to several clients at once using some special API to be provided. So you can query clients and not with three providers. That's the main reason. So another example of the CLAP app. We made a UI for the CLAP, the Goetheum signer. And this is how it works. So we have here, to the left side and the sidebar, we have the CLAP client. So we just open it, it will prompt you. It has two requirements. One is CLAP itself. The other is GAP. So when you start this app, it will prompt you and then click OK. So we didn't download those clients if you don't have those all. So there's lots of things out in the hood. And then you can just approve and sign messages or transactions using this pretty app. Another example is the RPC Taster app. This one makes you test RPC calls for several clients. None of the gap, but you know, every client that we have today in Grid. So it's a really nice way to test, you know, oops, sorry, to test those methods and then to get returns. It's like a little postman for each year. And this is a small app. So we made it out of fun and not of grammatical purposes and then, you know, people can do their own. So Grid. It is to discover, download, update those with just one click. It can even detect requirements just such as, you know, in the case of BSU, you can do our own magic to make sure that you have it if you don't need to prompt you to, you know, go get it or you don't try to sell it. Easily configure your nodes with some sensible defaults. The metamask of presets and registries that allow for product plugins and integrations. And that means you could have such as a stream of plugins that are specific to your company if you work on an enterprise and that only your employees would see instead of having, you know, that preset that we have today can have, you know, your own custom stream of plugins. So we do have tutorials of things that you can do and accomplish with Grid. Here's the link. Have fun. So you can use metamask in a fully decentralized way. In that tutorial, we explained how to start GAT in the live client mode and then connected using metamask preset. And, you know, GraphQL, IDFS, you can open it using Grid. So, yeah, TUNAPStore and Modspad, onboarding developers, and the 2.0 folks. Thank you for your time, visit the team, and this is the URL of the website. We love you, too. Thank you. We have one more minute. One minute. What happens if you run two apps and they have conflicting requirements for the flags? You try to start GAT twice. Sorry. Oh, okay, that's right.