ARB Protocol
  • โ™ป๏ธARB Protocol
  • ๐Ÿค–Arbitrage Bot
    • โš™๏ธSetup
      • Preperation
      • Installation
      • Running the bot
    • ๐ŸŽ๏ธOptimization
      • Connection / RPC
      • Jupiter API
      • Configuration
      • Additional Tips
  • ๐Ÿ—๏ธJupGrid
    • ๐Ÿ‘‹Introduction
    • ๐Ÿ› ๏ธInstallation
    • ๐ŸงฎConfiguration
    • ๐Ÿƒโ€โ™‚๏ธUsage
  • References
    • ๐Ÿ’ฑArbitrage
    • ๐Ÿ“V2 Config
    • ๐Ÿ“V2 Env
  • ๐ŸŒŽSocials
    • X (Twitter)
    • Discord
  • ๐Ÿช™ARB
    • Jupiter Swap
    • Birdeye
    • CoinGecko
Powered by GitBook
On this page
  • Simulation
  • Price ranges
  • Profit BPS
  1. Arbitrage Bot
  2. Optimization

Configuration

PreviousJupiter APINextAdditional Tips

Last updated 11 months ago

The botโ€™s configuration is key to its performance. The details all the options available to you, but here are a few things you should look out for:

Simulation

Simulating transactions increases the time-to-chain of each transaction by basically requiring the RPC server to process it twice. Unless youโ€™re paranoid, or you have an extremely good reason to keep it on, we recommend turning it off. catches any non-profitable arbs on-chain and reverts them for you, enabling a brute-force approach to find profitable trades while keeping peace of mind.

Price ranges

Setting a large price range, or high trade size decimals, can slow down the bot by forcing it to check a very similar route twice or more. Keep tight, high ranges to cycle through different routes as fast as possible.

Profit BPS

Setting a high BPS will ultimately make the bot send a lower amount of profitable txs, as it becomes very picky about what it considers for profit. This can be good if youโ€™re looking for high-profit trades, but it also lowers the total trade volume. A good range to start testing would be 5-10bps, with a high trade price.

๐Ÿค–
๐ŸŽ๏ธ
config reference
The ARB Protocol onchain program