EIPIP Meeting 113

Transcript

[Music] oh

[Music] in progress welcome to EIP meeting 113 this is issue number 378 on E cat herders EIP IP GitHub repository um I have shared the link in chat chat for people to refer to in agenda we have some added two final proposals simple request for consideration we will look into call for input which I think have passed their deadline we just need to make a decision

and close those call for inputs among other discussions I have a reviewers report uh the survey that we conducted last month uh on the interest of people who are interested in joining and how they are doing and uh then there would be some updates from eips inside team yeah I see someone joined from the team um mostly all about it so beginning with the first item on the agenda which is edit to final proposals the first PR here is um PR number 866 which is for ERC 6381 it seems that author has already approved it but for some reason this is

not merged I'm not sure if we need a force merge here yeah I mean it's a final final ERC yeah they can obviously merge since it's a small just a little tyo yeah right and I think author has also approved it so seems okay and the next one is also the

similar case we are discussing ERC PR number 870 which is a final proposal for uh 7528 is the final proposal and we are discussing the merging of PR which is uh with respect to this proposal it seems like it has already been approved by the author but since it is a final proposal we are waiting on editor's approval to Marg it or maybe force Mar it so that was

6381 you said yeah okay uh no 7528 oh 7528 next one all right yep that's fine by me all right a matter I I think it's again Sim similar case okay perfect uh the third one is U add proxy call to 6492 reference implementation any thoughts on this

one I think it is failing two of the bot checks yeah that like the bot doesn't matter too too much for these it's more okay proxy call using Factory to stop yes this is a normative change like like you said uh I'll open a call for input for this one just because yeah okay okay that makes sense okay I have a quick query here with

respect to change U I know there are lot of changes coming up with uh the network upgrades Suppose there is a small change to an existing PR which was deployed in one of the one of the network upgrades if we have to move the pointer like just change make a small change to the spec here do we need a new proposal or we can just go back and update that old one um I think if it's a small change it's probably okay um I don't know how everybody else feels yeah I mean mind a small

change okay it's good to know um I was discussing it with the one of the um meeting with Peep and and there's a proposal that may be changing a small spec for future upgrade and I was just wondering from process point of view like do we need to create a new EIP all together to be deployed with the future upgrade or we can just go back and update it oh so sorry is this like something that's already deployed on the network and in a new Fork they want to change the behavior of it uh yes the pointer um they want to change the endpoint I guess hm see that that would be different so

like if like for example if you were changing the gas cost of an OP code that would have to be a new EIP okay yeah I think it was mostly related to blob base fee um with respect to 7706 when it is deployed we may have to change a little bit there but it's not the problem to deal with today I was just curious from process point of view how do we deal it when it comes yeah if it's hit the network it has to be a new EIP and if it hasn't hit the network then it's probably fine not to yeah that sounds like a good one we'll keep that in mind thank you moving ahead uh we

had the stagnant bot issue that was discussed in the last meeting um I don't know if anybody has new thoughts but I see that um Point added in the agenda later on to be discussed by the eips inside team I believe they have some suggestion solution around that uh yeah uh we want to discuss a few things related to that let me share my screen and I made a presentation for that okay just to give some context here in the last meeting we discussed that the stagnant ISS stagnant bot is causing

ISS isue to some of the eips where the eips are not currently actively pursued because they have been moved to the Future upgrade so they may be used in future upgrades and uh authors wouldn't want that uh marked as a stagnant so how do we deal with this issue yeah please go ahead so uh like first shall give you basic overview of how it is working and what modification we can make uh so these these are the stagnant statuses which is being checked in the process while moving to stagnant by the EIP board and uh actually I also have one additional question over here

like here we are checking for the um draft and review status for the stable status is last call I mean uh can last call also be included for the stagnant status this uh this is one of my question question if anyone can answer that that would be helpful I have noticed some of the I have noticed some of the erc's which are in last call since 2023 so my best guess would be yes they should be I'm sorry Sam you were saying something oh I was just going to say if you could repeat the question

um so uh like currently EIP B is shaking uh if it is in draft or review then it can be considered for the stagnant status if if if it is not in one of these two states I mean statuses then it won't be include I mean considered for the stagnant status that is how it is working right now can last call also be included for that uh is my question um I think if it's in last call it doesn't go to stagnant it should just go to final should probably open a poor request to move it to final um I don't know how you feel about that

Matt I I agree okay yeah so we could we could do that but it it shouldn't go to stagnant because it's it's done there shouldn't be any more edits to it okay um okay then I'll go ahead for the rest presentation uh so this is how it is working for the code part currently first it is checking the um State I mean the last interaction when it was made the last commit made by the author or someone else and then it is applying the stagnant protocol so uh if we'll uh update it so that it it will be checking the request field and I

mean uh as per what Pua Puja man said just now uh if a meta EIP or any uh if a meta is included in the request field of AIP then it shouldn't be going to the stagnant Shad is it right or am I going wrong with that so you're suggesting that if an active meta EIP is pointing to a stagnant or is pointing to an EIP that would go to stagnant just don't move it to stag yeah yeah that is what I'm suggesting to um if we can add that check uh then it would be solving the issue is

what we were able to propose so I H so that that kind of makes like that makes sense but it also has the problem of like what if what if the meta EIP is never updated um but I guess if it goes stagnant and then then the other one could all yeah okay so as long as there is a non- stagnant EIP referencing it you can keep it out of stagnant and I think that's fine I don't even think it needs to be

meta it just needs to be any active EIP oh yeah we can make it like that yeah we we can talk like we can talk about this after but yeah I think this is this is a reasonable way of doing it yeah uh and I also have one other question like currently the EIP bot is using one particular commit I mean in one particular Committee in the past for the stagnant uh Bard um so like in case if we want to change it uh how do we change it like current code is is entirely different from what it is using for the stagnant board oh like uh there's like an

undeployed um commits on like in the repository that haven't been deployed to the repository yet uh so the cas is uh like I'll give you overview of that currently there is a ipb code and uh it is buil uh I mean the current eips repository is using one particular commit that is made way back in the past of the EIP bot so uh like uh they are using that particular commit of VIP bot for stagnant bot and in case if we want to edit it uh like it will it is completely different from the existing code of the EIP board like the current

code right now yeah yeah so it's been Rewritten since and we haven't switched to using it is is kind of say like in case if we have to edit anything how do we do that is my question um I guess we have two choices there we can either Branch off the old commit and make our changes from there or we can uh use the new commit but we have to test to make sure that it works um so Panda pip used to maintain uh the stagnant bot I Matt and I have pretty much zero idea how it works um so I guess um if we can come up with a way to test

uh the bot and make sure that it works um then I guess we start from the latest commit in that repository um but if we have no way of testing it I'd say probably just make a new Branch off of the old commit and develop from there yeah okay uh that's it from my side regarding this one if there are any questions or any comments that would be helpful I have just one concern um slash comment here so when we are talking about last call like uh I understand last call proposal should not go to stagnant it should either go to final or

um I mean it should go to final but the reason why there we haven't been uh sending it to fin or creating a pull request for that because we expect authors to be around to be able to make the pull request making sure that author is convinced that this proposal should go into final um so I'm not 100% convinced that there should be generate PR yeah that's a good point maybe like if it opens the PR but doesn't like force it I don't I don't know yeah so I mean like uh if we do not do anything that proposal will be in the

last call forever but that defeats the purpose of sending into stagnant however I feel like okay if if the person or the author would get the message by B that this proposal is marked for being stagnant perhaps they will come back and just make a new PR or maybe we can add this uh statement in the bot whenever you are sending the message to last call proposal please that just create a new PR to move it to final and it will be done so that way we can persuade authors to finish the proposal don't just end up living in the last call forever for example I have shared ERC 5008 it seems that proposals last call ended in August 2023 but it's still

there not in stagnant ideally it should be in my mind sorry yeah I I think so if it is not final it should be stagnant it cannot be in any other status for forever maybe we can work on nuances of this a little bit more for now we can exclude last call if people think that's the right approach to go forward with and we see how the stagnant mod comes up um honestly I think just move like moving to stagnant would be acceptable um as long as it's past the last call deadline um yeah yeah let let's just move everything

to stagnant um with the exception of uh like check the last call deadline and I think that's better yeah right generally speaking last call deadline is there for two weeks only and the stagnant bot hits only if it is 6 months pass very work for me thank you um moving forward we have uh we have call for inputs to be discussed I see there are three call for inputs there and all of them have passed their deadlines Sam if you would like to maybe yeah sure um so we have uh 373 um which is moving hard Forks to

informational um I just changed my vote on this to opposed and closed it um so we'll just leave them as meta um we also have um forcibly withdrawing EIP 7675 um and and we want to withdraw it because it is um a list and uh yeah right now I think we're leading towards withdrawing it and then uh like doing some work in the renderer to make it to make it work um and then finally we have uh number 376 and this is a allwing links to blockchain

commments um right now there's me opposed and Ginder is neutral on it um just leave a comment on it perfect um I'll close that at end of day today well thank you for that and thank you for clarifying 373 I was wondering the stagnant bot is based on that like it is checking the meta e so if we move it to informational then we also have to check the informationally but since we are keeping it in meta everything should work out well next on agenda is U other discussion and updates from the past

meetings so if people remember about a month ago we organized EIP editors uh Workshop in which we invited people who are interested in becoming EIP editor or reviewer I have uh um I have shared a survey in there like how many people are there interested in participating in the process and um uh like U uh what is their areas of expertise um I just shared Link in the chat perhaps I can share my screen to share this second I don't know it is taking too

[Music] long three okay I think it should be visible now um is screen sharing working well let me know if it doesn't yep you look good okay perfect so here is the editors review interest form so we collected this interest form suggesting like how many people are interested in in participating and what are their area of expertise by which we can get some input and we will be able to help process the proposals which are added as PRS um so we have received six um

interest which are from code development that means either they are part of a client development team currently or they actively contribute to the code development side of it the protocol side of it and there are a couple of peoples for networking Pedas as well so I'm I'm very much hopeful that um we would be getting some um some reviews on the spec side of the pull request that's generally gets in and they are available to contribute to 1 to 5 hours per week I was also looking into um one of the dashboards that is created I think it will be uh shared later on in detail but uh it

was shared with me so I was looking into this leaderboard stuff here um we already have started collecting the input by these reviewers based on this interest form uh they have collected the GitHub uh ID and collecting uh uh their work over here I have two questions here with respect to this um reviewers set that we are going going forward do we need a place to document their name formally so we know that these people are reviewers if we can do it somewhere I'm I'm happy to do it in the reviewers document itself but if we

need to do it formally somewhere that would be nice to have as well as we would love to know the next step for them I understand when we were uh doing editors uh apprenticeship program the idea was to keep them there for next 6 months review their performance how they do and then perhaps promote it to the EIP editors um job uh I'm curious what people think about uh moving forward with the reviewer set of people yeah I already see some comments here in the chat Victor if you have to add something on that I don't know if you met someone somewhere okay can you connect us yes of

course so is the goal for these people to become editors like do they want to participate in the governance side of this as well they want to support pushing the pull request as fast as possible but uh from the last uh all core Dev it seems like there is some interest in participating in governance side as well because they would want to make some changes on EIP side sure so I think um I'd be happy to have a section in EIP 1 documenting these people and then we can give them permission to merge all the way up to say last call um maybe this would be too early for that may uh we can give the

permission part after 6 months down the line keeping keeping in mind the interest is still there um but I was just hoping to have like more formalized way of involving them with the process I would assume that EAP meeting could be the good venue for them to be actively participating if they want to be a part of governance uh other than that um is there any suggestion on how they can improve on reviewing side and be a part of um I mean coming to office hours is probably the best way to to do that maybe um we rotate like through them as different host posts um so that they can

do office hours and kind of get that side of of uh the reviewing process that's a very good suggestion any other editor has any thoughts to add yeah plus one to Sam it's a good one very well I'm going to share this review Report with uh with the community shortly um and uh then we will also add the recommendations um I think rotating host in office hour is a good one and we will also recommend them to um join the EIP meeting on a regular basis might be

helpful for them to go forward all right um with that next on agenda is eips Insight monthly APS status reporting yeah if you would like to take this section yeah yeah thanks appreciate uh let me start with a few updates uh this one you already mentioned we started to collect information regarding the reviewers and you can view the data in the uh leaderboard page over here

uh like the enter data is present over here we'll be adding more based on the inputs from your side and coming to the next thing uh like we like we discussed in the last EIP IP meeting Sam suggested that uh we should be integrating the uh ew bought to our website so that there will be only one check uh overall I mean everywhere so we have integrated the ew board here I'm am uh leaving the author section in the Preamble feed so that I can show you demo of that once I'll enter the inputs and click on validate

it will be validating and uh this is the uh ER that came uh I mean this is the output that came from the aw uh board check for this one so like we have integrated that to our website so it would be better accessible and usable and we'll be adding more features like importing an AIP so that it will be uh not just for the draft and we can also import and modify it based on that that is another thing we are working on and uh we let you know once it go updat and

then yeah before you move on to the next topic uh yeah ew does have ajason output so it's a little easier to parse um I don't know if you've seen it but yeah but continue yeah yeah uh and in the EIP uh EIP board we also added this filter for the labels in order to remove the unnecessary uh labels and also uh we have made some slight modifications so that uh the one that are in the withdrawn status will be more to the bottom as they least prioritized over this we'll be adding more Fu uh I mean general questions related to this so

that uh it can be understood by everyone even they are using the website for the first time and this is on update we have added a uh slot countdown for the Spectra upgrade for all these holia and Main net uh currently uh main net is not announced yet so it will be showing up like this but for Sephia and holki you can track it live over here it will be showing the number of Slots of and also estimated time that is under update and coming to the uh monthly inside

um there are three IPS three and one RP that mve to the draft State and two ercs and one EIP for the review and uh 14 for L colip and one for ERC and two uh eips were moved ercs were moved to the final State and two were moved for the stagnant state in the A and also we have added this last updated feature so that uh you can get an idea about when when it was last updated and when uh like in case if it is missing you can just look at this and

uh get to know that it is not updated yet and you can check back later so these are the updates from my side thank you for sharing um yeah that looks awesome thank you so much for all all the work on that great I see I see there is an open PR uh number 9244 yeah uh regarding that we we have added uh a full request to the eips doeum to add our website to the e.

ethereum.org and one editor responded and I think there should be at least two of them in order to uh get finalized is what I think if any other editor uh will also be responding to that it would be helpful thank you yeah to provide some more context basically this is for any new author who are trying to document The Proposal they can make use of this uh proposal Builder tool in which they can uh just add their text and they will get the MD file that can be made as PR and uh it will be pre-checked by eapw so there at least uh possibility of having some bot related

issues when they make the poll request so just uh to help out new Authors there all right um I see um that's that's pretty much for today's agenda for EIP editing office hour I am yet to get confirmation from um uh EIP only office hour for the next week if it is not planned then we will have our regular EIP editing office Hour 2 weeks from yesterday and uh yeah that's pretty much all about it anyone has anything else to add aare sorry um good afternoon I I think I'm lost somewhere um about the

reviewers um form can you can you please explain more so the reviewer form yes because um okay to be sure the reviewers have been selected already right I'm sorry can you please repeat I said to be sure the reviewers have been selected already oh it's not like that it's like free process if you are interested in doing that you can be a part of it it's not selection it's by choice like people are opting in for that so let me

provide some more context here about a month ago we announced um um a workshop in which we invited Community participants to join us asor I know about that and I feel the form I I I feel the form that's what I'm so what if ever whatever reviews you would be doing going forward will be um added to eaps Insight dashboard that I shared in the meeting here and with that we can we can get some data point to consider at the end of 6 months if you if someone is ready to be uh promoted as an editor uh and uh that individual

should be getting merged permissions on all so that's pretty much about the Rev program as of now but we are looking looking forward to have more um more resources made available to these new reviewers slash editors and yeah we we we are open to all kind of suggestions how we can improve this and get more people on board I also have one thing to add like uh if there is any possibility of providing the GitHub handles of the reviews that you want to track it would be help for us so that is one thing that I wanted to

add yeah yeah that's I think that's what Sam mentioned if we can have it added in EIP 1 then it will be easier for Community to follow um um but yes we will get there in the meantime I do have the list of people who have already filled up the form and I can share the GitHub handles of each one of them so the EIP Dash reviewer dashboard may be able to track their progress yeah that would be great uh Mercy I'm wondering if you have any more question on this or if there is any more support that we can provide you to actively contribute it here no no I'm fine thank you very well thank you so much um I um

I'm thankful to everyone who are volunteering their time to review these proposals this is very help helpful to all the editors and also the authors because the feedback will be integrated again and we hope to get better proposals anyone has any other thing for today I think I have one last thing that I would like to check with the editors how they feel about it I know EIP IP meeting has been managed by cat hers for quite long time we do open the agenda here I mean like create an issue to make an agenda item over here what are the

general thought and moving it to ethereum slpm especially for agenda creating agenda because I feel like um uh that is a place where all protocol meetings are being tracked and because this is out of the repository sometimes people um slip this meeting so if we add agenda over there may be helpful for people to follow and even more more client developers will be actively participating I got one thumbs up okay I got one more okay happy to see it moved I will uh initiate this conversation and um for now I am creating the agenda for the

next meeting in in the same repository as we did it till date but once we get approval to move it there I will close this one and U with will will add more from uh from going forward to the etherum pm get her repository well that's all from today's agenda I hope to see everyone third Wednesday I think it's March 19th the next time it is falling in the meantime we can still continue talking about it chatting about it in the uh Discord channel of e cats thank you everyone for joining us here today [Music]

a [Music] oh [Music] oh

[Music]