Land transactions, don't just send them.
A Solana transaction sender with JSON-RPC compatibility plus raw HTTP and QUIC relay paths, tuned for landing rate - not just submission. Co-located, route-aware, and you own the retries.
50% OFFLaunch offer on Trader, from $249/mo. Paid onboarding support on request.
◆ OVERVIEW
A transaction sender is the service that delivers your signed transaction to the validators producing upcoming blocks. Instead of forwarding through general-purpose RPC, it resolves the leader schedule and sends through configured fast paths, including direct TPU and Jito routes where authorized.
Sending a transaction is easy; landing it - fast, in the slot you wanted - is the hard part. rpc edge's transaction sender resolves the current and upcoming leaders from the schedule and uses configured fast paths instead of plain public RPC forwarding.
When you need atomicity, ordering, or to bid for inclusion, approved keys can use private Jito routes. Everything runs co-located with the cluster, so the path from your signed transaction to the producing leader keeps avoidable distance low.
Available on Trader from $249/mo.
◆ CAPABILITIES
What Transaction Sender does.
Direct to the leader
Submit through JSON-RPC compatibility, raw HTTP, or QUIC on relay.rpcedge.com.
Jito Block Engine path
Use Jito transaction and bundle routes where they are enabled on your key.
You own the retries
Set maxRetries to 0 and control resubmission within the blockhash window, so you never land a stale action.
Co-located delivery
Every QUIC packet and bundle submission starts next to the cluster, not a region away.
// deliver straight to the leaders that build the next slots
const sig = await rpcedge.sendTransaction(tx, {
route: "tpu", // current + upcoming leaders' TPUs
leaders: 3,
skipPreflight: true,
maxRetries: 0, // you control retries
});
// authorized keys can also bid for inclusion with a Jito bundle
const res = await rpcedge.sendBundle({
transactions: [setupTx, arbTx, cleanupTx],
tipLamports: estimateTip(),
});◆ WHY rpc edge
Latency is a location problem.
Subscribe instead of polling
Yellowstone gRPC pushes filtered account, slot, and transaction updates over one persistent stream, so your bot does not need to rebuild the same polling loop.
Choose the data your workload needs
Use standard RPC for state and history, Yellowstone gRPC for live validator updates, or preprocessed transactions when earlier intent matters to the strategy.
Start shared, move dedicated
Launch on a self-serve plan with included bandwidth. Move to private bare metal, regional placement, and an SLA when traffic or latency requirements justify it.
◆ USE CASES
- Arbitrage and MEV bundles that must land in a specific slot
- Liquidations competing for inclusion under congestion
- Any strategy where landing rate is the bottleneck
Frequently asked questions
What is a Solana transaction sender?
Why send directly to the leader instead of a normal RPC?
When should I use Jito bundles?
◆ GET ACCESS
Land transactions, slot after slot.
Pick a plan and point your client at a scoped endpoint, or talk to the infra team to scope a dedicated, co-located node tuned to your latency and volume.
50% OFFLaunch offer on Trader, from $249/mo. Paid onboarding support on request.
JITO · LEADER
- Direct to the leader
- Jito Block Engine path
- You own the retries
- Co-located delivery