Helius Sender: Ultra-Low Latency Solana Transaction Submission
Ultra-low latency Solana transaction submission with dual routing to validators and Jito infrastructure. No credits consumed, global endpoints, optimized for high-frequency trading.
Overview
Helius Sender is a specialized service for ultra-low latency transaction submission. It optimizes transaction latency by sending to both Solana validators and Jito simultaneously, providing multiple pathways for your transactions to be included in blocks.
Dual Routing
Sends to both validators and Jito for optimal speed
Global Endpoints
Multiple geographic locations for minimal latency
No Credits
Available on all plans without consuming API credits
High Throughput
Default 3 TPS, contact us for higher limits
Routing Options
Default Dual Routing: Sends transactions to both Solana validators and Jito infrastructure simultaneously for maximum inclusion probability. Requires minimum 0.001 SOL tip.
SWQOS-Only Alternative: For cost-optimized trading, add ?swqos_only=true
to any endpoint URL. This routes exclusively through SWQOS infrastructure with a lower 0.0005 SOL minimum tip requirement. Best for high-frequency strategies where tip costs accumulate.
Requirements
Mandatory Requirements: All transactions must include tips (0.001 SOL minimum, or 0.0005 SOL for SWQOS-only), priority fees, and skip preflight checks.
1. Skip Preflight (Mandatory)
The skipPreflight
parameter must be set to true
. Sender is optimized for traders who prioritize speed over transaction validation.
Since preflight checks are skipped, ensure your transactions are properly constructed and funded before submission. Invalid transactions will be rejected by the network after submission.
2. Tips and Priority Fees Required
All transactions submitted through Sender must include both tips and priority fees:
- Tips: Minimum 0.001 SOL transfer to a designated tip account (or 0.0005 SOL for SWQOS-only)
Designated Tip Accounts (mainnet-beta)
Designated Tip Accounts (mainnet-beta)
- Priority Fees: Compute unit pricing via
ComputeBudgetProgram.setComputeUnitPrice
to prioritize your transaction in the validator queue
Why Both Are Required
- Tips: Enable access to Jito’s MEV infrastructure and auction-based transaction inclusion
- Priority Fees: Signal to validators your willingness to pay for priority processing through Solana’s native prioritization system
- Dual Benefit: Tips give you access to Jito’s MEV auction, while priority fees improve your transaction’s priority with validators—together they maximize inclusion probability
Tip and Priority Fee Guidelines
Jito Tips: Minimum 0.001 SOL is mandatory for auction participation. For current best-practice tip sizing, see the Jito tip guidelines.
Priority Fees: Use the Helius Priority Fee API for real-time fee recommendations.
Endpoints
Sender endpoints are available in multiple regions for optimal latency:
Transaction Submission:
Connection Warming:
These endpoints only support HTTP connections (not HTTPS). Choose the endpoint closest to your infrastructure for optimal performance.
Connection Warming
For applications with long periods between transaction submissions, use the ping endpoint to maintain warm connections and reduce cold start latency.
Ping Endpoint Usage
The ping endpoint accepts simple GET requests and returns a basic response to keep connections alive:
Use connection warming when your application has gaps longer than 1 minute between transactions to maintain optimal submission latency.
Usage
The Sender endpoint uses the same sendTransaction
method as standard RPC endpoints but with specific requirements for optimal performance. All transactions must include both tips and priority fees, plus skip preflight checks.
Basic Request Format
The BASE64_ENCODED_TRANSACTION
above must contain both a SOL transfer instruction with minimum tip to designated tip accounts AND a compute unit price instruction. Without both requirements, your transaction will be rejected.
Simple Code Example
Advanced Example with Dynamic Optimization
The advanced example improves on the simple version with dynamic Jito tips (75th percentile), automatic compute unit calculation, dynamic priority fees, and retry logic.
Best Practices
Endpoint Selection
- Salt Lake City:
slc-sender.helius-rpc.com/fast
- Newark:
ewr-sender.helius-rpc.com/fast
- London:
lon-sender.helius-rpc.com/fast
- Frankfurt:
fra-sender.helius-rpc.com/fast
- Amsterdam:
ams-sender.helius-rpc.com/fast
- Singapore:
sg-sender.helius-rpc.com/fast
- Tokyo:
tyo-sender.helius-rpc.com/fast
For optimal latency, consider co-locating with Helius servers in Frankfurt or London.
Connection Warming
- Use the
/ping
endpoint during idle periods longer than 1 minute - Implement periodic ping calls (every 30-60 seconds) to maintain warm connections
- Warm connections before high-frequency trading sessions begin
Transaction Setup
- Use
skipPreflight: true
andmaxRetries: 0
- Implement your own retry logic
- Include minimum 0.001 SOL tip to designated accounts
- Fetch blockhash with
'confirmed'
commitment - Set appropriate compute unit limits
Rate Limits and Scaling
- Default Rate Limit: 3 transactions per second
- No Credit Usage: Sender transactions don’t consume API credits from your plan
Support and Scaling
For production deployments requiring higher throughput:
- Create a Support Ticket: Include your expected TPS and use case details
- Provide Metrics: Share your current transaction patterns
Contact support through the Helius Dashboard or join our Discord community.