Announcing Ironforge RPC Gateway 


Provisioning and managing RPC endpoints

To get started, you'll need to provision your RPC endpoint. You can do this by clicking on the +New RPC button in the RPC Gateway section of the Ironforge dashboard.

In the New RPC modal, you'll need to selected between Triton One, Helius, or Bring your own RPC.

Add new RPC Screenshot

After that just follow the intructions on the next step.

Add new RPC Screenshot

We recommend selecting Triton One or Helius since they are arguably the best providers in the ecosystem, and we have a highly optimized integration with them.

Routing strategies

Ironforge offers two routing methods: Round Robin and Parallel. Each method has its own advantages and considerations.

Screenshot of RPC Routing

Round Robin

The Round Robin routing method follows a sequential order when sending requests to RPC endpoints. When a request is made, Ironforge forwards it to the first available RPC endpoint in the configured list. If the first endpoint responds successfully, Ironforge uses that response. However, if the first endpoint encounters an error or is unavailable, Ironforge automatically moves to the next available endpoint in the sequence. This process continues until a successful response is obtained or all endpoints have been attempted.


The Parallel routing method is designed for maximizing performance and responsiveness. When a request is received, Ironforge simultaneously sends it to all available RPC endpoints. Ironforge then uses the response from the first endpoint that responds successfully, discarding the responses from the remaining endpoints. This approach leverages parallel processing to reduce response times. However, it's important to note that the Parallel method may incur higher costs due to the increased utilization.