EIP Editing Office Hour #71 (EIP + ERC)

Transcript

[Music] Super

interesting thing. is heat. Heat. Heat

up here. Recording in progress.

Welcome to EIP editing office hour meeting number 71. This is issue number 1721 on Ethereum/PM repo. This meeting is going to cover EIP plus ERC related pull request. On agenda, we have a couple of finals, a few review miscellaneous and draft proposals, and we are joined by editor Sam Wilson. Thank you, Sam, for joining us here today. Maybe we can go ahead and get started with the final one, and then we'll get into the proposal which is shared by one of the authors who is present over here.

>> Sure thing. So, going from last call to final. Um, okay. What change did you request? Oh, yeah. Okay. All right. Uh, we'll flip you to split and we'll give you a read.

So expirable NFTs and SPTs non funible SP tokens expiration time use cases that's good movement to final introduce an extension for nonk tokens expiration mechanism tokens become valid after predefined period there's additional layer functionality ensures the expiration mechanism does not interfere with existing NFTs or SBTs preserving transferability for NFTs and compatibility with current DAB such as a Yep that's all fine before there's the IP NFTs have custom mapping such as inconsistent. Yep.

Okay, that all looks good. Uh must implement the ERC set. Yep. Okay. Um sure. is Dr. Exper. Yeah. Okay. So, they just applied my

change there. Good. That's fine. Yeah, that seems good. Let's go to final with you. Actually, wait. We should check this one last time. Not that I suspect there is.

Yeah. Okay, we're good. Cool. So, that can move to final. Now, moving on to 7878 hasn't been reviewed yet. Okay. Bequathable contracts inheritance of tokens after the owner's death. Perfect. This proposes interface cred tok after the owner's death tok set up a will and yep that's fine crypto tokable interface. is.

Yep, that seems fine. Nice and simple. Let's make sure there's no ongoing discussions. Yeah, I mean that's not really

technical conversation, so I think we're okay to approve Yes. >> Hey, so we have two standards added today. >> Yeah. >> The next one we can perhaps take a look is uh ERC1149 is the PR number. Yeah. Uh I think it has already been reviewed before and we have author on the call to answer any further question. >> All right. it's going into draft.

Much better. Should expose the domain.

5267 5267. Okay. Type hashes. that's an interface.

Damn it. Cool.

So, let me do this. I think most of these I can just apply now and you can fix the other ones later on. Yeah. So with these changes, this proposal can be merged as a draft today.

>> Yep. >> Yeah. So >> and later on he can come back with other changes when review. Perfect. Y All right. Cool.

>> All right. We can move on to the reviews proposals. Yes. [Laughter]

Actually, can I just edit this one? That might be No, I can't. Okay. 363. Is it homorphic? I always forget.

Otherwise, I think this is pretty good. Um, cool. Uh I'm looking at uh the earlier approved PR 1178. It seems it's not getting merged. Although the bot says that uh all reviewers have approved it.

>> No. Yeah. It's because uh >> but it seems the changes requested by Victor is also Yeah. Incorporated. >> Cool. >> Oh, it's Mar now. Thank you. Okay. HD wallet and treasury management.

It's going into review. This represents okay with rapid development of blockchain defy secure management on assets traditional private key management shows to me. Yep, that's fine. That's that blob. Let's use the following. Okay. Link to the pip. Good. Good.

Yeah. That looks great. Here we go. So that was 7908 7829. Oh, this one was approved. Why didn't you approve? Because to add to the motivation. Okay, let's

see if that's been done. Yeah, it has indeed. You're going to merge or you just going to sit there?

this. There we go. There we go. 7829 7518. Just give me one minute here. This is moving into review.

Dynamic compliant interop security token. DCISD security token framework partitions for datm regulatory compliance management and crash interability. All right. Um this request security token set extends ERC 1155 to provide a flexible framework for managing compliant real asset security tokens introduces the concept of partitions where each token ID represents a distinct partition with its own set of rights and privileges both fairies.

Token locking H. It's weird. Okay. order includes features set for

security token sed periods for trans for recovery less keys address freeing for compliance efficient pay mechanisms dynamic compliance management using offchain vouchers by providing a standardized interface these features yep good it's fine I'm sure that's an interface mcate return the transport balance ID Thank you. Just

check. Okay. Mine 470.

Did we like sneak into rationale? No. Okay. Um Okay, cool.

So 7518. So now to MISK remove legacy deposit and ETH1 data fields. >> It looks like this is already approved but not merging for some reason. Yeah. So, it's >> Yeah, it's missing these things. do we need to leave a message?

>> Um, I mean, I could just take care of this stuff, I think. Um, yeah, this shouldn't be too bad. So, this should change to 8015, I think. Okay, then we need I've got a lot of messages on here. I should take care of those, too.

So this is a 015 this Okay. So, we can grab this. Bring it

over here. Put that there. so what else do we need to fix here? We needed the title is too long. That's that. Yeah. Okay. So, that should fix that.

This needs to be linked as well. So let's see if that will merge now. Yeah, that one doesn't matter too too

much. link check. So, this should merge when this is finished. Um, I'll probably need to reapprove it though. Cool. Let's go take care of some of these because I will forget otherwise. Bunch of likes. Okay. >> This is a very good message system that they have created at Eat Magician. >> What do you mean? >> I mean, I like it because it's helped us manage things, right? We need to I mean there are certain tasks that we can perform by getting these notifications directly.

>> Oh yeah. Yeah. They're super useful. Okay. Wait. What's going on this one? Uh okay. This isn't directed at me, I don't think. Cool. 8170 to 8174. Really?

8174. Huh? Yeah. Weird.

So this change is for EAP template, not for EAP1, right? >> Yeah. Yeah. It's just weird that uh we made that mistake. >> It's good to know that people are following it very closely. >> Yeah. Yeah. Uh so that means we also need to change this in Ethereum's Okay, so that's taken care of.

so this one here 7980 fix issues and EIP. I mean these are super super nitpicky. Um, but that's okay. >> Yeah, that's why I have added in miscellaneous like Yeah, >> this is fine. So what did this merge? Are you in final? Maybe you're in draft. And then the author is Sir Budington.

Sir Budington approved. Ah, that's why. So this should merge itself in a sec. Grammar and spelling corrections. Your draft. Yep.

Okay. This is in draft, right? Yeah. I'm going to have to force merge this

now. Oh well, it's okay. non relative lengths. Why? What's wrong with you? So 81 8015

That did I paste that there? I must have. Weird. Where's the other one? So that's 7864.

So contract feature detection Method to publish detect contract features that lack in your RC165 interface. Okay. Method to publish detect what features. So, you know,

Okay. Feature setting property of a contract that cannot be expressed for your C165. Feature name should be a reverse domain name that uniquely identifies duplication. Okay. Feature supports feature. Oh, you do have a May. So I guess

cards up here. Yeah, that certainly looks like spam.

>> Yeah, we can just close it. >> Look, another one. Chain specific subsection.

Ah, this is my own PR, >> but it has been approved, I guess. So you can go ahead and merge it. I don't know for what reason it did not get merged. >> Oh, it won't automerge to the template. >> Okay. >> Yeah. At least I'm pretty sure it doesn't auto merge to the template. Okay. Multi-dimensional gas metering gas

accounting by EVM resourcing from resource mining UX. Cool. Abstract. This propos introduce multi gas used at the block level. This enables Ethereum to increase throughput and better control excess resource usage with minimal changes to the protoc during transaction execution. Gas is meed for each resource dimension such as compute and state. At the transaction level, everything remains unchanged. Transaction still pays fees according to the sum of gas used across all resources and so it's a single gas limit imposed on the same sum. However, at the block level, only the gas used in the bottleneck resources considered when checking if the block is Oh, interesting. When updating the base view for the next block, this gives a new meaning to the blocks gas limit and and the block's gas target which now

corresponds to the maximum gas that can be metered in a bottleneck resource. This also separates transaction pricing in essence the way of measuring consumption of resource by transactions from block metering. More concretely introduc Oh, my monitor just decided to turn off for a second there. Okay, we're back. Um, specific operation gas cost enter the multi-dimensional metering model. Even operations are assigned a cost vector pure computer operations compute ops.

I know they actually split it up into like separate documents. That's nice. Actually, I don't think that's just

useless. Okay. The operations list and blah are assigned a guess cost vector equal to compute cost where memory cost defined by the function calculate gas extend memory. Uh, I assume that's Ethereum. It is.

So, let's go and grab let's say yes, it'll probably be in Yeah, gas. Uh do some of gas factory to the

operation list in place. and log operation seven of gas cost vector operations in log ops is TPD benchmarks. Okay. Under the multivention metering model each transaction intrinsic cost is defined by blah calculated intrinsic cost. Similarly, a nice link to that Gas account six dimensional cost factor

the gas accounting during block box execution. So changes keep track of single total gas representing the I operation of a transaction say with the cost factor. The following variables are updated. Cash remaining for the transaction is the set of these things. You need 64 bit unend Let me get that

done. Benefit of this proposal again. Okay. Okay, that's all fine.

Bounce And these are just lists of operations.

Perfect. Cool. And I think that's all the time we have for today. So, thanks everybody for coming out. Um, if we didn't get to your proposal, I'm sorry. I'll get to it when I can. Um, I guess our next meeting is in two weeks. Or do we have one next week as well? Yes, the next meeting is in two weeks. Thank you, Sam, for taking our time and yeah, so see new new proposals getting in and we have two finals as well here today. >> Yeah, it's exciting. >> Yeah. All right. See you in two weeks. >> See you.

Thank you. [Applause]

Heat. Heat.