Ethereum Sovereign Infrastructure

Our own Ethereum mainnet node, operated by RobotBase alongside our Bitcoin, Monero and Zcash nodes. The stack is a self-hosted Reth execution client paired with a Lighthouse consensus client, and every number below is read live from that machine — no third-party RPC, no hosted provider, no account. Read-only telemetry is published for developers and AI agents through a single MCP endpoint.

connecting…

Block height

—

execution layer · mainnet

Execution client

—

Reth · self-hosted

Consensus client

—

Lighthouse · self-hosted

Beacon slot

—

consensus layer head

Peers

—

execution layer p2p

NODE ENDPOINTS

Purpose	Endpoint
Read-only MCP endpoint	`https://robotbase.cc/mcp`
Tool catalog	`https://robotbase.cc/mcp/tools`
Node telemetry (JSON)	`https://robotbase.cc/api/nodes`
This portal	`https://eth.robotbase.cc/`
RobotBase gateway	`https://robotbase.cc/`

WHAT THIS NODE FEEDS

Live execution state (block height, client version, peer count) and consensus state (head slot, sync distance) behind the same read-only gateway that feeds the MCP oracle layer.
chain_status("eth") and robotbase_capabilities on the MCP server answer Ethereum questions inside the window this node actually retains.
No public JSON-RPC endpoint is operated for Ethereum. The former robotbase.cc/eth-rpc relay was retired on 2026-10-13; every read path is the MCP surface.
No wallet RPC, no accounts, no signing and no validator keys on this host — the node holds no balances of its own.

This portal is a read-only status surface. It is one chain on an eight-chain roster served by a single read-only MCP endpoint, and the larger matrix, MCP tool catalog and service status live at robotbase.cc.