eth_multicall Meeting, Mar 25, 2024

Transcript

let's begin uh from my side uh I finally got all my tests up and running merged the latest Branch into it and will'll ship you the docker image soonish and I would ask you to run uh the tests carefully because they have a extremely large amount of fixes and merges and REM merges so if you could like uh test all so the old stuff it would be good and of course all the things that are now fixed in trailer should be in them so yeah sorry for long delay but we had a little bit

of the merge hell and uh now we finally fixed it uh so is there a new container uh I think in like 30 minutes it will be out there okay and I saw that there was large disc discussion on this week so if you could highlight what happened on the chart it would be really really appreciated it's about the base feed that they want to the BL base fee in the what meant in the production in the main net just couple of weeks ago is that there's a PL base

fee which is kind of like named wrongly because there's a base fber gas so we feel that it should be REM named similarly so now uh there's a pool request that would change it to the plop base fee Bas Fe BL black I was looking at it and my head went a little bit crazy because it is always here using like snake case and it is mainly camel case in all of our API so my question would be do we want to keep it with this underscores is it from some ICS or or can we keep it CH case as we usually

do oh that's that is just about the spec not about our our spec and in their spec they're using the camel case or the well I know what it's called the UND scare the snake case yeah I don't remember but the basic idea is do they have RC any IC calls bound to This n case there's the blob base fee the E blob base fee I think which is bit annoying that that exist now but I guess is there a base it base fee as well no that's you have to get the block to get the base fee so it's be different so there's

the 4844 or whatever number it was spec itself which I think in those specs they usually use underscores so it really depends on who's writing it um that is unrelated to what ends up in the rpcs the rpcs always end up with I forget whether it's snake or camel but um they don't necessarily match the casine that's in the spec itself if that makes sense so this is say we can have we should have eth simulate Matt the RPC the standard RPC casing whatever that is regardless of what the 4844 spec says and that's normal behavior for how this process

works all right add of Cu can someone remind me is um Jason RPC for ethereum usually snake or camel it's been a while at least in our one it is is usually camel okay I believe it's nether mind matches gu for the parameters and whatnot so I'm guessing that means are both camel that would be bad if the RPC would be some of them would be camel and some would be snake so yeah yeah so so what we'll match we'll have eth simulate match whatever the standard is so it

sounds like camel and it's okay that that doesn't match 4844 by by hope they will change that but I I don't know how difficult it could change now afterwards I guess now it's on some them's list so I don't know what that means are you talking about the changes that um G11 proposed yeah yeah so my guess is it sounds like there's no push back on that so that one might actually go through um to get the renames of those variables to blob have blob included I am quite surprised if there's no pull back because it will some of the things will break I guess because they

have been using the wrong names unless they will make it so that the both names out there uh so I think that nothing actually uses those yet does it like there's no communication there's no communication between clients that uses any of those like just some something in your code that you would refer to yeah there the eat plop get one PL eat method that will get but I guess we we don't propose to change that but I I don't really care if that not changed but yeah of course would be

better I think the key is you just propose your spec change right around when everybody's exhausted from pushing to get ear and then no one will push back on your proposal like I'm just too tired you s like US government get getting some random rule through and you just package it with the others sure throw it in his pork with something else but I guess after we get this through then we could propose to get that it get plop plop what is the plop fever get Bas Fe blob gas that there

would be that kind of method but it could get Blob base fee that's bit conf that's named differently than it's in that method but yeah it's still quite different different kind of method I'm afraid that will be harder to rename the method if people are already using it yeah but you you could create a new method and then deprecate that old one ah do we have any other updates uh not much from

me didn't do a lot of simulate stuff last week but um I don't know if there is also a lot to do on my end there is no at the moment I think now when the nether mind is kind of f are long then I will do more testing and then I probably find some bug in the get if there there's going to be some mismatches uh you could release the main that oh yeah main line I mean yeah I mean ideally we should freeze this spec before we merge yeah I've been out for a while have we

made any significant changes to the spec recently last week oh okay but we just renaming of couple things and then one u g to 64 there to 56 so quite small ones but yeah there still somewhat breaking yeah naming one is quite breaking if they my my my guest server ran out of its two 1.8 terabyte drive and so I wiped the database and started over so we have until that runs out of dis space again I think my nether mind server also is going to run out of dis space and so hopefully I can this be the last time I

have to wipe it before I can just Outsource to some third party but I need to get into the main clients to do that that's why I want it yeah hopefully soon is the get changes reviewed by all the get developers so they would be kind of easy to get so there's no missing processes for those usually reviewed by two people um but yeah I mean now is is a good time because the hard work is over so like we are merging more stuff like I had one big PR merged last

[Music] week so there's more up that for getting big changes in actually is this change done in get that we renamed the validator index from camel case to that or I wonder wonder was it like that in get before it was just just a bug in the spec and it wouldn't didn't change the get uh we were on cam case I believe okay so that was just just a bug in the spec okay so so kind of if it didn't change anything and then I removed the blob

base fee from the uh header because it wasn't part of their and I guess get wasn't returning that anyway because it wasn't there for long uh the BL Bas yeah so when you're it's returning then then I added that we are also return in the block face fee as as in the block but then I removed removed that as it wasn't actually part of the block so where it is now you can set it but it's it's not returned as an object so that's because it's not part of the

header you can override Block Base fee but you cannot see what it was what it is for the block okay then we'll need to remove it from at least our implementation are you are returning it currently yes I probably I read your standard like when I implemented it two or three weeks ago when I implemented yeah yeah I added it there because I thought it was a part of the header but but then C said it it's not there so then I removed it uh right so wait I I haven't renamed it though yet so we can we have um blob Bas

fee as inputs yeah but it's called blob Bas fee it's blob base fer gas that's that's the new one blob base fer gas no B base Fe go oh yeah it is that yeah because we are waiting for that thing and I it I think we should keep it what it is at the moment unless they change it in the okay yeah so that's maybe something that we need still need to do the change if we can get that change through but I don't know what's the timeline is it someone going to discuss about in the it's it's on the team's list list here but I'm not

sure exactly what does it mean that it's there they want to move that spec to final but then there's some it's least there's a clarification so maybe it's coming there or not but yeah let's wait for okay has Lucas had time to look at the validator different

differences and the validation mode not really uh maybe you can do that it looked like I want yeah I think as soon as we'll push today's dock image we'll be able to look at them and uh now we have like cleared out the basic things that definitely happen before the block is published so we know for sure what happens to each transaction in what order and it will be like fast fast right out so I'll do it probably later today all right and you'll be able all to look at it sounds

good have we been running the test if there I more matching with get with the hash level not yet we have not done that yet okay well I guess if we don't have anything else y thank you all guys thank you yeah thanks thank you bye bye