🔗Transaction Submission

This page explains the bloXroute Trader API transaction(s) submission and how can you optimise your transaction submission.

Unlike a traditional RPC service provider, bloXroute Trader API sends your transactions to a handful of self-hosted node RPCs, external RPCs, and staked RPCs. The amount of channels is determined by the tier of your service and the submission controlling parameters you specified for your transaction.

bloXroute Solana Trader API will propagate transactions ONLY if they are marked with bloXroute memo Instruction. Transactions created with Trader API endpoints will automatically include the bloXroute memo instruction. Traders can also construct their own transactions and add the bloXroute memo instruction.

*Elite & Ultra tier customers will be exempted if the transaction submitted includes a tipping instruction, to save an instruction in the transaction.

• Controlling Transaction Submission

  • Understand Priority Fee

  • Understand Tip

Controlling Transaction Submission

Understand Priority Fee

Solana priority fees are additional fees you can specify and pay to Solana validators in order to increase the likelihood of your transactions being processed more quickly. For traders who are competing against the same trading/snipping/arbitration opportunities, the priority fees could be very high during any peak period.

Gaining access to live-time priority fee market information will help the trader to determine a good priority fee and act accordingly.

bloXroute Trader API provides a Priority Fee Stream to help you make decisions.

Understand Tip

Tip performs multiple important roles in submitting transactions through bloXroute Trader API. When you submit a transaction with a tip, you will have multiple options to control the submission flow.

1. frontRunningProtection When enabling this parameter (set to True) Trader API will limit who will get the transactions in order to protect from front running. An additional parameter fastBestEffort controls the behavior of Trader API. When enabling the fastBestEffort Trader API will submit the transaction to Jito as a bundle as well as leaders identified as low-risk for front running. When setting this parameter to False, only Jito will get the transaction. This is an option for users who want a good level of MEV protection but still want speed performance. Low-risk validators are identified with bloXroute's best effort. However, there is no guarantee that your transaction will never be attacked. If you want to learn more about transaction bundling servicer, you can refer to the page “Front-Running Protection & Transaction Bundle” for more details.

2. useStakedRPCs Enabling this parameter (set to True) will guarantee your transaction to be directly submitted to the Leader through a staked validator connection. frontRunningProtection must be set to False and a minimum tip of 0.001 SOL is required to use this feature. The cost will be 10% of the tip amount.

Similar to the Priority Fee Stream, we also provide a Bundle Tip Stream to help you decide the right tip amount for your transactions.