Configuring Blockchain RPC Providers for DEX Trading Connectivity

# Overview


## Overview

Starting with [v2.9.0](../release-notes/2.9.0.md), deep integrations with leading RPC providers like Helius and Infura are available to optimize speed and reduce latency for DEX trading. [v2.15.1](../release-notes/2.15.1.md) adds Chainstack as a cross-chain provider for both Solana and EVM networks.

The RPC provider controls your bot's connection to the blockchain network, which is crucial in DEX trading because it directly impacts the speed, reliability, and security of your transactions. A robust node connection ensures:

- **Low Latency:** Faster order placement and execution with greater rate limits.
- **High Availability:** Reliable access to blockchain data, minimizing downtime or missed trades.
- **Accurate Data:** Up-to-date blockchain state for price feeds, balances, and transaction statuses.
- **MEV Protection:** Direct connections to trusted nodes help reduce the risk of having your transactions front-run or  sandwiched.

## Setup

When you set up Gateway initially, the standard `nodeURL` for each network uses default public RPC endpoints. 

By adding an API key from a RPC provider (as shown below), you will override the default `nodeURL` for each supported network, ensuring more reliable and performant blockchain connectivity. This step is essential for optimal DEX trading performance.

All RPC provider API keys are stored centrally in `conf/apiKeys.yml`. After adding a key, set `rpcProvider` to the provider's name in the relevant chain config (`conf/chains/solana.yml` or `conf/chains/ethereum.yml`).

Run `gateway ping` to check your current network and node connection:

```
>>> gateway ping

Gateway service is online.
Testing network status for 2 chains... 

ethereum (mainnet):





solana (mainnet-beta): 




```

## Supported Providers

### Helius

[Helius](https://www.helius.dev/) is a leading Solana validator and infrastructure provider, offering fast, reliable, and scalable RPC endpoints and other services.

**Helius Supported Networks:**

| Chain | Network |
|-------|---------|
| solana | mainnet-beta |
| solana | devnet |

**Adding Helius API Keys:**

1. Create a free account at [Helius](https://helius.dev/) to get your API key

2. Run `gateway config apiKeys update` and set the `helius` value. Alternatively, modify the file `conf/apiKeys.yml` and restart Gateway.

3. Run `gateway config solana update` and change `rpcProvider` from `url` to `helius`. Alternatively, modify the file `conf/chains/solana.yml` and restart Gateway.

**Helius Configuration**

Set your Helius API key in the centralized `conf/apiKeys.yml` file:

```yaml
helius: 'YOUR_HELIUS_API_KEY'
```

When Helius is the active provider, Gateway automatically uses its WebSocket endpoint for faster transaction confirmation monitoring.

### Infura

[Infura](https://www.infura.io/), a division of Metamask, is a leading RPC provider for EVM-based networks.

**Infura Supported Networks:**

| Chain      | Network           | Chain ID            |
|------------|-------------------|---------------------|
| ethereum   | mainnet           | 1                   |
| ethereum   | arbitrum          | 42161               |
| ethereum   | avalanche         | 43114               |
| ethereum   | base              | 8453                |
| ethereum   | bsc               | 56                  |
| ethereum   | celo              | 42220               |
| ethereum   | polygon           | 137                 |
| ethereum   | sepolia           | 11155111            |

**Adding Infura API Key:**

1. Create a free account at [Infura](https://app.infura.io/) to get your API key

2. Run `gateway config apiKeys update` and set the `infura` value. Alternatively, modify the file `conf/apiKeys.yml` and restart Gateway.

3. Run `gateway config ethereum update` and change `rpcProvider` from `url` to `infura`. Alternatively, modify the file `conf/chains/ethereum.yml` and restart Gateway.

**Infura Configuration:**

Set your Infura API key in the centralized `conf/apiKeys.yml` file:

```yaml
infura: 'YOUR_INFURA_API_KEY'
```

### Chainstack

[Chainstack](https://chainstack.com/) is a multi-chain RPC provider covering both EVM networks and Solana. Unlike URL-templated providers, Chainstack uses **API-driven node discovery** — Gateway calls the Chainstack Platform API at startup and routes traffic to a node you have already deployed in your Chainstack project.

**Chainstack Supported Networks:**

| Chain    | Networks                                                                  |
|----------|---------------------------------------------------------------------------|
| ethereum | mainnet, arbitrum, polygon, optimism, base, avalanche, bsc, celo, sepolia |
| solana   | mainnet-beta, devnet                                                      |

Chainstack supports 50+ protocols on the platform. The networks above are the ones currently routable through Gateway; as Gateway adds support for new chains, Chainstack coverage extends without additional configuration.

**Adding Chainstack API Key:**

1. Deploy a node for your target network at the [Chainstack console](https://console.chainstack.com/). Chainstack discovery requires a running node to route to.

2. Create an API key at [console.chainstack.com/user/settings/api-keys](https://console.chainstack.com/user/settings/api-keys).

3. Run `gateway config apiKeys update` and set the value for `chainstack`. Alternatively, modify the file `conf/apiKeys.yml` and restart Gateway.

4. Run `gateway config ethereum update` and/or `gateway config solana update` and change `rpcProvider` from `url` to `chainstack`. Alternatively, modify the files `conf/chains/ethereum.yml` / `conf/chains/solana.yml` and restart Gateway.

**Chainstack Configuration:**

Set your Chainstack API key in the centralized `conf/apiKeys.yml` file:

```yaml
chainstack: 'YOUR_CHAINSTACK_API_KEY'
```

No additional configuration is required. Gateway automatically discovers and routes to the first running node in your Chainstack project that matches the active chain and network.

## Troubleshooting

#### Provider Not Connecting
- Run `gateway ping` to assess connection
- Verify API key is correct
- Check network configuration

#### Rate Limiting
- Change Hummingbot `tick_size` to a higher number
- Consider upgrading to a paid tier for better performance
- Distribute usage across multiple API keys