HyperRPC is an extremely fast read-only RPC for data-intensive tasks. It is designed to be a drop-in solution with a mind-boggling performance boost.

Overview (Alpha available) | Envio

HyperRPC is a high-speed read-only RPC designed for data-intensive tasks, offering a significant performance improvement for read-only calls. It is a drop-in solution that can potentially provide a 5x performance boost for data-intensive RPC calls such as eth_getLogs when compared to traditional nodes like geth, erigon, and reth.

Supported Methods

The current method support is limited to the following:

• eth_chainId
• eth_blockNumber
• eth_getBlockByNumber
• eth_getBlockByHash
• eth_getTransactionByHash
• eth_getTransactionByBlockHashAndIndex
• eth_getTransactionByBlockNumberAndIndex
• eth_getTransactionReceipt
• eth_getBlockReceipts
• eth_getLogs
• eth_getFilterLogs
• eth_getFilterChanges
• eth_uninstallFilter
• eth_newFilter

Performance and Usage Recommendations

For optimal performance with filter-related methods, it is recommended to use the \'stateful\' RPC endpoints, which include:

• eth_getFilterLogs
• eth_getFilterChanges
• eth_uninstallFilter
• eth_newFilter

Note that the performance of stateful RPC endpoints may not be as high for other calls as the standard RPC endpoint.

Chain Support and Testing

These methods are already supported on a variety of chains. The most up-to-date list of supported chains can be found here.

Testing the endpoint and providing feedback is encouraged. To access these endpoints for free, join the Envio Discord or log in via GitHub on the main website to access your endpoints.

Disclaimer

• HyperRPC is still under active development to improve performance and stability.
• It has not been audited for security purposes.
• It does not support all RPC methods.
• The team appreciates your patience and is available to answer questions on their Discord.