TriportRPC

sendBundle: Jito + Flashbots from one endpoint

Last updated:

Why bundles

A bundle is an ordered group of transactions that lands atomically — all or nothing, in sequence, invisible to frontrunners until inclusion. On Solana that means Jito block-engine auctions with tip accounts; on Ethereum, Flashbots relay submission that bypasses the public mempool. Normally each rail needs its own integration, endpoints and auth. Through Triport both are one JSON-RPC call away.

Submit a bundle

curl https://triport.io/sol \
  -X POST -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <api-key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"sendBundle","params":[["<base64-tx-1>","<base64-tx-2>"]]}'
# Ethereum: POST https://triport.io/eth with eth_sendBundle params

Pairs well with

Bundle strategies are timing games: the pre-execution stream shows order flow before execution and the first-shred signal marks slot boundaries, so your bundle lands with the freshest possible picture of the chain.

FAQ

Which networks does sendBundle support?
Solana bundles route to Jito block engines; Ethereum bundles route to Flashbots relays. Both are called through the same Triport endpoint and API key — no separate relay accounts or extra auth.
Do I need my own Jito or Flashbots access?
No. Triport handles relay connectivity and signing requirements on the routing side; you submit the bundle over JSON-RPC and receive the relay's bundle id/status.
Which plan includes bundle submission?
sendBundle is available on Pro ($249/mo) and above, alongside trace_*/debug_* namespaces and transaction simulation on Ethereum and Polygon.