All Core Devs - Testing (ACDT) #55, Sep 29, 2025

[danceratopz]

UTC Date & Time

September 29, 2025, 14:00 UTC

Agenda

Fusaka

• Devnet 3 update (will continue running throughout the testnet upgrades), dora.fusaka-devnet-3.ethpandaops.io.
• Fusaka Testnet Announcement on blog.ethereum.org.
• Fusaka & BPOs testnet schedule:
  • .ics calendar to import via URL in your calendar.
  • activation schedule in meta EIP (now also included in the Protocol Calendar).
  • First activations:
    • Holešky Fusaka: This Wednesday, 2025-10-01 08:48:00.
    • Holešky BPO1: Following Tuesday, 2025-10-07 01:20:00.
    • Holešky BPO2: Monday, 2025-10-13 21:10:24.
    • Sepolia Fusaka: Tuesday, 2025-10-14 07:36:00.
• Status of client testnet releases.
• EEST v5.2.0 release predominantly only updates the exception messages in client exception mappers.
• EEST v5.3.0 is pending, which will update the blobSchedule params used in the fixtures to match the params used in the testnets.
• STEEL testnet verification efforts:
  • Will verify client testnet configuration via execute config pre-launch.
  • Live Fusaka Testnet EEST Test Execution via execute as performed for Prague Mainnet.
    • Currently WIP: Defining a representative subset of tests to execute.
• Shadowfork discussion(?)
• Sherlock Fusaka Audit contest still ongoing: Started Sept 15th for 4 weeks.

Gas limit testing update

• Mainnet 60M gas limit target in Fusaka releases 📈
• Latest proposal for ./tests/benchmarks/ dir structure in EEST.

Compute-intensive benchmarks

• There is a new EEST test format benchmark_test that abstracts the tx gas limit cap for easier test implementation. There is still some ongoing work here.

State-intense benchmarks

• @jochem-brouwer would like to bring up benchmark tests using mainnet state snapshots:
  • Questions for client teams:
    • What triggers worst-case behavior in state-intensive updates?
    • E.g., in the XEN contracts: Updating existing storage slots, writing new slots, or deleting storage keys?
  • Questions about other known pathalogical cases on mainnet:
    • Does anyone have an overview of the biggest storage tries on mainnet?
    • Are there other exotic contracts on mainnet that mark multiple state trie nodes as dirty, which means they have to be updated before the state root calculation?

Glamsterdam Testing Updates

• New consenus-specs release last Thurs: v1.6.0-beta.0.

BALers be BALing:

• @raxhvl update on the state of BAL testing.
• bal-devnet-0 timeline: https://notes.ethereum.org/@ethpandaops/bal-devnet-0

eBPS:

• epbs-devnet-0 (targeting end of Oct 2025): https://notes.ethereum.org/@ethpandaops/epbs-devnet-0

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)

mario.vega@ethereum.org, danceratopz@ethereum.org

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

[jochem-brouwer]

I want to touch on the highly evolving efforts to run tests dedicated to the state - e.g. running tests against XEN on a recent mainnet snapshot - and to ask clients where they think their worst case behavior is (so we can write tests for this). For instance: updating existing slots in XEN, writing new slots to XEN, or deleting storage keys in XEN.
Or: other more "exotic" tests like not targeting XEN only, but also the other big contracts on Mainnet (in the same block, possibly marking more state trie nodes as "dirty" which thus have to be updated before we can do the state root calculation).
Does someone have a recent overview of the biggest storage tries on mainnet?

[danceratopz]

I want to touch on the highly evolving efforts to run tests dedicated to the state - e.g. running tests against XEN on a recent mainnet snapshot - ...

Thanks @jochem-brouwer, added to the agenda!

[raxhvl]

I would like to give a 5-min update on the state of BAL testing.

[danceratopz]

I would like to give a 5-min update on the state of BAL testing.

Added to the agenda @raxhvl 👍

[akashkshirsagar31]

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