Skip to content

Releases: getoptimum/optimum-gateway

Release list

v1.1.1

Choose a tag to compare

@swarna1101 swarna1101 released this 07 Aug 13:41
Immutable release. Only release title and notes can be modified.
66e391d

What's Changed

Full Changelog: v1.0.2...v1.1.1

v1.1.0

v1.1.0 Pre-release
Pre-release

Choose a tag to compare

@CryptoFewka CryptoFewka released this 21 Jul 03:19
e31987b

Optimum Gateway

This is the first public release of Optimum Gateway.

Optimum Gateway bridges gossip messages between libp2p clients and mump2p (RLNC) nodes. It currently supports Ethereum consensus layer clients (Prysm, Lighthouse, Teku, Nimbus, Lodestar), forwarding beacon blocks and attestations between the CL gossip network and the Optimum mump2p mesh.

Highlights

  • Bidirectional gossip forwarding between CL clients and mump2p nodes, with deduplication and per-topic subscription control
  • Beacon block decoding and slot-aware message handling on the forwarding path
  • Authenticated mesh membership: gateway JWT handshake with cluster binding, backed by the Optimum auth service
  • Built-in telemetry: Prometheus metrics, optional remote push, and structured health/self-info endpoints
  • Sidecar deployment support alongside an existing CL node (see docker-compose-sidecar.yml), plus a full local integration stack under integration/

Getting started

  • Docker image: getoptimum/gateway:v1.1.0 (images ship with signed SBOMs)
  • Configuration reference and quick start: see README.md, guide.md, and docs/
  • To run against your own consensus client, start from the sidecar compose file and the quick start guide

Licensing and source visibility

The source is published under the Microsoft Reference Source License (Ms-RSL): it is available for reference and review. Third-party attributions are listed in THIRD-PARTY-NOTICES.md and NOTICE. Note that builds depend on Optimum-internal Go modules, so this repository is not independently buildable; official binaries are distributed as Docker images.

Security

Please report vulnerabilities through GitHub private vulnerability reporting or as described in SECURITY.md.

Versioning note

Version numbering continues from Optimum's internal release line (most recently v1.0.2). This release is marked as a pre-release while it is validated across the gateway fleet.