EIP Editing Office Hour #44

EIP Editing Office Hours · 17 Sept 2024 · 32:07

Meeting 44 of the EIP Editing Office Hour, held on 17 September 2024. EIP editors and proposal authors work through open pull requests and questions about the Ethereum standards process. This meeting covers EIP and ERC pull requests heading to Review and Draft.

Topics

From EIP Editing Office Hours, hosted by ECH Institute.

Transcript

all right welcome to EIP editing office hour meeting number 44 we have a pretty light agenda today I'm going to get started with uh 7758 let's take a look at this so this is changing status to review doesn't seem like there's anything particularly complicated on this one Let's uh take a look so transfer with authorization all right set of functions to enable meta transactions and topic interactions with erc20 token contracts for your signatures conforming to the EP 712 type message yep okay cool 2612 is the sequential nones

us okay does okay more okay special problematic gas are very high multiple withdraw attack all right this all looks good VNS okay good that all looks fine

okay sure okay okay M transaction y perfect 72 looks good okay backwards compatibility sections really nice there's a reference implementation great and know this is a well written e let's approve that and we will move on to the next

one 728 uh okay review last call it's a lot of commits why are there some many commits here okay the link to read me but now the HTML proofer fails with okay that's odd so why is that fail assets ERC yeah but if you're look in

here at the other yeah they're all ERC so this needs to be yeah perfect that's nice so let's give this

whole thing a review okay launching data containers are series of interfaces yep that's fine stand okay okay yeah I don't think this changed

very much since uh the last time I read this yeah that's all good yeah that's fine otherwise so okay 6734 okay

so okay going to review token list for okay

all right so this looks fine just make sure there's no other errors in validator just the one perfect 3220 let's see if they have a p request open

to uh I think it's the RC's C's or requests 3220 no okay Z all

right 6735 what is this one thanks that's super useful okay so you're moving to okay all

right specification it's fine this is all specification for sure yeah this seems fine okay then we're going to go look at

7208 oh we have a another person on the call hi um do you have a particular proposal you'd like me to look at hi yeah we added it to the agenda to the last one oh this one down here all right yes okay did you have any particular questions uh about this or you just want somebody to look at it uh yeah no particular question I'm just trying to get it merged if all the comments all the commments should be uh addressed I will take a look I like your uh your abbreviation that's

awesome mechanism for D use the extension while it's API in a tamper proof for okay well s request and STS St with in a T man of your ass request the adap associat public key with Stud record corresponding private oh that's interesting so the idea is like you can prove that the owner of the domain is the one that is making the request exactly okay cool so uh take you off my editor hat and

putting on my technical hat um so does this mean that all of the requests have to be generated on the server side correct that would that's for the first iteration of it I think in the future we would like to discuss with the community adding something like CSP so that you don't necessarily need a server and you can do restrictions on like uh without necessarily signing the request but restrictions like what what contract your page is supposed to talk to or things like that cool yeah that's awesome um okay the tax URL Chase manifest is hosted should be a no another technical question couldn't you

just skip DNS entirely and just request this file yes you could uh we are we're trying to do both that gives more customization for people but you could uh you could just check the well-known part directly okay for

6 I think that's right but let me just double check and RFC editor. org RFC yep that's the one okay JWT practi cash okay the

ABS exp hours okay what yeah

okay I didn't call it a um I don't think anything's changed okay okay okay manest y browser

okay SCH okay typ script interface cool okay

1193 provider interface so do you need 1193 yeah okay okay interface you call E transaction and then you do wallet sign request and you pass yeah okay cool okay nope

read that wrong it's add makes back okay the request yeah that's good um yeah that looks great um few really small suggestions and then uh we can get

that merged I see we have a few other people joining the call um do any of you have a proposal you'd like me to take a look at all right well we'll just continue on with uh where we were sorry about that op error I left the oh no wores um I will solve the I'll

resolve the the comments shortly and if you're still around in an hour or two should be ready perfect I'll I'll take a look thank you thank you very much yeah okay so we did that one 7702 7208 oh it's just there twice that would be why okay okay so let's look at some eips going into draft okay so let's give this a

read so this is going into draft can I edit this I can perfect Okay C PR to increase number of block

provide more scale to etherum L2 yeah okay okay BL increases for transition okay testable changes okay so this looks good what were other people complaining about before I just merge this yeah this is

perfect all right blob through put no e transaction with freefor all tips pry pay transactions all right that looks good let's go in here 7768 okay so we're going to edit this and then we're going to set the EIP number to 7768 uh commit changes oh I have to

rename you as well 7768 and then are there any other references to eight in here I guess there's that one okay we're good so we'll Commit This refresh and start reviewing account having now ether consent transactions pay tips using new free all bucket all right a technique is introduced where an externally owned account having no ether can ciz the

origin. right for for the

client okay control Sal prepare transaction sign series of transactions if Alice would like to provide consideration for executing these transactions she would ensure that well-known address on the network the free FR a bucket with control tokens the end of the series of transactions all s transaction an carefully considering that they will AV the will maybe none of them on the yeah to service that communicates with block proposers for example consideration St to the free address this typically be the last in her series of transactions sign a transaction from any origin to send ether representing the current cast okay to the freefor all account to

preload any necessary responses start an execution Conta and include this send ether transaction all alysis transactions the execution context identify token sent to the freefor all contract address rather valuable consideration ACR to the freefor all contract sign a transaction two from any origin take security of the consideration from the fre account include this transaction the execution contacts the use send consideration to the block

proposer without knowing who they are and the block proposer must be able to realize this consideration the CIP proposes to use a wellknown contract account for the deployment for this purpose and here's the required interface execute okay back over here

edit you okay so that's five cool so that's 77 7 6 8 done and we will move on to's this one and this one so let's take a look at this vulnerability and exposure identifier

one ready commits after my last review let's see there we not so that can just stay there and then we did that one already so let's see if that's been finished here okay

good let's see all of the good yeah no reason not to approve this cool and I believe that is everything for this week thank you everybody for coming out and uh see you all in 2 weeks or tomorrow if you're coming on the call