HyperRPC Complete Documentation
This document contains all HyperRPC documentation consolidated into a single file for LLM consumption.
| What it is | An extremely fast read-only JSON-RPC endpoint - a drop-in replacement for traditional RPC nodes, built on top of HyperSync |
| Performance | Up to 5x faster than traditional nodes (geth, erigon, reth) for data-intensive operations |
| Read-only | Optimised for data retrieval only - cannot send transactions |
| Supported networks | 85 EVM-compatible networks, with new networks being added regularly |
| Endpoint format | https://[network].rpc.hypersync.xyz or https://[chainid].rpc.hypersync.xyz |
| Supported methods | eth_chainId, eth_blockNumber, eth_getBlockByNumber, eth_getBlockByHash, eth_getBlockReceipts, eth_getTransactionByHash, eth_getTransactionByBlockHashAndIndex, eth_getTransactionByBlockNumberAndIndex, eth_getTransactionReceipt, eth_getLogs, trace_block (select chains only) |
| API token | Recommended - rate limiting starts June 2025 |
| When to use | Drop-in replacement for existing RPC-based code; when tools expect standard JSON-RPC interfaces; when you don't have time for a deeper integration |
| When to use HyperSync instead | When performance is critical; for new projects; when you need advanced filtering and field selection |
| Development status | Under active development; not yet formally security audited; read-only only |
| Support | Discord · GitHub |
HyperRPC: Ultra-Fast Read-Only RPC
File: overview-hyperrpc.md
HyperRPC is an extremely fast read-only RPC designed specifically for data-intensive blockchain tasks. Built from the ground up to optimize performance, it offers a simple drop-in solution with dramatic speed improvements over traditional nodes.
For most use cases, we recommend using HyperSync over HyperRPC.
HyperSync provides significantly faster performance and much greater flexibility in how you query and filter blockchain data. Behind the scenes, HyperRPC actually uses HyperSync to fulfill requests.
When to use HyperRPC:
- When you need a simple drop-in replacement for existing RPC-based code
- When you don't have time for a deeper integration
- When you're working with tools that expect standard JSON-RPC interfaces
When to use HyperSync:
- When performance is critical (HyperSync is much faster)
- When you need advanced filtering capabilities
- When you want more control over data formatting and field selection
- For new projects where you're designing the data access layer
Table of Contents
- What is HyperRPC?
- Performance Advantages
- Supported Methods
- Supported Networks
- Getting Started
- Development Status
What is HyperRPC?
HyperRPC is a specialized JSON-RPC endpoint that focuses exclusively on read operations to deliver exceptional performance. By optimizing specifically for data retrieval workflows, HyperRPC can significantly outperform traditional nodes for data-intensive applications.
Key characteristics:
- Read-only: Optimized for data retrieval (cannot send transactions)
- Drop-in compatible: Works with existing tooling that uses standard RPC methods
- Specialized: Designed specifically for data-intensive operations like
eth_getLogs
Performance Advantages
Early benchmarks show that HyperRPC can deliver up to 5x performance improvement for data-intensive operations compared to traditional nodes like geth, erigon, and reth.
This performance boost is particularly noticeable for:
- Historical data queries
- Log event filtering
- Block and transaction retrievals
- Analytics applications
Supported Methods
HyperRPC currently supports the following Ethereum JSON-RPC methods:
| Category | Methods |
|---|---|
| Chain Data | eth_chainId``eth_blockNumber |
| Block Data | eth_getBlockByNumber``eth_getBlockByHash``eth_getBlockReceipts |
| Transaction Data | eth_getTransactionByHash``eth_getTransactionByBlockHashAndIndex``eth_getTransactionByBlockNumberAndIndex``eth_getTransactionReceipt |
| Event Logs | eth_getLogs |
| Traces | trace_block (only on select chains) |
Supported Networks
HyperRPC is available across numerous EVM-compatible networks. For the most up-to-date list of supported chains, please see our Supported Networks page.
Getting Started
To start using HyperRPC:
-
Get Access:
- Visit our Supported Networks page to find all available HyperRPC endpoints
- Each network has a ready-to-use URL that you can start using immediately
-
Add Your API Token (recommended):
-
Requests without an API token will be rate limited starting June 2025 (same timeline as HyperSync).
-
Append your token to the endpoint URL. Example:
https://100.rpc.hypersync.xyz/ -
If you don't have a token yet, you can generate one through the Envio Dashboard.
-
-
Use Like a Standard RPC:
// Example: Fetching logs with HyperRPC
const response = await fetch("https://100.rpc.hypersync.xyz/", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
jsonrpc: "2.0",
id: 1,
method: "eth_getLogs",
params: [
{
fromBlock: "0x1000000",
toBlock: "0x1000100",
address: "0xYourContractAddress",
},
],
}),
}); -
Provide Feedback: Your testing and feedback are incredibly valuable as we continue to improve HyperRPC. Let us know about your experience in our Discord.
Development Status
- HyperRPC is under active development to further improve performance and stability
- It is designed for read-only operations and does not support all standard RPC methods
- It has not yet undergone formal security audits
- We welcome questions and feedback in our Discord
Hyperrpc Supported Networks
File: hyperrpc-supported-networks.md
Please note we are rapidly adding new supported networks. If you don't see your network here or would like us to add a network to HyperRPC, pop us a message in Discord.
Requests without an API token will be rate limited starting June 2025 (following the same schedule as HyperSync). Append your token to the endpoint URL to maintain full speed:
https://100.rpc.hypersync.xyz/
These are HyperRPC endpoints. For HyperSync endpoints, see HyperSync Supported Networks.
Here is a table of the currently supported networks on HyperRPC and their respective URL endpoints.
Notes:
- Base Traces*: Start block: 39000000 (earlier blocks available on request)
- Injective*: Start block: 129846180 (non-evm before that)
- Sei*: Start block: 79123881 (non-evm before that)
- Sei Testnet*: Start block: 186100000 (non-evm before that)
Frequently Asked Questions (FAQ)
What is HyperRPC?
HyperRPC is an ultra-fast, read-only JSON-RPC endpoint built by Envio. It is designed as a drop-in replacement for traditional JSON-RPC nodes, optimised specifically for data-intensive blockchain operations like historical queries, log filtering, and block/transaction retrieval. Behind the scenes, HyperRPC is powered by HyperSync.
How does HyperRPC differ from HyperSync?
HyperRPC uses the standard JSON-RPC interface, making it compatible with existing tools and code that expect standard RPC methods. HyperSync is Envio's more powerful data engine with a custom query interface that offers significantly faster performance and much greater flexibility in how you filter and retrieve blockchain data. HyperRPC actually uses HyperSync under the hood to fulfil requests.
When should I use HyperRPC instead of HyperSync?
Use HyperRPC when you need a simple drop-in replacement for existing RPC-based code, when you don't have time for a deeper integration, or when you're working with tools that expect standard JSON-RPC interfaces. Use HyperSync when performance is critical, when you need advanced filtering capabilities, when you want more control over data formatting and field selection, or for new projects where you're designing the data access layer from scratch.
How fast is HyperRPC?
Early benchmarks show HyperRPC delivers up to 5x performance improvement for data-intensive operations compared to traditional nodes such as geth, erigon, and reth. This improvement is most noticeable for historical data queries, log event filtering, block and transaction retrievals, and analytics applications.
What JSON-RPC methods does HyperRPC support?
HyperRPC supports the following methods: eth_chainId, eth_blockNumber, eth_getBlockByNumber, eth_getBlockByHash, eth_getBlockReceipts, eth_getTransactionByHash, eth_getTransactionByBlockHashAndIndex, eth_getTransactionByBlockNumberAndIndex, eth_getTransactionReceipt, eth_getLogs, and trace_block (on select chains only). It does not support all standard RPC methods.
What networks does HyperRPC support?
HyperRPC supports 85 EVM-compatible networks including Ethereum Mainnet, Arbitrum, Base, Optimism, Polygon, Avalanche, BSC, and many more. New networks are being added rapidly. See the Supported Networks table in this document for the full list of endpoints.
Do I need an API token?
An API token is recommended. Requests without an API token will be rate limited starting June 2025 (following the same schedule as HyperSync). Append your token to the endpoint URL. You can generate a token through the Envio Dashboard.
How do I get started?
Find the endpoint for your network in the Supported Networks table (format: https://[network].rpc.hypersync.xyz), then use it like any standard JSON-RPC endpoint:
const response = await fetch("https://100.rpc.hypersync.xyz/", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
jsonrpc: "2.0",
id: 1,
method: "eth_getLogs",
params: [{ fromBlock: "0x1000000", toBlock: "0x1000100", address: "0xYourContractAddress" }],
}),
});
Is HyperRPC production-ready?
HyperRPC is under active development to further improve performance and stability. It has not yet undergone formal security audits and does not support all standard RPC methods. It is designed for read-only operations only. Envio welcomes feedback and questions via Discord.
Where can I get help?
- Discord: discord.gg/envio - the fastest way to get help from the team and community
- Telegram: Envio Telegram - the offcial Envio Telegram to get support from the team and community
- GitHub: github.com/enviodev
- Email: hello@envio.dev