Transaction Submission

This page guides you on submitting transactions using bloXroute's Solana Trader API and optimizing for speed and reliability.

How It Works

• The Trader API broadcasts your transactions to multiple RPC endpoints, including self-hosted, external, and staked RPCs.

• Your service tier and submission parameters control how transactions are propagated.

Optimizing Transaction Submission

1. Priority Fee:

   • Pay additional fees to Solana validators to prioritize your transactions.

   • Use the Priority Fee Stream to get real-time market data and determine the optimal fee.

2. Tips:

Tips serve multiple purposes in transaction submission:

• Front-Running Protection: When enabled (frontRunningProtection=True), the Trader API limits who receives the transaction to protect against front-running. This works alongside the fastBestEffort parameter:

  • fastBestEffort=True: Transactions are submitted to Jito as a bundle and to leaders identified as low-risk for front-running.

  • fastBestEffort=False: Transactions are submitted only to Jito, offering a balance of MEV protection and performance.

  • Note: While bloXroute uses best-effort methods to identify low-risk validators, there is no absolute guarantee against attacks.

• Staked RPCs: Enabling this parameter (useStakedRPCs=True) ensures your transaction is sent directly to the leader through a staked validator connection.

  • Requirements:

Use the Bundle Tip Stream to calculate appropriate tip amounts.

➡️ Next Steps: Submit your first transaction or learn more about Front-Running Protection, Revert Protection, & Transaction Bundling.