Ethereum researchers have reported major improvements in simulated execution payload propagation using EIP-8411’s segmented broadcasting design, cutting median delivery times for a 1 MiB payload from roughly five seconds to below one second. The results, published on Sept. 17, come from prototype client code and a 500-node simulation using home-builder bandwidth, geographic latency, and ten randomized network seeds—not from Ethereum mainnet measurements.
EIP-8411 replaces the single execution_payload gossip topic introduced by EIP-7732 with an execution_payload_chunks topic. A Merkle root committed in the builder’s execution bid allows nodes to verify each fixed-size segment independently and forward chunks before receiving the full payload. In the modeled topology, the Tier 1 segmented design achieved a median near 0.75 seconds and a tail close to one second, compared with about five seconds median and nearly six seconds tail for whole-message propagation. More advanced tiers added disciplined pull requests and Reed-Solomon erasure coding to reduce duplicate traffic and improve tail performance, though researchers noted tradeoffs in bandwidth and withholding attacks.
The proposal remains a Draft networking EIP and requires EIP-7732. Ethereum developers planned to discuss EIP-8411 for Hegotá inclusion during ACDC #187 on Sept. 17 at 14:00 UTC, after it was proposed as a replacement for EIP-8142. The work is tied to Ethereum’s Layer 1 capacity increases, with the gas limit having reached 60 million in late 2025 and larger payloads placing more pressure on node bandwidth.
Separately, Ethereum Classic node operators have been urged to avoid a disputed Core Geth v1.13.0 release after several mining pool nodes briefly migrated before returning to the maintained Argos v1.12.23 client. According to a Sept. 16 incident report from Classix, the disputed ethereumclassic/core-geth repository pushed 96 commits with 13,422 added lines and 3,977 deleted lines in 56 hours without outside review. The release was promoted as a security update, but Classix said existing Core Geth maintainers had not reviewed it and the maintained etclabscore/core-geth repository had not issued it.
The rogue software reenabled Modified Exponential Subjective Scoring and replaced DNS discovery infrastructure with hardcoded bootnodes and new signing keys. Four 2Miners nodes briefly ran v1.13.0 on Sept. 15 before reverting to Argos v1.12.23, and around ten or eleven individual nodes continued using the disputed client. Classix classified the incident as high severity but low impact, with no blocks lost, no chain reorganizations, no funds affected, and no service interruptions.
Classix challenged the v1.13.0 security claims, saying most cited vulnerabilities were already fixed in maintained releases or did not apply to Ethereum Classic. Operators were told to stay on or return to Argos v1.12.23, restore rotated P2P node keys, and avoid concentrating network hash power on Core Geth by considering clients such as Nethermind, Besu, and Getc.
