Best Performance for Landing Transactions
Last updated
Last updated
To ensure high speed and inclusion rate for singular transactions, follow these guidelines:
Priority Fee:
Add a compute price instruction to your transaction for better prioritization.
Use the to fetch the recommended fee in real-time.
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).
Submission Endpoint Configuration:
frontRunningProtection: false
useStakedRPCs: true
This table summarizes different submission modes by different parameter configurations.
Fastest mode
frontRunningProtection: False,
useStakedRPCs: True
Yes. Min: 0.001 SOL
Max speed by leveraging staked RPC connections.
Ideal for time-sensitive transactions.
MEV protected mode
frontRunningProtection: True
Yes. Min: 0.001 SOL
Protects against MEV attacks using Jito bundles.
Slightly slower if consecutive non-Jito validators are present.
In-the-middle mode
frontRunningProtection: True,
fastBestEffort: True
Yes. Min: 0.001 SOL
Balances speed and protection by propagating to Jito and low-risk validators.
Low-risk validators are identified by bloXroute.
Use the to determine an optimal tip amount.
If your language of choice is not included above, you can create an instruction referencing our
Use the with the following parameters for best performance: