technology
mump2p Uses Network Coding for Validators
By Metal · Chief of Staff · 20 Oct 2026
The Ethereum block propagation protocol went live on mainnet on Oct. 20, 2026. It offers services for receiving and sending block data to validators.
Release on Mainnet
The Ethereum block propagation protocol, released on Oct. 20, 2026, went live on mainnet with Signal and Accelerate services for validator operators.
mump2p, an Ethereum block propagation protocol, was released on Oct. 20, 2026. Per the company blog, mump2p went live on Ethereum mainnet and became available for any validator operator to run. This availability extended the protocol’s reach to connected validator nodes across the network.
Signal Service
mump2p carried beacon block data across the network to connected validator nodes. A service called Signal, built for receiving beacon block data, was open to all Ethereum validator operators. Operators could use Signal to obtain the data needed for network participation.
Signal operated as the entry point for receiving blocks. The service focused on delivery of beacon block information to nodes that connected to the protocol.
Accelerate Service
A service called Accelerate, built for sending proposed blocks to other validators, was offered through self-serve onboarding to larger operators. Accelerate supported the transmission of blocks proposed by those operators.
Larger operators followed self-serve steps to activate Accelerate. The service handled outbound block data to other participants in the validator set.
Operator Console and Dashboard
Operators signed up through a web console that combined self-serve setup, monitoring and admin tools. The console served as the central location for managing connections to the protocol.
A public dashboard displayed performance data aggregated from the nodes running mump2p. The dashboard presented summaries drawn from participating nodes.
Network Coding Method
The protocol used Random Linear Network Coding, an erasure code, to shard, encode and decode block data. This method divided data into shards for transmission.
Nodes known as Flexnodes forwarded coded shards across a global mesh and generated additional shards. Flexnodes handled the movement of these shards within the mesh structure.
The coding approach allowed shards to travel separately before reassembly at receiving nodes. Flexnodes contributed to shard distribution and creation of extra shards as needed.
Validator Access Overview
Validator operators connected to mump2p through the described services and tools. The release established Signal for inbound data and Accelerate for outbound proposals. The web console and public dashboard supported management and visibility of node activity.
Random Linear Network Coding formed the basis for data handling. Flexnodes operated within the mesh to move shards. All elements combined to support block propagation for validators on mainnet.