Appearance

Choose a path ​

Two answers during registration decide what you see. How do you take part? is Individual or Entity. Do you run validators? is Yes or No.

Optimum does not host gateways. Every path below is a container you run on your own host.

You run validators ​

The gateway runs beside the beacon node. You peer the consensus client, then register validator indices. Signal is the sidebar entry for that.

Accelerate is a later step, for entity accounts only. It needs active validators and enough proposed slots to measure. It is not part of connecting the gateway. See Account type.

You do not run validators ​

This is a supported account. The gateway takes blocks from the mesh and serves them to your own consumers. It does not peer a beacon node, and Console does not ask for validator indices.

The signup step gives you the stream-only command. The command on Signal is the one for a gateway beside a beacon node. If you start a second stream-only gateway from Signal, use the stream-only command instead. Otherwise /health reports the consensus-client checks as failing.

The container is started with OPT_STREAM_ENABLE and OPT_STREAM_ONLY. The libp2p port is not published. The feed, once healthy, is on the gateway host at ws://127.0.0.1:9600 and gRPC 127.0.0.1:9601. Both want a consumer token, minted under Keys → Stream consumers (invited operator accounts see that screen as Manage gateways).

Obol and other distributed validator setups ​

The gateway still sits beside the beacon node those validators use. Charon and the validator client do not change.

For an Obol Charon Distributed Validator Node (CDVN), use the Optimum Gateway overlay for Obol CDVN. It adds the gateway as an opt-in Docker Compose overlay on the dvnode network, dials the beacon node from the gateway side, and turns off by removing the overlay from COMPOSE_FILE.

WARNING

The overlay was written before Console enrolment. It uses an API key (OPT_API_KEY=ogw_live_...), pins GATEWAY_VERSION=v1.1.1, writes a mounted app_conf.yml, and its sample targets Hoodi. Console hands out an enrollment key (OPT_JOIN_KEY) and v1.3.2, run with -config "". Ask support which credential and version to use in the overlay before you mix the two.