Skip to main content
Parameters enable optimizations and incident management for your transactions on the fly—without having to redeploy your project. Changes take effect in real time, allowing you to fine-tune configurations based on performance feedback.
The network can often become congested during times of high usage, leading to a noticeable drop in transaction landing rates. During such instances, you can now simply update your parameters to increase the chances of your transactions landing.
The parameters currently available are as follows,

​
Compute Unit (CU) Price:

This parameter allows you to select the amount of price per compute unit you wish to pay. Each range corresponds to a percentile of CU Price paid in transactions that have landed previously on the Solana network:
  • Low: 25th percentile
  • Median: 50th percentile
  • High: 90th percentile

​
Jito Configuration:

  • Tip Amount: Select the tip amount for your transaction from these options:
    • Low: 25th percentile
    • Median: 50th percentile
    • High: 75th percentile
    • MAX: 99th percentile
Delivery Delay: Use this to set how long Gateway waits (in milliseconds) before sending transactions to Jito after attempting RPC delivery. If a transaction is successfully delivered via RPC, the Jito tip is refunded automatically.

​
Delivery Methods:

This section allows you to select and manage delivery methods from your organization for the current project.
  • Creating a delivery method from the parameters sidebar automatically links it to the current project. Once linked, this delivery method will be utilized whenever delivery requests are made for this specific project.
    • Delivery methods created from the delivery methods page will be available organization-wide but won’t be linked automatically to any specific project. They must be manually linked to be utilized for delivery requests.
  • You can manage linked delivery methods in two ways:
    • Unlinking a delivery method removes it from the current project but keeps it accessible for use in other projects within your organization.
    • Deleting a delivery method permanently removes it from your entire organization and all associated projects.

​
Transaction Routing

This parameter helps you to build your transactions so that one can distribute their transaction traffic between multiple delivery methods. Gateway currently uses a weighted sampling algorithm for distributing your transaction traffic. Depending on the weights one configures, the getTipInstructions and buildGatewayTransaction JSON-RPC methods respond with appropriate tip instructions and transaction respectively. The following image depicts how one would configure their weights to route **50% of their transactions to Sanctum Sender, 30% **to regular RPCs and **20% **to any other configured transaction sender, Transaction Routing Pn

​
Transaction Expiry:

This parameter allows you to configure your transaction to expire in the specified amount of slots. This is done by setting a latestBlockhash for your transaction according to your configuration. Since every transaction, by default, is valid for 150 blocks starting from the blockhash set in the transaction, we can thus calculate which blockhash to use so that your transaction expires in the specified number of slots.

​
Next Steps

  • Learn how to integrate Gateway endpoints here
  • Learn how to build your transactions here
⌘I