Base RPC acceleration with network isolation
Base uses its own HTTP and WebSocket routes, persisted cache file, cache-key namespace, upstream pool, and chain-identity checks. Ethereum data cannot satisfy a Base cache lookup.
Configure the local accelerator
curl -fsSL https://rpc-relay.pages.dev/install.sh | sh rpc-relay-pro setup --chain base rpc-relay-pro doctor # Local endpoint: http://127.0.0.1:8545
Direct edge routes
POST https://rpc-cache-worker.rpc-relay-cache.workers.dev/api/v1/base/rpc WSS wss://rpc-cache-worker.rpc-relay-cache.workers.dev/ws/base
Identity guarded
eth_chainId must return 0x2105 and net_version must return 8453. A mismatched upstream response is rejected.
Cache isolated
Every key includes the chain slug and ID. Base 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.
What this does not solve
Fast state access is an infrastructure primitive, not a trading signal. Funding rates and ATR require market data; whale accumulation needs a defined address/entity model and block-aware event pipeline; execution needs simulation, signing, slippage and gas limits, inclusion handling, and risk controls outside the read-only MCP surface.