Write Part 2: Setting up Signal

[swarna1101]

Covers journey pages 5 to 10. Every command and flag must come from the gateway, not from the design mockups.

Blocked by the Console fixes (#54). Until those land, Console shows a different command than the one these pages document.

Pages

• 5 Understanding Signal.

  • What improves: block and attestation arrival over the mump2p mesh.
  • How it is measured.
  • Reports need at least 500 registered indices.

• 6 Checking your network is ready.

  • Inbound TCP 33212 (CL) and 33213 (mesh), outbound 443.
  • Telemetry on 48123 stays on localhost.
  • Link to gateway latest/network-requirements.

• 7 Connecting your first gateway.

  • Use the join key (OPT_JOIN_KEY) from Console.
  • Pin the image: getoptimum/gateway:v1.3.2.
  • Mount volumes for the libp2p and mump2p identity directories.
  • Docker is the default. Add a Kubernetes tab that links to gateway latest/kubernetes.
  • Get the peer ID and multiaddrs from /api/v1/self_info.
  • Per-client peering:
    • Prysm: --peer
    • Lighthouse: --boot-nodes plus --trusted-peers
    • Teku: --p2p-direct-peers. Static peers alone get pruned.
    • Nimbus: --direct-peer, with a stable --netkey-file
    • Lodestar: trusted or direct peer

• 8 When the connection check fails. Three named failures, each with its fix:

  • the gateway is not reachable on 33212 or 33213;
  • the client is not peering;
  • the peer ID changed because the identity was not persisted.

  Use /health and /api/v1/self_info.

• 9 Registering your validator indices. Paste or upload a CSV. Explain how connected stake is derived on chain.

• 10 Your first Signal report. How to read it, and what shows below the 500-index threshold.

Done when

A clean machine following only these pages ends with the gateway healthy, the CL peered, and indices registered.

[linear-code]

OPT-1116