Skip to main content

Interactive DEMO

Note: You can explore our Interactive Demo using the Demo Project ID 8ry9f6t9dct1se2hlagxnd9n2a

Welcome to the Histori multi-chain archival RPC node. This service allows you to interact with Archival Nodes using a unified endpoint. This guide will show you how to get started, authenticate, and make requests.

1. Overview​

The Histori archival RPC node supports querying 60+ networks with a simple endpoint format. All requests use the JSON-RPC API, making it easy to perform common blockchain operations, such as querying blocks and transactions.

Base URL​

All requests are made to the following base URL:

https://node.histori.xyz/

2. Supported Networks​

A comprehensive list of supported networks can be found in the Supported Networks section

Format:

  • To query a specific network, use: https://node.histori.xyz/<NETWORK_NAME>/<YOUR_PROJECT_ID>

Replace YOUR_PROJECT_ID with the project ID from the Histori Dashboard. Replace NETWORK_NAME with the network you want to do RPC calls to. You can find a complete list of networks in the Supported Networks section

3. Authentication​

All requests must include an project ID for authentication. The project ID can be obtained from the Histori Dashboard. Again ,like the REST API, the Project ID can either be supplied as a path parameter, as a query parameter named projectId or in the x-api-key header.

4. Making Requests​

Request Format​

All requests are made using the JSON-RPC 2.0 format. The basic structure of a request is:

{
    "jsonrpc": "2.0",
    "method": "<method_name>",
    "params": [<parameters>],
    "id": <request_id>
}
  • jsonrpc: The version of JSON-RPC (always "2.0").
  • method: The Ethereum RPC method you want to call (e.g., eth_getBlockByNumber).
  • params: An array of parameters for the method.
  • id: A unique identifier for the request. You can optionally set these differently to keep track of requests

4.1 New Query Parameters​

The Histori RPC node supports additional query parameters to enhance flexibility and reliability:

  1. secure=true: Routes requests via the Flashbots Protect endpoint, ensuring private and secure transaction handling. This is particularly useful for Ethereum Mainnet to prevent front-running and MEV attacks.
  2. all=true: Sends the request to all RPC providers for the network and compares responses to ensure data integrity. If any discrepancies are detected, the system flags them.
  3. random=true: Sends the request to a randomly chosen RPC provider, balancing network load and decreasing likelihood of rate limits.
  4. fallback=false: Disables the default fallback mechanism, which retries the request on a different provider if the initial attempt fails.

4.2 Example Request Using secure=true​

Use Case: Submit a private transaction via Flashbots Protect.

cURL Example

curl -X POST "https://node.histori.xyz/eth-mainnet/8ry9f6t9dct1se2hlagxnd9n2a?secure=true" \
-H "Content-Type: application/json" \
-d '{
    "jsonrpc": "2.0",
    "method": "eth_sendRawTransaction",
    "params": ["<raw_transaction_hex>"],
    "id": 1
}'

4.3 Example Request Using random=true​

Use Case: Query a block using a randomly selected RPC provider. This is faster since a single RPC provider is being used. cURL Example

curl -X POST "https://node.histori.xyz/eth-mainnet/8ry9f6t9dct1se2hlagxnd9n2a?random=true" \
-H "Content-Type: application/json" \
-d '{
    "jsonrpc": "2.0",
    "method": "eth_getBlockByNumber",
    "params": ["latest", true],
    "id": 1
}'

4.4 Example Request Using all=true​

Use Case: Query a block and verify consistent responses across all RPC providers. cURL Example

curl -X POST "https://node.histori.xyz/eth-mainnet/8ry9f6t9dct1se2hlagxnd9n2a?all=true" \
-H "Content-Type: application/json" \
-d '{
    "jsonrpc": "2.0",
    "method": "eth_getBlockByNumber",
    "params": ["latest", true],
    "id": 1
}'

5. Error Handling​

Common Error Responses​

  • 400 Bad Request: Returned if the request payload is not properly formatted.
  • 401 Unauthorized: Returned if the projectId is missing or invalid.
  • 403 Forbidden: Returned if the projectId cannot use this product.
  • 429 Too Many Requests: Returned if the rate limit is exceeded.

Troubleshooting Tips​

  1. Ensure the projectId query parameter is included and correctly set. Replace projectId with your actual Project ID. You can get it from the Histori Dashboard.
  2. Double-check the format of the JSON-RPC request payload.

6. Rate Limits​

Histori's archival RPC node may enforce rate limits to prevent abuse. If you receive a 429 Too Many Requests response, you may need to reduce the frequency of your requests or contact support for higher rate limits. If the underlying RPC provider is rate limiting you, you can use random=true query parameter.

7. Additional Resources​

8. Support​

If you encounter any issues or have questions, reach out to our support team at support@histori.xyz or directly at our (Telegram)[https://t.me/+Khm3XK761_Y1NWI8]