Documentation — RELAYSTRIDE

1. GETTING STARTED

RelayStride is a smart JSON-RPC routing layer and provider failover system designed for the Robinhood Chain ecosystem.

To run RelayStride locally, use the following commands:

git clone https://github.com/RelayStrideRH/relaystride.git
cd relaystride
npm install
npm run dev

Open localhost:3000 in your browser to view the interface.

2. CLI REFERENCE

Available CLI commands (Note: CLI is not yet published. Run locally with npx):

Command	Description
`init`	Initialize configuration
`providers list`	List configured providers
`health`	Check provider health
`balance`	Get ETH balance for address
`receipt`	Get transaction receipt
`request`	Make raw JSON-RPC request
`receipts list`	List routing receipts
`mcp`	Start MCP server

Global Options

--json, --network, --timeout, --dry-run

Exit Codes

Code	Meaning
0	Success
1	Error
2	No providers available
3	Budget exceeded
4	Validation failure
5	Timeout
6	Unresolved payment

3. PROVIDER CONFIGURATION

By default, RelayStride comes configured with Robinhood Chain public RPCs.

To add custom providers, edit your configuration file. Rate limits apply strictly to public RPC endpoints.

Environment Variables

RELAYSTRIDE_NETWORK=robinhood-mainnet
RELAYSTRIDE_BUDGET=10.00
RELAYSTRIDE_PROVIDER_TIMEOUT=5000

4. MCP INTEGRATION

RelayStride supports Model Context Protocol (MCP) to provide tools for LLMs (like Claude and Cursor).

Available Tools

provider_health
get_balance
get_tx_receipt
get_token_balance
list_capabilities

Note: All tools are currently read-only.

Configuration for Claude Desktop

{
  "mcpServers": {
    "relaystride": {
      "command": "npx",
      "args": ["relaystride", "mcp"]
    }
  }
}

5. ROUTING ENGINE

The routing engine intelligently selects the best provider based on health, latency, cost, and priority.

Circuit Breaker States

Closed: Normal operation. Requests flow freely.
Open: Provider marked unhealthy. Requests are blocked and rerouted.
Half-Open: Testing recovery. A single test request is allowed.

Budget enforcement prevents accidental overspend by tracking the aggregate cost of API requests. Unknown cost providers require explicit opt-in.

6. RECEIPT FORMAT

Every routed request generates a local routing receipt (Note: these are NOT on-chain transaction receipts).

{
  "receiptId": "rec_1a2b3c",
  "timestamp": "2023-10-27T10:00:00Z",
  "method": "eth_getBalance",
  "provider": "robinhood-public-1",
  "latencyMs": 142,
  "cost": {
    "amount": 0,
    "currency": "none"
  },
  "status": "success"
}

7. LIMITATIONS & ROADMAP

Live Features

Network status, balance checking, transaction receipts, token metadata and balance querying, provider failover, response validation, budget enforcement (for free RPCs), browser terminal, and MCP tools.

Planned Roadmap

Paid API routing integration, npm package publishing, deployment features, and support for additional networks.

Known Issues

Public RPCs are heavily rate-limited. No paid provider integration is actively connected yet.