v0.0.1-rc8

This release supersedes v0.0.1-rc7.

Highlights

• Beacon block only: RC8 currently supports only the beacon_block topic for focused metrics collection and validation. This allows us to collect high-quality metrics, validate gateway performance with cleaner data, and ensure stability before expanding to additional topics. Future releases will support attestations, aggregates, and other Ethereum consensus topics.
• Fusaka BPO2 as default: c6ecb76c is now the active fork digest. The gateway continues to accept the previous digests (82556a32, ae9f70a0) so validators can roll forward without downtime.
• Stronger deduplication TTL: We closed a race in the TTL map that could surface the same message twice a few seconds apart. The cache now records the message hash immediately, so downstream peers only see one copy.
• Subscription handshake guard: The startup path now refuses to continue unless at least one Ethereum topic is present in the subscription request. This aligns the gateway with the upstream ingress validation and prevents silent drops right after boot.
• Sidecar service for trace collection: Added gRPC sidecar service support for Optimum P2P nodes. The sidecar listens on port 33211 (configurable) and enables trace collection and visualization for monitoring and observability. Important: This port must be exposed and not behind a firewall.

Configuration update

Beacon Block Only: RC8 currently supports only the beacon_block topic for focused metrics collection and validation. This allows us to collect high-quality metrics, validate gateway performance with cleaner data, and ensure stability before expanding to additional topics.

Set your eth_topics_subscribe to use the BPO2 digest (c6ecb76c) with only the beacon_block topic:

eth_topics_subscribe:
  # Currently only beacon_block is supported
  # Future releases will support additional topics (attestations, aggregates, etc.)
  - /eth2/c6ecb76c/beacon_block/ssz_snappy

Note: Your CL client will continue to receive all topics it subscribes to directly. The gateway's beacon_block-only limitation only affects what gets bridged to the Optimum network. This is intentional for the current validation phase.

New configuration option: The sidecar service port can be customized if needed:

sidecar_listen_port: 33211  # Default: 33211, used for trace collection

No other configuration changes are required. Dynamic configuration, slot toggling, IPv6 support, and the Docker host-mode fixes introduced in RC7 continue to work unchanged.