The Hiero JSON-RPC Relay is an open-source service that speaks the Ethereum JSON-RPC protocol on top of the Hedera network. EVM tools (Hardhat, Foundry, Ethers.js, Viem, MetaMask) speak JSON-RPC; Hedera consensus nodes speak gRPC. The relay translates between the two, plus pulls historical state from a mirror node. Repository:Documentation Index
Fetch the complete documentation index at: https://hedera-0c6e0218-chore-hide-placeholder-pages.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
hiero-ledger/hiero-json-rpc-relay. License: Apache-2.0.
Three ways to get an RPC endpoint
For most teams, “running the relay” means picking one of three options based on the use case.| Option | When it fits | Cost |
|---|---|---|
| Hashio (free public relay, development use only) | Development, hobby projects, low-volume reads | Free, throttled |
| Third-party managed provider (Arkhia, Validation Cloud, Hgraph, QuickNode, thirdweb) | Production traffic with SLAs | Paid, varies by provider |
| Self-hosted | Production workloads where you control config, retention, and rate limits | Infra cost only |
Public endpoints
| Network | Chain ID | Hashio endpoint |
|---|---|---|
| Mainnet | 295 | https://mainnet.hashio.io/api |
| Testnet | 296 | https://testnet.hashio.io/api |
| Previewnet | 297 | https://previewnet.hashio.io/api |
When to run your own
Self-hosting makes sense when you need any of:- Higher throughput than community endpoints throttle to
- Custom rate-limiting rules per consumer
- Tighter control over which mirror node the relay reads from
- An RPC endpoint inside a private VPC, not on the public internet
- Specific log retention, metrics, or audit requirements
Next steps
Setup
Install and run the relay locally or in a container orchestrator.
Configuration
Environment variables, chain ID, mirror node URL, caching, rate limits.