Most people think validator performance is mainly about hardware. But there’s another factor that can make a huge difference: how fast your node receives the block. That’s one reason I find @get_optimum partnership with @Nodemonste interesting. Ethereum has made huge progress on execution and data availability, but networking is still one of those areas where small inefficiencies can become big bottlenecks. As blocks get larger and validators become more geographically distributed, propagation latency starts to matter a lot. A validator receiving a block a few hundred milliseconds earlier can have a real advantage. That’s the problem mump2p is going after. Optimum uses RLNC-coded gossip as a sidecar alongside the node, giving validators a faster propagation path without forcing them to completely change their existing setup. Your client configuration stays. Your signing setup stays. Your security posture stays. And GossipSub still runs underneath. That’s what I find interesting about the design. It’s not trying to burn down the existing stack. It’s trying to make the propagation layer more efficient. The early testnet results are pretty strong too: ~150ms average block propagation, roughly 6× faster than the GossipSub baseline. But benchmarks only tell part of the story. Having @Nodemonste run mump2p gives Optimum something even more valuable: real validator-side feedback. Because infrastructure behaves differently when it leaves a controlled test environment and starts dealing with actual network conditions, bandwidth constraints and geographic latency. That’s where this partnership becomes meaningful. It gives Optimum another experienced operator putting mump2p through its paces, while helping build confidence that these propagation gains can translate into real validator performance. And if mump2p continues delivering across different operators and network conditions, Optimum could have something much bigger than a faster gossip protocol. It could become part of the next generation of Ethereum validator networking. Less propagation latency. Better synchronization. More efficient validators. Sometimes the biggest infrastructure upgrades are the ones users never notice. They just make everything underneath work better.