Appearance

Optimum Gateway – User Guide ​

Release Notes: See what's new in v0.0.1-rc12
Version History: CHANGELOG

The Optimum Gateway bridges your Ethereum Consensus Layer (CL) client with the mump2p network.

What does Optimum Gateway do? ​

  • Problem: Validators rely on CL gossip (libp2p) for block and attestation propagation. Latency variance hurts performance.
  • Gateway Role: Bridges your local CL client to the mump2p network for both blocks and attestations.
  • Result: Faster block and attestation propagation, reduced latency, improved validator rewards.

Architecture ​

Optimum Gateway Architecture

  • The Gateway subscribes to ETH CL topics (beacon_block + all 64 attestation subnets) and forwards messages to the Optimum mump2p network.
  • Peer discovery and fork digest are handled automatically. The gateway connects to the Optimum network on startup.
  • Config: See Quick Start and Configuration.

Requirements ​

  • CL Client: Prysm, Lighthouse, Teku, or Nimbus running
  • Docker: Docker Desktop or Docker Engine
  • Firewall: Required ports open (see Network Requirements)

Getting Started ​

Follow the Quick Start to get running in minutes.