Overview

You may prefer to route your submitted transactions to your blockchain node or a third-party node instead of using our default-supported blockchain nodes. There can be various reasons for this, such as your organization wanting more customization and control (i.e., you want to use nodes with specific, preferred features) or needing to do so for compliance reasons (i.e., you may be obligated to maintain your nodes in-house).

Use scenarios

There are two possible scenarios for using a Node Router.

Static dedicated route

A static dedicated route is when you can provide us with a dedicated node that will be used for all your outgoing transactions by default (API, UI, WC).

On-demand route

An on-demand route is when you can provide us with dedicated nodes that will be used on-demand via API--specifically, the desired node once the transaction API call is created.

Restrictions

• Only a single node can be provided in the Static Dedicated Route case. This node will be used for all vaults related to the tenant
• At this time this feature can work exclusively with EVMs
• Your alternative node is used for operations related to transaction preparation and submission (sendRawTransaction, getTransactionCount). All other operations that are considered publicly available are routed to our default nodes

How to activate Node Router

Contact your Customer Success Manager to activate the node router feature, which routes your transactions to your alternative, non-Fireblocks node.