Skip to content

All Core Devs - Testing (ACDT) #71, February 23, 2026 #1932

Description

@marioevz

UTC Date & Time

February 23, 2026, 14:00 UTC

Agenda

Fusaka:

  • blob-devnet-0 updates
  • partial cells / getBlobv3 implementation update

Glamsterdam:

  • bal-devnet-2 updates
  • bal-devnet-3 readiness
    • EIP-8037 specs/tests status
  • epbs-devnet-0 implementation update
    • client readiness check
  • Adding testing_buildBlockV1 for future devnets (4+)
    • Client teams readiness

Gas limit:

  • TBD

State bloat:

  • perf-devnet-2 updates

Call Series

All Core Devs - Testing

Autopilot Mode

  • Use autopilot (recommended defaults for this call series)
🔧 Meeting Configuration

Duration

60 minutes

Occurrence Rate

weekly

Use Custom Meeting Link (Optional)

  • I will provide my own meeting link

Display Zoom Link in Calendar Invite (Optional)

  • Display Zoom link in invite

YouTube Livestream Link (Optional)

  • Create YouTube livestream link

Activity

  1. added
    ACDType: All Core Dev calls - execution & consensus
    on Feb 17, 2026
  2. github-actions commented on Feb 17, 2026

    @github-actions
    Contributor

    ⚡ Protocol Call Resources:

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

  3. parithosh commented on Feb 17, 2026

    @parithosh
    Member

    I'd like to bring up the inclusion of testing_buildBlockV1 (ethereum/execution-apis#747) for bal-devnet-4 onwards (so not the next devnet, but the one after). cc @MysticRyuujin

  4. marioevz commented on Feb 23, 2026

    @marioevz
    MemberAuthor

    @yperbasis via discord on Erigon status for devnet-2:

    We've finished our bal-devnet-2 implementation (kudos to Mark Holt) and pass all the tests more or less. We're working on a couple of remaining flaky tests and pesky races in parallelized execution.

  5. spencer-tb commented on Feb 23, 2026

    @spencer-tb

    I want to briefly bring up some issues we've been having with the EELS testing framework for 8037. The EIP adds a new paradigm at a high level on the framework: gas costs are now dependent on the block gas limit via cost per state byte. This impacts not only the framework but a lot of tests >600 files. We're working on a good framework solution for this but if we don't get there by ACDE we might want to consider making the cost_per_state_byte a fork constant, this massively reduces he complexity on the framework side, and will enable us to get tests out.

    Similary on 8037, how do we want to tackle tracing (originally brought up by SamWilsn). We have added stateGas and stateGasCost to the EELS tracer alongside gas and gasCost. Should we update EIP-3155 with this?

  6. MariusVanDerWijden commented on Feb 23, 2026

    @MariusVanDerWijden
    Member

    Making cost_per_state_byte a fork constant would kinda defeat the purpose of 8037 tbh.
    The whole idea is to be able to change the gas limit independent of hardforks, otherwise we could just go with fixed costs. Maybe a way forward would be to postpone 8037 to devnet-4 to give testing teams more time to update their framework with this new paradigm. But I do think we will use this paradigm more and more in the future, so it makes sense to spend some time to create a good solution for it

    I think we should update 3155 with the stateGas and stateGasCost.

  7. akashkshirsagar31 commented on Feb 23, 2026

    @akashkshirsagar31
  8. jtraglia commented on Feb 23, 2026

    @jtraglia
    Member
  9. bomanaps commented on Feb 23, 2026

    @bomanaps
    Contributor

    Just for more spotlight on this https://hackmd.io/@bomanaps/rJiHuPFOZl

  10. github-actions commented on Feb 24, 2026

    @github-actions
    Contributor

    This meeting occurred more than 24 hours ago. Closing automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ACDType: All Core Dev calls - execution & consensusprotocol-callAutomatically applied by issue template

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions