 Hi, everyone. Thanks for having me. I'm Amir. I'm a private manager at CryptoSat. And what we do is that we build trust infrastructure for HEP3. And we do that by launching satellites that are able to run cryptographic computations. And before we get into that, we're just very proud to share the launches of our two satellites. The first one was of May of last year, almost exactly one year. And the second launch happened. This had to be very... So now we have two satellites in space that are able to do really cool things for web free applications. This is a little bit of our milestone. One recent thing that we're pretty proud of is that we participated in the KZGs ceremony this April. The Ethereum KZGs ceremony, what this means is that we got our contribution from our satellite and then sent it back to the sequencer. A little bit about the architecture, essentially these are CubeSats. So these are very small boxes that can fit on your desk. After we launch them into space, we're essentially able to provide a pretty standard REST API through our AWS infrastructure that is responsible for communicating with the satellites and making sure that your requests are responded to. And with that in mind, I think we're ready to jump into the demo. This is the Cryptosat simulator. What this does is show us where our satellites are in relation to Earth. These are low Earth orbit satellites. So essentially they change sometimes depending on the time of day. So they have to be in range of a ground station for us to be able to communicate with them. That's obviously something that a lot of users are thinking about before being able to adopt this in production environments. And that's also something that we are always improving based on launching new satellites. Our next launch is scheduled for this year. And also with every launch, we also improve our capability to communicate with the satellites. Since this is a company called Cryptosat, I think the first thing that people are interested in is what is the way to communicate with the satellite? So the first way to know that you're communicating with the satellite and not when anything else is using the Cryptosat public keys. This is a key that anything that is provided by the satellite will be signed with. I can also present it in a better way. This is a public key. If we want to verify, and we will in the next section, this is how we verify that what was provided to us was actually signed by the satellite. I should have mentioned before that this is a key that was generated in space. So it was never on Earth. Once the satellite gets launched, we run a key generation when published on the public key. So the private key was never on Earth and never will be. Example, the idea being that if you want a timestamp for the satellite, the satellite check of its own time, it will return it. And you can also verify that the timestamp that you received was in fact created by the satellite or sent by the satellite. A next use case that is recently we've seen some interest in is your standard randomness. You've probably heard of TTRAND. The idea here is that you can request a public random number from DRAN. So I'm sorry, I'm going to set and then verify that indeed this was a random number that was generated by the satellite. Here we're talking about a different flow where it'll be a private random number. Essentially how this would work is you would create a client. You would create a key pair on your computer. You would give the satellite the public key and the satellite will encrypt the timestamp with the random number with your public key. So only you have access to that random number. So pretty long flow. So in the sake of time, I will skip through it. This is a demonstration on how the satellite can sign messages on behalf of users. Pretty similar to what we started before. A nice use case here is the telling encryption. If you have ever thought about like seal bid option, for example, this is where this can be an interesting use case. The ability to create a key pair, publish the public key, everyone can encrypt their bids before the time expires. And then once the time expires, the private key will be placed and the results of the option will be done. We also have a test board where we do a little bit more debugging the people that are trying to use it. But they need some help, for example. That's a great place to go. And obviously, we're on Twitter and LinkedIn too. So I'll share all the info right after the demo.