Parithosh Jayanthi:Okay, let's start off then. The first topic on the agenda is Fusaka. Barnabas, do you want to give us updates on forks slash BPOs that happened the last week?
Transcript
Barnabas:Sure. We went through Sepolia hard fork last week, and the first BPO is scheduled for tomorrow in…
Barnabas:A few hours.
Barnabas:BP01 will, increase the target to 10, and max to 15 blobs on Sapori as well.
Barnabas:And then the next BPO will be a week from now, on the 28th of October, and on the same day, later on, we're gonna have the hoodie, hard fork as well.
Parithosh Jayanthi:And were there any… were there any bugs to discuss from Sepolia's fork?
Barnabas:No, the only issue that we had is a few operators forget to update their node, but other than that, we didn't discover any bugs.
Parithosh Jayanthi:Perfect. Are there any bugs or issues that client teams are tracking that they want to bring up?
Parithosh Jayanthi:Okay, that's good in that case. I know that the Ethereum Foundation blog has a new post.
Parithosh Jayanthi:Especially for, the consumers of blobs, regarding what, changes when you… for example, you need to compute proofs now before you submit your transactions.
Parithosh Jayanthi:There will be another blog post coming out as well that will detail the transaction cap limit. So we have a 16 million transaction cap limit that goes live with Osaka, and there's a couple of considerations for people who are using transactions. For example, if you have a cold store with pre-signed transactions.
Parithosh Jayanthi:You might need to make sure that the…
Parithosh Jayanthi:upgrade doesn't break anything for you. So we're gonna have this, released soonish, and yeah, just please keep an eye out for that. And if there's any other UX or RPC-related, issues that
Parithosh Jayanthi:users of blobs have realized, were enabled after Fusaka on Sepolia, then please reach out to us, and we start tracking and fixing those issues before we end that.
Parithosh Jayanthi:Okay, anything else regarding the fork updates? Are there any client releases that are scheduled for, Hoodie? Or are we good to go with the existing releases?
pawan:I think we are going to release, a newer new RC, maybe tomorrow?
pawan:yeah, that's it for us.
pawan:It has a few bug fixes, and
pawan:We are also trying to get in the semi-super node mode for it, but, yeah.
pawan:No promises on this semi-super node one, but, like, we needed to get a few bug fixes out.
Parithosh Jayanthi:Okay, perfect. If you want us to deploy the release anywhere before it goes out, then please let us know.
Parithosh Jayanthi:Andrew?
Andrew Ashikhmin:Yeah, so we had an issue with Aragon producing invalid blocks on Hoodie, and that was fixed in our latest release, 3.2.1. It was released today, so that is the recommendation for Hudi.
Barnabas:May I ask, why was it only producing in, like, blocks in Hudi and nowhere else?
Andrew Ashikhmin:I think, it actually happened, when, a transaction
Andrew Ashikhmin:Depended on the beacon route, maybe on other chains, there were no such transactions.
Parithosh Jayanthi:Well, could we maybe discuss more details on our shared chat? We'd probably want to have this as a codified test somewhere as well.
Andrew Ashikhmin:Yeah, so we wrote about it on the Steel Discord.
Parithosh Jayanthi:Okay, perfect, then it should be tracked.
Parithosh Jayanthi:Awesome.
Parithosh Jayanthi:Thank you. Lucas?
Łukasz Rozmej:Not that mine had a release today, but it's optional for Hudi, nothing required.
Parithosh Jayanthi:Okay, perfect.
Parithosh Jayanthi:We'd probably be doing an update of the blog in that case, but we'll batch both the Lighthouse as well as Aragon and Netherland issues. And yeah, it seems like there's an optional release of GET as well, so seems like a round of updates for releases are in order.
Marius van der Wijden:Yes. So, one thing about that release, it, our release on the gas team, it enables, the conversion for blobs on send raw transactions.
Marius van der Wijden:So, for those L2s that are still,
Marius van der Wijden:That are still sending the wrong transactions.
Marius van der Wijden:Just… they can either…
Marius van der Wijden:fix their code, which is preferable, or they can use a version of Geth, like, like with a new release that will convert those.
Parithosh Jayanthi:And will Gets do this by default, or is this a new flag that needs to be enabled?
Marius van der Wijden:This will be done by default.
Marius van der Wijden:And it's also… there's no flag for it, so… Yes.
Marius van der Wijden:it, it puts… additional strain on the… on the… on the RPC providers.
Marius van der Wijden:So that is something that RPC providers may want to look out for in the future, is that they…
Marius van der Wijden:They themselves, reject non… Cell-approved transactions in the future.
Parithosh Jayanthi:And does this mean GET would do this indefinitely, or for, let's say, the next 100 epochs or something after the fork?
Marius van der Wijden:Probably, like, the next one or two releases.
Marius van der Wijden:After the fork.
Parithosh Jayanthi:Okay, thank you.
Parithosh Jayanthi:Cool, okay, Bezu has, an optional release as well.
Parithosh Jayanthi:And to Mehdi's point, Hoodie should already be at 60 million, if I'm not wrong.
Mehdi Aouadi:Okay, cool. Then, we will also have a new release for Teku. We were hesitating if we had to reverse the 60 million guests or not, so yeah.
Parithosh Jayanthi:Nope.
Parithosh Jayanthi:Yeah, Hoodie's already at 60 million, so we should be.
Mehdi Aouadi:Okay, perfect. So, we will have a release, pretty soon in the next coming, days, probably.
Mehdi Aouadi:With some, yeah, with some fixes.
Parithosh Jayanthi:Perfect. Thank you.
Parithosh Jayanthi:Any other Fusapa topics?
Barnabas:Maybe not Fusaka, but, Hosky,
Barnabas:POSCI is going to be shut off by the end of this month, which is basically next week, Friday. I started to see some operators already shutting off their node now, so if you know anyone that is running any infrastructure on POSCII, please let them know to migrate as soon as possible away from it.
Barnabas:Because I would expect non-finality on Hosky by probably the end of this week, if latest by end of next week.
Parithosh Jayanthi:Yeah, I think there's at least a few providers who are also just, like, they'll have their infra up until this billing cycle, and then they're gonna not renew their infrastructure, so…
Parithosh Jayanthi:Yeah, please expect Polsky to not necessarily be a control shutdown that will happen at a specific epoch, but a gradual degradation.
Barnabas:Ideally, I think we should also put out a blog post regarding this to remind everyone.
Parithosh Jayanthi:Yeah, maybe we can work on that this week.
Parithosh Jayanthi:Marchin, you had a update for ModX pricing, do you want to go? I guess I was… that is semi-related to Fusaka?
Łukasz Rozmej:I'm not sure if you're talking to Martin, I think Martin is absent.
Łukasz Rozmej:But…
Łukasz Rozmej:We were doing… never mind, we were doing investigation into, does, Fusaka changes, and especially Modex pre-pricing, make any existing transactions fail? Does it… is it problematic for the users?
Łukasz Rozmej:We scanned 100,000 blocks, And found some issues with user operations, with account obstruction, but,
Łukasz Rozmej:Upon further investigation, we think that, you know, they would just be repriced in the, after Fusaka and priced correctly, so no major issues found.
Parithosh Jayanthi:Yeah, Marek?
marek:Yeah, let me chime in a little bit here, because, our approach is to increase the gas limit for the transaction, and the problem is that you cannot do this with the patterns like you have in account abstraction user operations, when you bundled many transactions.
marek:And, those user operations has their own gas limit, so we cannot trace it correctly. And I think it will be relevant for Carl, because I know that he's doing some exploration for gas pricing in general.
marek:how to… how to test those things. Yeah, so only issues that we detect are related to this user operations, so far, with this amount of blocks.
Parithosh Jayanthi:Okay, thank you. Are there any follow-up questions or discussion points?
Parithosh Jayanthi:Okay.
Parithosh Jayanthi:Last call for Fusaka. Is there anything else to discuss on Fusaka?
Parithosh Jayanthi:Okay, cool. Then we'll move on to gas limit and PUFNet updates. I can start with, I guess, Puff DevNet 2.
Parithosh Jayanthi:End of last week, there was a bit of forking. There was Carlos from the Nethermine team who was looking into it, and some of the nodes are healthy now. There is still a Nethermine node that's unhealthy.
Parithosh Jayanthi:And we synced up a new node to start allowing us to switch the network ID, and make sure that the network doesn't immediately break.
Parithosh Jayanthi:But we didn't want to do this while the network was still unhealthy, so I guess once the Nethermine node is fixed fully, then we'll start rolling this out. I also know that, there's someone from Eragon who wants to run a few tests on PostDevNet2,
Parithosh Jayanthi:But is there… are there any other, state testing updates or gas limit updates that people want to share?
Parithosh Jayanthi:Okay, then keep an eye out for…
Parithosh Jayanthi:For some updates on both DevNet, too.
Parithosh Jayanthi:Let's move on to block-level access lists, then. Stefan, do you have an update on that?
Stefan Starflinger:So far, we're…
Stefan Starflinger:pretty good progress with Bezo and Geth. They're working pretty well. And in my tests, NetherMind seems also very close, so I think we should be very close to a definite zero with Bezo, Geth, and NetherMind. And we're gonna start setting it up this week.
Stefan Starflinger:So far.
Stefan Starflinger:And otherwise, for, like, other, spec changes, like FOSSO, it would be nice to know what the status is and EPBS. That would also be nice, if the clients have some updates on those.
Parithosh Jayanthi:Yeah, but before we move there, I just wanted to quickly ask Tony or someone from his team if they also have any
Parithosh Jayanthi:Block-level access list-related changes we should keep an eye out for before we launch the DevNet.
Toni Wahrstätter:Nothing really in particular. So, we will have a block of access list breakout call on Wednesday, and we will discuss, Coinbase handling, so how we will treat, the Coinbase address. There are some
Toni Wahrstätter:Interesting edge cases around that, but nothing we didn't already, have in the specs or in the tests.
Parithosh Jayanthi:So, awesome. So, even if there's a breaking change, I guess that can belong to DevNet1 instead of DevNet 0.
Toni Wahrstätter:Right, yeah. But there, I wouldn't expect the breaking change there.
Parithosh Jayanthi:Okay, perfect. In case anyone wants to help, I think one of the bigger topics right now is how to best visualize the block-level access list.
Parithosh Jayanthi:Especially in DORA, and to make it simpler for debugging, so… Yeah, we're gonna be shipping some things, and if you don't like it, then tell us what we can improve to…
Parithosh Jayanthi:Make it easier to debug.
Parithosh Jayanthi:Good.
Toni Wahrstätter:Laura, we have already something.
Toni Wahrstätter:So, there is already a tab in the Explorer, in DORA, where we can see the entries of the block web accesses. Something we, still have to, do is the metrics. So, Katya was introducing that.
Toni Wahrstätter:So feel free and look into the block of Access List Discord.
Toni Wahrstätter:This is something that is still open.
Parithosh Jayanthi:Okay.
Parithosh Jayanthi:Anything from the EPBS crowd? Do we have anyone to give us an update?
Justin Traglia:I guess I can start.
Justin Traglia:What did I say? We have an upcoming breakout call this Friday. I just posted the agenda. Please comment if there's anything you'd like to bring up.
Justin Traglia:Last week at ACDC, we did decide to keep the,
Justin Traglia:like, trusted, trustless payments thing, as is. So, like, what the spec currently is.
Justin Traglia:And, I guess I don't know much else. Maybe client teams can give an update on their implementations for DevNet Zero?
Parithosh Jayanthi:Yeah, Justin, is there a spec that we can tag in the, DevNet spec sheet?
Justin Traglia:Yeah, the Beta 0, spec is for DevNet 0.
Justin Traglia:We do plan on releasing a new Beta 1, release probably sometime this week, but we're not gonna update the…
Justin Traglia:spec version for DevNet Zero.
Barnabas:But this spec is pretty much, as is, and you don't expect much changes anymore, right?
Justin Traglia:I can't answer that.
Justin Traglia:I mean, I'm sure the spec is gonna change from now, between, over the next few months.
Justin Traglia:But yeah, I mean, it's in a good spot for DevNet.
Parithosh Jayanthi:Yeah, I think the last update we got was it'll still take a few weeks to get the implementations out, but if any client has something ready and wants us to start testing early, then please reach out.
Parithosh Jayanthi:The next topic on the list was RPC updates. I see that Lukash and a few others have been engaging on the, on the JSON RPC API.
Parithosh Jayanthi:chat on, R&B Discord. Do you guys want to give us a summary? What's the biggest topic being discussed right now?
marek:If not, who cares?
Łukasz Rozmej:I can say, sorry. Don't think that much, so there was some discussion if, for example, should we parse very strictly or more loosely? I'm leaning to more loosely, but
Łukasz Rozmej:Felix was trying to convince me that we should go more strictly,
Łukasz Rozmej:So overall, we adjusted our implementation a lot, and for example, for this, we will be parsing strictly by default, but have a flag to parse loosely if, like, some client really want it, some of our users really want it. And I think we, like, we and Bezu and Aragon and,
Łukasz Rozmej:Ref,
Łukasz Rozmej:increased compatibility a lot with Hive tests, RPC Compat and not only, so I think that's really…
Łukasz Rozmej:Good progress here, something is moving.
Łukasz Rozmej:Marek, do you want to add something?
marek:No, no, you covered it well.
Parithosh Jayanthi:Awesome. Thank you for the update, and also, just as a reminder, we have a weekly, bot that will post how RPC Compact is doing.
Parithosh Jayanthi:And I think there's at least two clients with positive improvements this week, and never mind with passing 13% more tests than last week, so this is definitely a good direction.
Parithosh Jayanthi:So yeah, thank you for that.
Parithosh Jayanthi:Anything else for the RPC slash RPC compatibility, discussion?
Parithosh Jayanthi:Okay, the next topic on the agenda was that we're modifying a bit of our comms approach from both the testing teams.
Parithosh Jayanthi:So, we have the, Steel Discord server, and if you're a client dev, you should have gotten an invitation to the server.
Parithosh Jayanthi:The PandaOps team traditionally had a lot of disparaging chats, like, they were all over the place, some were on Discord, some were on Telegram, some on MetaMost, and instead of having them all over the place, we decided with the testing team that, we would have one channel per
Parithosh Jayanthi:client team, and one channel that both Steel as well as the PandaOps team would share with you.
Parithosh Jayanthi:And this is the channel that we would use for all future communications, for debugging, etc. And if you haven't gotten an invitation, if you're unaware of this, then please let us know. But this should allow us to streamline comms a bit more, also between the two testing teams itself, so that we know what's going on, and if either one of us has to update tests.
Parithosh Jayanthi:That was just a brief update on our side, and, yeah, I guess we're mostly done with the agenda. Is there any open topic people would like to discuss today?
Parithosh Jayanthi:If not, we'd be ending early.
Parithosh Jayanthi:Okay, then thank you everyone for coming, and see you at the…
Parithosh Jayanthi:Sorry, I'll see you at the next book.
Parithosh Jayanthi:Bye-bye.
Manu:Thank you.
Marius van der Wijden:B-bang.
Antoine James:Thanks, everyone.
Andrew Ashikhmin:Thank you.
marek:Bye.
Justin Traglia:run.
Chat Logs
00:06:39
James He:We have a new release coming for prysm to fix blob endpoint on mainnet
00:06:48
Parithosh Jayanthi:https://blog.ethereum.org/2025/10/15/fusaka-blob-update
00:08:43
Andrew Ashikhmin:Freshly released Erigon 3.2.1 is recommended for Hoodi
00:09:40
jochem-brouwer:This sounds like a test case we should add to EEST
00:10:12
Marius van der Wijden:We also had an optional release of geth
00:12:02
Ameziane Hamlat:Besu also has an optional release https://github.com/hyperledger/besu/releases/tag/25.10.0
00:12:05
Mehdi Aouadi:Are we enabling 60M gas on Hoodi?
00:14:25
Parithosh Jayanthi:https://github.com/ethereum/pm/issues/1769#issuecomment-3421983277
00:18:53
draganrakita:We have passed all bal blockchain tests, will have it in branch soon(tm)
00:19:43
draganrakita:Is this site, up to date: https://pokebal.raxhvl.com/ ?
00:20:19
Barnabas:its using bal-devnet-0 branch
00:20:22
Barnabas:yes
00:20:22
raxhvl:Yes.
00:20:27
Justin Traglia:https://github.com/ethereum/pm/issues/1759
00:21:01
Barnabas:@Justin Traglia is the spec now done?
00:23:27
marek:Nethermind rpc combat 165/190 now 🙂 only 25 left
00:24:49
Barnabas:If you are a client dev and haven’t got an invite please let us know.
00:25:27
Barnabas:unless you just don’t wanna talk to us
00:25:45
Parithosh Jayanthi:We have memes
00:25:59
nixo:byebye
Summary
17 highlights
· 2 decisions · 4 action itemsExperimental
Summary
17 highlights · 2 decisions · 4 action itemsExperimentalfork status
documentation
client updates
- Prysm releasing new RC with bug fixes for Holesky00:08:08
- Erigon 3.2.1 released - fixes invalid block production on Holesky00:08:44
- Geth adding automatic blob transaction conversion for L2s still using old format00:10:24
- Besu and Teku have optional releases available00:12:04
- Holesky already running at 60M gas limit00:12:15
critical infrastructure
testing progress
organizational
- All testing communication consolidating to Steel Discord server - one channel per client team00:24:23
Decisions
Action Items
- EF: Release blog post about transaction cap limit and pre-signed transaction considerations00:07:41
- EF: Update blog with Lighthouse, Erigon, and other client releases00:10:20
- Parithosh and Barnabas: Work on blog post reminder about Holesky shutdown00:13:50
- Client teams: Reach out to pandaOps if ePBS implementations are ready for early testing00:22:02