All Core Devs - Testing (ACDT) #54, Sep 22, 2025

[barnabasbusa]

UTC Date & Time

September 22, 2025, 14:00 UTC

Agenda

• Devnet 3 update
• BPO analysis open discussion
• Scheduling fusaka & BPOs on testnets:
  • Holesky
  • Sepolia
  • Hoodi
• Shadowfork discussion
  • Mainnet osaka style BPO for nethermind config - feat: update osaka style blob schedule eth-clients/mainnet#10
• Gas limit testing update
• Glamsterdam testing updates
  • bal-devnet-0 timeline discussion
  • epbs-devnet-0 timeline discussion

Call Series

All Core Devs - Testing

🔧 Meeting Configuration

Duration

60 minutes

Occurrence Rate

weekly

Use Custom Meeting Link (Optional)

• I will provide my own meeting link

Facilitator Emails (Optional)

No response

Display Zoom Link in Calendar Invite (Optional)

• Display Zoom link in invite

YouTube Livestream Link (Optional)

• Create YouTube livestream link

[github-actions]

⚡ Protocol Call Resources:

✅ Zoom: Join Meeting
✅ Calendar: Add to Calendar
✅ Discourse: Discussion Topic
✅ YouTube Live: Watch Live

[siladu]

Besu devnet-5 issues report: https://hackmd.io/@siladu/rkePw-Rill

We have some issues we'd like to improve on for Mainnet, but don't see a reason to block the testnet release.
We are currently soaking a testnet-ready release so we expect to be ready for Thursday.

[jochem-brouwer]

Gas limit testing for I/O heavy operations such as a lot of storage writes against big storage trie contracts (e.g. XEN) which I want to test against 60M gas limit and 100M gas limit to see how "bad" these kind of contracts behave. If someone has a better idea for even worse scenarios, let me know! I think for these kind of scenarios we want to make as many trie nodes "dirty" (so the amount of trie nodes we have to edit in order to get the new state root), and I think that only targeting XEN is not the worst case here 🤔 This sounds like a rather general topic to me, if someone has already researched this please drop the URLs 😄 👍

Initial result on only 1 client, N=1, super-ideal circumstances do not look alarming ethereum/execution-spec-tests#2101 (comment). I am targeting next ACD-E this Thursday for an usable report on this which covers the 5 mainnet clients for the worst case scenarios I can come up with for XEN.

Request for Nethermind: I'd love to get access to the nethermindeth:nethermind:gp-hacked source code, because I need to edit the timestamp of the payload such that I can also run other scenarios which need updated timestamps. See also here (discord).

[akashkshirsagar31]

X Stream: https://x.com/i/broadcasts/1BdGYZLWpNoJX