Appearance

Optimum Gateway - User Guide ​

Required upgrade: v1.0.2 is a mandatory upgrade for all partners. It replaces every earlier release — previous release candidates (rc11, rc12) are no longer supported. Upgrade as soon as you receive your API key.

Release Notes: What's new in v1.0.2

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 ​

subscribe topicpublish↑ peer list · fork digest · known validators↓ heartbeat↓ metrics + logs · remote pushClientCL clientbeacon_block, attestations64 subnetsGatewayOptimum GatewaySubscribes to CL topicsAggregates & packs attestationsPublishes to mump2pPushes remote telemetryNetworkOptimum NetworkInterconnectedmump2p nodesDiscoveryBootstrapStateless discoveryTelemetryMimir · Lokivia CloudflareAPI keygateway_id · chain · validators(exchanged for short-lived JWT)OnboardingPartner Consoleconsole.getoptimum.ioAPI key issuance
  • 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.
  • Identity, chain, and validator scope all come from your API key — there is no per-network YAML to edit.
  • Config: See Quick Start and Configuration.

Requirements ​

Getting Started ​

Follow the Quick Start to get running in minutes.