SolanaMevBot
DeprecatedJupiter Bot (Deprecated)

Common Workflow

Common tasks and workflows for the Jupiter bot

Deprecated: This is for the Jupiter bot, which is in maintenance mode.

Upgrade

  1. Download the new release
  2. Extract to the same directory (or a new one)
  3. Copy your config.yaml to the new directory
  4. Restart the bot

Downgrade

Same as upgrade — download the older version and use your existing config.

Run in Background

screen -S smb
./run.sh
# Ctrl+A, D to detach

Reattach: screen -r smb

Multiple Bots with One Jupiter API

Run the Jupiter API once, then point multiple bot instances to it:

# Bot 1
JUPITER:
  PORT: 18080

# Bot 2 (same machine, different config)
JUPITER:
  PORT: 18080  # Same port, reuses the running instance

Save Logs

./run.sh 2>&1 | tee bot.log

Migrate from 0.2.x to 0.3.x

The config format changed between versions. Key differences:

  • YAML structure reorganized
  • New strategy names (blind_quote replaces old naming)
  • Jito config simplified

Use Multiple IPs

For advanced users running on servers with multiple IPs:

# Route specific traffic through a different IP
iptables -t nat -A POSTROUTING -d <JITO_IP> -j SNAT --to-source <YOUR_SECOND_IP>

This allows you to send Jito bundles from multiple IPs to avoid rate limits.

Switch Config Files

./run.sh --config another-config.yaml

On this page