Practical overview
When it fits
Use it when developing or evaluating an automated circular-arbitrage workflow across Solana DEX markets, particularly when you need to inspect how quote thresholds, transaction construction, Jito bundles and on-chain profit checks fit together.
Who it is for
- Developers extending Solana DEX arbitrage routes or profit calculations.
- Technical operators working with Solana RPC, swap transactions and Jito bundle submission.
Documented uses
- Find circular arbitrage opportunities, such as WSOL → USDC → WSOL.
- Compare quoted input and output amounts with a minimum profit threshold.
- Build and submit swap transactions as Jito bundles.
- Track execution time and slot information.
- Develop transaction-level checks for realized profit and tip conditions.
Requirements & limits
The repository is public and identifies an MIT license.
- The README gives a current minimum-profit threshold of 3,000 lamports; this is a project setting, not evidence of realized profitability.
- Quote-based checks do not by themselves account for all fees, tips or price changes at execution.
- The README says an on-chain program should validate realized profit and conditionally pay the Jito tip; confirm the implementation before relying on it.
- The repository describes TypeScript code and Solana RPC, Jito, swap instructions and address lookup tables as parts of the workflow.
- The README names pump.fun, Meteora, Raydium and Orca and describes multi-pair support, but does not specify route-adapter interfaces.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Follow the bot’s circular-arbitrage execution flow
Describe how the bot discovers, evaluates, submits, and monitors a circular arbitrage transaction.
Before you start
- A Solana RPC connection for blockhash and address lookup table (ALT) lookup.
- Access to the Jito block engine; the README identifies Frankfurt for bundle submission.
- An on-chain program for checking realized profit and conditioning the Jito tip.
Steps
Continuously query circular routes such as WSOL → USDC → WSOL for quotes.
Compare input and output amounts and proceed only when the potential profit exceeds the stated minimum threshold of 3000 lamports.
Build a versioned transaction with compute-unit limits, setup instructions, both swap legs, and a Jito tip; submit it as a bundle to the Frankfurt block engine.
Monitor execution time and slot information.
Expected outcome
The described flow submits qualifying circular-arbitrage transactions through Jito bundles and tracks execution metrics.
Guide limitations
- A quote-time threshold does not guarantee realized profit: tips, transaction fees, and price movements can cause losses.
- The README says an on-chain program is required to check realized profit and pay the tip only when profit exceeds costs, reverting if profit is insufficient.
- Zero-slippage configuration is listed as supported, but it does not eliminate the stated loss risks.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- WSOL12/Solana-Arbitrage-Bot · Official homepage title · retained in its source language

