Skip to main content
Gateway categorises the various of ways of sending transactions to the Solana network as Delivery Methods. They are as follows,
  • RPCs/SWQoS
  • Jito Bundles
  • Transaction Senders, such as Sanctum Sender, Nozomi, etc.
Gateway allows you to configure appropriate delivery methods based on your project’s requirements, which are then used to send your transactions to the Solana network. The delivery methods currently supported by Gateway are as follows,

​
RPCs/SWQoS

RPCs are the most common way of sending transactions to Solana nodes. You can an RPC URL for many RPC providers such as Triton One, Quicknode, etc. One can also use set up SWQoS solutions such as Triton Cascade to use with Gateway.

​
Configuration for RPC:

  • Name: Identifier for this method.
  • Cluster: Select between devnet (for testing) or mainnet.
  • URL: Endpoint URL of the RPC node. Any URL that supports sendTransaction JSON-RPC method and requires no additional tip of any sorts will work here.

​
Jito Bundles

Jito is an enhanced validator client (Jito-Solana) that allows transactions to be bundled and sent through Jito’s Block Engine using relays. These bundles participate in an auction, where the amount tipped determines which transactions are included on the network. Since most Solana validators now run Jito, transactions delivered via this method benefit from much faster execution and higher success rates at the price of an additional tip. Gateway sends each of your transactions as individual Jito bundles which include a refundable tip. You can leverage this along with sending transactions to RPCs to not only increase landing rates but also lower your tip expenses.

​
Configuration for Jito:

  • Name: Identifier for this method.
  • Region or URL:
    • Select a predefined region to use Jito’s default endpoints (Rate limit: 1 request per second)
    • Provide your custom Jito endpoint URL for higher throughput without enforced rate-limiting.

​
Sanctum Sender

Sanctum Sender is Sanctum’s transaction submission service. It optimizes transaction submission by leveraging SWQoS and Jito simultaneously, providing multiple pathways for your transactions to be included in blocks. All new projects on Gateway are provider with a Sanctum Sender delivery method by default, making it the easiest way for teams to start sending transactions. There is currently only one global URL for using Sanctum Sender. Hence, no further configuration is required.

​
Helius Sender

Helius Sender is Helius’ transaction submission service. It optimizes transaction latency by sending to both Solana validators and Jito simultaneously, providing multiple pathways for your transactions to be included in blocks.

​
Configuration for Jito:

  • Name: Identifier for this method.
  • Region:
    • Select a predefined region to use Jito’s default endpoints (Rate limit: 6 TPS)
⌘I