WEBVTT

1
00:05:19.350 --> 00:05:20.460
stokes: Hello!

2
00:05:27.830 --> 00:05:29.809
stokes: Just checking, can people hear me?

3
00:05:31.530 --> 00:05:32.830
Matthew Keil: Loud and clear.

4
00:05:32.990 --> 00:05:34.010
stokes: Okay, thanks.

5
00:05:35.440 --> 00:05:38.660
stokes: Been having some headphone issues lately, just wanted to make sure.

6
00:05:39.470 --> 00:05:49.269
stokes: Okay, so I think the way this is set up now is, this is streaming from Zoom, and it's already started.

7
00:05:50.470 --> 00:05:55.979
stokes: So, let's give people maybe another minute or two, and then we'll get started.

8
00:06:29.870 --> 00:06:38.489
stokes: Okay. We're just about at 50 there we go. So, yeah, it says we're 50 people. Feels like a good number to get started with. So

9
00:06:39.390 --> 00:06:50.799
stokes: Hello, everyone. This is ACDC number 188. It's issue 2227 in the PM repo.

10
00:06:51.440 --> 00:06:53.369
stokes: I put the link here to the agenda.

11
00:06:53.950 --> 00:07:02.800
stokes: And, yeah, let's go ahead and get started. So today, we should touch on Glamsterdam, as I think everyone hopefully knows, Sepolia

12
00:07:02.920 --> 00:07:05.039
stokes: Is forking, next week?

13
00:07:05.810 --> 00:07:12.110
stokes: Then we'll move to Hegota. We'll continue the scoping conversation, working through the list of EIPs there.

14
00:07:12.410 --> 00:07:18.170
stokes: And then there are a few other comments along the way. So let's go ahead and get into that.

15
00:07:19.410 --> 00:07:30.390
stokes: For Glamsterdam, I just have to ask, any relevant updates from any devnets or, you know, similar testing we've been doing over, say, the last week?

16
00:07:33.370 --> 00:07:37.619
stokes: I imagine we're pretty good here, but I would just ask.

17
00:07:39.070 --> 00:07:41.169
stokes: If there's anything anyone would like to share.

18
00:07:42.590 --> 00:07:51.569
Barnabas: We are preparing a Sepolia Shadow Fork as we speak right now. We are done with the Muzits right now and hopefully launching within the next hour or so.

19
00:07:52.440 --> 00:08:01.789
Barnabas: We're expecting the shadow fork to be alive for a day or two. Probably we'll be shutting it off before the weekend begins.

20
00:08:02.140 --> 00:08:07.560
Barnabas: We just want to send to check that everything is, working as expected before the fork.

21
00:08:08.590 --> 00:08:10.959
stokes: Yep, makes sense. Alright, amazing.

22
00:08:11.760 --> 00:08:17.410
stokes: Cool. Then we'll turn to the Sepolia upgrade itself.

23
00:08:18.140 --> 00:08:22.599
stokes: Let's see here, let me just make sure I have the exact right date. Okay.

24
00:08:22.760 --> 00:08:28.720
stokes: So Sepolia will be forking to Glamsterdam on October 6th, at…

25
00:08:29.010 --> 00:08:32.120
stokes: You know, it's seven minutes before two PM UTC.

26
00:08:32.380 --> 00:08:38.999
stokes: So that's… 1pm, 53 minutes. And…

27
00:08:39.490 --> 00:08:43.549
stokes: Yeah, I don't know what else to say there,

28
00:08:44.690 --> 00:08:51.170
stokes: The fork is soon. That's… let's see… depending on your time zone, it's something like next Tuesday, so…

29
00:08:52.350 --> 00:09:01.130
stokes: It's coming down the pipeline. And, yeah, should be exciting. Again, I know everyone here has put in a ton of work to get to this point. So

30
00:09:01.320 --> 00:09:05.510
stokes: We will start the network upgrade season. We'll start with Sepolia.

31
00:09:05.650 --> 00:09:12.450
stokes: Assuming that goes well, we'll move to Hoodi and then ultimately Mainnet. So

32
00:09:13.820 --> 00:09:24.810
stokes: Unless, yeah, there are any other general comments here. I did want to touch on… the incident response plan.

33
00:09:25.500 --> 00:09:29.290
stokes: Actually, let me grab a link really quickly…

34
00:09:30.110 --> 00:09:32.799
stokes: So, if you go to the PM repo…

35
00:09:33.840 --> 00:09:37.579
stokes: And I just had this. Okay, protocol upgrades.

36
00:09:38.930 --> 00:09:47.310
stokes: So, Barnabas, just to your question, did we already pick a Hoodi date? And the answer is no. As far as I know, we have not.

37
00:09:50.020 --> 00:10:00.550
stokes: Yeah. Unless something's changed, maybe it was discussed on ACDT this week. I'm not sure. But the last that we had discussed here was that we wanted Sepolia to go well.

38
00:10:00.840 --> 00:10:02.699
stokes: Then we would pick a date for Hoodi.

39
00:10:03.080 --> 00:10:05.970
stokes: I think we had said something roughly, like…

40
00:10:06.590 --> 00:10:08.350
stokes: Let me look at the calendar again.

41
00:10:10.690 --> 00:10:17.999
stokes: Okay. I don't remember. It was either the twentieth or the twenty seventh. Okay. It was the twenty seventh, maybe the twenty sixth, one of these days.

42
00:10:18.330 --> 00:10:21.529
stokes: Essentially just the week before Devcon. So

43
00:10:22.920 --> 00:10:26.809
stokes: I imagine if Sepolia goes well.

44
00:10:27.370 --> 00:10:34.609
stokes: then, we should go ahead and have that discussion on ACD next week, during ACDE, so…

45
00:10:35.250 --> 00:10:37.650
stokes: Let's, do that then.

46
00:10:39.290 --> 00:10:44.660
stokes: Okay, jumping back to the topic here. So we have this document I linked.

47
00:10:45.200 --> 00:10:48.819
stokes: Protocol upgrade under processes, again on the PM repo.

48
00:10:49.190 --> 00:11:00.129
stokes: This document is kind of long, but there's a lot of good stuff in here. Many of you were involved with the drafting of it, and ultimately, this has come out of our experience of doing

49
00:11:00.610 --> 00:11:05.249
stokes: Dustin upgrades, even mainnet, kind of this whole end-to-end process.

50
00:11:05.470 --> 00:11:13.320
stokes: And, ultimately, it just encodes, you know, I think some good postures to have in the event something goes wrong. And, you know, to be clear.

51
00:11:13.660 --> 00:11:20.830
stokes: We're all hoping and expecting things to go super well. But in the event they don't, it's good to have a plan to fall back on.

52
00:11:20.960 --> 00:11:22.449
stokes: Just so you know.

53
00:11:22.560 --> 00:11:34.889
stokes: If something does happen, you know, everyone will be on alert. This gives you just kind of, like, a nice framework to think about, okay. What do we need to do to get back to stable? Who's doing it? And how does that process kinda play out?

54
00:11:35.500 --> 00:11:40.480
stokes: So… From there… Let's see…

55
00:11:41.360 --> 00:11:54.419
stokes: I'm gonna give you a slightly more specific link here, to this incident response plan. And, again, usually how this works, this, especially, I think, for the testnets will be pretty lightweight. We just need to kind of have

56
00:11:54.520 --> 00:11:57.439
stokes: Different people on point for different things.

57
00:11:59.630 --> 00:12:07.100
stokes: I wanted to ask today for client team coordinators, maybe before that point though.

58
00:12:07.520 --> 00:12:11.589
stokes: We'll jump into the others here. So

59
00:12:11.870 --> 00:12:18.919
stokes: I think to kick things off, I just wanted to introduce Will here as the communication coordinator.

60
00:12:19.170 --> 00:12:26.959
stokes: So, you know, he'll be helping to kind of, again, coordinate all these different things. I think Will's here on the call. Yeah.

61
00:12:27.430 --> 00:12:36.600
stokes: Will has been yeah. If you haven't met him yet, he's been, over many, many breakouts all over the place. So you probably run into him at some point.

62
00:12:37.080 --> 00:12:43.330
stokes: But yeah, so he'll be helping with just general comms in the event something does go wrong.

63
00:12:43.630 --> 00:12:51.049
stokes: Will, did you want to… did you have someone in mind for the DevOps Coordinator, Testing Coordinator, and Security Coordinator?

64
00:12:51.230 --> 00:12:52.580
stokes: Just for Sepolia?

65
00:12:54.110 --> 00:13:06.689
Will Corcoran: Not so much. We created the signal channel yesterday, and we've got, you know, the correct people from the EF teams, for security DevOps, and…

66
00:13:07.470 --> 00:13:13.290
Will Corcoran: Testing. And then, yeah, I guess the open question is the degree to which we…

67
00:13:13.660 --> 00:13:19.189
Will Corcoran: Wanting to have client team coordinators involved in the testnet versions of this.

68
00:13:20.850 --> 00:13:31.789
stokes: Yeah. I think it would be good just to name explicit people. So, yeah, like, Pari here says that Barnabas and himself would be DevOps coordinators.

69
00:13:32.410 --> 00:13:33.910
stokes: No surprises there.

70
00:13:34.710 --> 00:13:40.079
stokes: And… yeah, you know, it's okay if teams, I think, need…

71
00:13:40.380 --> 00:13:46.450
stokes: you know, another day or two to nominate someone. But if you know today, please speak up.

72
00:13:46.620 --> 00:13:49.840
stokes: And if not, I can follow up async.

73
00:13:50.620 --> 00:13:55.660
stokes: But, again, just in the event something does go wrong, it's good that we have specific people on point.

74
00:14:01.880 --> 00:14:08.130
nixo: I posted the link to the, place where people can put their, their coordinators.

75
00:14:08.270 --> 00:14:10.300
nixo: It's already in the PM repo.

76
00:14:10.710 --> 00:14:11.850
stokes: Oh, great, okay.

77
00:14:12.930 --> 00:14:14.839
stokes: Perfect, okay, excellent.

78
00:14:15.200 --> 00:14:27.860
stokes: Yeah. Okay. Yeah. This is helping me remember. Yeah. We yeah. Historically, people just made a PR to this. So then ask for client teams. Yeah. If you're not ready to label someone now.

79
00:14:28.520 --> 00:14:30.379
stokes: Just make a PR here.

80
00:14:30.920 --> 00:14:34.969
stokes: And okay. This is the mainnet document.

81
00:14:35.630 --> 00:14:39.199
stokes: I imagine it's not gonna make a huge difference, but if you want to

82
00:14:39.690 --> 00:14:43.850
stokes: have different people between the testnet and mainnet, that's perfectly okay.

83
00:14:44.840 --> 00:14:46.360
stokes: Just make it clear.

84
00:14:48.330 --> 00:14:54.279
stokes: And Barnabas says here, if you don't nominate someone, he'll be nominating for you, so…

85
00:14:54.850 --> 00:14:56.290
stokes: Go ahead and get ahead of that.

86
00:14:56.810 --> 00:15:04.359
stokes: I guess, yeah, ultimately, we have ACDT on Monday, so yeah, we can, touch on this again there, if… if necessary.

87
00:15:07.260 --> 00:15:16.239
stokes: Okay. So I wanted to give that on everyone's plates, just something to have on your mind. Again, Sepolia should go well.

88
00:15:16.370 --> 00:15:22.039
stokes: We've put in a ton of R&D effort to get to this point, but good to have a plan just in case.

89
00:15:24.620 --> 00:15:25.640
stokes: Okay.

90
00:15:27.100 --> 00:15:32.699
stokes: I think that's it on Sepolia slash Glamsterdam. Any other comments or questions here?

91
00:15:39.910 --> 00:15:40.780
stokes: Okay.

92
00:15:42.160 --> 00:15:42.960
stokes: Great.

93
00:15:43.100 --> 00:15:49.929
stokes: Then, I guess we'll have one more ACD with ACDT on Monday, but then it will be time for the fork, so…

94
00:15:50.280 --> 00:15:51.810
stokes: Happy forking everyone.

95
00:15:53.800 --> 00:15:56.510
stokes: Let's move to Hegota now.

96
00:15:57.290 --> 00:16:05.090
stokes: And the main thing here is to continue with, scoping, and we have a number of EIPs.

97
00:16:05.250 --> 00:16:14.319
stokes: just to help you remember, the last ACDC, we DFI'd some, BFI'd some, and then had sort of this, like.

98
00:16:14.750 --> 00:16:17.479
stokes: batch of EIPs where it wasn't, you know.

99
00:16:17.610 --> 00:16:20.219
stokes: And immediately, obvious yes or no.

100
00:16:20.580 --> 00:16:23.840
stokes: So, we should continue working through those.

101
00:16:24.040 --> 00:16:27.199
stokes: There have been a number of updates.

102
00:16:27.570 --> 00:16:33.990
stokes: one to one of the EIPs, where we had said last call, we wanted to update the IP before

103
00:16:34.320 --> 00:16:35.800
stokes: there'd be support.

104
00:16:36.190 --> 00:16:37.409
stokes: or CFI.

105
00:16:37.860 --> 00:16:46.830
stokes: There have been two EIPs that have been withdrawn, so… perhaps we'll just start with the withdrawn EIPs, just to get that out of the way.

106
00:16:47.680 --> 00:16:54.159
stokes: There's a comment here from lodekeeper, which looks like, an AI agent, which is pretty cool.

107
00:16:55.910 --> 00:17:01.300
stokes: Withdrawing 8333. This was Align Checkpoint with Epoch Boundary Block.

108
00:17:02.280 --> 00:17:05.000
stokes: I'm not sure if anyone on…

109
00:17:05.609 --> 00:17:08.280
stokes: Okay, sorry. I just saw the chat here.

110
00:17:09.680 --> 00:17:13.839
stokes: Let me do this. But yeah, is anyone from… Lodestar.

111
00:17:14.150 --> 00:17:17.530
stokes: Slash associated with lodekeeper. Would you like to just…

112
00:17:17.530 --> 00:17:21.300
cayman: Yeah, we look further to decouple consensus, and…

113
00:17:21.500 --> 00:17:25.569
cayman: It's just not worth dealing with it now, so…

114
00:17:26.210 --> 00:17:32.060
cayman: We just agreed to withdraw it and save everybody the… Hassle of debating this thing.

115
00:17:33.250 --> 00:17:34.929
stokes: Okay, sounds good.

116
00:17:35.760 --> 00:17:46.490
stokes: Okay. I'm trying to share my screen. And, yeah, Ryan, you said, you'd like to make a comment. Can you can keep it brief? Yeah. I appreciate that.

117
00:17:46.490 --> 00:17:58.889
Ryan Berckmans: Go ahead and do that now. I've been speaking extensively to folks involved in L2s and the app layer, and the general sentiment is that they would really like to see quick slots included.

118
00:17:59.090 --> 00:18:18.729
Ryan Berckmans: It's not so much that the reduction from 12 to 10 seconds is gonna be, you know, an operative benefit, immediately, it's that beginning the system of reducing slot time seems like something that would be great to get in front of now, to reduce the risk that slot times are still 12 seconds, you know, 3 to 4 years from now.

119
00:18:20.110 --> 00:18:25.360
Ryan Berckmans: We really like this one, we really appreciate all the work on it, and, you know, thanks for considering it.

120
00:18:28.170 --> 00:18:30.980
Ryan Berckmans: Okay. That's all. Thanks, guys. Appreciate everything. Have a good day.

121
00:18:31.530 --> 00:18:32.770
stokes: Thank you. Yeah.

122
00:18:34.360 --> 00:18:47.050
stokes: So that's, yeah, statement in favor of quick slots. Let's not jump into that one just yet. Let's finish with these withdrawal EIPs just so the scope is, you know, the scope of the scope is smaller.

123
00:18:48.300 --> 00:18:53.809
stokes: Let's see. I'm trying to figure out sorry. I got okay. I wanted to get the chat up.

124
00:18:53.970 --> 00:18:56.699
stokes: Because it's a little hard when I'm also screen sharing.

125
00:18:57.060 --> 00:19:00.149
stokes: So… okay, I also lost the agenda.

126
00:19:00.690 --> 00:19:02.110
stokes: There's too many windows.

127
00:19:03.410 --> 00:19:09.270
stokes: Let's try it like this. Okay. So EIP-8333 is withdrawn.

128
00:19:10.160 --> 00:19:13.010
stokes: Yeah, for the reasons Cayman gave.

129
00:19:13.910 --> 00:19:21.090
stokes: Now… Okay, Zoom. So many, so many… questions.

130
00:19:21.680 --> 00:19:24.450
stokes: Comments. Okay, is that better?

131
00:19:26.820 --> 00:19:29.610
stokes: Okay, I can zoom in more, just so you guys see something here.

132
00:19:29.800 --> 00:19:33.269
stokes: It's a little fragile here with all the different screens I have to juggle.

133
00:19:35.430 --> 00:19:36.340
stokes: Okay.

134
00:19:37.370 --> 00:19:47.090
stokes: So, 8333, and… okay, also then, we got a message, an update for 8363, this was the issuance change.

135
00:19:47.520 --> 00:19:55.330
stokes: There's a post here I linked on ETH Magicians, essentially saying that, it's been with John as well for consideration for Hegota.

136
00:19:55.680 --> 00:19:58.629
stokes: Yeah, the champions here.

137
00:19:58.850 --> 00:20:08.220
stokes: Realized, ultimately, you know, this wasn't the perfect venue for this, and wants to have a slightly different.

138
00:20:08.780 --> 00:20:12.619
stokes: Approach here with building towards consensus.

139
00:20:13.160 --> 00:20:15.640
stokes: Is Jerome on the call?

140
00:20:19.740 --> 00:20:26.930
stokes: I think he wanted to say something if he was. Okay. Anyway, yeah. So, essentially, yeah. The

141
00:20:27.040 --> 00:20:28.810
stokes: I dropped a link here.

142
00:20:29.410 --> 00:20:38.089
stokes: to the post from Jerome, it's, yeah, pretty straightforward, please take a look. But ultimately, yeah, just instead of pushing for, you know, kind of

143
00:20:38.230 --> 00:20:51.560
stokes: shoehorning this into scoping, and it's not clear, you know, how ACD scoping squares with what should be, like, you know, a very broad community-driven process, given that this is more of, quote, a policy change.

144
00:20:51.860 --> 00:21:00.790
stokes: They decided to withdrawal and take a slightly different approach. There's even a schedule here in the post around.

145
00:21:01.250 --> 00:21:05.810
stokes: essentially a timeline for how they want to approach things. So, yeah, please take a look.

146
00:21:08.560 --> 00:21:09.590
stokes: Okay.

147
00:21:10.140 --> 00:21:15.160
stokes: So let me go back to the screen.

148
00:21:16.190 --> 00:21:21.019
stokes: Okay, I don't know if I can do this live, but ultimately…

149
00:21:21.290 --> 00:21:25.840
stokes: Just to call it out, so we have 8333 here, this has been withdrawn.

150
00:21:26.460 --> 00:21:31.290
stokes: We have 8363 here. This has been withdrawn.

151
00:21:31.690 --> 00:21:32.570
stokes: Okay.

152
00:21:34.420 --> 00:21:44.179
stokes: And let me just double check here. Okay, so then, going back to the agenda, we should probably just touch on 8365 next, so let's do that.

153
00:21:45.370 --> 00:21:46.210
stokes: Okay.

154
00:21:47.370 --> 00:21:55.059
stokes: So, like I said, right, we had… Okay, title changed, I think.

155
00:21:55.160 --> 00:21:57.679
stokes: We had CFI 8015,

156
00:21:57.830 --> 00:22:13.259
stokes: And then we had discussed 8365. It had pretty broad client support. That being said, there was a part of the EIP that people wanted to see changed, and that's where we left it on the last call, was that we

157
00:22:13.510 --> 00:22:20.079
stokes: Yeah, the champions here are making updates and come back to present this again for CFI.

158
00:22:20.250 --> 00:22:21.150
stokes: So.

159
00:22:22.360 --> 00:22:29.749
stokes: That's where we're at. And the champion here is NC. Are you on the call? I'll hand it over to you.

160
00:22:30.190 --> 00:22:30.850
stokes: If so.

161
00:22:30.850 --> 00:22:34.419
NC: Yeah, so the chain is pretty straightforward.

162
00:22:34.570 --> 00:22:37.070
NC: Basically, just keep the deposit guard.

163
00:22:37.270 --> 00:22:41.809
NC: part of the original EIP into EIP-8365.

164
00:22:42.150 --> 00:22:47.179
NC: And then, the forced exit part is gonna be a standalone EIP.

165
00:22:47.570 --> 00:22:51.870
NC: That would not be proposed for Hegota, but a future fork.

166
00:22:52.770 --> 00:22:57.489
NC: Other than that, yeah, it's… It's pretty straightforward change.

167
00:23:01.310 --> 00:23:02.339
stokes: Okay, great.

168
00:23:02.940 --> 00:23:10.140
stokes: Yeah, so… Yeah, proposal would be to go ahead and CFI this version of the IP.

169
00:23:10.470 --> 00:23:15.239
stokes: We had said last time that this is what we would do, so… everyone okay with that?

170
00:23:18.880 --> 00:23:21.080
stokes: Seems like there's plenty of support in the chat.

171
00:23:27.330 --> 00:23:28.140
stokes: Okay.

172
00:23:28.400 --> 00:23:35.270
stokes: Let's go ahead and CFI this then. Great. Thanks for the updates, NC. And, yeah, we'll go ahead and do that.

173
00:23:36.690 --> 00:23:39.499
stokes: I think there's a way…

174
00:23:39.700 --> 00:23:44.219
stokes: I can do this. And actually, we can track this. So yeah, we'll do CFI for that.

175
00:23:44.220 --> 00:23:45.999
marc | wolovim: T. Alex. Yeah. There you go.

176
00:23:46.000 --> 00:23:47.290
stokes: Yeah, can you see it?

177
00:23:48.910 --> 00:23:49.770
marc | wolovim: Yeah, you're good.

178
00:23:50.260 --> 00:23:51.230
stokes: Okay, thanks.

179
00:23:51.430 --> 00:23:59.810
stokes: yeah, Mark showed me this cool feature here. There's, like, a facilitator view to kind of do this live, which will be helpful, just because we have a number of these to go through.

180
00:24:01.190 --> 00:24:11.449
stokes: Yeah, just in case you're wondering, these markers don't go anywhere. It's more just yeah, a visual. It's just so we could track, and then yeah, this will be updated.

181
00:24:11.770 --> 00:24:17.220
stokes: on forecasts after the call with, these decisions, so… Cool.

182
00:24:19.500 --> 00:24:26.540
stokes: Okay, let me just make sure, I think now we can get into the rest of them.

183
00:24:26.680 --> 00:24:29.749
stokes: Just double checking… okay.

184
00:24:30.640 --> 00:24:31.639
stokes: Let's do that.

185
00:24:32.700 --> 00:24:37.420
stokes: Okay, from here, I figured we'd just kind of go top to bottom.

186
00:24:38.080 --> 00:24:51.350
stokes: The one thing is we had kind of said, given that 8411 was proposed pretty late in the process, we would kind of, again, hold it to the end of the scoping process, kinda do a first come first serve thing.

187
00:24:51.920 --> 00:25:00.090
stokes: I think also at the same time, at least as of this, it looks like some clients haven't had time to weigh on this.

188
00:25:00.510 --> 00:25:03.479
stokes: So I propose we just hold this for later.

189
00:25:04.710 --> 00:25:10.220
stokes: And yeah, unless someone's super called to chat about it now.

190
00:25:10.540 --> 00:25:15.139
stokes: We can move to, like… yeah, well… This is a question.

191
00:25:17.640 --> 00:25:21.709
stokes: Let's just go ahead and do that. I mean, I think we kind of agreed last call that this was okay.

192
00:25:25.130 --> 00:25:28.579
stokes: In which case… We'll move to quick slots.

193
00:25:30.520 --> 00:25:34.279
stokes: Is Barnabe on the call? I know that he had wanted to…

194
00:25:34.280 --> 00:25:34.820
Barnabé Monnot: Yep.

195
00:25:34.820 --> 00:25:36.480
stokes: Save some words here. Okay.

196
00:25:37.870 --> 00:25:40.430
Barnabé Monnot: Yeah, thank you.

197
00:25:40.660 --> 00:25:42.820
Barnabé Monnot: I have a couple slides.

198
00:25:43.500 --> 00:25:47.800
Barnabé Monnot: I think you need to stop sharing your screen so I can share mine.

199
00:25:50.490 --> 00:25:51.539
Barnabé Monnot: Just a few.

200
00:25:54.610 --> 00:25:55.919
stokes: Okay, yeah, let's go for it.

201
00:26:03.410 --> 00:26:04.570
Barnabé Monnot: Alright, can you see it?

202
00:26:06.800 --> 00:26:07.970
stokes: Yep, I can.

203
00:26:08.490 --> 00:26:09.460
Barnabé Monnot: Okay, cool.

204
00:26:09.740 --> 00:26:17.759
Barnabé Monnot: Yeah, I wanted to jump in today to make the case for considering for inclusion quick slots in Hegota.

205
00:26:17.890 --> 00:26:22.640
Barnabé Monnot: Wanted to give a bit of a status report, and what are the next steps here?

206
00:26:24.240 --> 00:26:35.019
Barnabé Monnot: Quick recap, we think, QuickSlots has a lot of value to ethereum users. You've heard it from Ryan a little bit before in the call.

207
00:26:35.150 --> 00:26:45.010
Barnabé Monnot: But just to like brush up on where exactly this value comes from, it's many different places. There's better UX from confirmation being faster.

208
00:26:45.010 --> 00:26:56.350
Barnabé Monnot: better markets from prices being updated more often, less MEV leaked to arbitragers, faster finality, faster confirmation rule as well.

209
00:26:56.390 --> 00:27:02.479
Barnabé Monnot: And more censorship resistance from having, more proposals per unit of time.

210
00:27:02.540 --> 00:27:05.970
Barnabé Monnot: So our thesis is that a faster ethereum in general

211
00:27:05.980 --> 00:27:23.379
Barnabé Monnot: makes for more valuable Blockspace, which is value that accrues to the network, to the users, and to ETH as well, in particular. And if you don't want to take it from me, you can take it from 20 teams that are building very well-known applications on Ethereum who

212
00:27:23.520 --> 00:27:34.460
Barnabé Monnot: have given us quotes in support of, of quick slots in Hegota in this fairly long but very interesting ecosystem survey that we published.

213
00:27:36.590 --> 00:27:41.549
Barnabé Monnot: So as a recap again, our proposal for Hegota is basically two things.

214
00:27:41.600 --> 00:27:53.940
Barnabé Monnot: The first one is removing the hard-coded 12-second slot assumption where it exists, so both in client code, as well as tooling, as well as smart contracts that are deployed on-chain.

215
00:27:53.950 --> 00:28:06.000
Barnabé Monnot: And then, second step, proceed with a first decrease. So, our target for Hegota is 10 seconds. You may have seen 8 seconds in the EIP that's in the process of being

216
00:28:06.150 --> 00:28:10.779
Barnabé Monnot: Updated, but our target really is, 10 seconds.

217
00:28:13.610 --> 00:28:18.300
Barnabé Monnot: Some of the progress since we proposed for inclusion.

218
00:28:18.570 --> 00:28:29.299
Barnabé Monnot: quick slots. The specs are now merged. You can check this PR5592. Shout out to Francesco, Jihoon, and Justine for their help with this.

219
00:28:29.450 --> 00:28:39.479
Barnabé Monnot: After the specs merge, I'm also reviewing the EIP, it's now in this branch, just waiting for Carl to do a review so that we can merge that.

220
00:28:39.810 --> 00:28:49.219
Barnabé Monnot: We have a Prysm prototype implementation that's ongoing, thanks to Terence. You can also find the PR here, and I'll link the slides in the chat after this.

221
00:28:49.630 --> 00:28:58.529
Barnabé Monnot: We're currently doing outreach after our ecosystem smart contract survey that we prepared with Sourcify, so what we did is we

222
00:28:58.950 --> 00:29:01.929
Barnabé Monnot: Analyze the Sourcify codebase.

223
00:29:02.460 --> 00:29:09.800
Barnabé Monnot: We've just, like, static analysis, figure out, like, which contracts are relying on the… on the slot time, and we found quite a few, but we've…

224
00:29:09.840 --> 00:29:28.280
Barnabé Monnot: already have, like, some fairly, positive impressions from teams that have very valuable contracts that, tell us that, yeah, it's possible for them to… to make changes, so that, they adapt to the… to the new slot time. So, Lido

225
00:29:28.290 --> 00:29:39.780
Barnabé Monnot: off-chain, EFFI, like, these… these are all teams that have looked into the possible problems that come with, with a slot time change, and said they're okay with it, and in fact, in support.

226
00:29:39.890 --> 00:29:43.050
Barnabé Monnot: Of the quick slots proposal, generally.

227
00:29:43.690 --> 00:29:49.140
Barnabé Monnot: We also spent quite a bit of time thinking through the interactions with

228
00:29:49.250 --> 00:30:05.789
Barnabé Monnot: the transition to post-quantum, the transition to the decouple consensus, and to ZK proving. There's a bit more on that in our Hegota view, but what I would say is that we're very confident that 10 seconds in Hegota is not a blocker at all for any of these, transitions.

229
00:30:08.580 --> 00:30:27.610
Barnabé Monnot: So, yeah, this is it for your consideration. Just to conclude here, EIP-8198 is really meant to open the door. Like, without it, we just literally cannot do latency improvements on the slot time, and take this first step that's moderate, but still, I think, very meaningful.

230
00:30:27.670 --> 00:30:39.419
Barnabé Monnot: And without committing that to Hegota, I don't think we can do that in ISTAR, given the size of decoupled consensus, so we're really committing to not having this door open for a long time.

231
00:30:39.630 --> 00:30:52.460
Barnabé Monnot: It's definitely significant, don't want to minimize that, but I think it's reasonable, according to a few people that I've been in contact with around… and code and testing, and I think it's a really high-value feature, so…

232
00:30:52.610 --> 00:30:59.270
Barnabé Monnot: Definitely worth at least spending the time to look at it closely and understand the possible challenges.

233
00:30:59.300 --> 00:31:12.820
Barnabé Monnot: And I don't think there's a better time to start than now, especially if we're concerned with ecosystem implications. So, yeah, a CFI today would help us, like, continue de-risking the challenges, like, keep the momentum high.

234
00:31:12.910 --> 00:31:23.289
Barnabé Monnot: And as EF Labs, I think we're very dedicated, we'll support your efforts, we'll be active and responsive, and make sure that this goes as smoothly as possible.

235
00:31:24.390 --> 00:31:25.680
Barnabé Monnot: That's it for me.

236
00:31:28.490 --> 00:31:29.660
stokes: Okay, thanks.

237
00:31:30.160 --> 00:31:34.799
stokes: Let's just take the hands here, Matt, and then Frederick.

238
00:31:38.470 --> 00:31:53.959
Matthew Keil: I tend to stand on the other side of this discussion, and I side with Justin Traglia's sentiment, quite strongly, that, while it's not technically difficult in order to implement the short slots, I think it…

239
00:31:53.960 --> 00:32:11.810
Matthew Keil: the tuning of the client, like, it's not, it's not easy to tune the client in order to reduce slot times. And then, but more importantly, taking the focus off PQ, I think, is something that we really, really, really need to, be fervent about.

240
00:32:12.070 --> 00:32:20.620
Matthew Keil: PQ is an existential threat, and all development efforts really should be focused on that, in particular, decoupled consensus.

241
00:32:20.620 --> 00:32:42.999
Matthew Keil: There's one other piece of that that I think should be at least highlighted, is, decoupled consensus is gonna drastically rework how slot mechanics, are… are organized, and how work is scheduled within the slot. And I think there is, something to be said about, the potential of

242
00:32:43.000 --> 00:32:47.410
Matthew Keil: shortening slots when we're doing decoupled consensus.

243
00:32:47.410 --> 00:33:10.789
Matthew Keil: because of how the rework happens, I think it opens the door for possibly even more drastic slot time reduction. But it feels kind of like chasing our tail to do so much effort in order to test shorter slots and prove it out now when we're literally going to be doing that

244
00:33:10.790 --> 00:33:16.550
Matthew Keil: Again… once we rework the slot mechanics. So…

245
00:33:16.550 --> 00:33:33.609
Matthew Keil: this is something that… that's my personal feeling. Our official stance as a team, though, is that we're open to the idea of adding the machinery in order to adjust slot times to the client, because again, it's not a technically difficult

246
00:33:33.610 --> 00:33:56.709
Matthew Keil: process in order to, to make that, something that is, you know, set with a flag or variable. However, the actual reduction of slot times is something that, I think is probably not best fit for Hegota. So that way we can spend the next, period of time working through

247
00:33:56.710 --> 00:34:09.170
Matthew Keil: the challenges of what's required in order to tune the client and make sure that as slot times are reduced, we're scheduling work on the CPUs effectively.

248
00:34:11.480 --> 00:34:17.719
Matthew Keil: And testing that, with real-world numbers on Mainnet, not just on devnets.

249
00:34:21.409 --> 00:34:23.629
Barnabé Monnot: Thanks. Should I reply now, Stokes?

250
00:34:23.630 --> 00:34:25.220
stokes: Oh, sure, yeah, yeah, go for it.

251
00:34:25.780 --> 00:34:32.119
Barnabé Monnot: Yeah, yeah, I think these are good thoughts. I would say there's 3 points in there. So, the first one is.

252
00:34:32.239 --> 00:34:33.540
Barnabé Monnot: about…

253
00:34:33.949 --> 00:34:49.909
Barnabé Monnot: Does 10 seconds threaten the post-quantum transition from, like, an architecture perspective? As in, like, is 10 seconds not enough time, for instance, to have the signatures? Are we painting ourselves in the corner with this?

254
00:34:50.090 --> 00:35:07.409
Barnabé Monnot: here, I think the answer is unequivocally no, like, because of the design of decoupled consensus, we're very, very confident that 10 seconds is just ample time to do the work necessary to do the fork choice on the slot time, so that's, in my opinion, not a problem.

255
00:35:07.600 --> 00:35:10.800
Barnabé Monnot: The second point is probably about, like, how much

256
00:35:11.070 --> 00:35:27.879
Barnabé Monnot: testing, is required. That testing will always be required whenever we want to change the slot time, but particularly so the first time we do so. And I think here the concern is more, should we be doing, like, all this work when PQ is an existential threat?

257
00:35:27.940 --> 00:35:35.760
Barnabé Monnot: And any delay on Fox kind of threatens, like, doing that transition to PQ. I see the concern, I think.

258
00:35:36.030 --> 00:35:41.860
Barnabé Monnot: I would not… Go as strongly as if I didn't feel that, yeah, we're very, very

259
00:35:41.950 --> 00:35:54.090
Barnabé Monnot: like, vanishingly low probability we are threatening the PQ timeline at all. Like, if anything, I think I'm very bullish on us moving to PQ infrastructure as soon as possible.

260
00:35:54.130 --> 00:36:08.900
Barnabé Monnot: So in… in that respect, yeah, I think this is why, to me, CFI need today would help a lot, like, have more eyes on how much work is this exactly in terms of testing on the clients and everything, so I would really welcome

261
00:36:09.060 --> 00:36:11.990
Barnabé Monnot: Us, like, taking a very strong look here.

262
00:36:12.290 --> 00:36:14.119
Barnabé Monnot: And then on the third point.

263
00:36:14.290 --> 00:36:17.109
Barnabé Monnot: Should we just bundle that with decoupled consensus?

264
00:36:17.580 --> 00:36:27.530
Barnabé Monnot: I'm not particularly confident speaking to people who are working on decoupled consensus that they would think it's reasonable to do both at the same time, like.

265
00:36:28.020 --> 00:36:43.899
Barnabé Monnot: decoupled consensus changes a lot of things. One thing it doesn't change that much, actually, is the slot structure. Like, this is still a blog that is produced, and then there's a row of attesters. In fact, it's a subcommittee of them, so 512, so much smaller than today.

266
00:36:43.970 --> 00:36:52.859
Barnabé Monnot: you will have the ePBS mechanics, you'll have FOCIL, so there's not that many things that change in terms of the slot mechanics, where

267
00:36:53.260 --> 00:37:00.030
Barnabé Monnot: Yeah, so it means, like, if we do do the work of making the slot time reduction in Hagota.

268
00:37:00.290 --> 00:37:09.459
Barnabé Monnot: not like very little to none of that work is is wasted because decoupled Consensus kind of throws all of that out of the window. This is

269
00:37:09.640 --> 00:37:25.920
Barnabé Monnot: not at all the case, as far as I… as I know. But yeah, these are just counter-arguments. I understand that some of them, obviously, are subjective, but I think for me, still would lean to CFI so that we can do the proper due diligence in terms of testing and changes.

270
00:37:29.700 --> 00:37:34.300
stokes: Okay, let's go by hands here. I think we're at Frederick, then Ben, then Barnabas.

271
00:37:35.780 --> 00:37:40.829
Fredrik: Yeah, I don't question the usefulness or the value of Quick Slots and I think

272
00:37:40.980 --> 00:37:48.690
Fredrik: It's definitely something we should strive for and implement, and we should strive for something that's much less than

273
00:37:49.560 --> 00:38:02.309
Fredrik: 10 seconds, what the lower bound is, I'm not sure, but I hope we can get very, very, very low. And I know that Barnabe and everyone else who's working on this are…

274
00:38:02.350 --> 00:38:10.520
Fredrik: like, great researchers, and they are… they do have the ability to look at all the edge cases and so forth. My concern is…

275
00:38:11.470 --> 00:38:14.789
Fredrik: I guess, similar to Matt, how this will…

276
00:38:15.270 --> 00:38:21.110
Fredrik: affect our ability to basically secure Ethereum from the post-quantum threat, and I think…

277
00:38:21.250 --> 00:38:32.540
Fredrik: we've been talking about 2030, etc, but I do think this is likely to accelerate. Who knows what's going to happen from an AI point of view next year?

278
00:38:33.290 --> 00:38:48.819
Fredrik: And it might not be that a post-quantum computer arrives, it might just be that existing cryptography is broken in various ways, and the sooner we can migrate away to something that's more secure, that's probably better.

279
00:38:49.220 --> 00:38:53.460
Fredrik: And I guess my… Where is that…

280
00:38:54.060 --> 00:39:05.130
Fredrik: quick slots in some way might end up delaying Heguta, primarily because of these unknowns that might affect the ecosystem at large.

281
00:39:05.250 --> 00:39:09.940
Fredrik: So basically, I'm primarily concerned about

282
00:39:10.470 --> 00:39:16.239
Fredrik: that. I'm not sure how long it will take from a technical point of view to implement.

283
00:39:16.820 --> 00:39:18.060
Fredrik: Quick slots…

284
00:39:18.770 --> 00:39:32.270
Fredrik: But unless it's very easy, then… I mean, that basically means that CL teams are spending time on implementing quick slots instead of starting on the PQ items in ISTAR, for example.

285
00:39:32.800 --> 00:39:39.469
Fredrik: Maybe some kind of a middle way here could be to say, you know.

286
00:39:40.090 --> 00:39:45.259
Fredrik: EF is very easy to implement this, technically.

287
00:39:45.520 --> 00:39:55.450
Fredrik: And… It turns out that… Actually lowering it from 12 seconds to 10 seconds is going to…

288
00:39:55.970 --> 00:40:07.039
Fredrik: take months of research and reaching out to ecosystem and so forth, then maybe there could be an agreement to just simply keep it at 12 seconds, and

289
00:40:07.220 --> 00:40:18.699
Fredrik: do the, like, lower the amount later. But again, I'm not sure how long this would take from a technical implementation point of view. If we're talking months, or…

290
00:40:19.090 --> 00:40:24.120
Fredrik: days or weeks for most of the clients, so I think that would be interesting to hear as well.

291
00:40:28.130 --> 00:40:32.290
stokes: Oh, no, yeah, go ahead, Bernaman, if you had a response.

292
00:40:32.290 --> 00:40:43.010
Barnabé Monnot: Just a couple of thoughts. Yeah, I think, I mean, still agree on this might be work, and we have to be mindful of any work that delays, shipping Hegota.

293
00:40:43.310 --> 00:40:50.600
Barnabé Monnot: on its own, because I think delaying forks is never nice, but also in the context of the PQ transition.

294
00:40:50.870 --> 00:41:02.079
Barnabé Monnot: I hear in what Frederick said, and also what Matt said, like, this idea of maybe there's exit ramps, where we can do some of the work, but then we can decide later whether to move from 12 to 10.

295
00:41:02.560 --> 00:41:18.830
Barnabé Monnot: I… I mean, we can always do that, like, in principle. There's work that can be done on the clients to remove some of the dependencies, but then keep 12 seconds in there. I think it's still worth pushing for 10 seconds. Like, in my opinion, it's not really the…

296
00:41:18.920 --> 00:41:36.039
Barnabé Monnot: like, moving from 12 to 10, that's, like, the hard part. I think it's more about preparing all the test beds to test these things, making sure that, the client tunings that Matt was talking about, you also have, like, ways to

297
00:41:36.320 --> 00:41:41.900
Barnabé Monnot: Yeah, to inject the right values, essentially, so… So yes, I think…

298
00:41:42.410 --> 00:41:49.099
Barnabé Monnot: The work, anyways, will look like, allowing us to change the slot time, and then making that slot time change.

299
00:41:49.250 --> 00:41:58.009
Barnabé Monnot: My guess, from where I stand today, is doing the work of allowing ourselves the slot time will very likely lead us to

300
00:41:58.600 --> 00:42:06.500
Barnabé Monnot: to understand that, yeah, going then from 12 to 10 is not that much work, but… Then again, I think we need more data on this.

301
00:42:06.500 --> 00:42:11.960
Fredrik: But I think, like… On the protocol level, changing from

302
00:42:12.130 --> 00:42:17.350
Fredrik: 12 to 10 probably isn't the hardest part, isn't it? More…

303
00:42:17.510 --> 00:42:26.980
Fredrik: let's say, the ecosystem point of view. I think you guys had Sourcify do some kind of analysis on contracts that would be affected by this, and so forth.

304
00:42:28.080 --> 00:42:36.979
Barnabé Monnot: Yeah, but we're we're going to do this work anyways of reaching out to every smart contract that we identified, and we already like started with with this work.

305
00:42:37.040 --> 00:42:51.750
Barnabé Monnot: Like, we can't delay that until we have certainty that, oh, actually, yes, we are flipping the switch from 12 to 10. Like, some of these smart contracts, they need, I don't know, there's governance, there's delays and stuff like this, so… so there's no reason to…

306
00:42:52.300 --> 00:43:07.110
Barnabé Monnot: backload that work until we make the active decision, let's say, to go from 12 to 10. So we started already, as of a month ago, we're doing that, like, fairly rigorously at the moment. I think it would help, actually, to

307
00:43:07.280 --> 00:43:11.650
Barnabé Monnot: At the CFI, some of the teams, sometimes we have to spend some time thinking about their

308
00:43:11.760 --> 00:43:16.699
Barnabé Monnot: their contracts and everything, so they want to make sure that it's not time that they are wasting.

309
00:43:16.850 --> 00:43:24.600
Barnabé Monnot: But yeah, this work is definitely happening and we're very serious about doing it properly over the next weeks and months.

310
00:43:24.600 --> 00:43:29.209
Fredrik: And how many contracts was… like, would be affected by this?

311
00:43:30.470 --> 00:43:38.409
Barnabé Monnot: I think there is… 100 contracts that I would say…

312
00:43:38.630 --> 00:43:44.069
Barnabé Monnot: Our main contracts, obviously, like, the…

313
00:43:44.340 --> 00:43:50.429
Barnabé Monnot: The static analysis detected a lot more, because there's many contracts that are just, like, forks of well-known contracts.

314
00:43:50.580 --> 00:43:56.209
Barnabé Monnot: But I would say, yeah, order of magnitude, there's probably 100 that we need to be

315
00:43:56.470 --> 00:44:00.749
Barnabé Monnot: Thinking clearly about, how does it…

316
00:44:00.970 --> 00:44:04.710
Barnabé Monnot: get mitigated here? Who is the team to reach out to?

317
00:44:04.970 --> 00:44:06.540
Barnabé Monnot: Yeah.

318
00:44:06.800 --> 00:44:15.889
Barnabé Monnot: I don't think it's infeasible, and again, like, many contracts are just, like, forks of other contracts, so once we figure it out for one, it's not that hard to figure out for others.

319
00:44:21.810 --> 00:44:24.890
stokes: Okay. Ben, then Barnabas, then Matt.

320
00:44:26.440 --> 00:44:36.210
Ben Adams: Yeah, I mean, so the EL has, in Glamsterdam, has the slot num opcode, which, so you, you don't need to use the timestamp versus the

321
00:44:38.200 --> 00:44:38.860
Ben Adams: Okay.

322
00:44:39.690 --> 00:44:40.590
Ben Adams: Blocks.

323
00:44:41.000 --> 00:44:47.199
Ben Adams: To work out what SLOT is. But also, it seems like…

324
00:44:48.080 --> 00:44:54.760
Ben Adams: doing… I mean, you can do the work, otherwise the work will never get done, it'll just get postponed and postponed.

325
00:44:54.960 --> 00:45:02.060
Ben Adams: But then maybe if people are a little bit hesitant, you can hold it at 12 on the actual fork.

326
00:45:02.280 --> 00:45:07.000
Ben Adams: And it's been mentioned in… chat, do something like a BPO.

327
00:45:07.670 --> 00:45:08.830
Ben Adams: Mid-fork?

328
00:45:08.940 --> 00:45:11.469
Ben Adams: To… to bring down the… the slot time.

329
00:45:12.470 --> 00:45:13.559
Ben Adams: As an option.

330
00:45:18.400 --> 00:45:25.920
stokes: Yeah, I think… The simpler the better. But, yeah, I'll just pause there. Barnabas and then Matt.

331
00:45:27.050 --> 00:45:31.159
Barnabas: Yeah, so my point is basically, what I also put in the chat, that

332
00:45:31.270 --> 00:45:45.650
Barnabas: Personally, I feel like we shouldn't make up the protocol today, just out of the fear of what, post-quantum will require later. Like, we are not at the point right now where we could be implementing post-quantum work just yet.

333
00:45:46.010 --> 00:45:59.010
Barnabas: So, just out of the fear of that, we shouldn't be limiting what we start including in the protocol today. I think we should do our best effort in improving the protocol, and

334
00:45:59.050 --> 00:46:14.870
Barnabas: in case later on, this seems like a bad decision, then we can always revert back to 12, or if… if needed, even more, because this EIP will actually allow us to adjust this later on at.

335
00:46:15.080 --> 00:46:16.740
Barnabas: But the future Epoch as well.

336
00:46:17.090 --> 00:46:28.259
Barnabas: I know that that's not something that we want to do, but it's something we could do. And yeah, if every client implements this array feature.

337
00:46:28.930 --> 00:46:32.490
Barnabas: I I think it's it's a EIP that should be included.

338
00:46:32.660 --> 00:46:33.850
Barnabas: Or, Heather?

339
00:46:36.170 --> 00:46:43.650
stokes: To be clear, when you say array feature, is it something like, you know, this slot param only type thing, or, like, how we handle VPOs?

340
00:46:45.170 --> 00:47:03.990
Barnabas: That's… that's basically how it was added in the, config yaml right now. There's an array for it, where we define, at specific EPOC, we will use this slot time. And we are planning to deprecate the, old, seconds per slot, which is already gone, and the…

341
00:47:04.530 --> 00:47:08.959
Barnabas: Slot period, millisecond, or… I'm not sure what the…

342
00:47:09.140 --> 00:47:09.700
stokes: whatever.

343
00:47:09.700 --> 00:47:14.660
Barnabas: But that can also be deprecated, once this array is being used.

344
00:47:15.410 --> 00:47:16.060
stokes: Yeah.

345
00:47:16.170 --> 00:47:18.230
stokes: And just to make it clear, like.

346
00:47:18.460 --> 00:47:26.279
stokes: There's how this is sort of configured or parameterized in the client with, you know, this is, like, the config that Barnabas is talking about right now.

347
00:47:26.840 --> 00:47:32.800
stokes: I do think we should keep clear that this SPO idea is separate, and, like, the difference is that

348
00:47:32.910 --> 00:47:37.570
stokes: You know, changing it at a hard fork, which has a lot of attention on it, is…

349
00:47:38.030 --> 00:47:44.119
stokes: yeah, I think different to how we do BPOs. Not that BPOs don't have as much attention, but…

350
00:47:44.400 --> 00:47:47.250
stokes: Yeah, it does feel a bit different.

351
00:47:48.860 --> 00:47:50.400
stokes: Anyway, Matt.

352
00:47:52.730 --> 00:47:59.529
Matthew Keil: Thank you. I do tend to, disagree with Barnabas that.

353
00:47:59.580 --> 00:48:24.439
Matthew Keil: we could increase slot times. I think that's never going to ever happen. Like once a market gets something, it's impossible to go back. And I think this is also part of the sentiment that initially I pushed back on even adding the complexity of being able to modify slot times because there's going to be pressure in order to reduce the slot time.

354
00:48:24.440 --> 00:48:30.420
Matthew Keil: At every single fork and I, while I agree that it's a very important thing.

355
00:48:30.510 --> 00:48:53.300
Matthew Keil: for the protocol. So I don't necessarily think we're going to kneecap the protocol by not shortening slot times. But at the same time, there's going to be intense pressure because of the economic benefit that comes from shorter slot times and arbitrage opportunities, and really, which is the best benefit, like, the most important thing that you're going to get out of shorter slot times is cross-chain arbitrage. And…

356
00:48:53.300 --> 00:49:15.479
Matthew Keil: There is just so many other things that the teams need to be focused on right now, in particular PQ, privacy, encrypted mempools. Like there's just a ton of features that I think are more important than increasing profitability of certain stakers or excuse me, certain stakeholders.

357
00:49:16.970 --> 00:49:21.670
Matthew Keil: I do agree that it's very important in order to shorten slot times.

358
00:49:21.830 --> 00:49:38.769
Matthew Keil: Sure. And this is why I think we have, we as a team have advocated to add the machinery in order to be able to make that adjustable. But there is one other piece of this, is that 10 seconds was kind of arbitrarily chosen, because it felt like a… and I don't know this to be a fact, I just…

359
00:49:38.770 --> 00:50:02.399
Matthew Keil: after reading the chat, it feels like a politically feasible target. Like, 10 seconds is not that much of a difference, but, like, there's no real backing that says that that's the right number, or it's like a toe in the door, and this is where the idea of adding the machinery to the clients now, at H, but not actually adjusting the slot times, and then it's relatively easy to dial that as we go forward.

360
00:50:02.400 --> 00:50:26.859
Matthew Keil: But we would have the machinery in order to be able to get real-world metrics, we'd be able to test to see how things are actually working, and we're pulling the testing, which is going to be very… it's… like, the amount of effort to add the machinery to dial the slot times is very easy. Literally, we built it in 10 minutes. The thing that's difficult is scheduling work on the CPUs when you've got an EL that's running

361
00:50:26.860 --> 00:50:51.820
Matthew Keil: faster and you've got a seal that's running faster. And like, this is where the rubber hits the road. It's, it is, there's going to be hot pass that come up and it's not like, it's not like your timers in, in the client are just going to scale linearly and you're not going to have any issues. There's going to be hot pass that come up that are going to be different today than they are, at 12 seconds or excuse me, that are going to be different at 10 seconds than they are at 12 seconds. And when you get to decouple consensus, that

362
00:50:51.820 --> 00:50:54.129
Matthew Keil: thing is going to apply is that

363
00:50:54.130 --> 00:51:18.540
Matthew Keil: the work is going to be spread throughout the slot in a very different way, especially with aggregations coming out of slot-wise mechanics. So, like, because of that, there's going to be a very different scheduling of work when it comes to what happens on core, and we have no idea what that looks like. And we also don't know what it looks like when you go to 10 seconds, and there's just a ton of variables, and it feels like an optimization that is

364
00:51:18.620 --> 00:51:24.690
Matthew Keil: is… I don't know if premature is the right word to say, but it feels like it's… it's…

365
00:51:24.880 --> 00:51:35.890
Matthew Keil: it just needs to wait for the decouple consensus, which is critical for the PQ roadmap, because of how long aggregations take, so that we can

366
00:51:36.780 --> 00:51:41.100
Matthew Keil: properly test, what the adequate slot time is.

367
00:51:45.200 --> 00:51:48.250
Barnabé Monnot: And maybe a quick reply here, I…

368
00:51:48.660 --> 00:52:08.350
Barnabé Monnot: Yeah, I agree that 10 seconds looks like a bit of a magic number, but I will say that to me, the most pressure on not going lower than 10 seconds came from concerns around the proving time and zkVM, and are we able to get real-time proving fast enough with 10 seconds? So it's a lot of, like.

369
00:52:08.380 --> 00:52:15.780
Barnabé Monnot: decision-making under uncertainty, because, yeah, when are we shipping X, Y, or Z, and what will be the performance by then, etc.

370
00:52:15.830 --> 00:52:27.489
Barnabé Monnot: Like, for PQ, again, like, given the design of decoupled consensus, using a subcommittee, not aggregating, having 512 validators with a 1KB signatures.

371
00:52:27.490 --> 00:52:28.100
Miguel: Nick.

372
00:52:28.100 --> 00:52:39.819
Barnabé Monnot: It just feels like every measurement today tells us that this is easily feasible, and not really the bottleneck of a constraint that we would hit first.

373
00:52:39.980 --> 00:52:43.979
Barnabé Monnot: But yeah, obviously, like, more testing, always better.

374
00:52:44.170 --> 00:52:51.070
Barnabé Monnot: So, not claiming that this shouldn't be done, but would love to… to make that possible.

375
00:52:55.800 --> 00:52:59.849
stokes: Okay, thanks, everyone. There are obviously many considerations here.

376
00:53:01.730 --> 00:53:09.010
stokes: I do want to be mindful of time, but it would be nice to hear from some other client teams, who…

377
00:53:09.240 --> 00:53:11.909
stokes: ranked in favor of CFI in this.

378
00:53:12.170 --> 00:53:19.980
stokes: I feel like we've heard… So far from, you know, people with reasonable concerns, but…

379
00:53:20.640 --> 00:53:32.760
stokes: Following along in the chat here. Yeah. It's it was a little tricky, but, you know, just to surface some things, I think a number of people chimed in saying that, yeah, you know, technically, to get the parameterization in place.

380
00:53:33.080 --> 00:53:39.739
stokes: You know, that's actually not a big deal, pretty straightforward. Yeah, and I think some of the other people who…

381
00:53:40.080 --> 00:53:43.840
stokes: Rated this well in their client rankings, or also speaking of Aver.

382
00:53:44.560 --> 00:53:50.409
stokes: So okay, we have some hands. Now, let's do Terence Walter, then Salius.

383
00:53:50.910 --> 00:54:04.490
terence: Hi, yeah, so I think Prysm Team rated, A. I think it was mostly between S and A, but we only want to give one S, and then we found that faster execution, or faster block.

384
00:54:04.690 --> 00:54:20.439
terence: is more important and slightly easier, because it essentially gives more, room for broadcast, so it kind of sets up quick slots nicely. In terms of implementation, Prysm has a prototype, and then.

385
00:54:20.440 --> 00:54:26.800
terence: When he was on leave, I also picked up the prototype, and then I updated it against the latest spec.

386
00:54:26.890 --> 00:54:39.810
terence: We have gone through some several weeks of fairly, I would say, detailed-ish audit on what the changes on the Prysm codebase, with the help of AI.

387
00:54:39.810 --> 00:54:49.879
terence: And then, I would say overall, like, I mean, it's not easy. I mean, so is every other EIP is not easy, right? Unless your EIP is something like.

388
00:54:49.900 --> 00:55:04.129
terence: 8015, something I propose, and then every EIP is hard, right? Every EIP is engineering challenge. The question is whether the trade-off is worth it, and I… we think the trade-off is worth it. We think, like.

389
00:55:04.560 --> 00:55:19.069
terence: it's important to reduce the stall time, and then we shouldn't wait for another… if we don't do it now, we have to wait another 3 years to reduce the stall time, and to us, it just seems like a no-brainer to do it now. But yeah, that's… that's our take.

390
00:55:21.860 --> 00:55:29.370
stokes: Okay, thanks. Walter, Solius, and then Lukasz, and then I think we should probably move on after that.

391
00:55:29.990 --> 00:55:33.610
Walter Himmelsbach: CPU is now really expensive.

392
00:55:33.800 --> 00:55:40.289
Walter Himmelsbach: Did, we can buy CPUs in the next, years a little bit cheaper, what do you think?

393
00:55:45.910 --> 00:55:48.939
stokes: Do I think CPUs will be cheaper in the future?

394
00:55:49.680 --> 00:55:52.970
stokes: That's a good question.

395
00:55:53.730 --> 00:55:54.600
stokes: Yeah.

396
00:55:54.770 --> 00:55:58.590
stokes: Let's just assume they will be. Solius?

397
00:56:03.300 --> 00:56:05.109
Miguel: Yes, CPUs are expensive.

398
00:56:07.020 --> 00:56:14.159
saulius: Yes, we are not in support of the EIP and I think that

399
00:56:14.630 --> 00:56:29.910
saulius: Maybe a way to move forward with that would be something similar like we had with the stable containers, where essentially the feature was not accepted at the beginning.

400
00:56:29.910 --> 00:56:49.360
saulius: And then some teams pushed it, and during the hard fork implementation, it was… it became clear that it's possible to ship it. So my suggestion would be, as there is some people that are pushing shorter slots, I think maybe we can just

401
00:56:49.480 --> 00:57:05.859
saulius: not accepted for now, but some teams could push it and share their experience, and then maybe it will happen, you know, in a few months or so, after it becomes much more clear what are the efforts to ship this quick slots.

402
00:57:08.200 --> 00:57:17.389
Barnabas: It's usually the other way around. We CFI first and then find out if it's problematic, then we drop it because the scoping would end by the end of this month.

403
00:57:19.200 --> 00:57:27.169
saulius: Well, I'm, I mean, I don't like to, to, you know, to, to agree to this feature right now.

404
00:57:27.540 --> 00:57:35.229
saulius: I mean, I think it's… it will… it's really something that will delay the, the hard work.

405
00:57:40.290 --> 00:57:48.879
stokes: Yeah, I mean, I think the ask is more agreed to accept doing the work now, so that we can then, you know, be in a better place to make the right call.

406
00:57:50.480 --> 00:57:55.650
stokes: Lukasz, Terrence, and then Enrico, okay, and then after Enrico, we should definitely move on.

407
00:57:55.650 --> 00:58:08.670
Łukasz Rozmej: Two points from me. We'll try to be quick. CPUs, I don't know what you guys are planning to do. CPUs currently tail block processing on EL is from 50 to 200 milliseconds, depending on the

408
00:58:08.670 --> 00:58:20.959
Łukasz Rozmej: On the client and on the reference hardware, so I don't think CPU is a problem. BALs will increase that a little bit, but, or maybe not, we'll see, but I don't expect huge changes.

409
00:58:20.990 --> 00:58:28.249
Łukasz Rozmej: So we not a problem, in my opinion, from the EL side, even in the Crist load. I don't know what is planned on CL.

410
00:58:28.270 --> 00:58:41.710
Łukasz Rozmej: So we'll see about that. But I don't see CPU as a problem. And zkvms and I'm telling from the person who's currently optimizing guest program for zkvm

411
00:58:41.710 --> 00:58:52.889
Łukasz Rozmej: I wouldn't allow them to hold the protocol hostage and improvements to the protocol hostage. They need to keep up both zkvm and guest programs. They need to be optimized.

412
00:58:53.080 --> 00:58:59.180
Łukasz Rozmej: And here we can at least throw more hardware at the problem if really needed, so,

413
00:58:59.770 --> 00:59:15.090
Łukasz Rozmej: I don't see this as a blocker either, so never mind this for, shorter slots. I wouldn't commit to any, actual numbers, before we measure them, but I would, I would, I am very far,

414
00:59:15.280 --> 00:59:19.140
Łukasz Rozmej: actually… Putting the work to be able to do it.

415
00:59:21.680 --> 00:59:26.889
stokes: Okay, Enrico and Terrence, you can have 10 seconds.

416
00:59:28.680 --> 00:59:29.540
stokes: Okay.

417
00:59:29.960 --> 00:59:35.859
terence: Yeah, I would say to Saulius point, right, if we were, oh, sorry, go ahead, Enrico, did you want to say something?

418
00:59:35.860 --> 00:59:44.340
Enrico Del Fante: Was mute. Sorry. Yeah, just a quick update. So Teku put it in S. We have this

419
00:59:44.680 --> 00:59:51.740
Enrico Del Fante: On the implementation side, we believe it's not that complicated.

420
00:59:52.270 --> 01:00:08.609
Enrico Del Fante: I do think, personally, that it's worth having, and I don't actually buy much the argument from Matthew on the CPU things, because we change every time the slot, and how

421
01:00:08.640 --> 01:00:12.359
Enrico Del Fante: the hot path… hot path on the… on the SLOTR.

422
01:00:12.410 --> 01:00:15.189
Enrico Del Fante: are happening even now in Luas.

423
01:00:15.250 --> 01:00:18.889
Enrico Del Fante: There will be a lot of changes, and…

424
01:00:19.010 --> 01:00:25.240
Enrico Del Fante: in Hegota with FOCIL, there are… there will be others, probably. So…

425
01:00:25.400 --> 01:00:30.570
Enrico Del Fante: That seems like a weak argument to me, but I feel instead the argument of

426
01:00:31.390 --> 01:00:44.499
Enrico Del Fante: Opening the door of future pressure to shortening the slot, because now it's easy and just a parameter change, and there will be some economical pressure to

427
01:00:44.700 --> 01:00:49.859
Enrico Del Fante: to… to shorten, even if I believe that

428
01:00:50.980 --> 01:01:02.420
Enrico Del Fante: A technical argument to not do that will stand because it's not just the technical implementation. There will be other reason why we can push back.

429
01:01:02.620 --> 01:01:11.679
Enrico Del Fante: So I definitely believe that this… this machinery should… should go in, and then we can…

430
01:01:12.010 --> 01:01:19.460
Enrico Del Fante: Make the old ecosystem smart contract analysis, thing to actually kick, kick.

431
01:01:19.580 --> 01:01:23.569
Enrico Del Fante: Kick the work there, and make this thing move forward.

432
01:01:26.940 --> 01:01:29.300
stokes: Okay, Terrence, did you have… a very.

433
01:01:29.300 --> 01:01:31.489
terence: No, that's okay.

434
01:01:31.490 --> 01:01:31.820
stokes: Okay.

435
01:01:31.820 --> 01:01:32.980
terence: Yes, you can go.

436
01:01:33.650 --> 01:01:34.520
stokes: Okay, thanks.

437
01:01:35.670 --> 01:01:46.070
stokes: So okay. Yeah. Again, thanks, everyone. And you see there's a lot going on here. But, yeah, ultimately, you know, in terms of distilling rough consensus.

438
01:01:46.460 --> 01:01:49.940
stokes: I do feel like it is what Barnabe has here in the chat.

439
01:01:50.410 --> 01:01:55.910
stokes: Everyone agrees to the value, both here, but also, you know, broadly in the community, and…

440
01:01:56.150 --> 01:02:02.590
stokes: Given the sort of stage approach that, you know, we've been discussing throughout this call.

441
01:02:03.150 --> 01:02:11.400
stokes: of going ahead with CFI today, you know, put in this additional legwork, to validate, you know, specific numbers and things.

442
01:02:12.380 --> 01:02:22.530
stokes: we go ahead and do that, and that gives us another point later in time that, you know, if we need to pull it out, we can. So, you know, that actually maps quite well to CFI today. And then before we SFI.

443
01:02:22.920 --> 01:02:28.689
stokes: you know, we'll have time to dig deeper into all these things everyone is bringing up. So…

444
01:02:29.500 --> 01:02:33.040
stokes: I feel like that's a pretty nice way to move forward.

445
01:02:34.360 --> 01:02:35.409
stokes: Shall we do that?

446
01:02:42.570 --> 01:02:43.380
stokes: Okay.

447
01:02:43.700 --> 01:02:45.050
stokes: Getting some thumbs up.

448
01:02:48.160 --> 01:02:48.960
stokes: Okay.

449
01:02:49.880 --> 01:02:58.140
stokes: So let's go in CFI and again the understanding here is that you know we still want some more data to validate the change from twelve to ten.

450
01:02:58.400 --> 01:03:05.519
stokes: there will be, you know, the opportunity to revisit this before it goes to SFI in the event that things come up in implementation.

451
01:03:05.650 --> 01:03:06.410
stokes: So…

452
01:03:08.000 --> 01:03:09.169
Ben Adams: Do you rush?

453
01:03:09.280 --> 01:03:10.810
Ben Adams: Could you share screen again?

454
01:03:11.590 --> 01:03:12.140
stokes: Yep.

455
01:03:19.990 --> 01:03:20.810
stokes: Okay.

456
01:03:21.140 --> 01:03:22.589
stokes: Can everyone see this?

457
01:03:27.060 --> 01:03:31.170
stokes: Okay, I'll just assume that you can. I… here, let me get the chat back up.

458
01:03:32.540 --> 01:03:34.270
stokes: anyway.

459
01:03:35.790 --> 01:03:43.350
stokes: Okay, so CFI quick slots, again, some caveats here around getting DASFI, but I think we all understand

460
01:03:43.670 --> 01:03:45.059
stokes: What needs to be done there?

461
01:03:46.800 --> 01:03:53.400
stokes: Okay. Let's see. So we have about thirty minutes left. Let's keep trying to get through these.

462
01:03:54.060 --> 01:03:54.980
stokes: Okay.

463
01:03:55.140 --> 01:03:59.089
stokes: Next one up, then, would be 8379.

464
01:03:59.420 --> 01:04:01.749
stokes: This is Top Up Sync.

465
01:04:01.870 --> 01:04:05.679
stokes: Let's see. Dustin here is listed as as the champion.

466
01:04:05.880 --> 01:04:11.840
stokes: Would you like to say anything about this? And then from there, we can get into client opinions.

467
01:04:13.510 --> 01:04:19.820
Dustin: Yeah, so I can… so first I can, I just have a,

468
01:04:21.180 --> 01:04:26.079
Dustin: A slide, but I, you know, it's not, it's not super critical,

469
01:04:26.400 --> 01:04:32.459
Dustin: I don't have a whole presentation in the sense that, you know, Barnabe did. So I want to…

470
01:04:32.940 --> 01:04:37.690
Dustin: Essentially, this is a way of, of

471
01:04:38.340 --> 01:04:52.619
Dustin: Driving… so the CL can… can drive the sync on the EL side, and… and it can do so by, sort of distinguishing between different kinds of, sort of…

472
01:04:53.710 --> 01:05:10.219
Dustin: so if we have a blockhead and execution head, as if… so where… how many blocks this… the EL might have, even if it hasn't calculated the state through that, which means it can backfill the block from the exact right place the EL, rather, needs to actually sync.

473
01:05:10.220 --> 01:05:29.270
Dustin: which is a capability that doesn't really exist today. So, and I would say there's a few general items that sort of enable sort of functionalities, resilience that we don't have in a standardized way right now. One is, as we're talking about sort of potential

474
01:05:29.690 --> 01:05:37.959
Dustin: sort of recovery plans, and earlier on. Well, one of the things here is that one of…

475
01:05:37.960 --> 01:05:50.320
Dustin: In Pectra, in Holesky, one of the things that went wrong, right, is that when you had the CLs and ELs, the CLs couldn't actually sync fully properly without the ELs, syncing.

476
01:05:50.320 --> 01:05:51.170
Dustin: And

477
01:05:51.530 --> 01:06:08.249
Dustin: both found it difficult for the same forked chain reasons, but both at the same time was even more unlikely, and that made it more likely to get stuck, so therefore, this would enable… only the CL has to stay synced, the EL can

478
01:06:08.410 --> 01:06:14.839
Dustin: sort of follow along with this CL much more directly. So that sort of enables resilience there. So that's the point one.

479
01:06:14.850 --> 01:06:33.729
Dustin: Point two is it enables, it reduces duplicate and inefficient gossip traffic, in a much more, systematic way. The ELs can simply stop listening if they… if they choose, right? This is a… it adds flexibility. This is all optional, right? But… but they can… they can…

480
01:06:33.730 --> 01:06:42.810
Dustin: Avoid, listening to certain, on certain things they have to listen to today, without actually losing functionality, and

481
01:06:42.810 --> 01:07:05.319
Dustin: this reduces all sorts of surface, attack surface as well on the ELs, potentially, as well as, in a longer term, potentially we can look at a sort of less-protocol reliance on our ethereum overall. And finally, the third or fourth, depending on how you're counting, I'll wrap up here, and then we can, you know.

482
01:07:05.320 --> 01:07:23.529
Dustin: So try to be quickish about this, is it enables a broad concept of a flexible delineation between exactly how and where storage is deduplicated.

483
01:07:23.600 --> 01:07:35.769
Dustin: Between CLs and ELs. Now, right now, this is, something that some CLs and ELs already do, obviously. Some CLs will offload

484
01:07:35.820 --> 01:07:41.619
Dustin: payloads in the future. I'm sure envelopes say to ELs, things like this.

485
01:07:41.620 --> 01:07:56.769
Dustin: So, this… this allows for an arbitrary kind of set point to be defined at some level, because you can kind of load up the EL with it, and then the… or the EL can… can drop things, and they can be re-added, and it can… it can be this,

486
01:07:56.920 --> 01:08:07.999
Dustin: somewhat bidirectional thing that, yeah, can be tuned in a flexible way. So, I'll… there's some other points, but I'll stop there, and then, you know, have some…

487
01:08:08.400 --> 01:08:09.990
Dustin: Discussion.

488
01:08:12.400 --> 01:08:13.400
stokes: Marion, thanks.

489
01:08:14.540 --> 01:08:22.370
stokes: Let's see, I think I can see hands here, and the UI… So, yeah, any comments immediately, Lukash?

490
01:08:23.109 --> 01:08:33.609
Łukasz Rozmej: So, our concerns with TopUpSync are that we extremely optimize our sync process on the EL side, and this, is.

491
01:08:33.909 --> 01:08:39.629
Łukasz Rozmej: This EIP… is… Removing…

492
01:08:40.079 --> 01:08:44.529
Łukasz Rozmej: Our control from us, to some extent, so we are very wary of it, and…

493
01:08:45.099 --> 01:08:47.409
Łukasz Rozmej: That's our problem with it.

494
01:08:53.330 --> 01:08:54.259
stokes: How do you lose control?

495
01:08:54.260 --> 01:08:54.680
Dustin: So.

496
01:08:54.689 --> 01:08:57.949
stokes: I didn't follow. Or yeah, Dustin, you can jump in.

497
01:08:58.569 --> 01:08:59.089
stokes: Well…

498
01:08:59.090 --> 01:09:04.129
Dustin: No, no, I'll, I'll, I'll, I'll, no, if Lukasz wants to, you know, I'll say, I'll.

499
01:09:04.620 --> 01:09:06.020
Dustin: See, wait for responses.

500
01:09:06.029 --> 01:09:13.159
Łukasz Rozmej: Or did I, or did I, or did I, confuse the APs? Okay, let me get, get back, actually, sorry.

501
01:09:13.379 --> 01:09:14.259
Łukasz Rozmej: Maybe…

502
01:09:15.870 --> 01:09:23.220
Łukasz Rozmej: I confused the EIPs because there are two sync EIPs in proposed. Sorry, I'm not sure. I got confused. Too many things.

503
01:09:23.229 --> 01:09:24.069
Dustin: Oh, oh, oh.

504
01:09:24.339 --> 01:09:25.709
Dustin: Oh, okay, okay.

505
01:09:30.029 --> 01:09:39.559
stokes: Can you tell us Dustin does it? I'm also I haven't had time to look at this too deeply. And it sounds like it's just exposing more information from the EL, which the CL can.

506
01:09:39.560 --> 01:09:40.000
Dustin: Right.

507
01:09:40.000 --> 01:09:40.890
stokes: However it wants.

508
01:09:41.600 --> 01:09:54.900
Dustin: Yes. No, so I would say it removes zero control from ELs. The one thing it qualitatively newly asks from ELs, really, is it has to… so…

509
01:09:55.280 --> 01:09:57.459
Dustin: This, this end… this,

510
01:09:57.640 --> 01:10:02.710
Dustin: It's called engine I mean, currently called engine get sync status, but that obviously can be

511
01:10:02.940 --> 01:10:16.110
Dustin: Bike shedded endlessly. And in fact, I should say in in honesty, it's it's really aimed more at an SSZ world, so it would be renamed anyway. But, yeah, you know, just synchronization of of EIPs in that kind of sense here.

512
01:10:16.110 --> 01:10:26.290
Dustin: So, but this endpoint, but this is an informational endpoint. This is a reading endpoint more than anything else. This is not, this doesn't ask the EL to do anything.

513
01:10:26.470 --> 01:10:28.849
Dustin: It gets information from the EL.

514
01:10:30.690 --> 01:10:39.649
Dustin: And so in that sense and and then what CLs do with this, is then up to the CLs, but the ELs can then

515
01:10:39.850 --> 01:10:44.709
Dustin: React as they will, but yeah, it does not remove any control, no.

516
01:10:49.260 --> 01:10:51.729
stokes: Francesco, you had a hand.

517
01:10:51.870 --> 01:10:53.099
stokes: But it disappeared.

518
01:10:56.280 --> 01:10:58.200
Francesco D'Amato: No, it was from Guadalupe.

519
01:10:58.790 --> 01:11:02.310
stokes: Different Francesco, Risitano Tau.

520
01:11:08.350 --> 01:11:22.509
Francesco Risitano (Tau): Yeah, I was just, gonna touch on the point of, efficiency. I guess I was also confused because, I was of the understanding that, the CL would be feeding blocks to the EL for sync.

521
01:11:22.580 --> 01:11:41.600
Francesco Risitano (Tau): Which may have also been Lukasz's, point around efficiency, because the ELs have, you know, highly parallelized, pipelines for syncing. You can just, provide the sync target over the engine API, and then, yeah, the ELs can use.

522
01:11:41.780 --> 01:11:46.250
Francesco Risitano (Tau): Those processes to sync, to the chain tip, essentially.

523
01:11:46.540 --> 01:11:57.780
Francesco Risitano (Tau): And I believe there's, like, an alternative which was DFI'd, which was 8237, which was more aligned with, kind of, delegating

524
01:11:57.940 --> 01:12:11.649
Francesco Risitano (Tau): EL sync to the EL, and then just having, like, a binding commitment, once the sync is completed, to kind of ensure, cross-chain consistency.

525
01:12:11.910 --> 01:12:13.659
Francesco Risitano (Tau): But yeah.

526
01:12:16.260 --> 01:12:22.639
Dustin: Okay, so… The.

527
01:12:24.590 --> 01:12:25.530
Dustin: And.

528
01:12:25.680 --> 01:12:32.839
Dustin: Sorry, so actually, first I want to say, as far as Lukasz's, the

529
01:12:36.760 --> 01:12:39.360
Dustin: The so I.

530
01:12:39.740 --> 01:12:44.520
Dustin: Sorry, the, Lukasz's thing about the,

531
01:12:44.730 --> 01:12:48.860
Dustin: I don't see the loss of control in that so, like, I'll just say.

532
01:12:50.000 --> 01:12:53.839
Dustin: But anyways, as far as the efficient pipeline,

533
01:12:53.950 --> 01:13:00.509
Dustin: The, yeah, this is not meant to replace like the snap sync say, like from, from.

534
01:13:00.860 --> 01:13:01.620
Dustin: From.

535
01:13:01.720 --> 01:13:03.290
Dustin: To a recent pivot.

536
01:13:03.520 --> 01:13:06.369
Dustin: Like, it's not going to be efficient at that, because it is serial.

537
01:13:07.150 --> 01:13:25.700
Dustin: And especially if you're talking about, anything where it has no way to direct the EL to, like, get the state, like what SnapSync can do, and then efficiently build on that, especially as we're going into a sort of, I guess, are we still calling it 4-4s? But the sort of, expiry.

538
01:13:25.700 --> 01:13:31.769
Dustin: history expiry world where the whole history won't even be available.

539
01:13:31.960 --> 01:13:35.900
Dustin: Right? So indeed, that it's it's complementary to that.

540
01:13:36.780 --> 01:13:45.599
Dustin: Right? It it is not the point is not to replace, you know, you're going from Genesis block by block by block by block. That would be generally absurd.

541
01:13:47.910 --> 01:13:58.299
Łukasz Rozmej: Yes, but even if we have a relatively small gap, we, currently, and I don't know, have to think, let's say…

542
01:13:58.630 --> 01:14:10.650
Łukasz Rozmej: thousand blocks. We do it very aggressively, in parallel onto multiple peers, and… you know, we spread the load, etc, and get that in.

543
01:14:10.730 --> 01:14:20.070
Łukasz Rozmej: resolved in a matter of seconds, literally, if you have the bandwidth and CPU, and now we will have to wait for someone to feed those, and…

544
01:14:20.270 --> 01:14:21.900
Łukasz Rozmej: It's out of our control.

545
01:14:24.440 --> 01:14:39.229
Dustin: Well, it doesn't require the EL this is it does not require the EL not to do this. Right? The nothing about this EIP requires the only the only specific change that this EIP requires is this new endpoint.

546
01:14:39.920 --> 01:14:40.780
Dustin: That's it.

547
01:14:41.580 --> 01:14:44.169
Łukasz Rozmej: Okay, then it needs to be spaced.

548
01:14:45.040 --> 01:14:52.629
Łukasz Rozmej: yeah, specified, because this read for me like it was okay. Now you don't do anything, and you wait for us to feed you the data.

549
01:14:52.630 --> 01:15:01.050
Dustin: No, I, I see, I see, no, it, it is that, ok, so that is sketching out possible worlds, possible ways of

550
01:15:01.140 --> 01:15:15.419
Dustin: one could create an EL, and whether this is a good idea or not is a different question, and I… to your point about the efficiency and getting things in with, you know, enough peers in parallel and doing things in seconds, I understand that. But.

551
01:15:16.740 --> 01:15:35.430
Dustin: that is a… it basically, it creates the possibility of, for example, kind of the library EL, which can't really exist today, but that there's not… every existing EL or any EL which wants to use the existing, their own sort of sync mechanisms can absolutely continue to do so.

552
01:15:35.660 --> 01:15:46.599
Dustin: And if that's not clear in the EIP, I can certainly make that clearer. But yes, that's what… part of what I mean by optional with that, what we mean by optional, I guess, three authors.

553
01:15:49.110 --> 01:15:55.630
stokes: Okay. Let me jump in here. Yeah, Enrico, I wanted to hear from other SEAL teams just while we're here.

554
01:15:55.630 --> 01:16:15.670
Enrico Del Fante: Just one quick comment. So, this belief… this enables possible ways of thinking, and then there was another EIP that was taking a completely different direction, assuming that CL doesn't want to

555
01:16:15.690 --> 01:16:24.590
Enrico Del Fante: take care of anything about payloads, and want to fully, fully give up and let the EL do

556
01:16:24.620 --> 01:16:31.669
Enrico Del Fante: completely its own thinking. So there are two completely different approaches, and I get the fact that this

557
01:16:31.810 --> 01:16:45.909
Enrico Del Fante: DCIP could enable different approaches, but I believe that the end game is not having multiple possible scenarios. I believe that those two things need to be discussed.

558
01:16:46.090 --> 01:16:54.240
Enrico Del Fante: So, what… I believe in one of the, meetings that we had, somewhere.

559
01:16:54.400 --> 01:17:11.230
Enrico Del Fante: we discussed the fact… we need to think about what will be the end… the end deployment of CL and EL, which are… which will be the responsibility, and then when we… when we envision what we… what we want as an end game, then we…

560
01:17:11.230 --> 01:17:16.619
Enrico Del Fante: We decide to go in one direction or the other. Keep having both

561
01:17:17.020 --> 01:17:22.690
Enrico Del Fante: possible conditions, I believe, is just not addressing the issue.

562
01:17:22.950 --> 01:17:26.230
Enrico Del Fante: But we should actually be clear on.

563
01:17:26.360 --> 01:17:31.540
Enrico Del Fante: On the responsibility, on one side and on the other, and going in one direction.

564
01:17:43.490 --> 01:17:44.889
stokes: Any response to that, Dustin?

565
01:17:46.010 --> 01:18:03.100
Dustin: about, what, defining specific areas of responsibility and sort of making that… codifying that? I don't necessarily… I mean, at one level, you can see this EIP as moving that towards the CL side, if you'd like, but at the same time.

566
01:18:03.100 --> 01:18:14.279
Dustin: it is optional, and so I don't want to emphasize that too much in the sense of saying the ELs can still do everything per Lukasz's question before, etc, that

567
01:18:14.290 --> 01:18:24.209
Dustin: That they do today, but yeah, I mean, at some level, it envisions a world where it's kind of CL driven in that, in that sense, if you want to frame it that way.

568
01:18:24.730 --> 01:18:28.889
Dustin: But again, that is optional in that sense. And ELs can just ignore this.

569
01:18:29.360 --> 01:18:38.590
Enrico Del Fante: Yeah, it seems like we are spending time and effort doing something that, without Without taking the decisions on.

570
01:18:38.930 --> 01:18:45.140
Enrico Del Fante: what will be the end game. So in some sense we should do some planning first.

571
01:18:45.400 --> 01:18:48.809
Enrico Del Fante: And then… And then go in one direction.

572
01:18:52.870 --> 01:18:55.619
stokes: Would it help to take this to ACD next week?

573
01:18:56.090 --> 01:18:58.439
stokes: Or, I guess, whenever they can get to it.

574
01:19:05.390 --> 01:19:16.819
Dustin: I mean, I'm wondering, though, in terms of, like, the other thing was, it was DFI'd, so, I mean, One Direction was considered, and that was not taken.

575
01:19:17.310 --> 01:19:18.120
Dustin: So.

576
01:19:18.710 --> 01:19:19.490
Dustin: I mean…

577
01:19:21.260 --> 01:19:26.320
Enrico Del Fante: Which means DFI also this one, and take the argument one.

578
01:19:27.110 --> 01:19:30.860
Dustin: I… okay, I don't necessarily obviously agree with that.

579
01:19:30.860 --> 01:19:31.740
Enrico Del Fante: Nice.

580
01:19:31.740 --> 01:19:43.800
Dustin: or understand it. Well, no, but to say, like, I just say, oh, one thing on one topic is DFI, therefore all things on that topic must be DFI, I think is not sound reasoning, but.

581
01:19:44.030 --> 01:19:54.229
Dustin: Sure. In any case, I mean, I kind of addressed your question, though, about like, well, it does pick a side to some extent. It says that.

582
01:19:54.340 --> 01:19:56.740
Dustin: That it offers some.

583
01:19:56.910 --> 01:20:04.970
Dustin: Visibility in the process from ELs but I also don't necessarily buy your framing, honestly like the idea that we

584
01:20:05.220 --> 01:20:08.770
Dustin: Have to, like, pick a, like… yeah, I…

585
01:20:08.930 --> 01:20:13.509
Dustin: The way you're setting this up is not something I necessarily think is.

586
01:20:13.720 --> 01:20:14.840
Dustin: as.

587
01:20:14.840 --> 01:20:16.269
Enrico Del Fante: I mean, is…

588
01:20:16.270 --> 01:20:16.720
Dustin: wired?

589
01:20:16.720 --> 01:20:19.050
Enrico Del Fante: Network efficiency. So you need to.

590
01:20:19.050 --> 01:20:19.530
Dustin: Yes.

591
01:20:19.530 --> 01:20:28.789
Enrico Del Fante: One Direction, because you don't want to have always the duplication of things going on one.

592
01:20:28.790 --> 01:20:29.140
Dustin: Yes.

593
01:20:29.140 --> 01:20:40.099
Enrico Del Fante: And on the other. So, at some point, you need to take the decision, so you cannot maintain one approach, because the net… 90% of the network goes into another direction.

594
01:20:40.430 --> 01:20:51.340
Enrico Del Fante: So, it won't work. If we want to make an efficient and real deduplication, we need to take decisions.

595
01:20:53.160 --> 01:20:54.250
Dustin: Well, the…

596
01:20:56.320 --> 01:21:06.250
Dustin: Right now, the status quo is there's a certain amount of duplication, on the gossip side, and I'm putting aside sync, because as we've sort of discussed, like, sync is…

597
01:21:07.190 --> 01:21:15.639
Dustin: And storage. Yes. Yeah. Gossip and storage. But sync is is look. It's a separate issue. Snap sync, etcetera, we've got it is not gonna replace that.

598
01:21:15.640 --> 01:21:16.040
Walter Himmelsbach: and.

599
01:21:16.040 --> 01:21:21.279
Dustin: realistic world for the most part, fine. But for gossip and storage, yes.

600
01:21:21.320 --> 01:21:24.780
Dustin: And and so in that regard,

601
01:21:24.780 --> 01:21:43.119
Dustin: Right, the status quo today is we have that inefficiency, and this would allow tools on a node-by-node basis to opt in to reducing that inefficiency. And yes, the way they opt in to reducing that inefficiency, it would be by moving it practically from

602
01:21:43.250 --> 01:21:50.169
Dustin: toss it from the EL if they choose to do this. If the CL and EL are configured for that node pair to do this.

603
01:21:50.580 --> 01:22:05.270
Dustin: And so that enables a fairly safe, gradual transition towards that side, if that's what one wants to do. So that is, to the extent you're asking for, like, a side to be picked, it picks that… the CL side.

604
01:22:07.570 --> 01:22:13.419
stokes: Are there any other CL teams or, I mean, even EL teams here that wanna speak in support of the CIP?

605
01:22:24.970 --> 01:22:29.040
stokes: Because I'm not hearing a lot of support.

606
01:22:29.320 --> 01:22:31.479
stokes: There was a comment from…

607
01:22:31.880 --> 01:22:42.029
stokes: Part of us about essentially just, you know, we could have this we can move ahead with this as an optional thing where it's not necessarily scheduled for the hard fork, but, you know, if

608
01:22:42.290 --> 01:22:46.349
stokes: You know, a given pair of clients wants to implement this, then they can move forward.

609
01:22:47.250 --> 01:22:48.950
stokes: Francesco then came in.

610
01:22:50.820 --> 01:23:06.359
Francesco Risitano (Tau): Yeah, I'm just following on from the vision of having the EL kind of inside the CL as a, library. Would this method, still be required? Because one would assume that, the CL has

611
01:23:06.360 --> 01:23:14.590
Francesco Risitano (Tau): direct access to state, of the EL library, so to speak, and can, you know, simply query

612
01:23:14.590 --> 01:23:20.909
Francesco Risitano (Tau): the database or whatever storage mechanism, the CL is using.

613
01:23:21.070 --> 01:23:26.910
Francesco Risitano (Tau): So, does this still make sense in the, kind of, unified client world?

614
01:23:28.670 --> 01:23:40.079
Dustin: Full-on unified client, not quite as much, but it does allow for a standardized interface, which still has…

615
01:23:40.210 --> 01:23:55.780
Dustin: which still has significant value in a case where they are not literally the same thing. So they can communicate through, say, a local RPC, any number of options like that. And whether or not that ends up being the shape of

616
01:23:55.780 --> 01:24:08.960
Dustin: quote-unquote unified clients people end up wanting is actually not that clear to me. It's not been a well-explored space, let's say, but for certain parts of that design space, it still provides value.

617
01:24:16.540 --> 01:24:17.250
stokes: Karen?

618
01:24:20.230 --> 01:24:24.880
cayman: Yeah, just voicing some support for this EIP

619
01:24:25.080 --> 01:24:28.589
cayman: from, I think, from my perspective, it looks like a minor

620
01:24:29.050 --> 01:24:32.120
cayman: engine Api tweak that doesn't really mandate any

621
01:24:32.490 --> 01:24:36.070
cayman: Changing behavior of clients and unlock some flexibility.

622
01:24:36.400 --> 01:24:37.400
cayman: that…

623
01:24:37.700 --> 01:24:44.600
cayman: we want to. Some people want to explore. So I I say, let them cook if it's a small thing, but it's optional. So

624
01:24:44.840 --> 01:24:45.820
cayman: That's it.

625
01:24:51.790 --> 01:24:53.299
stokes: Mark, you have your hand up?

626
01:24:53.710 --> 01:25:04.269
ethDreamer (Mark): Yeah, I mean, I need to verify this, but if it is, especially if it is just engine API tweaks, we have, I want to point out that we have the Git capabilities.

627
01:25:04.430 --> 01:25:12.310
ethDreamer (Mark): Like… Endpoint, and so… We could potentially utilize that to even decouple this upgrade from a hard fork.

628
01:25:14.160 --> 01:25:29.849
Dustin: So… so the challenge with GET or exchange capabilities, or I believe it's what it's called, but GET capabilities, exchange capabilities, the, is that it's, it's a talk-to. It is simply not reliable over multiplexers. We know people use these.

629
01:25:30.100 --> 01:25:48.819
Dustin: Sometimes they use them without telling us. But the endpoints are not stable. The endpoint identities on the other end are not stable. So like an EL can get upgraded or downgraded. It can swap to another EL, which may or may not support the same set of things.

630
01:25:48.820 --> 01:25:50.460
Dustin: You end up having to get into.

631
01:25:50.940 --> 01:26:01.099
Dustin: Caching, you know, do you cache the answer? Does it get… do you try it optimistically? Etc. So, I mean, without getting into too much of the weeds there, the point is, like, the…

632
01:26:01.550 --> 01:26:10.060
Dustin: This capabilities discovery is not a great general purpose mechanism, and not something that's ideal to rely on.

633
01:26:13.790 --> 01:26:14.460
stokes: Okay.

634
01:26:14.930 --> 01:26:21.000
stokes: Thanks, everyone. I do think, yeah, we should go ahead and wrap up on this topic.

635
01:26:21.860 --> 01:26:30.650
stokes: again, I'm not hearing a ton of support, I think, from the people who are supporting this. They're very open to it being an optional thing that's outside of the hardcore cadence.

636
01:26:31.500 --> 01:26:38.079
stokes: So then, you know, with the frame of keeping the works, you know, as light as we can.

637
01:26:38.670 --> 01:26:45.640
stokes: this feels like a DFI today, but of course, if you want to move ahead with adding these engine API endpoints, you know, you definitely should.

638
01:26:46.520 --> 01:26:51.319
stokes: So, let's go ahead and DFI this with that understanding.

639
01:26:51.660 --> 01:26:52.859
stokes: Does that work for everyone?

640
01:27:05.400 --> 01:27:10.389
stokes: Okay. I'm not getting… any response, so I'll just go ahead and assume.

641
01:27:10.520 --> 01:27:12.230
stokes: That sounds good. So…

642
01:27:12.810 --> 01:27:21.539
stokes: Let's go ahead and say DFI this. Although, again, you know, if you wanna experiment with, you know, what this EIP would enable, you definitely can.

643
01:27:21.920 --> 01:27:23.390
stokes: Yeah.

644
01:27:24.690 --> 01:27:25.640
stokes: Okay.

645
01:27:26.110 --> 01:27:31.650
stokes: Then let's go to the next EIP. We just have a few minutes, so let's see what we can do here.

646
01:27:32.400 --> 01:27:35.339
stokes: The next one here is EIP-8383.

647
01:27:35.610 --> 01:27:37.940
stokes: Reduce CL block retention window.

648
01:27:38.700 --> 01:27:48.119
stokes: Let's see, I think this was… yeah, Kev, is Kev on the call? I think it would help if you could walk us through this a bit.

649
01:27:48.670 --> 01:27:52.709
stokes: I'm not sure clients have had time to get into this one too deeply.

650
01:27:55.820 --> 01:28:11.059
Kevaundray Wedderburn: Yes, I am here. I think there's been quite a lot of conversations with regard to the retention windows, even in Glamsterdam. If clients haven't looked into it, then I'm okay with skipping it until the next ACDC.

651
01:28:15.660 --> 01:28:16.200
Kevaundray Wedderburn: And then…

652
01:28:16.200 --> 01:28:21.039
Barnabas: Maybe we could just defer it for the next call and move on for the other EIPs.

653
01:28:21.040 --> 01:28:22.320
stokes: Yeah. Okay.

654
01:28:23.210 --> 01:28:27.829
stokes: Okay, but then can we agree to take a look for the next call?

655
01:28:28.630 --> 01:28:31.290
stokes: So, everyone, you have a little… little homework.

656
01:28:32.980 --> 01:28:35.090
stokes: But sure, I'll defer this for today.

657
01:28:36.450 --> 01:28:43.810
stokes: Okay, next one up, then, is optional execution proofs 8025, and…

658
01:28:44.490 --> 01:28:48.440
stokes: Let's see, we have Ignacio and then Francesco here.

659
01:28:48.900 --> 01:28:51.750
stokes: Would either of you like to say something about this?

660
01:28:54.900 --> 01:28:56.309
ignacio: Yeah, sure.

661
01:28:56.460 --> 01:29:03.689
ignacio: Well, we actually want to propose CFI in this.

662
01:29:03.990 --> 01:29:14.260
ignacio: I know I've been talking about with many people around this EIP, And I think the most,

663
01:29:14.740 --> 01:29:19.280
ignacio: Contentious thing is that it's an optional feature for the network.

664
01:29:19.610 --> 01:29:28.799
ignacio: I don't know, we will have time, within 6 minutes to fully discuss this, but… Instead of me shilling about.

665
01:29:28.930 --> 01:29:31.820
ignacio: DCIP, I would also prefer to

666
01:29:31.930 --> 01:29:42.570
ignacio: hear from CL clients what they think about it, or which are the angles of the proposal that they might have more concerns, and maybe that's more useful.

667
01:29:45.700 --> 01:29:52.829
stokes: Yeah, so we do only have a few minutes, but also, I think… Any other EIP?

668
01:29:53.440 --> 01:30:00.139
stokes: It's just gonna take a while. So we could start the conversation today if people want.

669
01:30:01.000 --> 01:30:06.180
stokes: But yeah, unless we can get to a decision in the next, yeah, 5 minutes, then we'll just defer this until next time.

670
01:30:06.580 --> 01:30:08.280
stokes: Then we'll pick up with the rest.

671
01:30:08.920 --> 01:30:10.030
stokes: On the next call.

672
01:30:10.630 --> 01:30:16.040
stokes: So, yeah, I guess any… any brief comments, for this, or…

673
01:30:19.390 --> 01:30:21.400
stokes: Lukasz, you can go ahead.

674
01:30:25.250 --> 01:30:35.210
Łukasz Rozmej: Okay, I have 2 problems with the CIP. So to give a bit more context, I love the idea of execution proofs.

675
01:30:35.250 --> 01:30:53.879
Łukasz Rozmej: I am working on a Nethermind guest client that would support creating execution proofs in zkVMs. We already have support for 3 different zkVMs, and currently I'm optimizing it, so just to give you the context.

676
01:30:53.880 --> 01:31:01.399
Łukasz Rozmej: So, I love the whole concept, but I'm… I'm not sure if I can get behind, CFI-ing this.

677
01:31:01.420 --> 01:31:11.369
Łukasz Rozmej: with 2 to be major problems. One problem is that historically, when we ship something in in the fork, it's ready for productional use.

678
01:31:11.440 --> 01:31:29.140
Łukasz Rozmej: even if it's optional, this won't be actually secure enough due to, for example, gas repricing that will need to happen for this to actually be secure. So we'll ship something that we know that isn't secure enough, and that users shouldn't actually use it, so

679
01:31:29.140 --> 01:31:32.350
Łukasz Rozmej: I don't see the point of shipping it in the fork.

680
01:31:32.490 --> 01:31:46.679
Łukasz Rozmej: That's one thing, right? So, we are giving mixed signals to the community. Okay, we ship something, but it's not really production ready, so this is… this is wrong to me, this is not what's…

681
01:31:46.710 --> 01:31:50.329
Łukasz Rozmej: We should be putting into the the fork.

682
01:31:50.360 --> 01:32:10.139
Łukasz Rozmej: And second problem is that I think with the current solution, unless it's changed, the, pairs of guest programs and zkVMs are kind of chosen by committee. So historically, anyone could write.

683
01:32:10.250 --> 01:32:21.410
Łukasz Rozmej: protocol implementations of clients, and they could compete on their technical prowess, for example, security, stability, and technical prowess.

684
01:32:21.520 --> 01:32:38.060
Łukasz Rozmej: Here, there will be some decision made up front, and some clients and VM pairs will be embedded into protocol. Which, okay, they can change later, but this is a process, so this kind of.

685
01:32:38.380 --> 01:32:53.550
Łukasz Rozmej: breaks the current, like, culture of creating Ethereum software that I have a problem with. So those are my two problems with the EIP. And I love execution proofs, so…

686
01:32:53.700 --> 01:32:55.960
Łukasz Rozmej: Just, just, just saying that.

687
01:32:58.820 --> 01:33:03.970
stokes: Okay. Yeah. Ignacio, let's just take, your comments, and we'll wrap up.

688
01:33:04.120 --> 01:33:06.479
stokes: Yeah, just to be clear here.

689
01:33:06.600 --> 01:33:11.170
stokes: We will pick this one back up. We will not make a decision today. We just are at time.

690
01:33:12.200 --> 01:33:23.760
ignacio: Yeah, I just wanted to touch on Lukasz's comments. I think many of his concerns are more related to mandatory proofs than to EIP-8025, which is optional proofs.

691
01:33:23.890 --> 01:33:34.389
ignacio: EIP-8025 is not really committing to any kind of pairing of guest programs on zkVMs or enshrining any kind of proof system or anything like that.

692
01:33:34.630 --> 01:33:40.809
ignacio: It's mainly about defining the specs and upstreaming this work into.

693
01:33:41.540 --> 01:34:01.369
ignacio: a repository where we can settle a lot of work that we have done, that we know it is useful, and we can defer all this discussion about, okay, which guest programs, which zkVMs, and all that to mandatory proofs until we have more data, and we know what is safe.

694
01:34:01.380 --> 01:34:07.329
ignacio: The main idea for us, on why we think EIP-8025 is important to

695
01:34:07.550 --> 01:34:18.930
ignacio: to be included in the specs is that it will de-risk a lot of analysis on how zkVMs behave on other protocol changes, such as PVD.

696
01:34:19.070 --> 01:34:20.010
ignacio: Umm.

697
01:34:20.140 --> 01:34:29.209
ignacio: If we don't do this, we have to maintain, like, a zkVM branch on the specs, PVT branch on the specs, we have to mix both, and this is…

698
01:34:29.440 --> 01:34:34.109
ignacio: Increasingly inefficient, considering that we have limited resources also to work.

699
01:34:34.400 --> 01:34:36.890
ignacio: on many other important things for Ethereum.

700
01:34:37.040 --> 01:34:47.929
ignacio: So that's kind of a short answer to these points, but I'm happy to keep talking about this in the next call, if needed.

701
01:34:47.930 --> 01:34:54.369
Łukasz Rozmej: So would you consider this an informational EIP? Basically, it's defining the spec, but not shipping anything.

702
01:34:55.830 --> 01:34:58.920
ignacio: Well, I already know if information on the EIPs means that

703
01:34:59.140 --> 01:35:03.830
ignacio: will get merged into these specs. Maybe I'm not…

704
01:35:03.970 --> 01:35:08.229
ignacio: Fully aware how precise the process is on this front.

705
01:35:10.270 --> 01:35:16.299
stokes: Just to jump in here, we are at time. Are we okay just to hold this conversation until the next call?

706
01:35:20.200 --> 01:35:21.070
stokes: Okay.

707
01:35:21.660 --> 01:35:35.259
stokes: Okay. Lots of thumbs up. Okay. Cool. Then, yeah, thanks, everyone. We'll keep working through these EIPs on the Hegota scope, next time. And, yeah, again.

708
01:35:35.390 --> 01:35:40.399
stokes: Let's all keep an eye on Sepolia. The fork will happen in just a few days.

709
01:35:40.580 --> 01:35:45.140
stokes: So… Happy forking, and I'll see you next time. Thank you.

710
01:35:46.180 --> 01:35:47.070
potuz: Bye-bye.

711
01:35:49.750 --> 01:35:50.460
Barnabas: Okay.

