EIP Editing Office Hour #101 (EIP + ERC)

Transcript

Welcome to EIP editing office hour uh EIP plus ERC today and this is meeting number 101. We have completed 100th uh office hour and this is 101st. Uh people if you have missed the recording from the 100th meeting you can perhaps find it um on Ethereum YouTube channel. On agenda today we made a slight change uh just for announcement purposes. from um this meeting onwards we are also going to include PRs which are supposed to be discussed in the upcoming meeting or has been discussed in the previous meeting.

So uh authors if you have PR which you are taking it to all core dev and would like to get it reviewed you can perhaps add it in the future office hour. Uh for today I have collected uh the PR from the previous ACD meeting. Other than that we do have our regular PRs for review like uh proposals which are moving into different statuses. We have one for review, couple of them for miscellaneous, a few for draft and yeah we are joined by >> we are joined by editor Yam Ber. Welcome Yam.

>> Thank you for joining Yam. If you would like to maybe share your screen and we can look into PRs and uh authors if you are on the call if you have any PR for review kindly drop it in the chat as well as your questions if there are any and we will try to u get answers to all those questions by the editor on call. >> All right, let's get started. Okay.

Did you already have any decision about uh the solidity version um idea what we had? I I think on last last EIPIP meeting we did not um get to like a a very strict rule about this right or do I remember >> I think uh uh Sam added something in contributing MD as like general guideline that it can be as generic as possible not stick to specific to solidity only. >> Okay. Okay. Cool. Cool.

And I guess there is one more suggestion here to maybe write the version of the solidity so it makes sense for people in future if they are referring to. >> Oh yeah right. Yeah. Yeah. Okay. Yeah, like my my general feeling about this because this EIP has like a lot of the these these methods, but yeah, I

don't know. I'm getting the feeling that that that maybe these kind of definitions should actually land in an ERC. That's that's just my initial initial feeling. >> Yeah, >> slightly out of place. Yeah. I don't know. >> Damn. Yeah, maybe it's also my mental model

that EIPs are more like at the protocol level and and ESC's are more at the at the well at the user/contract level. So it might feel like a little bit out of place, but yeah, this seems to be unspecified here. >> Yeah. Yeah. I mean of course we can bring it up later on because this is for like discussion for ACD meeting because this is an EIP. >> Yes. >> Sure it will come up. >> Yeah. Let me actually write that as um as a review comment because this will not uh block the draft patient. Yes.

>> Yeah. Right. And that way we can also collect more feedback what people generally think about having such element in EIP. >> Yeah. Exactly. Exactly. >> Okay. Yeah, maybe for the for the people also

in the chat like I will review this EIP and then the idea is that I will actually move to the people in this room now so that we can have like an interactive uh office hour. Uh, so I will then go to George and then to uh I will tell him to Right.

Yeah. What what puja what do you think about this? Because this is like it it refers to of course like an external um paper or study or or research. Um and so so this is of course allowed but I think we all also allow like uh DOIs. >> Right. We do. >> Okay. So then we should ask them to include the DOI to this I think. Yeah, that would make sense, right?

>> Yeah, of course. I mean like mentioning is fine but linking would be better if it is alone. >> Yes. Yes. Yes. All right. So, let's do that. can be added as a footnote.

>> Yes, exactly. Exactly. >> It's here now. Yeah, master I will go by the order of

the chats. Um so uh yeah if if I have the time then I will review your All right. Okay.

Let's move to George. George here is the first time ERC editor ERC author I believe. So yeah uh George if you have any questions about the process or anything please feel free to drop in.

Okay. So, we just add these links for the uh for the people reading it. That's just nice because then you can click it. Let's see if I do this correctly. this. Oh yeah and I will check these these links to these other ERPs because likely you have linked them as okay let's see um okay yeah so if you link to other EIPs uh or well ears in this case you should link it uh into the current directory and I will just make the

suggestions here because that will be like this and then we should not forget the extension. Let me see if this is correct. Um, yes. Yeah, it might be a little bit weird but uh so we have the EIP and the ERC repository and these get merged and then the ERC uh ERC's get renamed to EIP. So this is like a maybe a little bit weird from the technical perspective but this is how it currently works. So this is how you would link to uh well ERC's which are now EIBs. Um let me quickly check

this is correct. This

Yeah. So if you if you change uh all these so these patterns of where you link to a.fm.org network to the variant where you where you do um well as my suggestion which I just posted here. Uh then the bot should u well not flag it as incorrect. Yeah, maybe like as a review completely

you likely want to define the types of these um this data because otherwise people might add it wrong. I will add it as a review comment. All

right. All right. Well, this is almost ready to

be merged. Uh if you address these comments, then uh I think we can we can merge it. All right. Okay. Let's see. We are going to Let's see. I missed it. Uh yes, Arto can me. But um what question or chat did you want to to do here?

So uh Herman I believe you are on the call and um uh you wanted to quickly mention about uh some tool that you um the team has built on. >> Yes. Hello to everyone. Thank you >> for this opportunity to show this very fast. Uh can I share my screen? >> Yes. Uh, I guess >> it's okay because I saw that that you were sharing so I didn't want to overlap you.

>> Okay. Can you see it? >> No, I see a black screen. Oh, no. Now, now I see it. >> It's okay. Excellent. Well, what we are building based on our experience on EAPS and EVDM. EDVDM is is a project. Uh, I'm the founder. and we are five co-ounders is to deploy virtual blockchains on any VM chain. It was show h showcased in the in the in the cat herers ecosystem program also. So what you do is with just a smart contract you can deploy a virtual machine on any VM including of course Etheum. So it's a

full abstracted chain where all the execution logics nonsense gas and everything is abstracted on these contracts and well here is some videos that you can uh know a little more. We have here in our X account more information but what we just made that is the the purpose of this. We made a the EAP lab and we are in an alpha version now. The beta release will be for the end of this month and maybe the production production good one for for July. And what this let you do is basically I will show you very fast is you you select any any um AI provider. We we are working with

with now GPT and um with I think OPUS are the best one for this and you give later the EAP link here or your own MD file in this example 8182 and what you will do is start reading the EIP understand it make you a few questions about it to understand it together and after that you confirm and we'll start writing a virtual blockchain for you on a smart contract that when you deploy them you will have on any EVM for just $1.5 cost uh your EAP h introduced into

contract doesn't matter that is an infra for example the 8250 the the k nons we already have it called async nonses in the in the EVBM and like this you can have any infra and you deploy these contracts and you will have this environment on sepoleia that is with your EIP already so it's a little complex to understand from first h time this concept of virtual blockchains but basically it's a ch root for Linux but for blockchain now so no infra needed you just deploy the contract and you will have this abstracted chain that use

the the nodes and all the infra that is already there with some change on the execution rules on an EBM. So this will let you test any any AP. Here is the the URL to test this tool specifically. I will put in the chat uh without having to change any any infra you know to to to change a client to fork it and deploy to make the test of on or anything like that. So it's a very easy to use tool and also let you validate your EAP and maybe doesn't need infra changes and with just this deployments of the smart contrast is enough. For example, the X42 is already uh working on on EVVM as

well. There is there is many other other improvement that are very good. So that is the what we build is EAP lab is for help EAP editors and maybe to to help also Ethereum in in improve very very [clears throat] fast and and make a faster moves also on the implementation of services uh functionalities and everything. I didn't want to take too much time. I don't know if you understood it and and what do you think about >> All right. Thanks a lot. Yeah, I think this might not be the the the right uh the right call to share share these things but still still thanks thanks

thanks for sharing. Um but I think that the public here might not be directly the public what you are targeting here. All right, I should share my screen again. Um let's see where is it. Yes. So let's move to to let's see to to to to mask. Um yeah. All right.

What's l comment on these uh mask so you can directly apply it if you me. Oh, these are like editorial things. So, or linking linking these RFC's. Okay, that's that's fine. That's fine. I

would just comment on on these things and uh if it's just like these edits then we can also merge it after but let's see where we go. Oh, nice. Wait. All right. Okay. Well, this looks uh

mostly good. Just like a few style comments. Um Oh, wait. You already refreshing things. That's That's nice. Um okay, I will just comment on this. If you address all these comments Oh, not look good to me. Um yeah then we can merge the thumbs up. Okay. Boom. Let's see. I will go back to the agenda because I think there are not more people.

>> Right. Yeah. Yeah. Maybe we can take the review and miscellaneous. We only have few minutes left. >> Oh yes. Yes. Um so these are this is the tiny one right? Okay. Okay. Let's first do these. >> Uh this just require additional uh approval because it is for tooling and SAM has already approved. So if we get another uh approval by editor it will merge automatically. >> All right. Okay. Let's let's see because this All right. I guess I will just sh this one.

That's okay. Um yeah. Yeah. Okay. That's match it. Okay. And let's see. Move to withdraw. >> Yeah. The only thing what we do with the withdrawn piece is we have this with reason why >> reason. Yes. Yeah. That's >> okay. Great. Then we can can withdraw

Yes. Okay. 2770. Yeah. Okay. Let's see if uh what this all changes if we can do that in the last Oh, wait. This looks >> big one. >> Yeah. I mean it's it looks like just a spec change with some uh Okay. This is your C changes. Yeah. Okay. Let's maybe not not not rush this one. Um

uh I have added some PRs with comment which were requested by author in previous meetings but we could not address them on time. So yeah. >> Right. Which are these? Um >> uh wherever you see comment it's from the previous meeting. >> Okay. All right. Okay. So let's see uh these are comments uh which were not addressed uh in the previous meetings. >> Right. I see. I see.

>> Yeah. >> I think if you're >> Yep. Yes. Please go ahead. >> Yeah. I mean this this this is too too big for four minutes. Yeah. >> Yeah. So I think the one small thing that we can perhaps do it today is uh 9594 which is the first in the draft because I that was there existing but u maybe stagnant and they requesting it to move it to draft again. >> Okay let's see because this okay this was stagnant.

Mhm. Let's make these It's also very old EIP. So that's that's

nice to see these being revived. Hold on.

man when I thought it will be smaller and quicker one but because it's a revival there are a lot of changes in this PR as well. Mhm. >> Yeah. I don't think I will finish this now, but I will finish after the office hour this uh because it will likely have some small stale things like if it is just a like an PR which just revives uh it it just would move it back to draft then it is of course easier to to review. >> That's right. >> But if you brush it like because it is a very old don't know when when this was moved into stagnant. Okay. Last year.

Okay. That's weird. Oh, right. This is like a very old PR. Um, but yeah, we also have to check like maybe our ERP1 has updated. So, we have to check if this now complies with the new uh um EIP layout. So, yeah, this is not like something what what we can now. >> Yep, that makes sense. Yeah. >> And while you would be looking into PR async, the PRs where you see comment are coming up from earlier meetings. So if that can be addressed uh would be nice otherwise we can pick it up in in the next office hour.

>> Yeah. Yeah. Maybe maybe for for for like scheduling these things for the office hours. So I think it's it's nice that people uh would join these office hours to do like this this sync directly. Um and then also if people have commented like on these um on on on yeah I'm actually not sure if if we should um yeah maybe like from from previous meetings uh if people comment then also maybe um yeah prioritize this. Yeah.

Okay. Yeah. >> All right. Yeah we can do that. >> Yeah. Yeah. Well, thank you so much, Johan, for taking our time today and thank you authors for joining us here. Hopefully, see you around and we'll meet in the next office hour next Tuesday at 1600 UTC. Thank you everyone. >> All right. Thanks everyone. Bye-bye.