New Ethereum talks, every Monday. The week's conference uploads by event, in your inbox.

Loading player…

ETHWarsaw 2023: Muhammad Tunrikulu, ENS - CCIP-Read

ETH WarsawMon, Oct 7, 2024, 12:00 AM

Presentation - A brief talk by Muhammad Tunrikulu about the Ethereum Name Service (ENS). Discover the key roles of human-readable addresses in the Ethereum ecosystem. Follow us for more updates: https://twitter.com/ETHWarsaw

Transcript

yeah hey everyone uh I'm mamed tanu working in ens as a fullstack developer and this is my handle or favorite handles and on the right uh yeah on the left right uh this is the the C that we were issuing in the the couple of different events and I don't know how many of you have those cars or how many of you have the ens names uh none oh actually yeah there are a lot so uh we were actually planning to do this in this event too but there wasn't much time so unfortunately but for the next one for sure especially if you are joining into Dev connect Istanbul we will have the cards uh today I will talk about the CCI read and just before that a little bit like what is enss and what ccip does and some key components and use cases the ethereum name Service uh like uh probably most of you already know uh just in case uh so the ens is just like uh the regular like traditional domain system uh it Maps your uh information uh through the like human readable names to the machine readable quotes or the names basically uh just think like a regular domain when you go to google.com you don't write the IP address of the the server instead you just write the domain and the DNS service resolves this information for you so we do the similar thing in ens uh through the blockchain basically instead of using a digital sorry the like um the alpha numeric characters for your wallet you are able to use ens and then then anybody can just send you a um token the assets or you can basically uh use it for the sharing with the people instead of checking those addresses and uh this is the one use case the another use case is the ens is your the web tree profile so instead of the registering all the profiles through the the other decentralized applications basically when you connect with your wallet the all the information retrieve from the blockchain and you can just add or edit or remove all this information that belong to you and everything is on chain and the third uh use case is basically it's a it's just like a traditional domain you are able to create a website over the ens and through the gateways it resolves like uh probably you heard about the decentralized storages like ipfs rwa and these kind of storages so if you put uh your content into those decentralized storages and have the content hash you can store this content hash under the ens and uh the all the supported browers will resolve the ens name for you uh in a um let's say censorship resident Manor and the main topic CCI period uh cross chain interop operability protocol the secure data retrieval uh the CCI read uh is a protocol uh crafted by the the founder of the ens Nick Johnson and uh this is for basically the reading uh and information from onchain uh sorry from offchain to onchain or from onchain to onchain so what what does it mean uh it means that uh sometimes uh doing uh some verifications some Pro like proving something in chain is super expensive and uh in our case in ens uh we are like in ens we are not a competitor to DNS we are extending the DNS so we want the the DNS owners to be able to uh import their DNS names into ens and use all the features that they have in the ens basically just like it and uh the thing is uh when we tried to do that there was a huge problem of the verification basically or the the DNS SEC proof it was super expensive and it's still super expensive if you try to do it own chain so like you have to pay hundreds of bucks for the the the fees and everything uh to solve this problem we were uh thinking about what to do what to do and just we came up with this protocol uh basically it works in a way uh we just use one little trick from the smart contracts uh basically just reverting a custom error and implementing a custom uh Behavior to the clients that as we know as like atgs weem and this kind of libraries so how we do that we basically ask the smart contract to resolve an address and then the smart contract checks if this address is available and if it's not it just goes to the uh sorry it just reverts the information about you know like I don't have this information but you can find this information with the proof in here so we are literally addressing under the error and then uh this error goes back to the client and uh then the client sends another request to the uh to the information to the Gateway so we have the sender information who is us and the Gateway URL who is like where we going to like which is where we're going to get the information from and the call data basically like what kind of information we are looking for and the Callback function who is going to check this proof and if it's correct and the extra data some additional information and later we do a request to a Gateway and asking you know like we are looking for the records and then if uh This Record is available please send me with the proof and then we get the proof and we are using this callback function selector and just call the resol resol call back and the resol call back checks for of verification and if everything is correct it just returns to data so this is how we are handling the offchain information and as you can see there are two topics here like one offchain interaction and the second thing onchain interaction uh which means that the the Gateway is depend on your setup so either you can keep all the information in just in some traditional database or you can basically write your information in any other um L2 blockchain and then get the information from there and uh so how the the others or how others in ens using this uh feature so possibly you heard about the coinbase wallet and when you register through the coinbase it asks you to get a handle and this handle is a subname and uh so basically uh if they would do this onchain they had to provide they had to just register all the subnames through the you know like the regular transactions and pay G for each members but uh with CCI period they are just keeping all the subdomains Recon offchain which means that they are just like having their own infrastructure for it and there are some other uh the projects as well just using the ccip read here as you can see like the origins and lens and uh in the future the the some of them are planning to just switch from offchain to the onchain like for example for Co coin base they want to use the base as an L2 option so they will have their own subdomains like they will just transfer the subdomains to their own uh chain basically and uh recently there was a post from wiic the how ccip read will help ens to scale through the L2 and this I would love to go in detail but I don't think I can do that in this short time I'll just quickly explain that it's all just the same structure as I showed in the I don't know like two three slid ago so like before it's just like uh basically from here like we are asking we are asking contract that like if I have the subdomain and the contract checks and say that no I don't have it but I don't I have any information like where where can you find it and then it goes to a Gateway and the gateways goes to the L2 any L2 I don't know it can be base arbitrium optimism like whichever you think and then the from the L2 we get the Merkle proof and the this time is not an offchain it's an onchain layer as you can see and this Merkle proes go back to the Gateway and the gate Gateway just use the call callback function to prove that this Merle proof is wallid and in Elva L sorry L one layer we are just checking if this Merle uh proof is correct or not if the proof is wallid we just send back the value if it's not we just return the error so basically this is how we're going to scale on different uh l2s and uh yeah these are some some other examples I don't know I just put it right after it should be before so uh basically like all this the subnames are like you are able to just resolve it through the wallets so they are just wallet DNS names yeah if you are interested with the protocol or anything about like how we're going to scale so please contact with me uh I would all to have much more detail but with the short time of period that's it [Applause] so

Automatic transcript — names and jargon may be misspelled.