Best Performance for Landing Transactions

Optimizing Transaction Performance

circle-info

For paid tiers, bloXroute automatically enhances transaction propagation using multiple advanced features.

To ensure high speed and inclusion rate for singular transactions, follow these guidelines:

1. Priority Fee:

  • Add a compute price instruction to your transaction for better prioritization.

  • Use the Priority Fee Stream to fetch the recommended fee in real-time.

const modifyComputeUnits = ComputeBudgetProgram.setComputeUnitLimit({ 
  units: 1000000 
});

const addPriorityFee = ComputeBudgetProgram.setComputeUnitPrice({ 
  microLamports: 1 
});

const transaction = new Transaction()
.add(modifyComputeUnits)
.add(addPriorityFee)
...
  );

2. Include a Tip Instruction:

  • Ensure your transaction includes a tip for enhanced propagation.

  • The service fee is based on the features used (e.g., staked connections).

  • Use the Bundle Tip Stream to determine an optimal tip amount.

If your language of choice is not included above, you can create an instruction referencing our tip-receiving addresses

3. Submission Endpoint Configuration:

  • Use the submit endpoint (*You shall submit the transaction to the closest region and the global endpoint in parallel) with the following parameters for best performance:

    • frontRunningProtection: false

    • useStakedRPCs: true

    • submitProtection: SP_LOW

4. Send to the right regions

Global — Submit ONLY

Use the Global endpoint to automatically route your transaction submits to the closest Trader API transaction-handling instances. This reduces end-to-end latency and improves landing performance—especially when your bot is within ~2 ms RTT of a Trader API region. For best results, send to the Global endpoint in parallel with your preferred regional endpoint(s).

Host: global.solana.dex.blxrbdn.com

How to use

  • Primary target: Point your Trader API base URL/host to the Global endpoint

  • Parallelization: Also send the same transaction to your nearest regional endpoint(s) in parallel to maximize time-to-first-land.

  • No other config changes needed.

  • Global supports http, https, ws, wss, and gRPC

Region
Host

Global (recommended)

global.solana.dex.blxrbdn.com

circle-check

Choose your closest region

For consistent best performance, pair the Global endpoint with the closest region to where your bot runs.

  • Find regions & hosts: See the full, always-updated list here: https://docs.bloxroute.com/solana/trader-api/introduction/regionsarrow-up-right

  • Pick the nearest region: Choose the region with the lowest RTT from your bot host. If you’re already ~2 ms from a Trader API region, the Global endpoint will typically select it—and parallel sends ensure you still catch the fastest path.

  • Practical tip: Measure latency from the same machine that runs your bot.

Latency check examples

Parallel submit pattern (pseudo-code)

Guidance

  • Always include Global in your send set.

  • Add 1–2 closest regions in parallel for resilience and the best possible landing time.

  • Keep your region list current using the Regions page linked above.

5. Make sure to keep the HTTP connection live.

The maximum duration for the Trader API keep-live is about 60 seconds. We recommended doing a "keep-live" request every 60 seconds

Commonly used Submission Modes.

This table summarizes different submission modes by different parameter configurations.

Mode - Nickname
Parameter config
Minimum Tip
Description

Fastest mode

frontRunningProtection: False, useStakedRPCs: True, submitProtection: SP_LOW

0.001 SOL

  • Max speed by leveraging staked RPC connections.

  • Ideal for time-sensitive transactions.

MEV-protected mode

frontRunningProtection: True, submitProtection: SP_MEDIUM

0.001 SOL

  • Protects against MEV attacks based on the bloXroute Malicious Leader detection system.

  • Slightly slower if consecutive flagged malicious validators are present.

  • submitProtection: SP_HIGH can be used to further the MEV protection level.

Transaction Revert Protection

frontRunningProtection: True, reverProtection: True

0.001 SOL

  • Transactions will only be sent to the Jito block engine and the Paladin leader.

  • Failed transactions won't land on the chain.

  • This method is the slowest method as no public RPC propagation channels will be used. If consecutive non-Jito nor non-Paladin validators are present, it could be even slower.

Last updated