The Challenge: Inconsistent Transaction Landing
On Solana, transaction landing can become inconsistent because of:- Blockchain congestion during peak periods
- Network latency between clients, relays, and leaders
- Differences in infrastructure quality
This uncertainty has the biggest impact on power users such as traders, bots,
and dApps, where execution quality and consistency are critical.
Our Solution: Stake-Enabled, Multi-Path Submission
Stellium uses staked connections and automatically submits transactions to validator leaders through low-latency routes. By optimizing the networking stack end to end, Stellium improves landing rates and reduces transaction finality times.API Usage
Stellium accepts the standard SolanasendTransaction JSON-RPC format:
$UUID is a unique ID generated by the user for request identification.Regions
We provide regional endpoints in Frankfurt, Amsterdam, New York, London, Tokyo, Dublin, Singapore, and Lithuania.Contact us for endpoint access or to request additional regions. Please avoid testing on unsupported regions.
Transaction Tip
Each transaction requires a system transfer instruction to one of the Stellium tip addresses below with a minimum tip of 0.001 SOL. Use any of these Solana addresses for transaction tips to improve priority:Keep Alive
To keep your connection warm, send a lightweightGET request to the same API URL you use for sendTransaction.
Use this as a heartbeat every 60 seconds when traffic is idle. It does not submit a transaction.
API Reference
Integrate acceleration into your dApp