FOCIL Breakout #31

Transcript

Jihoon Song: Hello, guys, I think we can start in, like, 30 seconds.

Justin Florentine: Good morning, Jihoon.

Jihoon Song: Alright guys, thanks for waiting, let's get this started. Hello everyone, welcome to FOCIL Breakout 31. Today we can share Development updates, backup days, and then testing. Right, so, let's start with development updates. I know CL teams are busy with ePBS, so maybe we can start with EL teams?

Justin Florentine: Hey, yeah, so on the basis side, we haven't done a ton since last call. We still have a PR out there, it's still in review right now. No surprises to report from the spec? So, you know, it is basically mostly just engine API implementation and some building stuff, so it's going well. It's just not, not a super high priority. Most of the team is focused on, optimizations and Glamsterdam stuff at the moment.

Jihoon Song: Cool, do you have any, like, rough timeline?

Justin Florentine: Mmm…

Jihoon Song: Or…

Justin Florentine: No, not at the time, at the moment, we don't really have a rough timeline. Certainly, Hegota wouldn't be a challenge. you know, with a typical DevNet rollout for whenever Hegota hits, we don't see a challenge, but I would need a little bit of time to consult with Fabio. I'm actually going to be going on holiday shortly, and so I wouldn't want to try to commit to any usable builds.

Jihoon Song: Got it, got it. yeah, I just wanted to ask you about, like. What we can expect in the interop.

Justin Florentine: Interop. Okay, so I won't be attending Interop… Alright. I mean, I would imagine we would have something build-ready for… for Interop? Yeah, I mean, I mean… Probably? I don't see any reason why not, I guess.

Jihoon Song: Yeah.

Justin Florentine: the, the, you know, the testnets and the kurtosis stacks that, we would use to validate for that, once we get one of those, we can give a better, better answer. Or, like, once we get that set up, rather, we can give a clearer answer on that. But A month. It's about a month out. Right? So 4 weeks… 4 weeks from now for being able to join a DevNet, I think is pretty reasonable. I don't really see a problem with that.

Jihoon Song: Got it, thank you.

Justin Florentine: Yep.

Jihoon Song: Nico, do you have any updates for Lodestar?

Nico Flaig: No, sorry. Right now, no real updates. I saw your comment on the Beacon API, but I also think it's just minor, like updating the containers. Yeah, I hope we have something for the indoor. If not, I think we can hack something together in, like, a few hours. I think it's pretty simple, to be honest.

Jihoon Song: Yeah, no worries. But was my comment on Beacon API?

Nico Flaig: I think this is currently based on Fulu, But I don't see major changes to rebase it on Hegota.

Jihoon Song: Right, yeah, yeah, yeah, yeah. I was updating all specs, so I was just, I just wanted to ask if there is anything that we have to make change on Beacon API, so… yeah. Yeah, I wouldn't.

Nico Flaig: Probably do this, once we update our implementation, and then we can use that as reference.

Jihoon Song: Gotcha. And if you have a time, then, It'll be appreciated if you could review the spec yourself. Because, yeah. It is currently not reviewed at the moment. But it will get reviewed over time, but still, like. It's nice to have more eyes on the spec, so…

Nico Flaig: Yeah, I think once we have our implementation, it's easier to give feedback there. Gotcha. But yeah, I can see if I find time to look at it.

Jihoon Song: Okay, cool, thank you. Speaking of which, for spec updates, I'm working on rebasing all specs on top of Hegota. Avery-based execution spec and engine API spec. I guess you guys already have a link, but… It's a lead. If anyone is interested. So they are currently on top of Glamsterdam. And I can update it from time to time, just in case Glamsterdam changes. CL spec is already on top of Hegota, but… There will be some changes regarding deadline. The gist of it is… so currently we have two deadlines. IL submission deadline at 9 seconds into the slot. And proposals cut off at 11 seconds into the slot. And I think we should add another deadline for a tester's cutoff at, let's say, 12 seconds into the slot.

This was found by Mikhail around 9 months ago. well, there is another deadline, which is 8 seconds into the slot, but as Nico pointed out nearly a year ago, I think this should be removed. This is just… Implementation-dependent example. So the reason why we need this new 12-second deadline is… to prevent split view among the testers, let's say there is an inclusion list, that… the block fails to satisfy, and that IR committee member actually equivocates. which, in turn, should make that block become canonical, but let's say that that equivocation happens at 2 seconds into the swap. So. Then, attester who saw the block before 2 seconds will vote against it, while a tester who saw it after will vote for it. So if

Half of a tester vote for it, half of a tester vote against it, because they haven't seen that equivocating IL committee member, we're gonna have a split view. It's… this is still work in progress, and I think I can continue working on it. After 8cc… And… Once it's done, I will also update the EIP, So, yeah, that's for the spec updates. Before we jump to… testing updates? Do we have any questions or comments? Otherwise, we can just move on. So for testing, I guess you guys already know, but there are… all types of tests that we can do on the CL. Reference tests, buzzing, deafness, and compliance tests. Among these, we can focus on

Reference test for a while, and extend testing over time. On the EL side, we will be working on a steel team. We don't have anyone from testing team today, but this is… Asia Tracker… for AL testing. So… the idea… we had a call with testing team the other day, and the idea is to update the testing infra in the tests to support inclusion list, and then start from there. Besides that, besides specs, updates. Nothing special updates we have today, but I expect we can make some progress after ECC. And that's all for testing updates. Yeah, so, before we wrap up this call. Does anyone have any comments or questions?

Thank you, Nika. And thank you for your comments. From, a year ago. I wanted to find that comment, but I guess it's not on Discord, I think it's on some PR, but yeah. I've been thinking about it from time to time, and now it's time to update it, so yeah. Alright, I think that's it for today. If anyone here goes ECC, we can see each other there. Otherwise, let's catch up in 2 weeks. Thank you, guys!

Nico Flaig: Thanks, everyone.

Fabio Di Fabio: Yep.

Jihoon Song: Bye-bye.

Transcript adapted from ethereum/pm, CC BY-SA 3.0.