Skip to main content
TLDR:
  • Hummingbot Gateway v2.15 adds Chainstack as a built-in RPC provider for both Solana and EVM networks.
  • You set rpcProvider: chainstack and add one Platform API key. Gateway calls the Chainstack Platform API and routes to a node you already deployed, so there are no per-chain endpoint URLs to paste or rotate.
  • It is the only Gateway provider that spans Solana and all nine supported EVM chains from a single key.
  • This guide covers deploying nodes, configuring the provider, and verifying live swap quotes on Solana and Ethereum.

​
What this integration does

Hummingbot is an open-source framework for building market-making and arbitrage bots. Gateway is its standalone API server that connects those bots to DEXs such as Jupiter, Meteora, Raydium, Orca, and Uniswap. Every quote, swap, and liquidity action Gateway performs runs through an RPC node. By default Gateway points at public RPC endpoints, which rate-limit and drop requests under trading load. As of v2.15 you can route Gateway through your Chainstack nodes instead, for lower latency and more reliable execution.
What makes Chainstack different hereOther providers want a manually configured endpoint per network. Chainstack uses the Chainstack Platform API to discover and configure your deployed nodes automatically. One key covers both Solana and EVM, with no endpoint URLs to manage.

​
Run Solana and EVM nodes on Chainstack

You can run global, regional, or warp transaction nodes with Chainstack. Warp routes your sends through a faster propagation path, made for latency-sensitive trades like arbitrage.Start for free and get your app to production levels immediately. No credit card required. You can sign up with your GitHub, X, Google, or Microsoft account.

​
Prerequisites

Before starting, ensure you have: The key here is the Platform API key, not a node endpoint authorization key. The Platform API key is what lets Gateway discover your nodes automatically.

​
Supported networks

Chainstack discovery in Gateway covers:
  • EVM — Ethereum, Arbitrum, Polygon, Optimism, Base, Avalanche, BNB Smart Chain, Celo, and Ethereum Sepolia.
  • Solana — mainnet-beta and devnet.

​
Configure Gateway

1

Deploy your nodes

Deploy a node for each network your bot trades on. For production market making and arbitrage, use Trader Nodes — dedicated resources keep latency low and avoid the rate limits of shared endpoints.For example, deploy a Solana mainnet node and an Ethereum mainnet node in the same project.
2

Create a Platform API key

On your Chainstack account, navigate to Settings > API keys > Create key. Give it a descriptive name, such as Hummingbot Gateway, and copy the generated key.See Chainstack Platform API: getting started for details.
3

Add the key to apiKeys.yml

In your Gateway conf/apiKeys.yml, set the chainstack field to your Platform API key:
chainstack: 'YOUR_CHAINSTACK_PLATFORM_API_KEY'
4

Set the RPC provider per chain

In the chain configuration files, set rpcProvider to chainstack. There are no endpoint URLs to add — Gateway resolves them from your account.
defaultNetwork: mainnet-beta
rpcProvider: chainstack
5

Start Gateway and verify

Start Gateway as you normally would (see the Hummingbot Gateway docs). On startup, each configured chain discovers its node:
Chainstack API key configured
Chainstack service initialized: node ND-123-456-789 (solana/solana-mainnet) for solana/mainnet-beta
Solana (defaultNetwork: mainnet-beta): Block #427,223,441
Chainstack service initialized: node ND-987-654-321 (ethereum/ethereum-mainnet) for ethereum/mainnet
Ethereum (defaultNetwork: mainnet): Block #25,342,330
Confirm a chain is live with a status call:
curl "http://localhost:15888/chains/solana/status?network=mainnet-beta"
Then pull a read-only swap quote through a connector to confirm the full path works. The quote is routed through your Chainstack node:
curl "http://localhost:15888/connectors/jupiter/router/quote-swap?network=mainnet-beta&baseToken=SOL&quoteToken=USDC&amount=1&side=SELL"
A successful quote returns the output amount, route, and price impact — confirming Gateway is reading chain state through your Chainstack node.

​
How auto-discovery works

When Gateway initializes a chain with rpcProvider: chainstack, it calls the Chainstack Platform API, finds the running node that matches the chain and network, and uses that node’s endpoint for all RPC. You never paste a node URL.
Gateway selects the first running node that matches the chain and network. For predictable selection, keep one node per network in the project tied to your API key.

​
Use a paid node for production trading

Free Developer-plan nodes are rate-limited and restrict some Solana methods. In particular, getProgramAccounts and getTokenAccountsByOwner — used for SPL token balances — require a paid plan, so token-balance and some swap operations fail on the free tier. For live trading, run a paid Trader Node. It serves these methods and gives you dedicated throughput. See pricing for plan limits.

​
Troubleshooting

​
No running Chainstack node found

Gateway could not match a running node to the chain and network. Check that the node exists in the account tied to your Platform API key, that it is running, and that its network matches the Gateway defaultNetwork (for example, a solana-mainnet node for mainnet-beta).

​
Chainstack API key is missing or invalid

Confirm the chainstack field in conf/apiKeys.yml holds a Platform API key from Settings > API keys, not a node endpoint authorization key.

​
Method requires plan upgrade

The node is on the free Developer plan and the connector called a paid-only method, such as getProgramAccounts on Solana. Move to a paid Trader Node.
Last modified on June 18, 2026