All Core Devs - Testing (ACDT) #39 | June 2 2025

Protocol Calls & happenings
,
2

ACD Testing Call #39 – June 02, 2025

Summary

  • Gas Limit Increase to 60M Accepted:
    Client teams aligned on raising the gas limit to 60 million. Any increase beyond 60M should be gradual.
  • Fusaka Devnet 0 Stable:
    All clients successfully tested BPOs. Devnet 0 is looking promising. Sync testing and tool integration (eth-das-guardian) are next.
  • Fusaka Devnet 1 Launch on June 9:
    Will include implementation of EIP-7917 and Validator Custody. PR #4190 needs review from all client teams.
  • Validator Custody in Progress:
    Most clients are implementing or finalizing custody features. Targeting readiness by Devnet 1. PR #4320 reviewed as canonical reference.
  • Metrics Inclusion Approved for Devnet 1:
    Both CL and EL side metrics will be added. A tracking repo for metric changes will be created.
  • Column Sidecar Improvements Coming:
    Custom implementation in Teku; plan to propose changes for wider client support via PR.
  • Next week’s ACDT (Interop) call is cancelled.

Quick Notes

Parithosh J lead the call.

Gas Limit Retrospective

Pari:

  • Hoodi gas limit: 60 million gas
  • Suggests slowly increasing limit in future.

Barnabas:

  • Should we move in two phases? (e.g., signal to 48M first, then 60M)

Kamil:

  • Decent percentage of validators already signaling 60M
  • 60M seems reasonable
  • Smaller incremental steps (e.g., 15–20M) are unlikely
  • 60M is a no-brainer

Barnabas:

  • Doubling gas limit is a significant change

Ben:

  • 60M seems fine
  • Above that, be more cautious

Justin F.:

  • 48M step seems unnecessary

Decision: Client teams are okay with a move to 60M. Future increases should be gradual.

Next Step:
Focus on max CL size this week.

Toni Wahrstätter:

If max CL size is 2.5 MiB, 65M gas may reach the 10min limit. 60M is safe.

Fusaka Devnet 0 Status

PeerDAS & Fusaka Devnet Updates by Will C.

Pari:

  • PeerDAS testing channel and PeerDAS Devnet 7 will be deprecated
  • Moving forward PeerDAS testing will happen on Fusaka testing stream
  • Fusaka Devnet 0 is the new focus
  • Communication moved to Fusaka Interop channel. Suggested to keep in thread.

Barnabas:

  • Fusaka Devnet 0 started out with Genesis.
  • Max blob cout at 9 on epoch 256.
  • Increased the max blob cout to 12 with the first BPO and at the second BPO, it is increased to 15 than to 18 and then went down to 9. Will be increased to up to 20.
  • All BPOs functioning well.
  • All clinet successfully upgrading and downgrading
  • No forks reported to BPO.

Pari: Devnet 0 is looking promising!

Note: ProbeLab team’s tool - eth-das-guardian is now open source.
will be integrated to testing stack. Clients Teams should check if their node is live.

Next Steps (Barnabas):

  • Repeat Sync testing planned to check if clients are able to backfill.
  • Building UI for integrating the new tool

PeerDAS Validator Custody Updates

Client’s update

Prysm (Manu):

  • Implemented validator custody
  • Backfill still in progress

Lighthouse (Pawan):

  • WIP, expected by end of week
  • Backfill not yet implemented
  • Tricky implementation wise, yet on track for interop

Nimbus (Agnish):

  • No backfill required at Nimbus
  • Validator custody can change within slot start

Francis:

  • Encourages everyone to review the PR Merged
  • Addresses concerns with backfill and custody changes

Justin:

  • PR was made to address frequent custody changes

Agnish:

For multi-Beacon Node setups, it’s better to act as a “super node”

Q&A:

  • Pawan: What endpoint does Prysm use to find attached validator node?
  • Manu: Beacon proposer from API
  • Kasey: Validator registration via Beacon API
  • Agnish: Could non-enforcement of custody lead to network partitioning?

Raul:

Some edge cases require deeper analysis – discussion to continue offline.

Next Step: Target validator custody for next week.
Barnabas: Will add PR to Devnet 0.

Fusaka Devnet 1 Plans

EIP-7917:

Client Updates for EIP-7917:

  • Justin: PR open, clients should review
  • Prysm: In progress
  • Lodestar (Phil): In progress

Decision: Devnet 1 will focus on:

  • Validator custody
  • EIP-7917 implementation

getBlobsV2 Metrics (EL Side)

Updates:

  • Besu (Gabriel): On track
  • Reth, Erigon, Nethermind: On track
  • Geth: Check async

BPO Networking Updates

Raul:

  • Adding a key to ENR to signal next upgrade
  • EIP incoming, tweaks expected
  • No network partition observed yet
  • May delay until Devnet 2

Justin T.:

  • Suggests keeping it for Devnet 2
  • It will allow time to add more tests in Devnet 2 for BPO

Other links

Metrics Implementation

CL side metrics
Katya:

  • Added metrics; potential spec change needed
  • Lodestar is testing
  • PR still in progress

EL side metrics
SunnySide (J):

  • Discord Reference
  • Reth, N/M, EthJS implemented original version
  • Awaiting EL feedback

Decision:
Include metrics changes in Devnet 1 and create a repo to track them.

SunnySide Labs Testing Update

Update – May 30, 2025

  • Ran 7 devnets
  • Blob count more stable
  • Focused on bottlenecks
  • LH: Up to 53 blobs per block
  • Prysm: Also high
  • Grandine: Failed beyond 10 blobs due to old image

Findings:

  • Grandine sometimes succeeded with retries
  • Column processing and gas combos might affect getBlobs
  • LH: Reported many column failures

Next Step:
J (Sunny side) will create thread on Interop channel for client by client analysis.

Column Sidecar

Dimitri:

  • Not available in Beacon API yet
  • Teku: Custom implementation exists

Pari:

  • Will propose PR to add this event

Meeting Scheduling Notes

  • Next week’s ACDT (Interop) call: Cancelled
2 Likes