EIP Editing Office Hour #63 (EIP Only)

Transcript

Hold [Music] on. [Music] Hold on. [Music] Hello.

[Music] Noo. [Music] Oh. Oh,

[Music] hey. [Music] Hello everyone. Welcome to EIP editing

officer meeting 63 for June 24. And uh as usual we'll go through uh some of the EIPs that are uh some of the PRs that are there for adding EIPs or updating the EIPs and then uh we'll see what issues are coming up over there and uh if there are any authors who are here would like to uh discuss the issues that they are having then we'll move on to that uh but going over to the agenda, let's start looking at the drafts.

Hello. Okay. So, um I have some EIPs that I'm kind of championing. Uh so, Mercy, you have uh some EIPs that you want to bring up. Yeah. Okay. All right. Uh so, we'll take that in the end after we have gone through the agenda.

Okay. Thank you. So I think uh this particular EIP the author intended as an ERC and uh I'm not sure whether this still intended as an EIP or not but uh even uh the bot the CI isn't passing but let's still look at the header.

Yeah, author updated the category as an EC but uh it's still an EIP. So I'll leave a comment for that. Do you have the access to take uh uh the

the list? Because I don't seem to be able to take uh the list. But moving on to the next EIP. So yesterday I assigned an IP number to

this EIP and seems like author has updated that I think we are all good here. So

approving the CIP Moving to the next uh I already had flagged this particular

issue where we don't want to mention MD the name uh of the files uh while the author is trying to refer the consensus specs uh but I think again author has left some of these so I have added a command for that we'll come back to this when author has address That So have added recommendation to name it

a bit better and uh once author has addressed that then we'll come back to it. I have already reviewed the rest of the EIP and that the rest looks fine. But uh earlier also had made the recommendation for changing the title and description to a bit more meaningful uh which author did and but maybe I think there is still some scope for improvement.

So I am going to skip ERC because uh this is an EIP only editing hours. light client has mentioned that uh this

is best not to be implemented as an EIP but as a smart contract implementation and uh I sort of agree with him because uh we don't want to complicate uh the logic that goes into EVM and uh we want to use our own dog food, right? So if something can be done at smart contract layer, we should not try to do it as a part of the protocol. So I sort of agreed to this but uh if the author feels uh very strongly about it they can still come to the EIP editing hours and talk

about it or u Akash if uh you could create a call for action for this uh for the other authors uh other EIP editors then maybe we can collectively take a look at this. So maybe I'll just tag Sam into this Okay, moving on to the next

last draft EIP. I have already reviewed this particular EIP uh send raw transaction sync method and Okay, I think uh there are still some discussions going on uh be regarding the specification of the

EIP. So what I'll do is I'll give it a bit more time and then uh circle back on it. moving on uh to the update section. So

wherever for smudge is required I think we'll have to escalate it to Sam. And so I'll move into the other section and uh start looking at the stagnant uh PRs because they could be easy to fix. Yeah. So as Puja has written that this

should be automerged but I think there is some time window that is provided uh so that the authors may want to request to not mark get it marked as stagnant or uh the EIP editor may itself decide that uh uh this particular stagnant uh PR is not applicable on a particular EIP. which they know is in active development.

7742 I know is uh sort of no longer uh inactive consideration because it was uh it was considered to be part of PCRA but then it was dropped out. So I leave these PRs to be automerged. So if any of the feel that uh these PRs their EIP should remain mark stagnant, please reach out.

All right. So, seems like I already approved this PR, but uh we have the B failing. So, I'll just close and reopen this or retrigger all the BS. Yeah, this is a genuine request, so I'll

give it my thumbs up. But it will require one more reviewer to approve it which I don't think uh there's going to be any challenge. I have already seen uh this PR but I

need to sort of uh figure out whether this is the website uh we should be able to link to and there is nothing malicious about it. So, let me just pl some onto it. now seems to be a PR by Sam to generate

out a list of pull requests. So I guess this is all good. Again,

this is regarding CI. So, I'll just flag it to Sam. Don't see any issue with this sphere but

I will again give it to Sam. So with this uh we have gone through all the PRs listed in the agenda and now maybe we can take a look at uh what Mercy was wants us uh to look into.

Are you there Mercy? Yes, I'm here. Yeah, I have already addressed uh this particular EIP. Do you have something else that you want to bring up? Yeah, 9832.

Uh what did you say? 9832. You've you've gone through this one. Which line number? No, I mean another EIP. You've you've done this one already. Yeah, we have done this one. Okay, cool. Uh, all right. Then we'll move to 9832. Yeah, I think uh this is more suited as an ERC which is what I

have already flagged as a comment uh on this particular EIP. So even when the user want to submit it as an interface I mean I'm not sure whether uh you know clients actually want to implement this. So I would like user to present me some evidence that clients actually want to do this.

All right. Uh, so with this we have mostly taken care of everything. Is there anything else Mercy you want to bring up? No, nothing else. Thank you. All right. I think uh then we are done with today's today's agenda

and uh thank you for being here. Uh so we uh we have left some comments on this particular PRS. So when the authors will address them or respond to them then we'll come back again but uh if any author has any issue they can always come to EIP editing hours and uh raise what they want to say. So that will be all from my side. [Music]

Hold [Music] on. Hold on. [Music] Heat. Heat. N. [Music] Heat. Heat.

[Music] Hey. Hey. Hey. [Music]