3.2 CLI Terminal

The CLI terminal is the reference implementation that ships with the repo.

3.2.1 How it looks

Once you run the engine, you’ll see:

• A header (what DEXs are monitored, min profit threshold, etc.).

• A streaming list of opportunity lines.

• A “stats” line that keeps updating.

Example (schematic):

Capture Engine - Real-time Solana Arbitrage
Monitoring DEXs: Jupiter, Raydium, Orca, Phoenix
Minimum profit threshold: 0.10%
---------------------------------------------------------
[16:15:02] SOL/USDC | jupiter@X → raydium@Y | spread Z% | profit 1.20% (120bps)
[16:15:05] JUP/USDC | orca@... → phoenix@... | spread ... | profit 0.65% (65bps)
...

Stats: 23 opportunities | Avg: 0.78% | Best: 2.10%

Each new line is one snapshot of “here’s a potentially profitable route right now”.

3.2.2 What each part means

• Header

  • Which DEXs/aggregators are included.

  • Current minimum profit threshold in %.

• Opportunity lines

  • Pair: SOL/USDC, JUP/USDC, etc.

  • Route: buy venue@price → sell venue@price.

  • Spread: raw price difference.

  • Profit: estimated net % and bps.

• Stats line

  • N opportunities: count since you started the engine.

  • Avg: average profit % across those opportunities.

  • Best: highest profit % opportunity seen.

3.2.3 How to use it in practice

Minimal workflow:

1. Watch the stream for green/high-bps lines.

2. When you see something interesting:

   • Cross-check the prices on your own aggregator/DEX UI or via API.

   • Decide if the spread is worth your size and risk.

3. Execute manually using:

   • Your own wallet.

   • Your preferred route builder / aggregator.

The CLI terminal is for power users who are comfortable reading text streams and driving their own execution.