When an app sponsors several Solana transactions, it needs them to be handled as one operation. If one lands while another is dropped or reordered, the app can end up in an inconsistent state—and the user sees a failed flow despite having signed nothing and paid no gas.
Openfort now submits sponsored Solana transaction batches through Jito bundles, using Quicknode's integrated Jito Bundler.
How it works
A Jito bundle is all-or-nothing: the transactions in the bundle execute in order, or the bundle does not execute. That is particularly useful for sponsored flows that depend on multiple transactions succeeding together.
For Openfort developers, there is nothing new to configure. Sponsored Solana transactions automatically use this path where applicable.
"We chose Quicknode because its Jito Bundler is integrated directly with its RPC infrastructure. That removes an extra provider and network hop from our transaction path, while giving us a more tightly integrated setup for sponsored Solana transactions."
— Joan Alavedra, Co-founder, Openfort
What it gives your app
- Atomic batch execution — dependent sponsored transactions do not partially execute
- Ordered submission — transactions within a bundle preserve their intended sequence
- Less infrastructure to operate — RPC and bundle submission are provided through Quicknode
Why it matters
For financial and trading applications, transaction execution is not an implementation detail. If a multi-step flow cannot reliably complete as a unit, "gasless" UX is irrelevant. Jito bundle submission is one part of making sponsored Solana transactions behave predictably in production.
Related reading
- Gasless transactions on Solana — sponsor gas so users transact without holding SOL, with code
- Announcing Openfort for Solana — our initial Solana launch and roadmap
- How to set up gasless transactions — the full EVM and Solana implementation guide
- Backend wallets — server-side wallet management for automated operations
