Dencun Interop Testing #35

Transcript

okay um I guess let's get started so uh there were three things uh today so one I just wanted to check in to see if there were any updates on devet 11 or any client issues people wanted to bring up to um talking about the launch of devet 12 which we said we're going to try to do before alord devs this week even if it's only with a subset of clients and then three Mariel wanted to talk about some of the tests running on hive interrup now um but yeah maybe to start on devet 11 um any um updates from any teams or

clients yeah I can give a brief um prism related update so we're still working towards the latest spec which is the block inclusion format changes so I think like my estimate is probably um two to three weeks on that so yeah so I think like in terms of D night 12 like if there's enough consensus client ready this week feel free to start don't wait for us we will join when we're ready got it for Lighthouse we've got all the changes implemented I just put a link in the chat to the branch where we have all the changes we're going through like a final review now but should be good to go uh quick question about Lighthouse do

you guys want us to still continue using quick or is that not included in this spanch uh quick will also be there um I guess it's fine to use I'm not sure I haven't personally been looking into like analysis around it but I guess I guess might as well use it any other uh any other kind team want to share an update uh in nether mind uh we have two

not uh from the branch uh which is supporting blob transactions reor like uh uh storing them until there is a finalization on the chain to be able to react them in case of reor and it would be really great if uh we would be able to have some rears on devet 11 like uh probably trigger it somehow artistically and it's uh I think important uh part which is not yet uh tested on on devet like the scenario of

reor is not covered and uh like because of uh of uh this uh reading of BL transactions which like there wasn't something like that before and it would be great to uh to to trigger some reor on onet 11 or 12 is there a way to easily do that yeah I think we can do some non-f finality stuff non-f finality and reorgs are quite a bit different though like uh we

would need to maybe skew the clocks on some of the nodes manually to trigger actual rears not necessarily sure if that would even do it um we yeah we should try to do this with the chaos testing tool realistically but yeah otherwise I think we can just do non yeah either combination of clock and non-f finality and then try and get it done in dbet 12 or yeah we can run multiple valuators on different machines that's also a good idea yeah but that's also not going to

guarantee uh especially on a small Network it won't guarantee that the blocks being caused are different from each other right cuz what you want to see is the blob transaction being included in block a and then reincluded in Block B exactly um they might both just include the same ones yeah but realistically I remember the that Hive had a lot of reop test right yeah do in the past yeah can you guys hear me yes okay so the way that Hive does it is basically just starts from Genesis onto different subnets so of the validators on one

subnet half on the of the validators on the other one they um then we wait for a couple of EPO and then we just connect everything every everyone together so by the what by the time they are reconnected we have two different chains um built by each of the half of the validators and they will try to reor one Ian at least one half will try to reor to the other half uh optimally um but I know I'm not sure how it's to do this on on adep it is um it is it's easy on high because you you start from um you you you simply start disconnected and then you connect at some point so it's fairly straightforward but I'm not sure how

easy it is to un adap that but on hive could we do that and then include Force include a different blob transaction on each side like on each subset of the validators so then you're sort of guaranteed that at least one of those blob transactions would reorg would be reorg and then checking for inclusion yeah yeah absolutely so I don't remember I I think I don't think we select transactions on hi but we can definitely do it so we could for example say blob a to subnet a and then blob B to subnet B and just verify that they are all included on

the on the Des sorry on the on the chain that is eventually become the canonical chain um yeah yeah any other thoughts on testing reworks okay so let's yeah let's maybe have a look at what we can do on high and and potentially on either the chaos testing or Dev Nets um but yeah we should definitely start testing that at this

point um anything else on devet 11 or the current uh implementations so on lar side I can share an update earlier lsar was sort of waiting for all the blobs and then then importing the block now we uh basically start importing the block as soon as we see it and basically then uh in parallel we wait for blob availability now uh and we also have some metrices added to it regarding to whatever is the additional delay which we can which I'll try to analyze this week but yeah this

particular change has been running on D 11 for some time now so with respect Lo star yeah we we have sort of settled on our final architecture as well nice any other team okay if not um so I guess so for devet 12 um we uh I believe on the aquar devs last week we had teu and was loar

or Nimbus the other client that was already ready loar on Lighthouse and oh um and then on the El side do we have all y's ready I guess so because there's no changes yeah there's no changes so it should be the same um the only thing that might have changed is which branch we need to use or whether they have like uh move something into Upstream into their Master Branch or something yeah I would be actually curious to know uh is anyone else is already following their latest Master other than uh

gu uh etherum DS is also latest Master only um Master for netherite only like one PR is not merged but probably we will merge it for Aragon everything is merged though it's the branch is called de devel instead of Master okay so I guess uh and then we should still be able to get this launched before award after this Thursday right yeah uh I did a initial test last

week already on Friday and everything looked pretty okay so I don't think there would be any blockers it would be good to have uh still Nimbus or prison already at Genesis but yeah if if not then it's not going to be a blocker yeah a very big Network anyway so we can just quickly make some deposits and uh include those also yeah and I guess based on what Terence was saying like prison won't be ready for another couple weeks so um we clearly won't have them at Genesis do we know if Nimbus is like almost there or is it uh because if they also still need a couple weeks then um if then in that case we basically

have all the clients ready today and then the obviously the editors uh will join later but is there some yeah are we waiting like on any last minute client and yeah I don't think there's anyone from Nimbus here um yeah I guess if we just follow up with them um afterwards but I don't think we've heard anything about their status right now um and I would just guess that we wait until all clients are

ready before we do a big Shadow for cuz we wanted to do one that's a couple hundred notes at least got it yeah so I guess as soon as we hear from Nimbus if they're ready soon we can wait for them to launch the devet uh as long as it doesn't happen after like Wednesday and then if not then I guess we're pretty much ready to to launch death 12 um any other thoughts comments on theet 12 okay uh if not uh Mario you had some

Hive interop updates right yes um can I share my screen uh yes please do you don't see your screen yet yeah it's let me see okay okay we do now yeah oh perfect um yeah just a quick update on um the things that we are running currently on the hive interrupt um this was just updated it contains the latest at to dcun branch which already contains the um the new consensus spec uh updates for Hive and basically you can come here

and just take a look at the all the SS currently we we only have um Lighthouse teu and load start running on this all in pair with uh nethermind um and I think go etherum also but I'm not I'm not seeing it here maybe it's that's a mistake but yeah never um yeah yeah nethermind is the is the main uh client we using to run and you can see there are basically four uh so uh test SS we are running currently so the first and the most important one is just a test nut basically we start uh we have two test cases here um and if you come here into the loow of the U of the of the test cases you can see um we reamped a little bit the description of the of the

test cases so if you come here you can see the configur ation for the for the test net you can see the verifications are done and this is done for every single test case um but yeah basically this two test cases here is just basically starting from capella and and then starting for the naap also and you can see that this is passing with the um latest um lat latest consensus spec version uh but we also have uh test uh test Su for the Builder and which also uses the new uh Builder API updates for the consensus spec and I've tested most of this uh locally with the sanity test and they are all passing so the the

errors that we are seeing here are probably um isolated errors or I I have to double check on exactly what's failing to and to to really know what's happening uh but if anything is f found I will just uh address this with every with each of the clients um and yes and also we have um the test suite for sync and we have the test suite for uh blobs goip ping so this is this blob gossiping is using the updated um blobber uh uh test uh tool that we are using that we used last time to to generate the equivocation uh blops and we are doing a very similar thing here and this is now

updated to use the um the the updated uh header sign sign header on the blops so you can go here and just click any of the test cases and you can basically see what's what's the what's the blobber doing in each of the test cases you can see um for example here is creating just ating block and just signing it and doing some stuff and this is done for every single test case so if you see your client here and it's failing some of the test you can easily just come here and see what the blobber is doing um at the moment to be honest there there might be some test issues still uh but I again I tested the sanity uh test cases on each of the swits and each

of the clients and they are all passing so um this these are more uh this some test cases that are failing but I I will double check this and then just go to each client to just um see if there's some issues that need to be taken care of um if you want to take a uh so yeah the description here is not very not very uh uh it's not V visually the best but if you want you can also go here I have the I I will share this link which is basically just branch that we're using and you can see every single test Suite that we have here you can you can just click on each of the test suits and see every single test case and what's what's the verifications what's the configuration

and everything for every single test case and also how to run it locally if you so wish to do so um yeah that's basically that's basically this the status right now um if you have any test case that you want me to run or double check just please um let me know and uh we can I I'll share the links of of of this uh in a bit are there any questions no questions it seems lots of clapping

hands um yeah this is very cool I just I just Shar the links uh on the both the hi interrup site and also the description of test cases oh I think I shared just one let me share the complete uh set yeah please and please take a look if there's any test case missing I obviously we're iterating and making more regression tests for Hive um but if you see any any anything that is obviously missing just let me know I we can just um Implement some new test cases if

necessary yeah that's that's basically it thanks Mario um yeah that's the last thing we had on the agenda for today was there anything else people wanted to bring up or discuss before we wrap up okay well yeah happy to close off here um so yeah thanks everyone um talk to you all on ACDC this Thursday and by then let's try and get devet 12 up

thanks thank you bye thank you bye thank you than you