EIP-7732 Breakout Room Call #26, October 24, 2025

[jtraglia]

UTC Date & Time

October 24, 2025, 14:00 UTC

Agenda

Specifications & testing

New consensus specifications: v1.6.0-beta.1

• eip7732: add tests for process_withdrawals block processing
• eip7732: add fork choice tests (part1)
• Add payload_status field to AttestationData
• eip7732: add slot field to DataColumnSidecar
• eip7732: fix zero-amount builder withdrawals
• eip7732: swap beacon_block_root and slot in places in DataColumnSidecar
• eip7732: set default value of BuilderPendingPayment.withdrawable_epoch to FAR_FUTURE_EPOCH
• eip7732: deal with zero value bids correctly
• eip7732: use bid in block parent validation
• eip7732: fix signed envelope yields for execution payload tests
• Clean up Gloas specs (part 1)
• Clean up Gloas specs (part 2)
• Clean up Gloas specs (part 3)
• TODO: Remove merkle proof tests in Gloas (reference)
• TODO: Add pending payment withdrawal epoch asserts (reference)

Implementation updates from client teams

• Prysm
• Lighthouse
• Teku
• Nimbus
• Lodestar
• Grandine

Proposed changes to AttestationData

There is a proposal to add a "payload status" field to AttestationData:

• Add payload_status field to AttestationData consensus-specs#4655

Overview from previous breakout call:

• EIP-7732 Breakout Room Call #25, October 10, 2025 #1744 (comment)

Discord thread:

• https://discord.com/channels/595666850260713488/1427220882811523157

Call Series

EIP-7732 Breakout Room

🔧 Meeting Configuration

Duration

60 minutes

Occurrence Rate

bi-weekly

Use Custom Meeting Link (Optional)

• I will provide my own meeting link

Facilitator Emails (Optional)

jtraglia@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

[potuz]

I'd like to discuss the issue of changing the attestation data that seems to be supported by @eserilev and @mehdi-aouadi

[akashkshirsagar31]

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

[ethDreamer]

The gossip conditions for BeaconBlocks have the following:

• [IGNORE] The block is not from a future slot (with a MAXIMUM_GOSSIP_CLOCK_DISPARITY allowance) -- i.e. validate that signed_beacon_block.message.slot <= current_slot (a client MAY queue future blocks for processing at the appropriate slot).
• [IGNORE] The block is from a slot greater than the latest finalized slot -- i.e. validate that signed_beacon_block.message.slot > compute_start_slot_at_epoch(store.finalized_checkpoint.epoch) (a client MAY choose to validate and store such blocks for additional purposes -- e.g. slashing detection, archive nodes, etc).

I'm wondering if we should add something analogous to the gossip conditions for payloads?