All Core Devs - Testing #84

Transcript

Justin Traglia: Good morning, everyone. Just a few more minutes, and we'll get started. Good morning. Just one more minute.

Alright, let's get started. Hi everyone, welcome to ACD Testing AD4. Let's jump right into DevNet status updates. Barnabas, are you here?

Barnabas Busa: Yep, I'm here. We currently have DevNet 5 up and running. Last week, I've onboarded all the remaining ELs, except Nimbus. As of right now, we have… Most of the Prysm nodes still offline. I'm not sure if we have a status update from the imPrysmment team, and we have… Teku and RES offline as well. I haven't had a chance to take a closer look yet, I can take a look right now. Other than that, DevNet 6 is targeting to launch in the next, Day or two. Hopefully, we can, start testing ePBS in the coming hours. If you have a… ready to go branch, please let me know, and I can add you to our, Google Justice metrics.

Justin Traglia: Which clients currently have DevNet 6 branches?

Barnabas Busa: So, on the.

Justin Traglia: ones are missing.

Barnabas Busa: On the ES side, it's ethrex is the only one that has it, and on the CR side, it's, Lodestar and Teku. Everyone's.

Justin Traglia: are the ones that do have it, or don't have it?

Barnabas Busa: They do have it.

Justin Traglia: Amazing. How are we feeling about a timeline for DevNet 6, Mike? Clients, what do you think?

Barnabas Busa: So it seems like, based on the comments, that Nimbus and Lighthouse should also work now? Must be a recent development, so I will be testing those as well. In the coming, hours, and then, We can… We could possibly launch a demo today, in case we have at least two more ELs already.

Justin Traglia: Okay, so that's the requirement, is maybe 2 more ELs, so there's 3.

Barnabas Busa: Jar. Preferably at least 3.

Justin Traglia: Okay. Great. Is there anything else from anyone regarding DevNets? Okay. Spec updates. Very quickly, I want to mention that there are specs for Glamsterdam DevNet 6 on the EL side, and for consensus specs, there's version 1.7.0, alpha 11. I believe both of these contain everything for DevNet 6. Okay. Alright, core discussions, Tersek, are you here to discuss, EIP7688 being included in DevNet 7?

Dustin Brody: Yes, I am.

Justin Traglia: What would you like to say?

Dustin Brody: Yeah, so… that, in general, that… I think we've actually had a pretty good stability on DevNet 5. We'll see with DevNet 6, so in terms of those… that criteria, or those criteria, of stabilizing EPBS, that's, of course, somewhat subjective, like, when is it fully stabilized? But I… I think we're kind of, let's call it asymptotically there. and a lot of the remaining things are tweaks. The other point I would make is that we have three, fully ready clients, on, on 7688, like, today. So, so Lodestar, Lighthouse, and, and, and Nimbus. er, and then, we have… talk of maybe Prysm being… that's a little… but that… that's, but, like, so 3 ready today, and, And finally, that this addresses

There's, what's called opportunity cost of not doing it, in particular. So, one might notice that we keep having… Gas limits at $190 million, for obvious reasons. And there have been several other, sort of, cases where people are brought up that are, sort of, will be… automatically resolved. There's been a question of, sort of number of attestations. Now, will we actually change attestations in a block? I don't know. That's a different point, in a sense. Or, like, whether it actually happens is a different point. But, like, to the degree that these things happen, there have been several proposals which would be… Quite a bit more… hmm… sort of awkward to do without 7688. That is, it would start providing concrete value quite Quickly.

And… and obviate the need to have, sort of, unfortunate workarounds. So… so that… those would be my, sort of, the three, sort of, core points I would make. The latter… the last part of that, the last section is sort of not new, in a sense. The… the four… the first two are kind of newer, which is to say. ePBS stability, I think I would argue we broadly have it, so the headliner is there, I would claim. And secondly, that the client CL support is Either there or close. And enough clients. So yeah, that's what I want to say.

Justin Traglia: Thank you. One initial question would be for the CL clients, which have not yet added support for this? Would they be ready to add support within, like, a week or two? Or sorry, let's say two weeks? for TechNet 7.

Dustin Brody: Cool.

Enrico Del Fante: Teco has a prototype, but we haven't spent time to… Update that prototype to latest changes, which also includes rebasing everything on top of Gloas. So… If there is enough… Appetite for that… I guess a couple of weeks seems reasonable.

Justin Traglia: Okay. Barnabas says, I think we would have a good, solid chance to have DevNet 7 be our final DevNet, by the way. Hopefully, that'd be nice. How are, others feeling about this, Terrence?

Terence Tsao: I feel like we should, have a sufficient understanding of, testing builder API, at least the basic working, before we… add for DevNet, final, something like that.

Barnabas Busa: Builder API is optional, as far as I know, so we can just keep adding, compatible clients to the DevNet, as they… Finish the implementation. So I think the only… only reason we would need to do a devnet is in case we would change the scope. That would require, like, a hard fork.

Terence Tsao: Yeah, but, like, I feel like testing Builder API, starting to test Builder API, like, the first test is on a testnet, then it kind of sucked, so I would highly, like, recommend we start doing that at DevNet level.

Barnabas Busa: Yeah, makes sense. But, yeah, this is also pre-orthogonal to, to the SSZ, I think.

Justin Traglia: Justin Florentine?

Justin Florentine: Yeah, I just want to tag on to what Terrence says, I agree with that. I think we should be looking at this as if, what is the next step to getting to a public mainnet? Not, did we get a DevNet that was, like, you know, stable and went down the happy path? So, all the additional testing that Terrence is hitting at, I think we really need to, plan for and accommodate it not being perfect.

Justin Traglia: Tony's asking in the chat, how long would we expect this to delay things? For the other clients that have not yet implemented this. maybe Teku? I mean, you said 2 weeks, right?

Enrico Del Fante: Yeah, to… to revive the… Prototype, but, Yeah, you need… we need any way to re-evaluate the… Code maturity, production readiness… on. Oh, that prototype, anyway.

Justin Traglia: Okay. How do we feel about, seeing how DevNet 6 goes, and maybe making a decision at ACDC this week? So, whether or not to include… 7688 in the next DevNet. It would require some work spec… spec side as well, like… Doing final reviews and merging it into master.

Dustin Brody: That seems reasonable on… Okay?

Justin Traglia: Enrico.

Enrico Del Fante: One thing that is worrying me a little bit is the… PTC thing that we are, Talking about in the PBS channel. If that turns out to be a thing that we need to implement, how… VCBN, Communication will have to change, how… If there is a real security behind the… those PTC… I'm talking about… voting on via PTC on, non-canonical forks… for…

Justin Traglia: Yeah. I think we should discuss this in the CL breakout. I don't think that our clients will care about.

Enrico Del Fante: But it's definitely relevant to the fact… to the so-called readiness of the PBS implementation, right? So…

Justin Traglia: That is true.

Enrico Del Fante: becomes… A real? How much will anyway impact on… On the readiness of clients, and probably… the SEG thing could add up to that.

Justin Traglia: Okay. Is that kind of to say that… this Thursday might be too soon to make a decision on whether or not 7688 should be included. Yeah, okay. How do other clients feel about those general vibe checks? Okay, we'll talk more about it at ACDC. That's the only discussion item that I wanted everyone to hear. Is there anything else that we should discuss, or that someone would like to bring up before we go out into break… sorry, into breakout rooms?

Yeah, just too quiet. I'll very quickly mention that ACDC this week will be at the original time, 1400 UTC. Which is different than last week's time, which was 3 weeks earlier… sorry, 3 hours earlier. And, excitingly, there will be a new REST SSZ Engine API breakout call this Friday at 13. Under UTC. So please, everyone, join if you're interested in that. Should be a great chance to discuss that.

Matthew Keil: Just to confirm, the plan for ACDC is that we're going to go back and forth between the new time and the old time every single, alternating every other week?

Justin Traglia: No. I don't believe her. I… maybe Barnabas can correct me, but I don't believe we're going back to the 3-hour before time.

Matthew Keil: At least that was, like, a one-off.

Justin Traglia: Yeah, I think so.

Barnabas Busa: Yeah, the attendance on it was, electric. Unfortunately.

Matthew Keil: Okay.

Justin Traglia: Okay, I guess that's it for the main ACDT call. Could someone help us set up these breakout rooms?

Barnabas Busa: Yeah, I got it.

Justin Traglia: Awesome. I'll be leading the CL workout room, if someone from the EL side could lead the other one.

Barnabas Busa: Should be very.

Justin Traglia: Thank you. Bye, everyone.

Barnabas Busa: Had some issues starting to agricultural militant.

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