EIP Editing Office Hour #54 (EIP + ERC)

Transcript

[Music] Hold [Music] on. Hold on. [Music] Oh

yeah. Heat. Heat. Hey. Hey. Hey. [Music] Oh, hey. Heat. Heat. N.

[Music] [Music] Hold

[Music] on. Hold on. Around. [Music] Heat. Heat. [Music] All

right. Welcome to EIP editing office hour meeting 54. This is uh issue number 384 on eat catarders EIP IP GitHub repository. We are joined by Sam Wilson the editor who would be reviewing proposals today and we are also joined by a few authors. Um I see uh there is already a link posted in the chat. Perhaps we can start from there. The PR number is 896. Absolutely.

It's an ERCA. All right. Yeah, I think I addressed all your comments. Thanks for the review already. Um yeah. [Music]

Okay. Yeah, that's fine. Um Okay. So,

Yeah, that makes sense. [Music] Um, okay. Good. Yeah, that's all uh it's all good. Thank you. We'll just keep this open. Make sure it merges. Um just after the last call now, Pujo. Yes. Yes, please. All right.

But just to say, can I just check? Is it should I merge it now because you approved it and then do this one change before it goes to review or do you want me to make that first? uh it's approved so it'll go into um draft and then you can just make a new poll request after and you won't have to wait for me to approve it. Amazing. All right. Thank you for caring. No problem. Yeah, assuming this works GitHub. There we go.

Okay, cool. Okay, so I still have my doubts about this thing. Um, okay.

So, just leave a comment on this one. So, That's Yeah, because this is this is super new.

Um, okay. Neat. Moving on to 918. Okay. Hi, Sim. I want to Hey, how's it going? Hi. I wanted to uh ask you a question. Um so we've done uh we've gone through the EIP process uh in the past and this was before um it was just raw EIPs. There was no ERC's. I wanted to ask now going about it wanting to produce a new ERC. Uh is it the same uh system that we have to go through uh and the same proposal process

and it's just for ERC's or or how is it different? Uh yeah it's just a different it's the exact same process just in a different repository now. Okay. So, we'd go through the idea, the draft stage, uh, review, last call. Okay. Exactly the same. All right. Marvelous. Not just, do you have any questions? Nope. That's all. Okay. All right. Marvelous. Thank you. Yep. No problem. Take care. Yep. Likewise. Okay. So, 7743. Let's see if they have a reference implementation. Oh, I think they

do. Cool. So, this one we can probably prove and go through with. So stated for non funible tokens by multiple owners the mole cool traditional fees shared over distribution collaboration maint provider fees. Okay. Okay. Token ID generated in the caller added to the owner set recorded as provided. Balance of the caller is incremented. Okay. Here's list of owners for each token owners to start an

innumerable set. Okay. Um trans okay or can transfer the token using. Okay. Three and four.

See transfer from Uh okay.

Okay. Done. Um then same kind of problem with the approval functions. Okay. Proof of functions. Okay.

21. Do these even have safe transfer? Yeah. Okay. Uh The orange should m ambiguous.

Um standard. Um so why do they disable those? Um, did they align with the ownership structure? Why Okay. Um

Okay, good. So, we can move on to yes to the review one. But I wanted to bring your attention towards a comment that is shared by the account abstraction team. It seems like they have bunch of uh shorter EIPs. Uh those are kind of a blocker to merge the other one. So I have the link in chat. So whenever you get a chance, please take a look. Sure. You do that right now. Well, capabilities for accountraction. So this one just hasn't been reviewed yet. 790. Wait, how did you get 7902?

sign 7902. Perfect. Uh well capability for new wall capabilities providing a way for depths in account walls to communicate. Um So, Okay.

Um, so what are the capabilities here? Okay. So, oh, there's several of them. Okay, that's fine. Um, Okay, good. That's fine. Good. Define

space deposate documents. Um, okay. So, Okay. Uh 4557 is contraction smart

contracts function Ethereum. However 4577769 define a low level frection. Um do not specify for advance aware comma wallet. No, actually we'll do that up.

Count abstraction. Okay, this address set of capabilities tail for a with specification everything must be done on a single chain and atomically we define the following listing capabilities which together

governance described in6 okay it's been a Um, okay. 770272 Okay.

Okay. Okay. The person gave us a lot of the application for one. Okay. Okay, cool. Yeah, that's fine. Um, unfortunately I have to end a bit early today, so I'm going to end here.

Um, I will see you all the the next uh office hours. Thanks for coming out, everybody. Thank you so much for your time Sam and [Music] for [Music] Move on.

[Music] Heat. Heat. N.

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

[Music] [Music]