EIP-7928 Breakout #11, Jan 28, 2026

[nerolation]

UTC Date & Time

January 28, 2026, 14:00 UTC

Agenda

Date/Time: Wednesday, Jan 28, 2026 – 14:00 UTC
Location: Zoom, livestreamed on YouTube

Discussion:

• Devnet 1 & 2 Updates
  • Client updates on optimizations
• Specs update/clarification
  • Discuss how clients fail invalid blocks in a timely manner
  • engine: define EIP-7928 API methods execution-apis#727
  • Update EIP-7928: Further clarify access EIPs#11066
  • Add EIP-7928 Block-level Access Lists JSON RPC methods execution-apis#726
  • Standardize otel traces
    • EIP-7928 Breakout #11, Jan 28, 2026 #1897 (comment)
• Testing updates

Call Series

EIP-7928 Breakout Room

Autopilot Mode

• Use autopilot (recommended defaults for this call series)

🔧 Meeting Configuration

Duration

60 minutes

Occurrence Rate

bi-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

[github-actions]

⚡ Protocol Call Resources:

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

[qu0b]

I'm looking to see if we might be able to standardize otel traces for block level access lists. Feedback would be appreciated: https://notes.ethereum.org/@ethpandaops/bal-otel

[qu0b]

I've added a feature flag section to the spec https://notes.ethereum.org/@ethpandaops/bal-devnet-2#Client-feature-flags. So we can test optimizations such as batch / parallel io.

[akashkshirsagar31]

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

[github-actions]

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

[github-actions]

⚠️ Past Date Detected

The date/time you selected (2026-01-28T14:00:00Z) appears to be in the past.

No resources were created to avoid scheduling conflicts.

To fix this:

1. Click the "Edit" button on this issue
2. Update the "UTC Date & Time" field to a future date
3. Save your changes

The bot will automatically process your issue once the date is corrected.

💡 Tip: Double-check the year! Common mistake: using last year's date by accident.