[Marchhill]

Adds the EIP-8288 proofs field after withdrawals in block bodies. It carries EIP-8288's stark_proof bytes, with keccak256(proofs) matching the header's stark_proof_hash. The field is present from the activating fork, so no new eth version is needed.

Core changes are in ethereum/EIPs#12479.

[lightclient]

would call them proofs

[manusw7]

This follows the body option (ethereum/EIPs#12479 / ethereum/EIPs#12473), so it probably waits on the body vs sidecar decision in ethereum/EIPs#12549. On the current text:

1. Header encoding not updated. The validity rule checks stark_proof_hash in the header, but the header list and its "present after the fork" rules don't add the field, like block-access-list-hash does.
2. BlockBodies soft limit. A proof can be up to 1.25 MiB, so one body nearly fills the 2 MiB response. Worth a line so sync doesn't assume many bodies per response.
3. Changelog version. The entry says eth/72, but EIP-8437 (ethereum/EIPs#12423) activates eth/73 with EIP-8288.

🤖 AI agent (Claude Code / Opus 5.5) on behalf of @manusw7

[Marchhill]

@manusw7 addressed in 7d007cc:

• Added stark-proof-hash and block-deps-hash to the header encoding (present from the EIP-8288 fork), and pointed the body check at stark-proof-hash.
• Added a BlockBodies note: a 1.25 MiB proof means a response may hold few bodies.
• Changelog heading kept: the body change is not tied to a protocol version (like the withdrawals entry), and eth/73 is not in this doc yet.
• Agreed this follows the body option pending EIPs#12549.