Ethereum Cat Herders PEEPanEIP, 1 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PEEPanEIP #106: ERC-4804: Web3 URL to EVM Call Message Translation with Qi Zhou

Description

Topics covered
-------------------------
0:50 - About EIP
1:05 - Meet the author
2:14 - What is Web3:// Acess Protocol
3:00 - Why do we need Web3 Access Protocol
5:55 - How to use Web3 Access Protocol
7:06 - How to Access EVM with web3://
9:25 - Applications
11:50. - Blockers
16:29 - Improvement & Extensions

Follow at Twitter
---------------------------
Qi Zhou @qc_qizhou | Pooja Ranjan @poojaranjan19

Resources
------------------
Slides - https://docs.google.com/presentation/d/1LaWbqqpQL3aBXrK9GDjcwY2yp8SY8IAZwObqtSQzI3I/edit?usp=sharing
Proposal - https://eips.ethereum.org/EIPS/eip-4804
Discussion - https://ethereum-magicians.org/t/eip-4804-web3-url-to-evm-call-message-translation/8300
Web3URL Firefox Extension - https://addons.mozilla.org/en-US/firefox/addon/web3url/
Vitalik's Blog Experiment - web3://vitalikblog.eth/
EthFS Uploader - https://socket.dev/npm/package/ethfs-uploader

PEEPanEIP - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F

ERC Playlist - https://www.youtube.com/watch?v=WzYQLF6p2SM&list=PL4cwHXAawZxqXee9EMQDIEz2CslTnsW0K&pp=gAQB

Questions for Guests - https://docs.google.com/forms/d/e/1FAIpQLSdsmujnH_ncIlSEJ23s9jzXAKwfpTGNeJqjREWPloBbkJVQTA/viewform

Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2

Contact Ethereum Cat Herders
---------------------------------------------------
Discord: https://discord.io/ethereumcatherders
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
Website: https://www.ethereumcatherders.com/

A

About a year ago, itidium cathered started a working group to help push the best URL URI proposal to final status to become a standard, and we succeeded if you are interested in learning about the latest URL standard that helps webto users to directly access the on-chain web3 content continue listening.

A

Welcome to p penny episode, 106 I am Puja ranjan and we are joined by an ERC author to discuss an EIP to revolutionize evm, call messages, ERC, 4804, web3, URL to evm call message. Translation was originally proposed in February 2022 and is in final status to talk about this standard. We are joined by he Joe the author of EIP. Welcome to the show key.

B

Yeah many thanks for the introduction, and so my name is chigil I'm. Currently working on erc404. We have to url2em evm call message, translation or sometimes we call it in a Charmaine called web3 access protocol.

B

So before our introduction introduce the protocol, uh let me briefly introduce myself: I have been actually working in ethereum ecosystem and discuss and wrote a lot of Articles comments in during research and magician. You can uh should be able to find my all my uh outputs there and also author and call us a release of eips, including 4804 and also list of others, and before that I was a former uh Facebook Google EMC Del software engineer and got a PhD from just Tech.

B

I also have been working on closely with Stephen foundation and received multiple grants from ESP program, including data available in sampling, research and also purpose storage using ethernet smart contracts. So um what is web3 assets?

B

Protocol is defined in erc4804 and it's already finalized thanks for the EIP editors uh a few months ago, and and the goal is able to render the web objects host device smart contract directly without using any centralized components or, for example, or other systems like ipfs, and it is very similar to http um it's, except that it's the authority part here, it is an HTTP is, for example, DNS or an IP address.

B

It is replaced by a smart contract or the EMS name, that map to a Smart contract, and so, first of all, why we need Webster access point Cloud, since we already have multiple particles ipfs, we have HTTP. One observation when we store this protocols start with this EIP is that we observe them more and more entities. They are moving towards to be fully on chain fully on ethereum this.

B

This is a couple of a few uh nfts that we found in Market, but that there may be much more, for example, set of Brokers nums numbers unblocks.

B

The reason they would like to to be fully Unchained is that they would like to have the users not only own the corresponding token of a smart contract on the theorem, but also all the data definitely on chain, because since 2017 2018 with the early nfts, people found a lot of data. Like some images, even people pay a lot of money by the Mt, but those data just because they rely on centralized servers or ipfs. They just disappear after a few years, and that is something um basically break.

B

The the what the ethereum kind of like say: Hey, you, the user, actually own, all the things on the order, not only the code token. So that's why now and more and more FTS. They are now moving towards these directions.

B

um So I also take a look at how they be able to support fully on chain ft, investigate their uh smart contracts from either scam and see how that is able to render this data, and if we are quite surprised that, even though all the data are now available on chain, but there's still no way to render this object directly. Is that in their token, information they're still using HTTP server, like members and or ipfs um link to in, to ask the users to find a corresponding metadata or images?

B

So that's something that I say hey why we sh? Why we should we already have the data? Why? Why not? We just directly be able to browse these images directly so that we do not need to rely on any third party like DNS, HTTP, server or ipfs, so that in the future, when there's a nft that is built on top of ethereum, they can use idiom native particle.

B

That is what our post website access protocol be able to directly render these images through smart contract and call the corresponding method for some random random broker and be able to directly display those images without any further uh third-party trust, and this is the the biggest motivation starting for the website access protocol and so how to use website as a protocol. Actually, it is very, very similar to http. Sometimes we call it decentralized HTTP.

B

It is consists of a decentralized Authority which is a contract by its address or a name service like, for example, ens and there's a way to call the contract, basically, basically how we are able to translate an HTTP path and query and to the corresponding core data that the evm can be accepted and there's a way to tell how to return the format of the data, including mime, so that we are able to, for example, not only to be able to display images but also be able to return the corresponding data in more complex format.

B

For example, I can query the balance of the user. I can query the call correspond token info of any token URI. So you can. We also build a website website URL to list all these uh examples and cases.

B

Besides how to use this webs URL, we also need a way to access the ubm with actually as a protocol. So uh we have. We are also working on the Gateway, which called must be ether.io, which is the current Gateway for the first supporting the ethereum, for example our home page, that is Webster URL.

B

Actually, it's already deployed onto the ebm and mapped to the corresponding contract and display all the our homepage homepage and it's either be accessible via website access protocol through webviewurl.eth or it can be accessed via HDR Gateway, which just plays the uh the the name of the contract in the subdomain and then put the rest of the path and query in the HTTP Gateway, and we also have the Firefox extension, which I can give a demo later, so that it will just help to directly type this full URL and it will automatically translate to the uh to the corresponding gateways link and also, there are a lot of committee members.

B

They are very interested in the whole idea. They were really buying these ideas and believe this is the future of ethereum. So one of the our company members is condensed you. He is very famous with all the browsers like, for example, uh electron and also chromium, so he create a evm browser uh while it's still in the early version, but right now it's already also natively septography VL.

B

So here, on the right hand, side is a snapshot screen snapshot from the from the application which I just typed, web3 comma, slash, size, retali block.eth, which will maintain our copy of a bitcoin's personal website on top of ethereum. And now this browser can directly pass this link and call the ethereum messages and then return corresponding left side so that the users actually do not need to touch any HTTP or DNS by forever.

B

So this is a really really amazing project.

B

um So, with all what we are all, we are now able to support a lot of interesting applications that are on top of ethereum. So one example is on chain FTS. So here we take a several block sex example. We have a way to this.

B

Very we first investigate how we is able to retrieve their own chain data of their images, and then we wrote a smart contract which to Route corresponding the um the images course to so that we are able to combine them so that we are with a single method to return as SVG file and then return to the front end.

B

And then we registered a name and points this name to the contract that we Deploy on top of ethereum magnet, and so now everyone is able to access these images directly on top ethereum using our website access protocol uh in this in this uh in this link, there's also more applications. We are also experimenting a very interesting idea.

B

We download the whole retardis blog, which is about 40 megabytes and then and then we also upload all the blog to a Smart contract on option Nova, because right now, using ethereum minion is still super super expensive, so using option Nova we are able to deploy or upload all the blog using about 0.13 Easter and we upload a hook block and run out the users or go to directly accessibility blocks, either using our Gateway or using our the communities native browser, and we also report this idea to the community and which receive a very good receptions and people are discussing all these ideas.

B

Besides the italic blog and all other concerns like physical gas costs and also, for example, where to storage, will be better.

B

um We are also exploring more applications, because now we are able to use a Smart contract and to do more complicated things like, for example, to run all kinds of the application to centralize application, Logics, uh for example, decentralized, blogger detentions, Dropbox art, essential emails, Essentials, git or detentions, correct list.

B

There are a lot of ideas, actually they're coming from communities, and we say hey welcome to be on top of that, and then let me know if you have any questions issues and then we are able to help to adjust those problems so um definitely when we gradually roll out the whole ideas and with more risk um like participation of long communities. We also have found a lot of blockers that um basically make the um so, for example, uh due to to make the project to proposal to be more successful.

B

um So there are a couple of blockers here. uh One block is how we are able to have more uh widely abduction with Native browser support, especially with popular browsers.

B

um So this is a very key for massive adoption and we've also, we believe, there's a huge impact on both web 2 and web3 users, because the now the website two users- they can directly type for example, and wraps as a protocol, but even with their wallet, because right now, erc404 only support read-only uh wrap contents to display. So they do not require wallet, but they are able to directly access web 3 content. That is closely on top of ethereum So.

B

Currently we are working with one of the top browsers in this four browsers, and also since this is a significant project. We are also contacting the evening foundation for more support for for this massive adoption.

B

Another interesting I was the interesting blocker is that it felt there are some malicious reporters that report US says: hey our website is malicious. It contains some decisive uh spanning information, so we found this report that is filed to, for example, Google Francisco, firewall capacity antivirus or their their database. So we have to submit the counter reports. They ask and say hey. This is something that we build and everything now we display is on top of ethereum and you can check the contract. We call the message we call.

B

This is the standard and for Google and Cisco. They just quickly fix all these issues and so now browsing for example, all this website that I can demonstrate right now, there's no such issue at the moment and well, at the same time, the capacity I'm. Actually, we have no idea how how they work, especially. We have submitted multiple reports, especially from our community members. We, and but still they are still says that they are reinvestigating all these things.

B

um So if you have any ideas on the broader Museum, Community can help, and that will be greatly help to us to solve this problem, but still when, when we make this like things forward for the ethereum, definitely there's always some bad guys. They would like to okay, accept us secretly, and um so another blockage is the storage issue which I just mentioned on top of ethereum.

B

If we are going to deploy the foods and the website or who the data in general, it will cost more than one 10 million US dollars per gigabytes per gigabytes causes that's just too too much expensive, um um so so compared to, for example, uh AWS cloud or even without coin, and so um definitely we need some solutions to solve two problems so that we are able to really realize our goal to make sure we are able to deploy all these.

B

uh For example, all kinds of these rich applications that, on top of ethereum on layer, one either or Layer Two, so current solution that we found is to able to use option Nova with DIC so option Nova. It is a layer two of the ethereum and it has a data availability committee so that they do not need to to upload all the transaction data on top of ethereum so that it's very friendly to upload a large amount of data to on top of action. Nova.

B

And this is something that we are also experiment on top of uh with the Vitality block and we are currently, we are also exploring with lower cost Solutions building on top of ethereum Da so that we are able to reuse ethereum trust model. While we are able to roll out all this transaction data using da and thanks for the uh fdm ESP program support right now.

B

We are working towards uh the to solving these problems so that we are able to uh to reduce the the cost to 1 to 1000 of the current Eastern storage cost and be able to scale the whole uh storage capacity to petabytes. um So if you're interested, you can also find the return latest announcement on the layer. 2 company grants, um besides others blockers. There are a lot of things that we need to improve and also need to extend the whole ecosystem.

B

um So one one proposal that we are also working is erc5018, that is on build on top of the erc404. That's to build a file like file system like interface, uh so that we can imagine the smart contract can provide kind of like file system interface and so that people can interact with basic file system like read, write operations and be able to, for example, uh to synchronize the local data. Imagine when in the web 1.0 we have FTP, but so we also create a web screen version of FTP, synchronizer or uploader.

B

So the following the standard we are able to synchronize a list of the folders files locally to the Smart Launcher, and this is something the two that we are built for: the uploading, the Vitality block just using single command, providing all the information, including, for example, the product key. Definitely that is required to sign a transaction, and everything will be automatically done by the by this uploader. So this is something we have done, and that is another ERC is erc5219 that is created by Panera pip one.

B

um This is basically provided more advanced semantics to request resources and so that we can provide custom, provide customized, headers and error code for erc404, and that is because, like that, the customers headers uh in is a is a feature in HTTP where HTTP.

B

Besides, we can see the uh the web contents, like images, there's also another side, information that is put in the HTTP request and response and in terms of headers included, for example, mmme status call others like some compression all kinds of this information, and so we need some customized header to fully support this, and the erc5 by 219 is the uh is the one that we are incorporating with the erc40 air force that we are able to reach support.

B

Much customized features that HTTP has and also understand, standard like erc686 0, which tells how to map the names name from the ens to the corresponding address culture address. How we are able to, for example, find the corresponding text field of call. We call uh content contracts versus like if you're familiar with IP address. That's called content hash that points to it best, uh since we may now calling the contract. So we we create this uh contract, address our contact uh content contract to basically to mount corresponding address.

B

uh This is the test record that we uh that we searched and there's also standardized, aim uh 6a60 and that's a more uh standards that we are thinking about, for example, how we are able to uh put the more standard info, debug information in the in the, for example, in the headers. So therefore the debug for the developers they they can easily figure out how the contract is being called, uh how many gas gas has been used? What is the actual core data which contract is called?

B

Which car which token, which change ID is being called like? Pixelmon, is either on mainnet or on optical. So there's a lot of interesting ideas that are building around surrounding um so yeah happy to be contacted and send information to me if you're interested in the standard and I'll be able to make this standard to be more um adopted by more applications and be able to encourage more, uh for example, pool ecosystem to more people.

B

um So that's pretty much. What I have um happy to answering questions or I can give some quick demo I.

A

Think the presentation was really great: I was really excited to see 304 and and like we are trying to extend this standard to be used by the users. It would be nice to have a demonstration, and we do have time so yeah. If you would like please go ahead with that.

B

Sure um so yeah this is my uh Firefox browser, um so I have installed. uh This is a Webster URL. So, on the right hand side you can see this. uh This basically is a Firefox extension. So five, five Fox extension, that's three URL, so you can find the corresponding extension to help to basically translate the webview out to uh to a Gateway. So here I've fixed up my typograph 3 and vitraulicblog.eth. So basically, I want to call the contract that host the Vitality blog as a copy.

B

So uh here then um it will translate to the HTTP way like Gateway, similar to ffs. Ipads have also multiple gateways, uhfs.io or ipfs like Cloud Fair. um So this is a gateway run by us, but definitely we are encouraging more people to run their gateways.

B

um So this is the basically the how to get away returns and also we have some debug information or, for example, when every time it called the HTTP request um and then it will basically translate this HTTP request to tell, according to our website, URL standard, what the cut which contract is being called and what is the core data and how to resolve the corresponding content and also the return types and what is the chain ID of Link service and also the corresponding chain ID that holds the whole contract of the content.

B

So everything or you can find the corresponding data here um so which so, basically, everybody is able to reproduce the the data by calling the corresponding contract and also the call data, um so I can also, for example, go inside the Vitalis blog and the good thing is like, since we are highly compatible with HTTP standard. So all the a very good feature of HTTP, for example, the relative path will be automatically supported by example. Taking this example as an images.

B

If he in this practice images in the URL, it is basically using a relative path to tell us hey. This is the some Parent Directory um and subfolder stock image, and something like that and in HTTP standard this will be automatically translate to uh uh some other solute URLs and then we'll commence to the absolute request of HTTP and since web3io is also comparable with this, so that all these requests will also be either translate to web3 request.

B

This is a defined in the political relative, your relative Ur standard in the in the basically IFC of the uh the whole UI and all the HTTP one so that we just naturally support all these rich features of HTTP in the in the sender um so that you can find the corresponding, for example, robot one dot image is called uh that in the either in the, uh for example, in the HTTP way and then corresponding the core data.

B

um So this is the um and and basically the example that we uh uh so right now, uh experiment, uh I, think I I really would like to convince Vitali one day say: hey: uh why don't you? You use the centralized server to host a website and you should use ethereum towards your website and your smart contract to control all the content and be able to access it just in a fully decentralized way in using website as a spot code, and this will be something that we really believe.

B

Something will happen and we'll be happy for more web 3 users and developers yeah. So yeah awesome.

A

That was great, I. I really hope. Your wish come true about the Metallica. Coming to this page and yeah, we can make people understand that difference. I have one question from your demonstration. Probably you mentioned about like when we are looking into all kind of data information. Those are available on side. uh It was about uh resolving it, and also the proposal mentions about resolve mode. Could.

B

A

Maybe uh briefly explain what are the resolve mode available using this as standard and in which particular case, which mode will be helpful? Oh.

B

Yeah, that's great, uh actually, that's a great question. I think the best way is probably to go to our website URL website and, if there's a way to tell the how the resource will works. So uh the result mode basically uh tells that when given uh URL how to translate the corresponding path and query into a ebm message, if you give me a message called Data, um so there's a two modes, one is called auto mode in auto mode.

B

um So the the front ends which are when we received this web 3 requests. It will basically figure out the corresponding method and corresponding a list of arguments by separated by the uh by the slash so that it's able to say how oh this is calling the balance of the method and with the Zuckerberg as the the address as the uh as the argument and the corresponding data will be returned in 256..

B

So the auto mode is more designed for existing smart contracts that have no aware of ERC, for example, but user would like to using a single link be able to query the data on those single contract can be images. It can be also any like a like a solidity.

B

Api return types um so that like I, can easily share a link, say hi, look at this present that this is the balance, and this is his balance or look at the ownership of this this this this uh nav T and just paste the single link here and also this is a column menu mode in many mode.

B

um It's quite straightforward. It said: hey I, don't want to do any further interpretation of the pub and query I just put the whole thing in the core data and let a smart contract to decide what the data to be returned.

B

um So this is more designed for the decentrals front-end contract, that is the contract design for smartphone for the the program so that they have fine grain control. What the actual user was typing without doing further translation and put the holding in code data, for example, in the rhetoric block. So every time when, uh when we, for example,.

B

A link, then the whole thing right now is interesting resource mode, so that uh uh so we can check that this system in the in the manual mode and so that the the core data is just actually the The Who uh to to link or who path of the, for example, images or travel time all this data, so that um we just look at the corresponding uh this data as the key and then find the corresponding data from the from the evm, so that we do not need to.

B

We do not lose the corresponding information that the user would like to pass to the smart contract.

B

um So this is uh two modes, and actually we are adding the third mode uh that is uh supported by erc58 uh child. The IP 5A 12.

B

5 2 19. 5219, um so, which will be able to add additional mode to support uh more fine-grained headers of the rap3 request has, for example, this is a control interface.

B

Let me see: control interface, oh, uh why not I just open, uh oh okay, so I kind of interface that contains a list of the headers and all this information that um that those study information that our HTTP request has so um so we are basically first starting from very simple way to translate this message now we are gradually going to more complicated ways to how to resolve this uh python query or from web3 URL, and so that we are able to satisfy more complicated applications. Yeah yeah.

A

That's great I mean I'm happy that you guys did not try to edit the same EIP but have proposed of 52.90 in a separate EIP to introduce the third mode that would be used.

A

um I have another question which is related to um nft and images like we were talking about that this standard help access to that as well. I'm curious. uh There is this another proposal, 4883 composable, SVG and ft, and it was also compared with the present proposal. Could you explain us the basic difference between this and that and that proposal.

B

Oh yeah, so um I think this is in the different layers of the of the different proposals for the website. Url is more like from the end. uh That's why we call it access protocols.

B

It tells how we are able to access the the data from the from them most likely the browser, but hopefully in the future, can be supported by other two like webgat or curl, um so in the next step is to be able to how to organize those data, be able to return to the front end and the way how to organize data is highly defined by the smart contract, how it is being implemented, and the composable nft is one of the I would say closely closely one version with the erc404 because, like we need a way to how to compose, uh for example, actually all this you can see all these images that are already deployed on their smart contract.

B

They are also in some way. They are composable topics. On my background, I am also different, hair or different bodies, all those things they are composable, and so we need a way to be able to put this different. Sometimes they call layers or components composed together so that we can return a uniform way to the front end, so users can easily be able to browse it or the developer can easily be putting all these components and using other tools to to just upload it and put them together.

B

So we are solving different layers of problems that the future application on top of ethereum like, for example, is special nft. They are they're facing. So we are very happy to see how the request on web URL can help to solve this problem, especially those svgs.

B

They need a way to run in those content directly on public ethereum, so we are highly related and and also we see how we are able to be able to satisfy their needs so that in the future we we would like to see that in five or ten years, all the images they will not using like HTTP or ipfs, they will use web series to say, hey be already on ethereum. So we should just play all this data on purpose, foreign.

A

That's the Hope here like move everything on chain, so we can literally migrate to web 3 world.

B

A

All right, um so, my next question is with respect to the process, the EIP process. You have documented the CIP and um we learned that there are a few more to come up. Would you maybe uh share your experience as an ERC author? How did you find the process in general and if, in your mind, is there anything that we could improve to like further help authors document their proposal as a standard.

B

Yes, uh yeah, first of all, uh I would like to express my appreciation for all the help from EIP editors and also definitely project and uh like your UI working group from ethereum ecosystem. um Actually, uh ERC 4804 is my first EIP. So when I started, writing the CIP, the first time I think in in February last year, uh actually there's a lot of uh issues. Then I I, even though I have a PhD I, realize a lot of uh like academic papers, but still the whole process um uh needs to get familiar to understand.

B

So, for example, I the common mistake, I I have amazed like I'm putting I misunderstand the the what's, the basically, uh for example, the rational. Why why we need to put rationale there and why we have this, for example, um um where to put the motivation and social so sometimes I, just mixed in and then I'm gonna write this content that our Engineers should put in the motivation by putting rational or putting them rational in motivation, all kinds of things, but I'm very happy that the EIP editors are very promoted to help say hey.

B

This is the this. Is the uh this you put this content in in this section? You should organize this, this data in this section and sometimes even help me to rephrase the whole sentences to make people to be more clear and help me say Hey, you can check out the EIP the reference to find out, find out the details.

B

um So so that is really helpful because you know, like feedback, is really important to make the whole thing to be from draft that is still very naive, but to the final version that people can really understand, it can be able to develop on top of it, especially for the, uh for example, for the developer. They developed this native integration from Community. The first thing they have to is to be able to understand the standard clearly, so they can reproduce all the work that we try to try to try to explain in EIP.

B

So this is something that really inspired me, because now somebody really can just follow the work and do these things and thanks to the help from the eips and also the communities, and also we I, found the EIP process become more and more automatic, especially there's a lot of new, uh the Bots that help to check out this formats and then so so. Every time when I, for example, modification I, said. Oh, it looks like there's a some new new corrections. I need to make to make the whole EIP small I would say, readable.

B

um So I think this is a really really good uh interact iterative process to help the whole process and be able to benefit a lot of newcomers so that they are able to quickly understand how to draft the CIP, how to be able to let the Erp to be more understandable to be able to to let more not only work to ethereum ecosystem, but more people Outsider be able to come and be able to contribute so yeah I think this is something that I personally would like to also like to contribute some of the discussion.

B

Some comments like this, for example UI working group and definitely there's also a lot of help from there to see how we are able to what kind of applications and what the uh how to, for example, like some some something that polish to be more. If they're native, for example, the the text text record, uh we originally using web3 record text record as the as the as the mapping and then um Sam Wilson is like. This is something not like easy to understand?

B

Why not using the contract content, and this is our content contract that is already have similar version in ens and people can quickly understand what is going on yeah. This is really good, great suggestion, and so a lot of these things that might adopt together so I think we hope that the whole thing is like become community owned and and also be able to contribute by all the community members. So we welcome everybody to have any good ideas, be able to pull contribution in this all the eips by adding more eips or polish existing ones.

B

A

That's uh awesome feedback. Thank you. So much for that I mean it's a really interesting to see that you have actually followed a process which was six months ago. uh Definitely there has been a lot of changes since then, I think when 4804 was introduced, there were most of the things were manual. Eap editor has to chime in. To that you know what needs of effects, but uh these days with the help of eipwbot and EAP Bots I think we are trying to do most of the thing on an automatic way.

A

However, we are still keeping this manual interaction uh there. We are also organizing EIP editing office hour for any new Authors to maybe come and ask their question. If there are any so I will definitely take your feedback and share it with other editors and your good verse as well. So we can increase the contribution and participation of community yeah.

B

Yeah yeah, that's great yeah.

A

Awesome I think it's time to wrap up.

A

With the community today,.

B

Yeah so I think um one thing I would say that, like we are now, especially with the scalability roadmap of ethereum, is gradually rollouts, uh for example, erp44 and then shorting. uh We believe that we are seeing the we are at the door of the new world that is building purely built on top of the referee. That is able to be more fair, to have to to be better to say, career order, assets or users and be able to offer much more freedom, um especially from ethene Technologies.

B

So we hope that there are more and more people can work together to come to build all kinds of these ideas through the EIP progress process and also, hopefully, for the ERC, for example, um on all aspects so uh welcome to build the future web 3.

A

Thank you so much. These are awesome words. He we really appreciate you taking out time to provide an overview of EIP 4804 of a three URL to EDM called message translation. They look forward to see uh standard being adapted in upcoming projects. On this note, thank you to all our YouTube viewers and ech podcast listeners for following this chart, don't forget to like And subscribe YouTube channel. Should you have any question on this EIP or any other topic? Let us know cheers.