OP Mainnet ยท chain ID 10

Optimism acceleration with network isolation

Optimism uses its own HTTP and WebSocket routes, persisted cache file, cache-key namespace, upstream pool, and chain-identity checks.

Direct edge routes

POST https://rpc-cache-worker.rpc-relay-cache.workers.dev/api/v1/optimism/rpc
WSS  wss://rpc-cache-worker.rpc-relay-cache.workers.dev/ws/optimism

Identity guarded

eth_chainId must return 0xa. A mismatched upstream response is rejected.

Cache isolated

Every key includes the chain slug and ID. Optimism persists separately from the backward-compatible Ethereum cache.

Freshness visible

Inspect cache status, local proxy time, data age, observed-head age, and canonical-validation age independently.

Install the local accelerator

curl -fsSL https://rpc-relay.pages.dev/install.sh | sh
rpc-relay-pro setup --chain optimism
rpc-relay-pro doctor
# Local endpoint: http://127.0.0.1:8545

Tiers

Pro

Local cache accelerator included. 300 calls per 10 seconds. Authenticated WebSocket, non-submitting simulation, and signed confirmed-log webhooks are available.

Pro+

Includes everything in Pro, plus supported trace methods through the normal JSON-RPC endpoint and token APIs. 600 calls per 10 seconds.

Free

10 calls per minute. Edge only. No local accelerator and no WebSocket.

What this does not solve

Fast state access is an infrastructure primitive, not a trading signal. Execution needs simulation, signing, slippage and gas limits, inclusion handling, and risk controls outside the read-only MCP surface.

For live decisions, enforce a maximum accepted data age and head lag. A fast stale response should fail the strategy's freshness gate.