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
  1. Arbitrage Bot
  2. Optimization

Connection / RPC

There are two main components to the botโ€™s connection:

  1. The Solana RPC

  2. The Jupiter API

The Remote Procedural Call (RPC) server is how the bot connects to the Solana network. A fast, reliable RPC is essential to ensure the bot can send transactions quickly.

Enhancing Speed:

  • Leader Information Solutions: Utilize solutions like Helius, Atlas, and Blockworksโ€™ Lite-RPC to send transactions directly to the network leaders, bypassing the default RPC speed limitations.

  • Geyser GRPC: For even faster performance, use a Geyser GRPC to stream data directly to nodes, avoiding additional RPC server delays. This typically requires setting up your own RPC, though some providers and community members offer standalone GRPC services.

PreviousOptimizationNextJupiter API

Last updated 11 months ago

๐Ÿค–
๐ŸŽ๏ธ