rpc-relay-pro

Local accelerator for RPC Relay Pro. Requires Node.js 22 or newer and a Pro or Pro+ token.

The local cache accelerator is included in Pro and Pro+.

Version 1.1 adds:

• zero-network warm reads with foreground leakage counters;
• fixed-size, randomized, padded miss batches;
• cache keys bound to observed block number/hash;
• multi-upstream safe-head validation and 64-block finality policy;
• reorg invalidation and bounded stale-if-error behavior;
• access-pattern learning and background predictive prefetch.

curl -fsSL https://rpc-relay.pages.dev/install.sh | sh
rpc-relay-pro setup                       # Ethereum Mainnet (backward compatible)
rpc-relay-pro setup --chain base          # Base Mainnet (chain ID 8453)
rpc-relay-pro setup --chain arbitrum      # Arbitrum One
rpc-relay-pro setup --chain optimism      # OP Mainnet
rpc-relay-pro setup --chain polygon       # Polygon PoS

Interactive terminals may omit PRO_TOKEN; the setup wizard requests it without echoing. Setup stores configuration with owner-only permissions, installs the active version under ~/.rpc-relay-pro/versions, starts the accelerator, waits for /health, and validates a real eth_blockNumber response.

Commands:

rpc-relay-pro doctor
rpc-relay-pro integrations
rpc-relay-pro restart
rpc-relay-pro benchmark
rpc-relay-pro audit
rpc-relay-pro mcp-config
rpc-relay-pro mcp
rpc-relay-pro stop
rpc-relay-pro start

The accelerator serves one explicitly configured network at a time. Ethereum, Base, Arbitrum, Optimism, and Polygon use different WebSocket routes and persisted cache files; chain identity is included in every cache key. Re-run setup with --chain <name> to switch networks.

Pro also exposes rpc_relay_simulateTransaction, which runs eth_call, gas estimation, and access-list construction without signing or submitting the transaction. Trace methods are forwarded when the selected upstream supports them. Transaction submission remains disabled by default.

Every localhost RPC response includes X-RPC-Chain, X-RPC-Chain-Id, X-Cache-Status, X-Local-Proxy-Ms, and X-RPC-Data-Age-Ms. Treat local lookup latency and data freshness as separate measurements. For timing-sensitive logic, reject responses whose chain, cache state, or age exceeds the strategy's explicit budget.

Proof benchmark:

npm run benchmark:moat
npm run test:accelerator-correctness

Local endpoints:

• JSON-RPC: POST http://127.0.0.1:8545/
• Health: GET http://127.0.0.1:8545/health
• Prometheus metrics: GET http://127.0.0.1:8545/metrics
• Redacted diagnostics: GET http://127.0.0.1:8545/diagnostics

Cache state is persisted atomically to ~/.rpc-relay-pro/cache.json every 30 seconds and during graceful SIGINT/SIGTERM shutdown.

Local MCP server

rpc-relay-pro mcp exposes allowlisted read-only EVM RPC, health, and diagnostics over MCP stdio for the configured Ethereum or Base network. It talks only to localhost; the Pro token remains in the accelerator's owner-only config and never appears in MCP messages. Run rpc-relay-pro mcp-config for copy-ready client configuration.

The MCP surface does not provide funding rates, volatility/ATR calculations, trade signals, signing, transaction submission, slippage protection, or stop management. Pair it with independent market and on-chain signal sources, timestamp every input, and let the execution system enforce freshness, liquidity, gas, and slippage limits.