v0.0.1-rc11

This release supersedes RC10, RC9, and RC8. RC8, RC9, and RC10 are deprecated.

Highlights

• Bootstrap-driven peer discovery – Proxy-host discovery is removed. The gateway uses Bootstrap for peer discovery and fork digest.
• Simplified topic config – eth_topics_subscribe now accepts short topic names (e.g. beacon_block). Fork digest is fetched from Bootstrap and refreshed periodically.
• Stricter topic/fork validation – Messages and handshakes from unsupported forks are rejected early.
• Libp2p direct peers – Automatic libp2p restart when direct peers are discovered.
• Enhanced self_info – /api/v1/self_info now includes gateway metadata, fork digest, chain, peer counts, and direct peers.

Configuration Migration (Required)

Config migration is required. Use the new config structure:

Cluster ID update: Update gateway_cluster_id to optimum_hoodi_v0_3. Gateways using the old cluster ID (optimum_hoodi_v0_2) will fail to connect to the network; see Migration from RC9 for the gateway_cluster_id step in app_conf.yml.

# Required
gateway_id: "your_unique_gateway_id"
gateway_cluster_id: optimum_hoodi_v0_3

# Topic names only – fork digest from Bootstrap
eth_topics_subscribe:
  - beacon_block

Removed: proxy_host – no longer used. Bootstrap provides peer discovery.

Config: See Quick Start and Configuration.

Migration from RC9

1. Update app_conf.yml – set gateway_cluster_id to optimum_hoodi_v0_3 (if you are on optimum_hoodi_v0_2 or another old value, change it so the node can connect), remove proxy_host, and use short topic names in eth_topics_subscribe.
2. Pull and restart:

docker pull getoptimum/gateway:v0.0.1-rc11
docker restart optimum-gateway

Deprecated Versions

Version	Status
v0.0.1-rc8	DEPRECATED
v0.0.1-rc9	DEPRECATED
v0.0.1-rc10	DEPRECATED

Upgrade to RC11 for continued support.