You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AllCoreDevs-EL-Meetings/Meeting 202.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@
29
29
# Intro
30
30
**Tim**
31
31
* Thank you. Welcome, everyone to ACDE number 202. We have a pretty packed agenda today, as you've hopefully all seen. and also a quick heads up. I'll have to jump out at the hour, and Alex will take over for the last 30 minutes. assuming we go for more than 60 minutes, with the current agenda, which I believe we likely will. so, we'll talk about how things are going with tech implementations.
32
-
* Ideally, get to a spot where we finalize the spec. I've tried to list all of the outstanding issues, at least the ones I could find. if we get through that, I think that'll be good. And then a bunch of other things to cover. So stick around 4444s, gas pricing and, transaction or payload sizes, a bunch of other EIPs and then a few announcements at the end. I guess to kick us off, do we have Parithosh or Barnabus to give a quick update on Devnets. Yes.
32
+
* Ideally, get to a spot where we finalize the spec. I've tried to list all of the outstanding issues, at least the ones I could find. if we get through that, I think that'll be good. And then a bunch of other things to cover. So stick around 4444s, gas pricing and, transaction or payload sizes, a bunch of other EIPs and then a few announcements at the end. I guess to kick us off, do we have Parithosh or Barnabas to give a quick update on Devnets. Yes.
33
33
34
34
**Parithosh**
35
35
* Yeah. So we have Mekong still live and what people are actually using to test on. that's still based on Pectra nets for specs. And client teams are slowly making headway into implementing. Devnet specs. There's been a consensus specs release already. And on the interop channel. On the Eth R&D chat, I have linked a kurtosis config for Besu as well as Teku. they're able to, produce blocks for Pectra with the net five specs, including over six blobs as the max.
@@ -135,7 +135,7 @@ Okay. If not, then I guess we should get this merge and add this to the specific
135
135
* And also add tests just to make sure that the precompiles aren't there after it as well.
136
136
137
137
**Tim**
138
-
* Yes. We've had many devnet and mainnet issues due to adding and removing DLS precompiles, so definitely we want to test both that the ones we expect to be there, are there and working, and that the ones we previously removed are not there. yeah. But in general, I guess this is the right time if we are going to do such a change. yeah. Just to make sure that, we have Devnet 5 running with the final set of Precompiles with the final set of gas prices. So even though it's a non-trivial spec change, it does still want, like, one that's worth, yeah, including in the next devnet and even having a small delay in terms of, like, getting the test out if, yeah, if that's the version we're going to ship.
138
+
* Yes. We've had many devnet and Mainnet issues due to adding and removing DLS precompiles, so definitely we want to test both that the ones we expect to be there, are there and working, and that the ones we previously removed are not there. yeah. But in general, I guess this is the right time if we are going to do such a change. yeah. Just to make sure that, we have Devnet 5 running with the final set of Precompiles with the final set of gas prices. So even though it's a non-trivial spec change, it does still want, like, one that's worth, yeah, including in the next devnet and even having a small delay in terms of, like, getting the test out if, yeah, if that's the version we're going to ship.
139
139
140
140
**Roman**
141
141
* I think we have historically tried not to overload. Precompiles like this. I think the obvious caveat with this being just the number of precompiles in 2537. So if people like this change, let's go ahead and move forward with it. Okay?
@@ -181,7 +181,7 @@ Okay. If not, then I guess we should get this merge and add this to the specific
181
181
* Okay. Okay, then. Yeah, let's do that. Let's try to get it merged by the end of the week, and then also include it for five. Anything else on 29? 35. Okay. If not, that was the last texture spec, update on the agenda. Anything else with regards to the texture specs that people wanted to discuss? Otherwise, then. Yeah, I think we're starting to look good. Perry has a question around the builder API. I don't know if anyone has updates on this.
182
182
183
183
**Stokes**
184
-
* Yeah, I think I can speak to this. I think the main thing was just the SSZ standardisation as a transport. there's a PR and yeah, I think it's pretty close to merging. but that being said, it can kind of happen in parallel with all of this. I don't think we need to lock on a particular devnet
184
+
* Yeah, I think I can speak to this. I think the main thing was just the SSZ standardization as a transport. there's a PR and yeah, I think it's pretty close to merging. but that being said, it can kind of happen in parallel with all of this. I don't think we need to lock on a particular devnet
185
185
186
186
**Tim**
187
187
* Okay. Anything else about the Pectra spec? Okay. Nice. Well, yeah. Well done everyone. Hopefully this is, the beginning of the end of polishing the specs. yeah. Last call on Pectra before we move on. If not, Piper posted an update on EIP 4444. Piper, do you want to give some context on this?
@@ -197,13 +197,13 @@ Okay. If not, then I guess we should get this merge and add this to the specific
197
197
* Thank you. Roman.
198
198
199
199
**Roman**
200
-
* Do you have any coordinated testing process rather than doing it on mainnet? Something like Devnet equivalent for the for the networking protocol change?
200
+
* Do you have any coordinated testing process rather than doing it on Mainnet? Something like Devnet equivalent for the for the networking protocol change?
201
201
202
202
**Piper Merriam**
203
203
* I don't have anything specific to share on that at the at this time. I will get with teams and see what kind of testing people want to make sure that they're doing.
204
204
205
205
**Tim**
206
-
* I assume we should at least run this on the test nets before, um. And I'm pretty sure like we had sepolia at the merge, I think Hoskey launched post merge, if I recall correctly. yeah.
206
+
* I assume we should at least run this on the test nets before, um. And I'm pretty sure like we had Sepolia at the merge, I think Holesky launched post merge, if I recall correctly. yeah.
207
207
208
208
**Piper Merriam**
209
209
* I don't have a strong opinion on this. The protocol version bump is a, it doesn't actually change anything in any of the message payloads. So we're not actually talking about any kind of change in sort in terms of, payloads going between clients. That doesn't suggest that we still shouldn't test this. but it is technically a very minor change.
@@ -451,7 +451,7 @@ Okay. If not, then I guess we should get this merge and add this to the specific
451
451
* Oh yeah. Go ahead. It was a bit late.
452
452
453
453
**Felix**
454
-
* So notably I mean this is an EIP, which is basically it's it says it's in a review stage, but in practice it's like in the final stage. But since it is sort of final, if we want to make an update, we can just make another Eth that like further restricted or changes it or whatever. But I would say that, you know, like it doesn't feel so productive to resurrect these like super old eaps and try to change the status when literally they are in the past and like have been dealt with.
454
+
* So notably I mean this is an EIP, which is basically it's it says it's in a review stage, but in practice it's like in the final stage. But since it is sort of final, if we want to make an update, we can just make another Eth that like further restricted or changes it or whatever. But I would say that, you know, like it doesn't feel so productive to resurrect these like super old EIPs and try to change the status when literally they are in the past and like have been dealt with.
455
455
456
456
**Stokes**
457
457
* So you're saying we should just ignore the EIP?
@@ -530,6 +530,7 @@ Okay. If not, then I guess we should get this merge and add this to the specific
530
530
531
531
-------------------------------------
532
532
### Attendees
533
+
[//] # cSpell:disable
533
534
* Tim
534
535
* Stokes
535
536
* Mikhail Kalinin
@@ -628,8 +629,13 @@ Okay. If not, then I guess we should get this merge and add this to the specific
0 commit comments