EIP Editing Office Hour #39

Transcript

welcome to EIP editing office hour meeting 39 this is issue number 341 on each C PM report sorry each C's EIP IP depository um I see Sam is already ready with the pull request so over to you Sam sure all right did you have any specific questions or you just want somebody to look at it uh No it should be just I think it's all done um had no more changes so yeah I double checked the yeah1 165 IDs as well thank you okay just go through

here make sure there's no recent perfect yeah I think I reviewed this uh pretty recently right I don't think anything significant has changed since then no it was moved to last call like two weeks ago there were like a few tiny knits that we merged in like a week ago um yeah changes all right okay that all seems

good game okay yeah so once it goes to final it cannot be changed anymore so I just want to make sure that your app absolutely ready this is your last chance yeah absolutely perfect I feel like we're absolutely ready okay redeem shares yeah this all looks basically the same it's not any license changes in [Music] here no good and good yeah I think this looks great cool

so than oh no problem thanks for coming out thank you so we can maybe take a look at the next final PR here 485 and Lily if you have any question you can please um write it down in the chat or maybe yeah just let us know so we can answer that question for you all right give me this link we

go okay okay so stealth meta addresses last call deadlines passed that's all good attributed these stealth addresses yep okay okay rationale looks like rationale

now there's a registry that all looks good so let's take a look at this 6538 6538 let's just make sure that their links are good yep perfect and yeah guess let's go check the assets quickly for that one assets 638 cc0 cc0

okay good uh and then we'll check the discussions link yeah nothing recent cool I think this is good to go to final all right so um feedback on the EIP and EIP process all right so um there's kind of two types of feedback that you'll get on your EIP um you'll get uh feedback from editors which will be mostly on the formatting and content like uh like the text of your EIP to make sure you conform with our rules uh and that happens automatically on your P requests

uh and the second type of Fe Feb back is like actually useful technical feedback um editors kind of provide some of that but not not nearly enough um it's mostly on the authors to go out and get um that kind of feedback uh so depending on what your um proposal is about can maybe point you at uh some places to look um but yeah for technical feedback it's mostly on on on you to find it cool cool um is there a way that this process can like go wrong like is there a way to like mess it up that like hurts the chances of the EIP being included like I I saw like in the last person

who's asking questions you said that like after M to final it can't be changed like are there like certain like I guess like pain points in the EIP process just to be like aware of um the whole process is kind of a pain Point um it's very slow so just your expectations accordingly for that um but yeah I I think actually getting so getting useful feedback and getting adoption are probably the the biggest challenges you'll have to overcome uh support for transaction so this is oh this is an EIP okay I haven't seen one those in a little while yeah

okay um so these are actually much easier to get feedback on um bring it up at an allcore devs meeting um I'm not sure if you're familiar with those or not but uh are you familiar with them I've heard of them I just haven't been to one okay so like I can start attending and watching the old ones just to get a sense of what's happening and then yeah exactly so so just watch what one of them it's kind of a zoo um and then ask Tim to put you on the agenda uh there's a I think it's uh yeah that one um and then you can talk about it there and people will comment on it and give you feedback so that that's pretty

easy oh nice yeah like I understand that this is like a a lot of changes I want to make there's like two new transaction types and like a new OP code I guess for like context I'm like a me researcher and this is just like something I ran across that I thought would be like useful or helpful so I'm just like trying to figure out like yeah just how to start the conversation with people about about it yeah so the the best way get visibility is definitely put it on the alra dev's agenda yeah okay should I have it oh should I have it like added like past this I guess like draft like PR stage to bring into the all the the other meeting yeah it's no you have the you have a number

now so you can you can bring it up whenever oh fine okay is there like I guess like danger of like me being like inactive on this for like too long and I get and it getting like marked as like stale or stagnant or something um so yes to both but neither of them is is a problem um so if you don't touch your PO request for 6 months and two weeks I think is what we have it set to it'll get closed automatically um but you can just make a new one it doesn't doesn't stop you from progressing and uh you get to keep the same number and if a proposal isn't changed like once it's merged um again I think it's it's 6 months I'm not sure on

the timeline it'll get moved to stagnant but again you can just make a port request to move it out of stagnant uh the only two like hard statuses are withdrawn and final so once you move a proposal to withdrawn or final it can no longer be edit like changed or edited awesome okay thank you no problem all right let me give this a read a proposal so it would not affect too much as it is final it will be final so you're breaking up a little bit Pua I couldn't couldn't hear you oh am I audible

now uh mostly all right oh my internet connection is unstable I'm sorry no I was just mentioning that because this is a core proposal there's a lot of support here once the proposal is accepted there is no chance of like getting it dropped dropped off unless there is something wrong or people would want to change see any changes to spe so um I think Lily you don't have much things to worry about here you just need to bring it up to all Cod of meing that would help you a lot okay awesome thank you this is the informational like looking for all right okay so yeah okay so that all looks good 217

that's fine so the CP introduces new 20178 transaction types and one new OP code enabling smart contracts and transactions the local sequen to an offchain entity all right these new transaction types work together to create bundles which is similar but weaker than PVS bundles okay I would say would probably be good for editors to be able to spell but alas I am lacking in that Department okay so which is similar similar to but weaker than the proposed Builder separation okay

okay okay one of the normal transaction that support specify the enti who can place the transaction in a bundle and optional block number that the transaction is valid the other okay a met transaction that do enter into execution but rather orders transactions of its own type and the other new type okay this meta transaction um okay transaction specif en allow to

include Bund block number theod oh give me one second e sorry about that I am

back okay the new UPG reveals to the evm and reveals to the evm The Entity that placed the transaction in a bundle if the transaction was placed in a bundle okay so I think the only other comment here is that Okay cool so currently in a single block

a single block build has unrestricted control over the final sequenc of a blocks transaction problem is sequencing the choice of who against to allow more parties to participate in the construction of single blocks by exposing sequencing Concepts inside of the evm this change would enable evm applications to reclaim some of the sequencing value that is currently monopolized by block Builders okay yeah great motivation okay okay okay cool that looks good so for

the delegated DX Tye the transaction payload should be interpreted as okay join with the rlp encoding okay the signature y par over okay for the should be interpreted as yep okay okay bundle sign cost okay up pushes the bundus

so yeah specs and then ethereum meter arog Glacier VM gas okay for delicated TX to be Val

transaction must be okay for delicated development included BX transaction okay good gas costs okay so this rational this in specification yeah I think we're still

in specification here execution yeah so okay the delated Tex T okay do not start execution contacts

must Beed before the start of any transaction list okay for should interpreted as okay transaction okay yep that makes

sense good search bundles okay security considerations and then Okay cool so I think that's everything

here um looks pretty good these are all really minor and should be easy to fix um and again you don't need to um get this review or get this merged before you talk about it um just bring it up when you're ready on AAR devs and uh yeah people will talk about it thanks for uh coming up awesome thank you so much for the review I appreciate it my pleasure 7636 unless there's somebody else on the call I don't think so all right okay can I keep on watching or like should I leave oh you you can keep watching it's kind of a boring call but you're welcome to stay oh cool yeah I'm

just learning thank you no worries and we also post these recordings on eaters YouTube so up to you oh um one thing I should mention is that this is an entirely author-driven process when you want to move between statuses you have to make the port request uh we won't make it for you what are this uh those different sort of statuses like sure what stat what status am I in right now so you are in no status right now you're but uh I guess idea is what we call it um and then once you're merged you'll be in the draft status uh so this is kind of the diagram of the

process it's an EIP 1 if you uh are ever curious about it um but yeah each one of these like arrows except for moving to stagnant are all um author driven so yeah awesome thank you no problem so that's good last okay so client for specific Cent bur number okay behaviors said two weeks out so I'll have to go to the n9th all

right exension of VIPs have for client yeah okay so I've read this one before let's see if there's any discussions on here okay I'm assuming that's been added yeah okay perfect so the a consist no running various climent implementations each client has its set of features optimization behaviors identify Cent software trans verion okay so understand landscape of

client software E network h

okay yeah that's great so we'll approve that and we'll move on to the next one 5625 to review all right oh yeah that's totally fine go for it oh actually what was the previous status of this [Music] yeah okay

7588 is the same idea draft into review okay blob transactions okay Rel M thir part Solutions okay okay yep it's all good

yeah that seems fine to review with you 7015 last call okay oh wait this is going to review okay nothing special there so let's pull this up and give it a read s nfts with cryptographically secured Creator attribution okay sure this Theory propos something Show creator attribution for nft standards blah blah blah propos mechanism with the

nft Creator sence required parameters creation parameters creators then validated and medat during the transaction with yes that's fine different wets yeah okay yep okay cons by okay so 712 needs to be in requires yep goodi def

theu be domain okay includes all the necessary fields for reconstructing the sign digest validating the signature okay okay 5375 okay so that's final so that's good

yeah I mean that looks good inter review with you all right 7578 okay this propos an extension of EC 721 implements additional functionality information pertaining the okay wait what are these are these like

terms for for what

for extension of the legal contract

disclosure Mak okay okay before can me the termset missing to a

document that is ipfs token has no properties what is set min revers set Min set properties of the token burns the properties must be deleted okay

okay um

okay set I don't really care about any of this okay function is c for token proper for token for should Behavior

contract called the contract supposed to be used okay the care properties function was properties for token properties for set okay forting so online this is 721

stand for for okay cool

721 blah blah blah y let's find the okay and then wait what why didn't that work that that that that why are you making three back decks now oh that's

weird uh and then I wanted to make a comment on here was it set property Serv it property set set

properties did I not already make this comment I feel like I did I guess not okay p for

for very common functions but AR part of

erc20 because there aren't any parties that need to coordinate our menting and bur burning the person who deployed the contract knows exactly how to call me burn and normal users said users aren't even allowed to call them um no no we'll go functionality Okay cool so that one's done and then we

can take a look at to draft Network upgrade inclusion stages this seems to be replacing the existing read me for execution specs that we have okay should replace this should test which is okay okay so this is probably going to need to be discussed on EIP IP yes I'm

also considering that yeah okay I mean we can skip that we can keep it for the next meeting and then consider merching it okay really five that doesn't make any sense God damn it why are these people

come here and do things okay I think sometimes we should take our time to even mention this in the all Cod meeting I try to pick up these PLL request from the repository directly but it would be really helpful for even for authors if they know about this placeholder and then they come and try to join their meeting like we did it with evm people so they try to join the meeting sorry could you say that again so I was suggesting that it would be nice if we can talk about EIP editing office hour in alore sometime okay yeah

so people are like Wily aware of this meeting happens every other week and um then they can also share their poll requests it will be like way easier that's a good idea I'll um I'll message Tim about that uh okay parameters of arbitrary

type this EIP defines a new box type uh boxes value arbitrary struct type is encapsulated H from the outer struct but transparent and type Jack by the wallet okay oh this is going to be complicated um yeah I was wondering like yeah okay to oh that's so weird why isn't that

working um okay view file and then we need to go here and then we need go to config what L is that that's screwing it up uh so this is markdown link status okay 7683 so let's let's go and find that

eips 7683 okay and if we go to the actual eips eips 63 yeah that EIP just doesn't exist oh it's probably an ercs that's why oh this is an interface proposal that's why like you know 712 it's talking about and but I don't find any other better place for it like I think

it has to be in this one no no that this is a decent place for it it's just yeah I see what the problem is here um maybe updating bot here yeah if you could create an issue we can perhaps allocate it to the St next go what are they what are they doing in here get out of here yeah there are plenty of spans yep yeah yeah

okay uh um so we need to create a bug for this so new issue bug report L to the P request and then relevant log output

should do [Music] that that go in there okay so take this go over here go over here go here and then we can reply to okay

but they should not be stopping from merging this PR if it is otherwise okay to be merge right yeah yeah I I'll force merge it Force merge okay um I new type box okay drain this parameter with type Define this parameter with type bites enabl the to contain arbitrary type and is sufficient to find the signature typ sure is a consequence Pig bit string yeah that makes total sense this is in motivation yep examples to make signature secure box members

encod okay box encod okay I'll just make these changes okay

refresh and I don't think there was any other comments I wanted to make on here so we get to just merge this um all

right so I'll create so what's the problem with this one okay for deterministic addresses okay okay

create okay okay nothing too terrible about that one all right and I think we have the protocol Guild Ops Call to go to so I'm going to switch over to that thank you Sam for joining us see you see you there