 My name is Nick Johnson. I'm the lead developer for the Ethereum name service, and I'm here today to give you, thank you very much, here today to give you an update on what we've done in the last year and what we're up to now. So first for the few of you in the hall who may not already be intimately familiar with the Ethereum name service, what is it? The ENS is a naming system that solves what we call Zuko's Triangle. It's a trilemma that says no naming service can be human meaningful, decentralized and secure all at once. And for a long time, people believed that was probably true. The advent of consensus systems with blockchains has made that untrue. And following a named coin's footsteps, we've been able to launch ENS, which satisfies all three of those properties. And so ENS is the Ethereum name service. It's a naming service built on Ethereum, but that doesn't mean it's just for Ethereum. It's not for naming just Ethereum resources. You can use it to name IPFS content, swarm content. You can use it to insert text records. You can use it to point to onion sites, as I'll show you later. So we really want it to be the new naming service for the internet that satisfies all three of those important properties. So today I'm going to talk about what we've done in the last year, how things have been going. I'm going to talk about our migration process to the permanent registrar. I'm going to talk about the short name auction process, which is underway currently. Then about DNS namespace integration, which is how we're making it possible for you to use your DNS names inside ENS. Our IPFS and onion integrations, and then a brief preview of the things we're working on now and what we're looking forward to launching in the next year. So first of all, the last year at a glance, this is the number of names registered on ENS, how it's evolved over the time since we've launched. The top line there in the blue is the total number of names in the system. The second line there in the red is the number of names with resolvers set. And the third line is the number of names that resolve to addresses. So as you can see, we've had steady growth in the nearly three years since we've launched. And let's drill down on that a little bit. October 2018, so this time last year, we had 224,000 names registered. And this year, that's up to 310,000. But I think the other two figures are the more interesting ones. First of all, we've got the number of names with resolvers. And so this is the first step in setting up your name. You first buy the name and then you set a resolver contract for it. And if you're buying the name just to speculate on it, to sell it to somebody later for more, there's no reason you'd set this up. So this is a reasonably good metric for actual adoption and use for ENS in the wild. And so it's gone up from 28,000 this time last year to 60,000 now. And it's not just an increase in absolute numbers. It's an increase in percentage from 12 and a half percent all the way up to about 20 percent. So we're really pleased with that and we want to keep monitoring this and we hope it will continue to grow. Likewise, names, sorry, addresses aren't the only thing you can translate ENS names to. But they're probably the most popular application at the moment. So we can monitor similarly the number of names of the addresses and that's up from eight and a half percent a year ago to 12 percent today. So we're really encouraged to see that this growth in ENS isn't just more people speculating on names, more people hoping to make a profit off reselling them, but it's more people actually using them for their intended purpose. So next up, I'm going to talk about a migration process. So in May, on May the 4th, we launched the new permanent registrar. That replaced the auction registrar, which required a lengthy auction process in order to register names with the new instant registration. So when we launched that, there's a one year migration period. During that period, anyone who owned a name on the old registrar can migrate it to the new one. And when they do that, they get their registration extended until May the 3rd, 2020, and they get a full refund of the deposit they put down to originally register the name. You also have the option to just release the name. You can do that and you get deposit back, but then the name becomes available for registration by others. So there's a one year migration period. The new registrar supports instant registration with just two transactions. And in order to keep your name, you have to pay $5 a year per name rent, and there's no limit on the renewal periods. So for instance, somebody has registered Walmart.Eath and ProtocolEath, and they have paid the registration all the way out to 2040, which means that that name is absolutely solidly locked into the system at least until then. So we've had 10,000 new registrations since launch, and the migration process is interesting to look at too. So on migration day, E&S had 309,000 names registered in it, and there was 176,000 ether locked in the deed contracts. So when you bid on the name on the interim registrar, you had to put a deposit down and you get that deposit back when you release the name or you migrate it to the new registrar. So how are we doing today? Today, we're down to 241,000 that haven't been migrated or released. We had 4,000 about 1% were released and 59,000 about 19% have been migrated. In terms of the ether, it's actually even less. There's 13% of the ether deposits have been returned and 86% are remaining. And you can sort of see the progress here with the exception of a blip around the middle of the year. It's been reasonably steady, but it's actually tapering off a little bit. So if you have E&S names that you registered before May 4th, 2019, there is free money sitting there waiting for you to claim it back. Release your name or migrate it, which is the better option to the new registrar. You'll get your registration extended and you'll get all of your deposit back. And we can stop sitting on all of this ether that's doing nothing. So next up, the short name options. We have been moving on with making shorter names. Three to six characters available via OpenSea. And some of you, probably most of you will be aware that we had a slight hiccup a week or two ago where somebody managed to obtain a number of high value names without paying full price for them. So I'm going to go into a bit of detail on just how that happened. What you're seeing here on the screen is an example of an OpenSea order message. So OpenSea works by people placing bids by signing a message offline and sending it to the OpenSea API. And that message contains a number of important fields, such as which exchange contract to use, who the maker is, the person making the bid, who the taker is, that's our contract, how much they're willing to pay and so forth. It also contains the target address, the address that should be called if the bid's accepted, and the call data for it. And we believed that OpenSea's API was validating all of this data. We also had a series of additional checks of our own against many of these fields. Unfortunately, we were mistaken and they were mistaken and neither of us was verifying the target data, which is embarrassing. The result was that somebody was able to place bids that were ostensibly against one low value name that ended quite soon, but in actual fact, would finalize another name. So by bidding on fubar.eath, they were able to finalize defi.eath before that auction should have ended. So that resulted in them obtaining 17 names and for very small bids in each case. So what we did, we obviously stopped the contract. We made an offer to them. We said, if you want to return those names to us, we will re-option them the way they were supposed to be auctioned. And we'll provide you with a bug bounty of 25% of the final sale price. And I'm pleased to say that they accepted the offer. They returned the 17 names to us and those are now back on auction. So if you are here, thank you very much. If you want a security consulting job, please talk to us. There was a second smaller issue with the auctions that we've also resolved while we were paused. And that was that some bidders were given the wrong information in terms of what fields to fill out in the bids. So if you were using the user interface via web browser, this was absolutely fine. But if you were using the SDK integration, if you were sending bids yourself with an automated solution, you may have been submitting bids with the wrong target field. We identified the roughly 30 or so auctions that were affected by this, where the top bid was a bid that didn't have the right target field. And those auctions have been extended a little further to give those users an opportunity to place valid bids that replace them. And if you were affected by this, you will have received an email that gives a full description of how to do that. So the short name auctions in general, we auction off all three to six character length domains in partnership with OpenSea. We sort of looked at all the effort we put in for the original auction contracts. And we went, well, we're not an auction business. We're trying to do naming. We're trying to build a naming system. We don't want to put hundreds of hour hours into building a system that somebody else has already built and they already know how to operate it. So we partnered with them in order to do the name allocation. So most five to six character names, all of these names are on auction now. The five to six character ones are ending between the 15th and the 22nd of October. Four characters a week later, 22nd to 29th and three character names, the shortest ones, ending between the 29th and the 15th of November. If you're interested in getting a name that represents you, some of these are quite contentious, but many of them are going for the minimum of five bucks a year. The auction process exists in order to make sure names are fairly allocated. But that doesn't mean necessarily your first name or your last name is going to be popular amongst a lot of other people. So if you want to get it, go there, have a look and maybe snag yourself a name that represents you. So next up, I want to talk about the DNS namespace integration. So, ENS is more than just .ETH. .ETH is the namespace that is native to Ethereum that we sort of completely control. We can enforce strong contractual guarantees on it, but it's not all there is. We believe that ENS exists as part of the global namespace, the same namespace that's inhabited by .COM and .XYZ and .TV and so forth. And so we're doing our best to integrate with that. And there's two ways we're doing that. One is a permissionless integration via DNSSEC, and the second is bespoke integrations with top level domains that are working with us. So first of all, how does the DNSSEC integration work? It permits anyone who has a DNS domain, like mysite.com, to register the same domain on ENS. So that means that if you have mysite.com in DNS and that's your website, you can also have mysite.com in ENS and people can pay you by typing in mysite.com. They can load up your smart contract by typing in mysite.com into any wallet or any application that supports ENS. So to set this up, this is deployed right now on .XYZ and that's our sort of test domain. We're gonna roll it out to way more top level domains like most of the 2,300 top level domains early next year. But right now, if you have a .XYZ domain, you can go to app.ens.domains, which is our new URL for the manager. You can enter your domain name and it will provide you with a series of instructions for setting it up. The second sort of integration we're pursuing is the individual bespoke ones. So these are top level domain providers who've decided to work with us directly to make it easier for their users to integrate with ENS. And the first of these was .lux. They launched a bit over a year ago. They have first pass support for ENS, which means that if you register a name with them using one of their supported registrars, you can go into the control panel into your ENS Serial Ethereum address, hit go and it's just done. It's several steps shorter than the DNS second integration. It's as simple as it could possibly could be. So if you're interested, get one of those and you can instantly start using it anywhere that a ENS name is accepted. The second integration is slightly different. We're working with .cred, the TLD, to support DNS record integration. The idea is that we can host the DNS zone for .cred on the blockchain. And effectively, this turns every Ethereum node in the world into a secondary name server for .cred. It means that if you have a .cred domain, it can't be taken out by, or the DNS servers can't be taken out by denial of service. It can't be taken out by service failure because anyone in the world can replicate those records and serve them up and verify them for themselves. Finally, we're also working with .art. You might be familiar of the .art's digital twin. This is their project to have physical artworks that have a corresponding existence on the blockchain, the form of a non-vungible token. We recently enabled their namespace on DNS, so they'll now be able to offer domains via DNS. Next up, we've been working with the IPFS team. We've got a generous grant from them and we've been working with them and Jim McDonald to build integration, closer integration, between IPFS and ENS. The way this works is you can point any ENS site on .eath or anywhere else at an IPFS content. And if you use it right now in MetaMask, it will just resolve. But you don't have to be running MetaMask for this to work. We, the ENS team, operate a DNS and an ENS and IPFS gateway on eth.link. So if you add .link to any eth domain and that domain has IPFS content, it will load in any browser anywhere in the world, no special integration supported. So as an example, go to almonot.eth.link and it will load you a directory of decentralized websites that you can access anywhere. You can operate your own gateway. You don't have to trust us to correctly serve up the right DNS records and IPFS content. You can run this yourself. And finally, something that we got working just in the lead up to this, we have a DNS over HTTPS gateway. If your browser supports that, you can point it at our servers and your browser with no plugins, with no special support, will start resolving .eth domains in the browser as if they were top level domains in the global route. And we're also been doing some integration with the Tor network. So we had a hackathon project in eth new York, a project called S Torgate, and building on that, ENS can now point at onion hidden services, which means that you can take an ES domain and point it at any onion hidden service. For instance, example, Facebook Tor.eth was set up by us, the ENS team. And when you go there, it will load the Facebook hidden service. If you load it in a browser that has both Tor and ENS support, such as the Tor browser with MetaMask. And if you look at the records for Facebook Tor.eth on our manager or on etherscan, you'll see that they're actually owned by nobody. And what this means is that once it's been set up, it is permanently that way. You don't have to trust that whoever set it up is not going to redirect it to a phishing version of Facebook tomorrow, because that resolution is now locked in. It's set in stone. So last up, finally, what are we working on next? So the first and biggest thing that we're working on right now is multi-chain support in ENS. It's EAP 2304, if you want to read the standards document. But what it means is it's a way for encoding addresses for multiple chains, for Bitcoin-based chains, for Ethereum-based chains, for EOS-based chains, for whatever you want in an ENS record. And that means that ENS can become the naming service not just for Ethereum, not just for internet resources, but for every single blockchain out there. So in supported wallets, if you have a Bitcoin wallet, you'll be able to use myname.eth or myname.com or myname.xyz to load your Bitcoin address or your EOS address or your Litecoin or Dogecoin or whatever suits you. And we really like to thank BinanceX for giving us a grant that helped us get this past the line. So we wrote the CIP about two weeks ago. We started sort of talking to wallets and so on, and I'm delighted to say that we already have so much support. Descent were the first to launch support, so thank you very much. And I want to specifically call out Bruntly, our outreach person, because some of these have arrived just now, like literally minutes before the talk. We now have Coinbase wallet, Trust wallet, I am token, Haven, MyCrypto, Portus and Opera have all committed to add support for this in their wallets. Just like I think it was amazing. And if you're building tooling and you want to do this yourself, the ENS libraries on JavaScript will support it, but Ethas.js is adding support almost immediately. So if you don't use it already, I suggest taking a look at it. If you do, then you will just be able to use this straight away. What else are we doing? So as I mentioned, we're rolling out DNS support to most TLDs. That's effectively every internet top level domain that has DNS sec enabled, which is about 80 to 90% of them. We're working on more manager improvements, of course. That's our ongoing work. We want to make it, for instance, easier to do multiple operations, updates to resolvers and a single transaction. We're working on improving the manager interface for short name registration. Again, fewer transactions. And of course, once the auctions are over, you'll be able to register three to six character names just as you can seven plus character names today. Adoption, adoption, adoption. It's unsexy in a way, but our main job now is making sure that DNS is as ubiquitous and universal as it possibly can be. And that means making sure that every wallet supports it. Every tool chain supports it. It should be the default. You should be able to write a DAP and not even know about DNS, but just have it work because your underlying tool chain already has support for resolving DNS addresses. So, want to hear more? We have a little more detail. If you'd like to see more about how we're reaching out past just a name resolution on Ethereum, then come see Bratley's talk tomorrow. It's 9.35 in the convention room and we're talking about how DNS is taking Ethereum to the rest of the internet. And that's all I have today for you. Thank you very much.