FOCIL Breakout #26

Transcript

Pooja Ranjan: breakout room meetings may not be streamed unless explicitly asked, and for that, there are some kind of settings that needs to be enabled when you create the agenda. But for this time, if you would like, we can go ahead and get streamed… get this meeting streamed, and Going forward, that can be taken care of.

Jihoon Song: Oh, I see, I see. Okay, okay, sorry for the confusion, guys, so I… yeah, this is a new thing that we haven't heard about, I haven't heard about, so… So… as Akash and Poojais are already here, maybe we can… try out, YouTube Livestream. Until by this meeting, and then we can just rely on the automated unload. infrastructure, Starting the next breakout call, I guess. So… .

Pooja Ranjan: Good.

Jihoon Song: Easter… Are we… are we live?

Akash | ECH: Yeah, we are live. Just give me a fire heads up so I can switch the screen.

Pooja Ranjan: So we're live with the pre-stream, we can move over the screen whenever you say.

Jihoon Song: Okay, yeah, we're good to go.

Akash | ECH: Yeah, real life.

Jihoon Song: Thank you. All right, let's start this all over again. So, hello everyone, welcome, man. I was wishing you all a Happy New Year. This is, FOCIL Breakout 26. So… We are in the face of… proposing headliner candidates for Hegota. We haven't written a proposal yet, but we'll write one soon. While we were off last year, and early this year, we have shared foster readiness for Hegota article. Here's a link. So, please have a look if you're interested. And Yeah, that's it for, what's it called? The proposal for Hegota stuff, and then I think we can move on to development updates, or research updates, if anyone has. Maybe I can go first. There are some changes made to the CL spec recently. So, I've updated fossil CL spec.

Here is the PR, if any CL dev is interested. There might be more changes coming, though, but… if I… make any changes to the fossil spec that I'm gonna share so that people can update their prototypes if they want to. So, yeah, that's it from my end. Does anyone have any… Updates to share?

Matthew Keil: Did have just a quick question, regarding the interop stuff. No specifics, though, obviously. But, it's my understanding we're gonna do some Hagoda interop. And I'm curious, only because I can't actually make it to the interop this year, for scheduling reasons, are we gonna livestream that stuff? And is there a way to participate remotely, or do we need to have a representative there?

Jihoon Song: well… I haven't been any interrupt, so I'm probably not the best person to ask, but maybe… Justine, you wanna say something?

Justin Florentine: It's doable. Generally, we don't do that, but, we do… can do ad hoc, remote stuff. The challenge is always, you know, zooming a couple of participants into a large room with lots of other participants and people huddled around fairly poor microphones.

Matthew Keil: Exactly.

Justin Florentine: Yeah, we've done that in the past. You know, if you can grin and bear it, it's doable. We're happy to give it a shot.

Matthew Keil: Okay.

Justin Florentine: I think fossil's important, I'm a booster, I'll bring a microphone.

Matthew Keil: Okay, and to be fair, we will have others, like, basically the rest of our team is gonna try to make it. I'm just slated to do H-star, and I know I just can't… I can't make it there this year.

Justin Florentine: Yeah, I mean, if you have specific points you'd like to have, you know, cared for, I'd be happy to advocate for you or your team, and try and present that best as possible.

Matthew Keil: If anything comes up, but honestly, it was just more that I know it's the… it's a valuable time in order to just get everybody together, huddled around, and so, like, we'll… we'll figure it out internally if we can find a second person that's also interested in the feature that can help out, and then we'll, We'll make sure we have someone there representing.

Justin Florentine: Cool.

Jihoon Song: Right, cool. Do we have any more questions?

Subhasish: Hello, I have a question around, there was an, existing PR on, a rebase, a possible rebase, onto Gloas. Can I know what's the overall status of that PR?

Jihoon Song: So, The PR, I think, I'll say we are… the PR itself is waiting for FOCIL to become a… headliner for Hegota, or not. So… we need to become a headliner to march the PR. And implementation-wise, we don't have, as far as I know, we don't have any working PBS implementation, so that's why we are still based on Fulu, and… We had, like, nearly 8 clients. based on the loop, but since… Many of them were built, like, many months ago, so they are not kind of… working today, so if you try to run intro. Among those fully-based clients, then you're gonna see they are not working. But… And, yeah, so… I would say current status is just waiting for the decision to be made regarding

FOCIL has a headline up for Hegota. But the PR itself is quite, up-to-date, so if you just read it, then I think… I believe you can get the gist of the change.

Subhasish: Right, so, on top of that, if, FOCIL is selected as, the headliner, then, would that PR be, again, updated, because I think the glowess, has been updated. A lot, maybe.

Jihoon Song: Yes, that's true. So, Gloas itself is… Still incorporating spec changes. And I haven't reflected those changes into that PR, I just wanted to wait a bit until we freeze global spec. So, yeah, you're right. Once we freeze below us back, I can update the PR based on the latest Gloss spec, and then… once we have working PBS implementation, after a few DevNets, once we feel like it is okay to rebase fossil implementation on top of it, then we were gonna have prototypes on top of Gloas.

Subhasish: Right, right, got it.

Matthew Keil: From a timing perspective, do we know when the… the Hagoda, headliner process is gonna happen? I don't remember hearing a timeline for that.

Jihoon Song: As I remember it, by early February, we are proposing headliner candidates, and then.

Matthew Keil: Okay.

Jihoon Song: In February, we're gonna select one. one for CL, one for Yale, I guess. But…

Matthew Keil: Okay, so by March…

Jihoon Song: different.

Matthew Keil: should have clarity.

Jihoon Song: Yeah. Yes, I believe so.

Matthew Keil: And then we could start rebate, because, like, I know, obviously, we're also built on Fulu, and as I'm sure everybody else's code is, and there's a lot of changes in Gloss, so I think it's gonna be… you know, I'm wondering if it's worth doing interop based on Fulu when, you know, when we're together, or… Is there enough time to rebase both the spec, get it merged, and And rebase all of our code. Just, just thinking out loud here.

Justin Florentine: So that… remember that this is a cross-layer, feature, so whatever decision we make here is gonna apply to the ELs as well. I think ELs would… Well, speaking for Besu, EO would prefer to be on top of Glamsterdam, I think. Than Trulu.

Matthew Keil: And I think we do, too. I'm just wondering time, like, is if we don't… if we don't get clarity until, you know, sometime late… late February that it is headliner, in order to trigger the PR process, or the rebase in PR of… of the spec on top of the Glamsterdam spec. That's not gonna leave a whole lot of time in order to rebase the code, with whatever changes that are necessary. So I think it's just worth something to think about.

Jihoon Song: Is it… Is it about the spec PR, or having… Or working in PBS client. Good, yeah.

Matthew Keil: Exactly. Like, we'd have to have a working EPBS client, and rebase all of the, all of the FOSL code on top of that. And I'm just concerned that it's… because, like, they're not expecting EPBS DevNet Zero until… I'm guessing it's going to be March from what we just heard on our testing call, if not mid-March. So it's gonna be… it's gonna be a tight timeline in order to be able to get everything, you know, all the pieces together for, you know, for us to actually have a meaningful… Session together.

Jihoon Song: Yeah, that makes sense. I think… On the CL side, we don't need to try to make the intro based on Fulu, but on the EL side, given that the changes we're gonna have on the EL on flu and on coloss are… quite minimal. So, we were using one client, I believe it was Lodestar, to try interrupt between Rez and Erigon, just to make sure that it is working correctly. But that was just about the EL. So, in general, I don't think we need to make every client's interop working. Given that we are not gonna be based on blue anyway. So, that's my thought. So, after we… have a working PBS client, it will be, like.

I don't know, mid-March or April, then… given that there is… there will be a lot of changes, then some clients might prefer to just build everything from scratch, I'm not sure, it's up to their choice. So, but… We We don't need to rush, right? we are targeting next to Amsterdam, so… I think we still have a lot of time to do, yeah.

Matthew Keil: Just wanted to put that thought in the world, only, you know, just because I know we're scheduling, so just get the… get the wheels turning, you know what I mean, mentally, so we can all think about it.

Jihoon Song: Yeah, cool, yeah. I think in the meantime, if you were to use some developer resources, you guys can give a review on the PR, just to make sure that if the PR makes sense or not. Alright, do we want to cover more questions? Yes, Katya?

Katya Riazantseva: Hello, everyone. Can you hear me?

Jihoon Song: Yep.

Katya Riazantseva: If you have some time, could you please make a short summary of your PR, so you shared it? Is it some tiny changes, or maybe something… Some new logic, or…

Jihoon Song: which PRR you're referring to?

Katya Riazantseva: The specs PR 804818. So…

Jihoon Song: Yeah, so, that's, I can give you a summary here. So, it's just about, like, a refactoring stuff we introduced in Gloas. spec, So we, we did some refactor to process withdrawals function. And… Some parts of that are related to… Part of the function that we are modifying. And… The second thing is… In the fork choice spec. although we are based on Fulu, there were… there was also some refactor to the existing fork choice function. And some were not exactly the same with full spec, so I changed it a little bit. to make sure we are in line with Fulu's spec. And… That's it. So, nothing fundamentally different from what we had yesterday.

But there are some refactors that we wanna… Commenting too.

Katya Riazantseva: Yeah, I got it, thank you. Nothing, like, very serious. Okay, thanks.

Jihoon Song: Cool, thanks. Do we have more questions? Otherwise, we can… Go ahead and wrap up the call. It seems we're good, so I think we can go ahead and wrap up this call early. We're gonna have a next breakout call in two weeks, so we can discuss anything there. yeah, sorry about the asshole. In the beginning of this call, we're gonna have a much smoother breakout call next time.

Thank you for joining this breakout call. Hope you guys have a great rest of your day, and… See you in two weeks! Thank you!

Katya Riazantseva: Thank you, bye.

Eitan Seri-Levi: Thank you.

Justin Florentine: Yeah.

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