EthCC 2: Dean Eingenmann

I'm gonna be giving you guys a talk on some of the updates we've been working at or working on at ENS over the past year I'm Dean eigen man I'm one of the developers and researchers over at EMS I guess don't use PDF so the first thing I'll be talking about is like a Year in Review then some of the documentation updates we've been working on recently some of you might have heard about a IP 1577 then about the formal verification stuff we're currently working on or starting to work on the DNS integration which some of you might have read about and then finally some of the changes to the route contract that we've been working on so just a quick year in review since last FCC we originally started with 8 public repositories we've scaled that up to 34 public repositories which we maintain not all are completely around ENS but there's certain other things like Seoul sha-1 our buffer libraries etc which many people have been starting to use in contributing to as well beyond like just the NS team last SCC we were pretty much three employees that was me Nick Johnson and Jeff Lau that's been changed to nine employees currently we started with the support for one TLD a year ago which was dot F and we now all may not currently support three TLDs which is dot X Y Z dot F and dot luxe [Music] we've also scaled from like 25,000 people or 25,000 resolver set function calls for addresses to 44,000 resolver set for address functions which kind of shows how much usage there is currently some of you or most of you have probably seen the redesign we've worked on over the past year which has been updates to our manager our entire branding and then we've deployed a fully new manager software which is like far better than the old one for some of you who might have used it before so to the documentation we used to have up until very recently completely different documentation and we're currently working on rewriting everything and making sure everything is documented in complete details so that people can really understand everything which is ENS that's been a task which Nick has been working on recently and I think continues to work on so that we really have good documentation then e IP 1577 that's an e IP I helped draft together with Nick which is supposed to make things easier or make hash is easier for crypto browsers to be able to understand whether a website is hosted on IP FS or swarm so that you can use ENS for websites what the AIP does is it introduces a new content hash field for e NS resolvers allowing for better defined systems of mapping names to a network and content addresses additionally the content and multi hash field are deprecated so the new resolvers don't contain that the standard is based on the normal multi hash standard where we have a type bit length bit along with than the hash of the actual content this is what it looks like as you can see the first section of the entire byte array is the storage system then the CID version the content type the hash function the hash length and then the actual hash that gets encoded into a byte array and then thrown into a resolver into the content hash field e IP 1577 is currently adopted by status opera and there is an open task in madam asked to get it integrated as well the current issue with meta mask is that the EIP integration was a community one so they don't have resources really to allocate to the integration so we're working on getting a bounty for that task for anyone who might want to integrate e IP 1577 integration formal verification this is like the next project which I'm going to be working on I'm gonna be working on formally verifying the registrar and the Reggie or the new Etheridge STR in the new registry in K that kind of helps us to ensure that functionality is as is and as we expect it to be then DNS integration so for those of you don't know about DNS SEC DNS SEC is the DNS security extension and what it allows us to do is it allows us to verify that domains exist in the DNS space meaning that we can validate those certificates bring them on to ENS and allow people to claim their DNS names on ENS the dot XYZ integration was the first TLD which we decided to do with that but as of recently we decided to expand that and allow for pretty much any TLD to be claimed we're currently testing this on curly and last night Nick decided to deploy every single TLD that was possible longer lis so for anyone who wants to test it with any dot IO domain or whatever girl is the place to do it this pretty much allows us to have one thousand three hundred and forty nine different TLDs on ENS so anyone who has a website and wants to accept payments and ëthe you don't need to buy an e NS name anymore you can use pretty much your normal domain which you were using anyways and accept payments to that domain then changes to the route this is one of the main projects which i've been working on over the past few weeks and months it allows us to take away the exclusivity which the multi-sig has on the ENS registrar or ENS registry and move certain components over to public functions for example like claiming DL TLDs was one of them it means that we don't need seven or four signatures out of seven to add a new TLD but anyone can pretty much submit the DNS SEC proof signature and a new TLD is opened up this is what it looks like so previously we had the multi stick to the ENS contract or the multi-sig own te NS contract and was the only one allowed to execute functions we changed that to being that the multi-sig owns a middleware contract known as the root and the root contract owns the ENS contract and the root pretty much opens up as said certain functions to the public so that we don't require those three out of or four out of seven signatures from the multi-sig that code is currently being audited by consensus diligence thanks to those guys for deciding to do the audits for us for both the root and the eighth registrar then to the registrar I'm not going to talk about this hence a question mark because Chris Remus is gonna have a full talk about it later on and he's going to tell you everything about how the new rent system will work etc so our plans or what's next right now some things on the timeline is deploying the permanent registrar and migrating everyone that's something we plan on doing shortly and Chris will definitely tell you more about the timeline and what the process is there and then really focusing on e IP 1577 further adoption making sure that people who are building gaps actually use DNS names with ipfs so that they don't use centralized domain name systems anymore and they start moving to this awesome tech that we've been building thank you for listening are there any questions I guess not okay thank you [Music]