 I hope you had a great DEF CON last day now. Great conversations, really great event. I want to talk about Ethereum, opportunities, and obstacles on the Android platform, not Android, the robot, Android, the operating system, mainly from mobile. First thing is quite obvious. There are now a lot of Android devices out there. These are basically the sales curves of Android. And you see it's just rising. And the rest, which is not open platforms, is basically fading out. Zymbian, yeah, Gansun, other platforms, Gansun. Also what is very important for me, the growth is mainly because you can get Android very cheaply on the emerging world, basically. So it's very distributed, Africa, South America, India, which is close to my heart. And because there are now a lot of devices out there, you can use them also for different stuff. You can use that, for example, to make offline transactions. There are some projects doing that. The Parity Assigner is the most useful one currently. There's even a project AirGap that is completely focusing on that use case. And with Wally's, I also support that flow. What you basically do, you use QR codes to build an AirGap between your key and your computer, for example, because you don't want to expose your key. Very nice in the discussion before, where do you store your keys? There's a project that goes in a similar direction, but without the AirGap, basically, to connect the desktop wallet to a mobile wallet, where the mobile wallet has the key. And the desktop wallet just does the UX. And the depth display, it's a wallet connect. I highly recommend you look into that. And later on, that will also work for mobile to mobile. Currently, it's desktop to mobile. But later on, we also can do that for native apps to make mobile to mobile. Another really cool thing you can do with Android is, for example, to use a Trezor via OTG. If you have value that you want to protect, you should really use a hardware wallet. Also, these offline wallets that, like offline possibilities, which I described before, are not like a hardware wallet. A hardware wallet is much more, basically. It protects your key much more. And with Android, you have the possibility to use USB OTG on the go. You cannot, unfortunately, use that with iOS. But it really protects your keys very nicely. And with the latest generation of the Trezor, you even have USB-C. So it's really easy to plug it in, basically, before it was a bit a hassle with this OTG adapter. But now, just USB-C device, you always plug it in the right direction. Another thing that I'm really excited about now, and nice to see the team behind the status hardware wallet also here, is the status hardware wallet. I've just seen that now in the crypto-life hackathon from status. It happened just before in the deep-gable workshop there. And I'm currently implementing that in Wallace to support for that. They are really cheap. So in volume, you can get them for a euro, but in real volume. So now, low volume, like five euros, but they are really cheap. The problem is they don't have a display, but they can still fulfill a lot of really, really nice use cases. For example, imagine who of you has used an Ether card before. But so you had to enter, basically, all these words, which is kind of a nuisance. It was nice for the time, but we can use them. And just tap them on your phone and you're finished. So you can really easily onboard users with Ether. And then you still have a hardware wallet. It's a full computer. So the key is on that computer. In the current flow, it's exposed for a backup. But for the signing flow, this one is not exposed. So you have a full hardware wallet for a real, and not a hardware wallet without a display, but for a very, very low price. Also, that's unfortunately not possible on iOS. You can use NFC on iOS, but you cannot use this custom APT use. So you cannot use it there. Another point, if you use Android. There's also one thing. It's Android protected confirmation, because now it comes to what are you displaying, basically. That's quite a new thing you see in 19th of October this year. They were talking about it, and until it's rolled out, it will take some time. But the big problem is you don't really trust your S that much. For example, it could hide certain information about what you're signing, and you don't really want to do that. So basically, trusted confirmation, you have a confirmation apart from the main operating system, basically. And I also want to use it for bank transfer, but we should use it to transfer die to some ENS address. And then you also don't go through the touch screen. You go, basically, through the confirmation buttons to really have at least ATT&CK servers as possible there. Android is not only mobile. Android is also Android Things IoT. We heard IoT is a really, really big topic right now. You can now also deploy Android apps on Chromebooks. You don't get the full features from the Android operating system there, but you can reuse the apps you are writing. So people that know me, there's no talk without me mentioning Kotlin. Kotlin is a really nice operating language. You can write Android apps in there. And at the last Kotlin Conf keynote, they were mentioning there is now one in four apps out of the top 1,000 apps uses Kotlin. And Kotlin is not that old, but it's a really, really beautiful language. And also, there was recently the Octoverse. That's basically from GitHub Census. And now Kotlin is the fastest growing language on GitHub. And as I like dry code, I didn't want all this code in Wallet. So I extracted a library that you can also all use. It's called Ketherium, Kotlin Ethereum. Currently, it's mainly targeted for wallet development, key holding, signing, ERP 155, ERC 55, and so on. But in the future, I would also like to extend that to DApps. Now let's talk about decentralization. Really like that. That was a topic of the discussion before. One big thing is most mobile wallets currently rely on central services like Infura or EtherScan. Unfortunately, I also removed the LiteClient from or I moved it to a special flavor from Wallet because the user experience wasn't yet that nice. The problem is the LiteClient is working, but there's no incentive layer yet. So when people need to run full nodes, running full nodes is expensive. So not many people are doing that. But just at DevCon this year, Slocket presented the Incubed Client. And I'm really excited about that. It's a minimally verification client, so you verify. It has an incentive layer, basically, and you don't need to participate in the peer-to-peer chatter. They basically did it for IoT. But the same problems they had on IoT we have on mobile, limited bandwidth, limited resource computation power, and so on. So we can use that. Looking forward, they released it two days before at DevCon. And I really had to don't look into that now, attend DevCon. But after DevCon, I really wanted to get in. And I really hope fast to support that. Also, distribution comes with a lot of centralization. Most get the apps now from Google Play. So that's a problem. That's Google controls. And that's often what people say, yeah, on Android you have the same problems. Like, it's centralized, you rely on Google. I say, you don't rely on Google. Because it's an open source project, you can fork it, Android. But the store is a big problem. Fortunately, there are alternatives already. There is, for example, FDroid, which is an open source store. So only open source apps can be hosted there. And they check that. And not only does the app is open source, but all libraries downstream are also a Libre software. But you should go even further. Time envisioning a store, basically, which is completely decentralized with reproducible builds where we don't rely. Because it's also a central party. That's a bit of a problem there. But it's already a bit better than Google Play. Unfortunately, these are all the results for Ethereum. After it currently, that's unfortunately not that much. So we should really, really push there to get more depth and bullets to be on the store. So go to your wallets, push them, and say, go to FDroid and release your apps there. I want to talk about subtraction a little bit, because Aya was mentioning it now a lot, and I thought a lot about that. And also, for Burleys, I don't want a browser in there. You should, in Unix, there's this thing, do one thing, do one thing right. And I only want that to be, basically, storage for keys, managing for keys, and then other apps should interact with that. Now we're doing a test balloon with peep droid. That's basically a peep web client to try out this concept. So I think the wallet should just do the wallet stuff, and then native depth are communicating with that. We talked a little bit about that at the Ethereum Magicians, which was just happening before DevCon, which was really nice. All depth developers coming together and talking to each other. And really great. You can find the notes on ethereumagicians.org. Thank you very much for listening. This is follow-up. This is a site where you can reach me. This is the Wally's project. Have a wonderful rest of DevCon. Thank you very much.