Dencun Interop Testing #37

Transcript

[Music] J [Applause]

for hello everyone welcome to the first 2024 testing call um I posted theenda on award Dev but uh here's a link as well um so I just caught up with the last cordev I think probably the most important important thing to check in on right now is uh how our teams uh looking with regards to client releases for Gordy um then Mario has some testing updates as well and uh finally I I know

from aord Dev there was some conversation about you know coupling uh sepolia and hoski or not uh if people want to talk about that today we can as well but otherwise we can also uh push that uh to the uh ACD call later this week um but yeah I guess maybe to kick things off um is there a team who thinks they can't get a Gorly release or pre-release out this week and then otherwise uh yeah it'd be good to hear when teams expect to have one oh yeah Terence when you say this week is is

there like a specific date because like we can make this week but it will probably be later in the week if that's okay so I would personally prefer the blog post to go up with all the client teams like Wednesday morning around this time because this gives a week before the fork I think like I mean yeah anytime after that uh I think we'd have to make a call about whether we want to just have the blog post like if say all the teams except one have things by Wednesday then it probably makes sense to have a blog post with all the other uh client teams and then have like a TBD for for one of them and update the post uh obviously if

no one is ready by Wednesday then it's it's not much use to put the blog post up um but and hopefully at the latest on Friday we can have an updated post with everybody's releases in um okay so that's SC yeah we will try to P for Wednesday yeah we got it um I was going to say for Lighthouse um we're planning to do a pre-release by Wednesday so that should work with the blog post timeline you ever thinking cool uh and then there's a comment by load Star as well yep same goes for lotar we'll also

be able to do our release by wday the tech will start release um tomorrow morning Australian time and uh we should be able to have the release by this time Wednesday uh maybe not exactly but should be okay a and then gu in the chat as well um is there anyone from Nimbus on on on the C side it doesn't seem like it so follow up with them and then uh Basu yeah we're good okay uh nether

mind uh we are testing uh our RIS cidate versions We have some issues with block production but uh probably it will not be a blocker for a release we are planning to do a release uh most likely tomorrow uh and it's likely that we will release once more before uh gly but uh we are still testing so we will know more uh tomorrow but uh for sure before Wednesday there will be some version supporting the work from newi awesome thanks and anyone from Aragon or re on

call okay I'll follow up with those two um offline um I guess okay so Gordy releases aside were there any issues that any of the client teams wanted to bring up um to discuss here uh so I did have one thing we were not totally sure about it's related to uh this change oh I think I referenced the lighthouse PR not the spec PR um the fork Choice filtering change I was wondering what the status of that was for client teams um do clients have this Fork Choice change implemented for girlyy or

are we waiting for like main that client releases to add this or have clients already added this for prism we have um already um added it and um it's running on the production Noe I think it was like a few months ago already okay gotcha does anyone else know about their client uh te is not yet added this at the moment okay I think for us it'll be unlikely to be in our Gorly release but I think in our hsky suppo release we might include

it got it and should we put this on the agenda for Thursday so that all the CL teams uh can at least have a look and chime in yeah that sounds like a good idea okay um I'll make a note here actually Sean do you mind posted it on the agenda I have so many tabs open because it's my first day back so thanks um sweet any other issue that the client teams want to bring up uh Matt I see you have the E blob gas price uh in the chat yeah I was just curious um have any client teams run into rpcs that we feel

like we need or we just kind of have some tooling setup that doesn't use them and we're only going to find out when wallets start sending blob transactions I guess has anyone implemented each blob gas price I think it's still just a proposal on the execution apis but there hasn't been much chatter on it I left the comment back in November it and I assume it just mimics the other gas price apis we have yeah exactly yeah uh I'll post this PR but there was a PR

to add this method to the spec and to add blobs to e fee history as well as another method and there hasn't been much discussion around that so if we could get a bit more clarity on which direction we wanted to go with then that would be great yeah so clearly we won't have this for Gordy but it feels like something we should at least get people to agree on hopefully by like the next CDE so that for the potentially last set of test Nets we have it or in the worst case that we have it for main net um because yeah I assume at some point wallets will start will want to start testing

um okay so yeah uh let's follow up on that one with teams and I'll make sure that it's at least flagged on the ACD agenda uh which gives gives us basically two weeks to uh yeah get some feedback on it and hopefully we can agree to a final proposal then um I guess yeah actually yeah we do have Roberto on the call right uh yeah from basis perspective is this urgent or um are youall able to work around it uh yeah this hasn't come up in

particular um yeah because uh we have you know hooked directly into into GA at least on the op stack side um where the blob gas price gets fed in directly through these deposit attributes in every block um so we don't need the API method but I'm not sure if other l2s how they work and how they get that information got it thanks so when you send a blob transaction how do you compute what to make the blob gas price do you just directly calculate it with the get API like the go API um for the gas price of The Blob transaction in the bach I'm trying to

think through that particular case um because without the API method you could just look at the parent header and compute the pr from the exos yeah yeah that's what's happening excess blob gas and and directly Computing The Blob price from it okay sounds good okay any other spec or client issue people want to bring up okay then then Mario you had some updates on the E testing

side yes uh can you guys hear me yes oh great um so yeah two things I would like to mention uh I think the most important one is that um the testing team has been working on supporting uh the state test format for the last month uh this is on the execution spec tests and we are close to making a release probably this week so we wanted to do just like a heads up uh to the execution clients that we will change the folders structure of the tests in the releases uh that we do in this in this repo to account for these new tests um so I I I we will make a a proper description when we make the release of what changes um basically just adding a new folder in there just to account for the new for

the other uh test format um it should be super easy to fix in the CIS or whatever you are using the AR tests um and the other thing is that um we want to include simple error passing in Hive for the invalid uh execution uh execution test so for example the tests in in Hive that have a an invalid block we want to check uh this uh the error that you guys return on the engine new payload uh just to do simple checking that uh uh that that the that the client is actually failing the the I'm I'm sorry

invalidating the block because of of the correct reasons um and I've checked uh and most clients to return some important some some uh some some information in this error string uh but nether mind and Aragon doesn't don't don't seem to return any meaningful information here so um I wanted to reach I I will reach out uh individually to each of the teams to just explain a little bit further what information we do need in this field um but but the other the other GLS are okay um so yeah that's that's about it awesome thanks any question comments

okay anything else people wanted to discuss um okay yeah happy to wrap things up uh early then um I know there was like some discussion around the dates and whatnot on aquar devs last week that seemed we seem to have settled back to like keeping the original dates we have and and having just a release for Gordy this week and then potentially a combined release for the other two test Nets assuming things go well um but yeah I think uh should be good to go for Gordy at least and then uh if we

want to maybe tweak things for the other test nuts uh it probably makes more sense to discuss it on award devs than here um but yeah aside from that I think we're good to move forward with with Gordy oh yeah mini Shadow Forks that's a good uh Point yeah I brought this up in uh Discord um I haven't followed up on it but uh the idea was just to do a small scale Shadow Fork ahead of the the the Big Fork um and Perry and Barnabas said that that would be possible yeah um do we want to just scope it out um we can do one of each node and do we want to do it before

curly with um production releases I guess yeah I think um you said it would take a couple days uh to get the nod synced up ahead of time um so does that mean that we'd be able to yeah like do it Monday yeah we'd um start probably sinking the no sometime tomorrow and then they should be ready by Monday and I'm assuming every client would have a release by Monday okay yeah I think that would be just a nice little extra sanity check we plan that then it doesn't need to be nowhere near the scale that we did last time right yeah yeah we probably just do one of

every note or something of that kind yeah and using the different client releases I think if yeah if we can get it done if we can have the fork and like Denon activate Monday European time then you know Monday American time we would know that thenon activated successfully or not uh on the shadow fork and then uh if we if we have to like pull the test s because we found some crazy issue then uh we have some time on Monday and then all of Tuesday to do that yep sounds good awesome anything do we also yeah pleas want to do Shadow forking for the

other bu I don't see a reason why we wouldn't um at the very least like a small Fork like all the basically when the blog post goes out whatever the the versions are in that um yeah if it's not too complicated to set up I I feel like it's probably worth doing yeah I think we can just keep it timed so when the block post is out we just use the versions there yeah and we usually try to have the blog post out mid week so that usually means like by the week after like the Monday after we should be in a good spot to Shadow fork and and presumably if we do find an issue after after the blog post you know

we'll use our normal release channels to let our user Gorly users know about that um but then uh you know if we if we have an updated binary hopefully we can still you know that's what we'll want to test uh on top of whatever we Post in the blog correct yeah and then obviously it's always a matter is it's like an issue with the client team or with like the spec and the fork themselves if it's just a small bug in the client we can just update the client version and move forward uh and if we find something like that affects everybody then the worst case we can always uh pull the fork sweet anything else anyone wanted

to bring up okay well um yeah that was uh short and sweet um for the Gordy releases I'll keep an eye on every uh every every team's repo and and just like their release page there if for whatever reason your team's release shows up somewhere different or there's a better place to look just paint me and I I'll I'll link that but by default I'll just link the GitHub release for everyone um and follow up with the teams uh who uh didn't have someone here to get their uh their releases sweet yeah let's wrap up then

thanks everyone and talk to you all soon thank you bye thank you by