Try   HackMD

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 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
  • Client teams meeting in interop.

Interop Testing Call #38 – May 26, 2025

Call led by: Mario Vega

Summary

  • Fusaka-devnet-0
    • Devnet-0 to be launched tomorrow with Fulu activation following the next day.
  • BPO & Config
    • BPO is live on devnet-0, but the final version of the EIP is still being discussed and will go live in devnet-1 or devnet-2.
    • Future devnets will align on genesis dates.
  • Devnet 1
    • EIP-7918 confirmed for inclusion.
  • CL Spec PR #4323
    • Mixed client feedback on usefulness.
    • Decision: Keep open; await further client input.
  • PeerDAS Testing
    • Decision: Use PeerDAS Devnet 7 for Electra → Fulu blob testing.
    • Malicious EL block tests planned to validate CL rejection behavior.
  1. History Expiry
    • No updates on rollout, testing, or documentation.

Fusaka-devnet-0 Status

Test Status

Mario

  • Latest EEST release includes Fusaka SFI EIPs.
  • Hive instance is running, but only Go-Ethereum is currently live.
  • Other clients should reach out to Pari or EthPandaOps for access.
  • Simulator not ready yet due to significant EEST changes; expected soon.

Parithosh

Barnabas

  • Devnet-0 to be launched tomorrow with Fulu activation following the next day..

Client Updates

  • Erigon (EL): WIP branch exists, not reviewed by Barnabas yet.
  • Nimbus (CL): Testing an image internally.
  • Lodestar & Lighthouse: No updates.

Devnet 0 – BPO & Config Discussion

Pawan

  • BPO EIP is available.

Pari

  • Live on devnet 0. Specs still in flux; final version may be included in Devnet 1 or 2.

ethDreamer (Mark)

  • Question on whether the BPO config includes blob schedule.

Barnabas

  • Yes, genesis includes blob schedule (but only Electra blobs, not Fulu).
  • Reference: config.yaml#L194
  • Future devnets will align on genesis date.

Devnet 1 Planning

SFI'd EIPs:

  • Includes EIP-7918
  • Could be slightly delayed to align with Interop in Berlin

Anders

Decision: EIP-7918 will be included in Devnet 1.

Demitri’s CL Specs – PR Discussion

Parithosh

Pawan (Lighthouse)

  • Not useful for LH currently, unsure if it helps bandwidth.

Gajinder (Lodestar)

  • Could reduce latency during multiple peer requests.
  • Not useful if most clients use gossip pools.
  • Favor of closing this PR

Manu (Prysm)

  • Doesn’t currently use it but plans to. Wants the PR merged for future readiness.

Decision: Wait for more client feedback before closing the PR.

PeerDAS Testing

Client Updates

Manu (Prysm)

  • Development is progressing well on PeerDAS testing.

Pawan (Lighthouse)

  • BPO implementation is still in progress for Devnet 0.
  • Merged a few synchronization-related fixes.
  • Resolved a bug with getblock; the fix has been merged.
  • Expected to be ready for the Fulu fork on Devnet 0.

Sunnyside Labs

  • Conducted PeerDAS testing last week: Test Report – May 20
  • Setup: 60 nodes with Execution Layer (EL) + Consensus Layer (CL).
  • Focus: Assess number of blobs that can be reached; current goal is to reach 72 blobs per block.

Observations

  • Bottlenecks identified in getblobs v2.
  • No significant performance difference observed between enabling and disabling getblobs.
  • Grandine was requesting blobs multiple times.
  • Grandine tested in standalone configuration.
  • Lighthouse and Prysm were performing better with or without getblobs enabled.
  • Further analysis and findings will be shared in the Discord channel.

Discussion & Troubleshooting

Pawan

  • Asked if fresh sync tests were done with current parameters.

Sunnyside

  • Yes, syncing was challenging:
    • Multiple nodes failed to start.
    • Required manual force-syncs and full network restarts.

Francesco

  • Asked about high CPU usage on supernodes.

Finding

  • High CPU usage was only observed on Lodestar supernode, not other clients.

Additional Testing Requests

Parithosh

  • Asked if any client teams had specific scenarios they want tested for PeerDAS.

Manu

  • Suggested testing:
    • Syncing in both finalizing and non-finalizing networks.
    • Running a few hours of blob transactions from Electra to Fulu.

Pari

  • Recommended using PeerDAS Devnet 7, which already contains Fulu.
  • Agreed on basic sync testing.

Manu

  • Confirmed Electra can be run on PeerDAS Devnet 7 for testing purposes.

Malicious Block Testing

Marius

  • Proposed creating an EL block with invalid/cell block transactions to ensure:
    • It gets correctly rejected by CL clients.

Pari

  • Acknowledged the need for a malicious block and that Marius can assist with its creation.

Pawan

  • Compared the testing with the rejection scenario to a deserialization failure over the Engine API.

EEST Testing Opportunity

Mario

  • Mentioned a new testing type in EEST that could support this use case.

Marius

  • Clarified that getblobs tests are different; this is focused more on consensus-level block validation.

Mario

  • Acknowledged the distinction.

History Expiry

No updates shared.

Interop Testing Call #37 – May 19, 2025

Facilitator: Parithosh Jayanthi

Summary

  • ModXP + BPO changes confirmed for Fusaka Devnet 0.
  • EL-only BPO hardfork agreed.
  • CL-side signaling discussion ongoing. Likely to avoid h/f.
  • PeerDAS testing and spec PRs progressing.
  • Perfnet v2 & Hoodi upgrades planned.

Next Steps:

  • Terence: Create Consensus Spec Issue
  • Pari: Update EIP for EL handling of BPO
  • Raúl: Finalize spec structure and open Consensus Dev thread
  • All clients: Prepare for Devnet 0 testing next week

Pectra Fork Retro

  • No issues reported post data collection.

Fusaka Devnet 0 Status

BPO Proposal (Marius)

  • Proposal includes scheduling explicit forks:
    • Example format: 
      ​​​​"bpo1": {
​​​​  "timestamp": 1747670415,
​​​​  "target": 9,
​​​​  "max": 12,
​​​​  "baseFeeUpdateFraction": 5007716
​​​​}
  • Treated as EL-only hardfork; CL remains unchanged.

Discussion Points:

  • CL teams prefer avoiding unnecessary fork boilerplate.
  • Marius: keep changes minimal, EL-only is cleaner.
  • Potuz: prefer handshake signaling if hardfork can be avoided.
  • Gajinder: handshake-only leaves room for inconsistent state.

Next Steps:

  • Consensus Spec Issue #4331 to be created by Terence.
  • EIP to be updated by Pari.
  • Raúl to lead long-term spec design and create a Consensus Dev channel thread.

Decision: Agreement reached for Fusaka Devnet 0 with ModXP + BPO changes.

PeerDAS Testing

Status:

  • Target release next week for ModXP and PeerDAS.
  • BPO tests to be run on Kurtosis (confirmed by Mario).

PeerDAS Spec Discussion

  • PR: beacon-APIs #524
  • Discussed local flag and validator-blinded block behavior.
  • Pari to reach out to maintainers for merge.

P2P Propagation Testing

Discussion between Potuz and Raúl (Zoom chat):

Builder Specs

  • Builder spec for Fusaka updated (Barnabas, Alex Stokes confirmed).

Devnet & Release Planning

  • Pari suggested, Devnet 0 completion will trigger team prep for release.
  • Perfnet v2 (mainnet-aligned) in progress – led by Kamil.

Hoodi Testing:

  • Plan to test 60M block size and attestation slashing.

Decision: Proceed with Hoodi block size test plan.

History Expiry

  • No new updates.
  • Portal client call scheduled post-meeting for interested teams.

Interop Testing Call #36 – May 12, 2025

Facilitator: Mario Vega

Topics: Pectra, Fusaka CFI, History Expiry

Next steps:

  • Fusaka Devnet 0
    • Launch Target: ~2 weeks
    • Devnet will include proposals:
  • History Expiry
    • History Expiry drop and Documentation (on Sepolia) target: June 1, 2025
  • Mario: Generally, the upgrade was smooth and uneventful.
  • Mikhail: eth1_data polling can be safely removed — smooth upgrade, great news!
  • James (Prysm): Still investigating performance issues.

Testing Fusaka

Updates:

  • Barnabas: PeerDAS Devnet 7 launched last week with 100% participation.
  • Will C:
    • Shipping Devnet 7 is the biggest one.
    • BPO blob schedule decision needed.
  • Justin T: Will decide in this call.
  • Will: Major components are documented; minor PRs remain open.

Next Step: BPO to be included in Fusaka Devnet 0.

Client Readiness:

  • Terence (Prysm): If Devnet 0 only includes BPO, Prysm will be ready in 1 week.
  • Som (Erigon): 2 weeks time requested.
  • Marcin (Nimbus) + Gajinder (EthJS): Ready whenever a date is set.
  • Barnabas proposed Target Launch Date: May 26, 2025 – Fusaka Devnet 0 with BPO.
  • Justin (Besu): Prefers Devnet 0 with BPO + PeerDAS only.

Additional Proposal Discussions for Devnet 0:

  • Som: Mentioned to include PAY opcode.
  • Mario: Suggests PAY be part of Devnet 1 due to complexity.
  • Tim: PAY / EIP-7212 / contract code size increase also being considered for Devnet 1.

Please contact Mario for any suggestions for Fusaka SFI Tracker

Francis Li: Suggested including EIP-9623 — originally an EIP, now part of PeerDAS spec.

Decision:

Launch Target: ~2 weeks
Fusaka Devnet 0 will include:

Introduce Blob Schedule

History Expiry

Status:

  • Barnabas:
    • Proposal: Start dropping history on Sepolia from June 1 (originally May 1).
  • Justin F. (Besu): Agrees with June 1.
  • Geth (Marius):
    • Code exists but not enabled.
    • Will produce documentation in two weeks.
  • Andrew (Erigon):
    • PR exists but not yet merged.
    • Won’t make June 1 release, documentation possibly within 2 months.
  • Reth: [No update provided]
  • Pari: All clients Will publish documentation and user guide when ready.

Decision:

Sepolia History Expiry Documentation target: June 1, 2025

🔗 Resources:

Interop Testing Call #35 - May 5, 2025

Facilitated by: Parithosh

Pectra Update

DevOps

Parithosh

  • Blogpost update.
  • 3 bug fixes released; no critical issues reported.
  • Flashbots infra improvement needed — team has been informed.

EEST

Mario

  • A few Hive tests failing — documented and reviewing edge cases.
  • Some scenarios seem unrealistic — will consult client teams.
  • Manual review completed across all client repos: Manual Review Notes.

Mainnet Shadow Fork

  • Deployed last week.
  • Sync issues on Erigon — now resolved.
  • Override flag bugs observed and patched.
  • Pectra features tested successfully.
  • Shadow fork now removed.

Latest EEST Release

  • First release includes all Ethereum tests.
  • Plan: migrate all tests to the unified execution-tests repo.
  • May affect CI pipelines, but no immediate action required.

Communication Channel for Pectra

  • Pectra Mainnet Plan document is added in PM repo.
  • A dedicated Pectra Upgrade channel will be created pre-fork and retired post-fork.
  • Each team to have a primary & backup contact monitoring Eth R&D Discord.
  • Mainnet Checklist
  • Lukasz suggested advance setup for emergency call link — Tim confirmed.

PeerDAS

Update by Barnabas

  • Devnet-7 expected to launch tomorrow.
  • Devnet-6 will be deprecated (except for Sunnyside labs which will stay for a bit but eventually deprecated).
  • Client teams to upload updated images.
  • PeerDAS discussions will move to ACDT after Pectra; PeerDAS calls end after tomorrow.

Gas Limit Testing

  • Jared: no current blockers.
  • Next step: decide testnet for gas limit testing in next week’s call.

History Expiry

  • May 1 deadline passed.
  • Documentation is lacking — clearer guidance needed.
  • Pari to follow up in the History Expiry channel.

Client Updates:

  • Nethermind (Kamil): Ready to support drop, will share docs.
  • Barnabas: Inquired about dropping by block height — confirmed possible.
  • Nethermind (Lukasz): Live pruning in PRs.
  • Suggestion to add history expiry info to release notes.
  • Need improved validator/user communication — plan for dedicated DevDocs page.
  • Reth & Geth: Work in progress.
  • Besu (Daniel): Still testing.
  • EF blog post planned once all clients releases are available.
  • Need to decide new "History Drop" activation target date.
  • Piper (History Expiry champion) should join next call.

Next Steps

Pectra Upgrade Monitoring
• Parithosh to set up and share a scheduled meeting link for monitoring during the Pectra upgrade. Set up and publicize the Pectra Upgrade Discord channel, including an emergency meeting link.

Testing & Devnets

  • Mario and the EEST team to assess and potentially add a new test for the EIP-7702 wording update.
  • Launch Devnet-7 for PeerDAS and deprecate Devnet-6.
  • Client teams to prepare and publish updated images for Devnet-7.
  • Confirm the testnet to be used for gas limit testing in next week’s meeting.

History Expiry

  • Parithosh to initiate discussion in the History Expiry channel to align on a new implementation plan and deadline.
  • Client teams to update release notes and clearly state their history expiry support status.
  • Create a dedicated documentation page to educate validators and users on History Expiry.
  • Schedule a follow-up with Piper Merriam for deeper coordination on rollout.

Communications
• Publish an Ethereum Foundation blog post to announce History Expiry once all client implementations are complete.

Interop Testing Call #34 and before

here

Last changed by 
 
poojaranjan
0
293
Published on HackMD