Ethereum researchers found that EIP-8411’s segmented broadcasting design reduced median propagation of a simulated 1 MiB execution payload from roughly five seconds to about 0.73 seconds in the least-favorable tested setting, with related prototype reporting at about 0.75 seconds and the slower end near one second. The proposal divides execution payloads into 64 independently verifiable segments, each linked through a Merkle proof to a root included in the builder’s bid. Nodes can validate and forward segments before receiving the complete payload, reducing the current store-and-forward delay. Tests used 500 simulated nodes, 50 Mbps upload and 100 Mbps download speeds, a home-builder source, real Prysm and go-libp2p-pubsub code, a simulated network and virtual clock, and 10 randomized network configurations. Researchers found that 16 KiB segments balanced propagation speed and network traffic, while 8 KiB segments increased control traffic without improving delivery times. The study evaluated three tiers: simultaneous segmented publishing, push-and-pull retrieval, and Reed-Solomon erasure coding for reconstructing missing pieces. The findings came from simulations and prototype code rather than Ethereum mainnet measurements. EIP-8411 remains a Draft networking EIP, depends on EIP-7732, and would replace the execution_payload gossip topic with execution_payload_chunks. Developers requested Proposed for Inclusion status for Hegotá, the upgrade expected after Glamsterdam, but no inclusion decision had been recorded at the time of the report.