EIP Editing Office Hour #37

Transcript

welcome to EIP editing office our meeting number 37 this is issue 335 on E cat herders EIP IP GitHub repository we have a handful of proposals uh listed here for status change and other reviews final last call and I think there are some miscellaneous proposals where we are not very sure like if they needs to be open or they can be closed so I'm having all of them listed here may I request Samson to perhaps go ahead and start reviewing the proposal we are joined by author of proposal 7575 which is PR number 411 on ERC GitHub reposit Tre yeah sure we can get started with

this one hopefully this will just be quick yeah let me know if you need any context oh yeah of course okay so have have there been have there been any significant changes uh recently to it or not really there were some comments that we clarified but it was really mostly about kind of clarifying how it worked and we added

kind of a reference implementation and a few other things just to make that clearer um yeah maybe yeah the reason why we're uh also i' really like to push this forward is the fact that this ERC is a dependency of ERC 7540 which is asynchronous B standard um so yeah yeah you want to get this one done yeah exactly that makes sense okay SC good fine and this is the uh correct

interface ID you've triple checked it I could duple check it now that you're saying it but yes okay we have it in our code already implemented so I think it's right but I mean I guess we can still make changes like that in the last call S right in theory if you find an issue yeah yeah you'd have to start it over again but yeah Oh you mean like the Lost call that plan yeah good let we have a reference implementation here that's

165c oh okay yeah that makes sense I think at least I think so if I'm looking at it yeah yeah it's in it's in all of them so that makes sense that's prob erc20 oh wait you can put functions inside functions I didn't know that oh that is actually a typo a okay good catch that should be two different fictions below each other yeah yeah I know I figure this for you no I can't okay I otherwise it looks fine so if you

just want to fix that typo um yeah it'll be good to go thank you can I ask a clarifying question in the process actually yeah of course so so I said 754 is dependent on this one so when this is mooved the last call can we also move 7540 to last call already then or does yep 7575 first need to be finalized or how does that work no you can move you can move it to last call yeah cool it just has to be equal to or or greater than so okay right awesome so I see there is one proposal

pending for final and then we can go to the last one here on for the last call [Music] okay so last call deadline is passed we're removing 6538 why are we removing

okay yeah so you can't move that well yeah I guess don't

okay let's see if there's new discussions that have happened down here not no okay okay the specification establishes a standardized method for interacting with st addresses which allow senders transactions private accounts exclusively accessible by the recipients the specification Del St that address protocols based on okay synchonization of non interative

stealth addresses yeah that looks good e okay

yeah this looks fine I'll this and improve okay so let's go take a look at 6538 yeah yeah there's no recent discussion on here okay yeah that's pretty minor typo fix

that's fine okay why are they defining registry contract I mean oh because there's only a single one of

them that makes sense guarantees propability that's fine yeah it looks good so the only thing we need to do is change the last call deadline so two weeks from today is June 4th June 11th there all right so the next one here is a bunch of

miscellaneous proposals like bulre was um as we can see 2 33 34 35 they are kind of going into together the proposal's last status is stagnant and before stagnant it was in draft status so I see there are two different set of proposals made here one is to move it to review which kind of makes sense because it is in draft to stagnant can be moved to review but then there is an ask to move it to final because this has already been implemented somewhere I wonder what could be done here

to me personally it doesn't seem like a right fit yeah but please take a look last calls they can become final to key deration my only worry is like this may create a bad precedent and people will say that because this is an ERC people can come back say that because my proposal has already been implemented mented in this in this project it should be moved to final okay gravity tree hierarchy balance 12

31 key space um e okay before the first use the keys

kid yeah I think this is pretty solid as far as the IPS go and cool

so we just I say two week on the 11th okay view we can move on this one so deter your account High structure

your description really doesn't add here for okay gettinger but Purp best yeah

[Music] okay be signatures over blah okay by integers yeah this all looks good

compatibility cool [Music] okay this View do the same thing here get

so you're likeing to those good good think this is all probably fine a Jason schem good okay cool do we want to merge that as well because uh uh you have already change the date so if you merge it it would be yeah so the problem is I I don't want to merge it just like setting the descriptions for Carl yeah all right in that case there is another request here like the pr 362 363 and 364 that can be closed now because all of them are being

addressed by 386 sure and for the next one I wonder if this needs to be closed because this seems to be a potential ERC open on EIP GitHub repository yes I think you're

right yeah there's solidity in here so we can simply close it because I think the message has already been conveyed yeah or you can always add it y all right and I think similar case with this one as well this is an ERC okay okay let me see oh no no no that was just the primary comment why oh yeah so there is this last comment by Bumble F like the these

are the same idea so we can close this I don't know if this is right or wrong but yeah you might want to take a look well this will close itself and three months so I'll just not touch it and uh all right eventually of course of course I am just trying to into proposals yeah but I mean like there's no need of keeping it open if it is not needed anymore but that's all right it can be closed all by itself unless author chooses to do that so there's one more proposal which is um

ERC uh that is ERC number 369 and has been requested in the comment of this agenda to be reviewed there this one here dual nure yeah yeah okay okay that seems fine proposal allance

integration of funable contract semi funable 2 contracts and secing operations between okay compare CH okay 20 okay

okay I that's a pretty pretty easy one and let's comment on this just these changes I'm probably going to have to leave a little bit early today I just got a call from my lawyer um so I will finish this and then I will um see you all in two weeks probably uh Sam if I may request you to whenever you get a chance to look into uh an EIP versioning scheme e that was also proposed in one of the ipip meeting and yeah I remember that one yeah these

people showed up uh the pr number is 8034 so if they can get a number it would be easier for them to communicate they also showed up on E of call requesting like they want to implement something over there had some proposal but they're not moving forward because this hasn't been merged yet okay yeah awesome yeah that is there thank you so much Sam for taking our time for this see you in two weeks yeah see you yeah by