 I'm talking about how ENS, the Ethereum name service, is taking Ethereum to the rest of the internet. OK, so our name, obviously, is the Ethereum name service. I want to explain what this means, because this is going to, I think, explain a lot. So how is it a name service? Naming services are things that people don't think about very much. It's kind of something in the background. And a lot of people actually misunderstand how they work. So a naming service is just a lookup system. That's it. It doesn't do anything else. You provide a name, it provides you with information. That's it. People overcomplicate this. Your computer might then do something with that information, but that is separate from the naming service. So for example, with ENS, a lot of people think that if you're sending to an ENS address, that ENS sends the transaction on to them for you or something like that. Nope, all ENS does is it tells the wallet which address to send to, and then the wallet sends the transaction. That all happens in the background. The user doesn't see that. That's what's really happening. So why do we have naming services? Obviously, computer identifiers, what makes sense for computers, what makes sense for humans, don't mix. The internet already has a naming system, a domain name system. So even for blockchain things, why don't we just use DNS? A lot of people that I've talked to haven't even thought about this. DNS could provide naming for cryptocurrency addresses. It's a naming service. It can provide naming for anything. So why don't we? Because DNS launched in 1985. It's fairly insecure. It's fairly centralized. And so it doesn't go along with the values of the blockchain world. But I just want to point out that DNS could do all these things for the blockchain world if we wanted to use it for that. So DNS is a naming service. It has names, owners of names. It has records that can store any information. If you have a name, you can look it up. You can do something with that information. But this is key. It can store any information. It's not just for Ethereum. So why is it the Ethereum name service? It's not because it's a naming service only for the Ethereum ecosystem. It's because it's built on Ethereum. This is common confusion. If you're thinking, hmm, if it's confusing, why don't you rebrand? Well, we're thinking about it. But right now, this is very important to understand. So just it's called this because the logic and records are stored on the Ethereum blockchain. But it can store information relevant to anything. So Ethereum is just like the infrastructure in the background that it happens to run on. But that doesn't restrict the types of information you could store on it. You could store phone numbers. You could store your home address. You could store a Bitcoin address. You could store anything. It's a common misconception that it can't. We have this right on our website. It's been there all along. So why do we use Ethereum as our back end? That's a good question. There's other blockchains out there, even if we wanted to have a naming service built on a blockchain. Here are some advantages. Ethereum has a very high security built into it. If we were making our own chain or something like that, we'd have to bootstrap security. It would be low security. It'd be probably less decentralized. Ethereum, we can build on Ethereum. It has high security and decentralized right out of the bat. We can benefit from all the ecosystem infrastructure. It's like Metamask and Fiora. I mean, tons of services that we benefit from right away. We don't have to reinvent those things. We benefit from standards. So all .eath names are actually ERC 721 compliant. So .eath names can just plug into NFT markets. That's a benefit that we have from being on Ethereum. Programmability. So you have things like conditioned ownership of name or something that's time locked for a certain period of time. And also interaction with other contracts on Ethereum. This is extremely powerful. The fact that E&S can do this. If we were building on our own chain or on a different chain, we wouldn't benefit from the Ethereum ecosystem in this way. So we think this is why Ethereum is the best place to be building a blockchain-based naming system. So to kind of sum up, E&S uses Ethereum to serve the internet, including and beyond the Ethereum ecosystem. And as a result, our goal is to make E&S and therefore Ethereum a basic piece of internet infrastructure used widely by people, whether they are part of the blockchain community or not. And the rest of this presentation is about how we are doing that. So of course, we do support the Ethereum ecosystem. I don't want to give the impression that we're moving beyond the Ethereum ecosystem. That's still a core thing that we do. That's kind of our bread and butter. But E&S does much more than that. And many people don't know that E&S does much more than that. So I'm going to be talking about, more in detail, all the non-directly Ethereum-related things that we support. OK, so IPFS, Interplanetary File System. IPFS is a peer-to-peer decentralized file system, file sharing protocol. E&S is a decentralized naming service. So together, they are the decentralized web. We actually have a partnership with Protocol Labs, a building out infrastructure on this and promoting this kind of duo of protocols. We already have native support for this pair of protocols in Opera. And Brave says they are also working on adding this. So we are getting a native browser support. But if you're using a browser that doesn't have native support, we benefit from MetaMask. MetaMask supports this. So if you are using Chrome, Firefox, Edge, Brave, or even the Tor browser, which I'll be talking about here in a second, you automatically support this decentralized web. And you can try it right now, actually. So we recommend this is a great starting place, almonit.eath. You have to put a slash at the end if you're doing it in MetaMask. So it will recognize it. If you type this in, it'll load up. And this is a directory of decentralized websites. So this is a great place to start. This works right now. We also have a project called ETH DNS, which is a bridge between DNS and ENS plus IPFS. There's much more that can be said about this. We actually just published a blog post yesterday with more detail, so go to our medium, check it out. But for users, the bottom line is we own ETH.link on DNS. We've set up a special server there. So that if there is a decentralized website and you don't have MetaMask or you're not using Opera, you can still access it. Just add .link to the end of it and it will resolve like a normal website. So this is a great way if you want to put your dApps front end on IPFS to make it accessible via ENS, but you still want normal people to be able to access it, use this. So tor.online addresses. So tor.online onion websites have been around for a while. They have a naming problem. They have the same naming problem that normal websites would have that they have an address to find the server. They need a naming system, but they don't trust DNS because DNS is insecure. It's centralized, right, and tor is all about security. So right now, if you wanted to go to a .online website in the tor browser, you have to go to something like this, right? This is very non-user friendly. ENS solves this problem. So ENS is obviously a decentralized secure naming solution that works today and we've added support for .online addresses in our records and you can use this in the tor browser if you have MetaMask. So the tor browser is Firefox based and if you add in the add-on MetaMask and you type in a .eath name that has a tor.online address in its records, it will resolve to that tor.online website. So this works today. You can try it right now. So we actually set up 10 of these addresses to kind of show off this functionality. So like duck.go tor.eath, Facebook tor.eath and all these here. And we actually set these up and then we gave up control of them so we can't change the addresses here. So this actually is showing off another functionality of ENS. This is to prevent phishing. You know, if I set this up, I could set it up correctly. You could start using it and then I could, if I really wanted to be bad, I could then change it to a different address and then you might not know that I changed it so you're going to and I could go to a phishing website or something like that. I can't do that. So actually nobody owns these addresses, but they still work. That's something you can't do with ENS by the way. Somebody always controls the ENS records. Ahuiz, we actually just launched this with text records in our manager. You can now put it to any ENS name. You can put like an email address, website, a link to an avatar, a description, anything you want. Like if you're trying to sell a name or if you just want people to know who you are or however you want to use it, this works right now. And we're going to be adding the ability to put custom text records very soon. This is what it looks like in our manager. Other cryptocurrencies. So you would have heard about this yesterday if you saw Nick Johnson, our lead developers presentation. But we just added multi-coin support on Mainnet. It works right now, at least on the ENS protocol level. And basically it works the same way as with Ethereum addresses. You just store like the Bitcoin address or EOS address or something like that in the record. And then the wallet, if there's someone types in the name, can grab that address and then the wallet sends the transaction, right? Some people are like, well, how does that work? Because it's on a different chain. Well, it's just where it's being stored. So for any cryptocurrency, any arbitrary cryptocurrency this works for. And we have a wallet that's actually just about ready to launch this. They said that their beta version of this would be launching either today or the next couple of days. And then in a normal production mobile app by the end of the month, a decent wallet. This is a hardware and mobile wallet based out of South Korea. This is their website, decentwall.com. They support a bunch of different currencies. And they were really great to kind of partner with us to kind of build this new functionality. And actually I want to show a video of this. Oh, darn it. Okay, we're not on a different computer. So we had a video of this working, a demo on Mainnet. You can imagine how it works. Exactly the same way as the theorem addresses but with Bitcoin addresses in this video. Sorry, we had to switch computers. Okay, but we have commitments from more than just decent wallet. We actually have commitments from seven other wallets to add this functionality either in the next couple of weeks or months. They are on board with this Coinbase wallet, Trust wallet, I am token, Haven, MyCrypto, Portis and Opera. And we are also in discussions with other wallets. So we'd really like this to be the standard for all wallet naming. And if you are involved in another multi-coin wallet, please let us know. We'd love to work with you on this. And this new functionality was actually funded by a grant from BinaxX. So thank you to BinaxX. We really appreciate the support. Okay, we are also working on DNS namespace integration. So this is really important to understand. A lot of people think that ENS is .eath. It's not, like banish that idea from your name. Banish the idea from your mind, okay? ENS is not .eath names. ENS is a naming system infrastructure. .eath is just one top level domain that happens to work on it. But any name could run on the ENS infrastructure. This is completely separate things that you need to have separately in your mind. So this distinction also holds true for DNS. So there's like the DNS infrastructure and then there's the DNS namespace, completely different. The namespace could remain the same even if the infrastructure changed, okay? And so ENS could support in principle any name. And this is exactly what we're trying to do. So we've actually devised a system so that if you own a name on DNS, only the owner of that name can claim use of that name on ENS. Not with .eath, but with the same top level domain. So for example, ethereum.org, the EF could, if they used our system, which is coming out here very soon, could have a DNS record and an ENS record for ethereum.org. Not ethereum.eath, ethereum.org. And we use something called DNSSEC to do this. I'm not gonna explain this in detail, but it's a pretty clever system that Nick Johnson came up with here. And we actually, this actually works right now for .xyz. So like Argent Wallet uses this, .xyz was kind of our test case and we're now confident in the system. We're gonna be rolling this out to all other DNS that can enable DNS top level domains, which is all the ones you've heard of. We also have some special use cases for these other top level domains.lux.cred.art. Oh yeah, so some people said, well, if you're gonna integrate the DNS namespace, why do we need .eath? Well, because .eath is native to ENS, it has special properties. So DNS names will still be subject to DNS controls because ownership goes only one direction. So whoever owns the DNS version of it owns the ENS version of it. But because .eath names are native to ENS, they have individual ownership and are not subject to the same controls. Some people ask about our relationship with ICANN. I'll just say a few words. It's friendly. We've gone to their conferences. We've given presentations. Almost everybody is very open and receptive to ENS. In fact, people approach us to, hey, we wanna work together. So we think there's a lot of potential to working together there. Also, this is a key thing to know. ICANN is not monolithic. Some people will say, this is what ICANN thinks or ICANN does. ICANN is a lot of different people who think different things. They don't always agree. So keep that in mind. All right, I'm gonna skip this. Running low on time. New DNS are our type. We are working on getting a new record type in the DNS system for Ethereum addresses so we can standardize our process for claiming DNS names on ENS. But this could be used beyond ENS. Just want you to be aware of that. And we're also working on getting eath.arpa. Domains are used for basic internet infrastructure and we are working on getting this for use for the whole Ethereum community. This would be another kind of a semi-official link of Ethereum to legacy internet. And then we're also working on traditional DNS records. Our public resolver actually supports this right now but we have a project going with .cred.cred as a DNS top-level domain. They have agreed to work with us to build a system to use ENS and IPFS to host all of their traditional DNS records for their whole namespace which would be an incredible kind of first step towards having ENS be used for that use case. So we are very excited about this. It's really, it's amazing they've agreed to do this with us. We've talked to lots of other top-level domains who are kind of interested but they tend to be very conservative. So they're willing to experiment with us on this and we're very happy about that. So that's it, thank you very much. Here are some important links. And we have one minute if anybody wants to ask a question. Yeah, so just run up to the mic here and we have time for maybe one or two. I can also talk, we can also talk afterwards. We have some of our developers here as well. What happens if DNS want to add .eath names? Are they going to? I mean in the DNS route? It's currently reserved as a three-letter country code for Ethiopia, although they are not using any three-letter country codes. They're just like reserved in defense. And I've talked to people who say that they're actually probably not going to give them to the countries. So at some point we might be able to get .eath as a GTLD but that may or may not happen. Okay. So it's probably unclear that ENS would ever be able to get the .eath TLD. So the main issue is that for you to be an I can't approve TLD, you must abide by something called the Uniform Domain Dispute Resolution Policy or UDRP, which basically says things like copyrights and trademarks are enforced. And we're not really going for that. We technologically can't do that without ease. Yeah, yeah. So I imagine that's probably just gonna be like just a non-starter. So I'm kind of hoping the idea that you could have some I can't approve TLDs that do enforce trademarks and then some that don't. But they have a very strict requirement that anything within their route does enforce trademarks. Right. I mean, we'll see how that goes. Right. Yes, last question. About the hardware wallet integration, does the hardware wallet actually display the .eath name when you confirm? The what wallet integration? With hardware wallets that are using ENS? Hardware. Yes. Like on the device it displays. I don't know if it's on the device, good question. But in their mobile app that uses their hardware wallet. Okay, I was just gonna ask because it's very hard for hardware devices to authenticate ENS entries because they can't see the blockchain. So they don't know the current state of the ENS name. And because you can't do multiple function calls inside of a single transaction, you can't just assert that the address is actually an ENS name. So I was curious how you saw it. Oh yeah, no, it's all on the mobile app. Okay, thanks. You would have seen that in the video. I'm sorry the video didn't work. Okay, thank you very much.