Getting Started

Hit the live network

The gateway is live at https://gateway.lodestar-dashboard.com. Every request must include your Ethereum address in the X-Consumer-Address header — the gateway uses it to charge GRT from your escrow on-chain.

curl -s -X POST https://gateway.lodestar-dashboard.com/rpc/42161 \
  -H "Content-Type: application/json" \
  -H "X-Consumer-Address: 0xYOUR_ADDRESS" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

No X-Consumer-Address header → 402 Payment Required. No funded escrow → the provider rejects the request. Fund your escrow at lodestar-dashboard.com/dispatch before making requests. See Payments for the full escrow setup. Every response carries an x-drpc-attestation header — an ECDSA signature from the provider over keccak256(chainId || method || params || response || blockHash). You can verify this with the consumer SDK (see Using the Network).

Smoke test a live provider

Fires real TAP-signed JSON-RPC requests directly at the provider endpoint (bypasses the gateway). Requires a key that is in the provider’s authorized_senders list.

DISPATCH_ENDPOINT=https://rpc.cargopete.com \
DISPATCH_SIGNER_KEY=<authorized-signer-key> \
DISPATCH_PROVIDER_ADDRESS=0xb43B2CCCceadA5292732a8C58ae134AdEFcE09Bb \
cargo run --bin dispatch-smoke

Expected output:

dispatch-smoke
  endpoint   : http://167.235.29.213:7700
  chain_id   : 42161
  data_svc   : 0x7101d5c1a5c89c3647f5118da118e56c023ba0b9
  signer     : 0x7D14ae5f20cc2f6421317386Aa8E79e8728353d9

  [PASS] GET /health → 200 OK
  [PASS] eth_blockNumber — returns current block → "0x1b1623cf" [95ms]
  [PASS] eth_chainId — returns 0x61a9 (42161) → "0xa4b1" [58ms]
  [PASS] eth_getBalance — returns balance at latest block (Standard) → "0x6f3a59e597c5342" [74ms]
  [PASS] eth_getBalance — historical block (Archive) → "0x0" [629ms]
  [PASS] eth_getLogs — recent block range (Tier 2 quorum) → [{"address":"0xa62d...] [61ms]

  5 passed, 0 failed

DISPATCH_SIGNER_KEY must be the private key of an address in the provider’s authorized_senders list. DISPATCH_PROVIDER_ADDRESS must match the provider’s registered address exactly — it is embedded in the TAP receipt and validated on-chain.

Run the drop-in proxy

Point MetaMask, Viem, or any Ethereum library at the Dispatch network without changing application code. The proxy runs locally and handles everything — key management, provider discovery, receipt signing.

cd proxy
npm install
npm start

On first run it generates a consumer keypair, prints your consumer address, and links to the funding dashboard. Fund the escrow at lodestar-dashboard.com/dispatch, then add http://localhost:8545 to MetaMask as a custom network. See Using the Network → dispatch-proxy for full configuration options.

Run the local demo

Runs a complete local stack on Anvil — Horizon contracts, dispatch-service, dispatch-gateway — makes 5 RPC requests, submits a RAV, and proves GRT lands in the payment wallet. The full loop in one command. Requires: Foundry and Rust stable.

cd demo
npm install
npm start

Build from source

cargo build
cargo test

Docker Compose

The quickest path to a full running stack:

cp docker/config.example.toml  docker/config.toml
cp docker/gateway.example.toml docker/gateway.toml

# Fill in private keys, provider addresses, and backend RPC URLs
docker compose up

The default stack starts dispatch-service, dispatch-gateway, and PostgreSQL.

Introduction

Overview

Guides

Components

Reference

Getting started

Getting Started

Hit the live network

Smoke test a live provider

Run the drop-in proxy

Run the local demo

Build from source

Docker Compose

​Getting Started

​Hit the live network

​Smoke test a live provider

​Run the drop-in proxy

​Run the local demo

​Build from source

​Docker Compose

Getting Started

Hit the live network

Smoke test a live provider

Run the drop-in proxy

Run the local demo

Build from source

Docker Compose