General Options

This section describes general bot settings responsible for connecting to the Solana network and working with the wallet.

---

REGION_DETECTOR

Description: Determines the method for selecting the region in which the bot is physically located. This setting is used to optimize network latency when interacting with infrastructure services — primarily transaction processors.

Purpose: Each processor (JITO, ZERO_SLOT, NOZOMI, etc.) has regional endpoints located closer to specific geographic points. The bot automatically selects the optimal endpoint for all services to minimize ping.

Options:

• MODE - Region detector operating mode:

  • "AUTO" - automatic region detection by the server's IP address via geolocation

  • "DEFAULT" - use the explicitly specified region from the DEFAULT field

• DEFAULT - Region to use:

  • In DEFAULT - is used as the primary region

  • In AUTO - is used as a fallback if auto-detection fails

Example:

# Region detection configuration
[REGION_DETECTOR]
# Region detection mode: AUTO (auto-detect) or DEFAULT (use specified region)
MODE = "AUTO"
# Default/fallback region to use.
# Available: DE, AMS, LON, NY, SLC, VA, TOKYO, SIN
DEFAULT = "NY"

Supported values: DE, AMS, LON, NY, SLC, VA, TOKYO, SIN

---

PAYER_PRIVATE_KEY

Description: Private key of the main wallet used by the bot to perform all operations. The key is provided in Base58 format and serves as the sole source of signatures for all transactions created by the system.

• The private key is stored exclusively on the user's side and is never sent to an external server.

• Neither the bot nor the infrastructure collect, transmit, or log this key.

Purpose: This wallet is used for all actions that require transaction signatures, including:

• executing arbitrage trades

• creating / extending / deleting address tables in the TABLE_LOOKUP_MANAGER;

• creating / deleting DURABLE_NONCE accounts

Example:

# Private key of the payer wallet in base58 format.
# Security note: This key is stored locally on your machine only. We do not collect or transmit any private keys or sensitive data
PAYER_PRIVATE_KEY = "4Z3Q...kQW1"

---

DEFAULT_RPC

Description: Defines the primary RPC node through which the bot executes all non-combat (non-arbitrage) requests to the Solana network. This RPC is used by the system to retrieve blockchain data, simulate transactions, load pools, run utilities, and other background operations

Purpose: Used for requests of blockchain state (accounts, pools, tokens, etc.); auxiliary utility requests (for example, creating lookup tables, checking statuses, analytics);

Options:

• URL — address of the primary RPC node.

• RPS — requests per second limit (Requests Per Second), controls load on the RPC and protects it from rate-limits.

Example:

[DEFAULT_RPC]
# Primary RPC node URL for blockchain interaction
URL = "http://fra.rpc.urbanaio.com"
# Maximum requests per second to the RPC node
RPS = 900

Recommendations:

• Use a stable RPC provider with good response speed and uptime. Free helius is acceptable, but it's better to use private RPCs.

---

GRPC

Description: Defines connection settings for Yellowstone gRPC. This connection allows receiving updates about blocks, transactions, accounts, and events with minimal latency.

In the current version, only one gRPC connection is supported. In future versions, support for multiple gRPC connections will be added to improve fault tolerance and data retrieval speed.

Purpose: This is a key data source for monitoring modules and system tasks, including:

• tracking blockhashes and the current state of the Solana network;

• monitoring Durable Nonce accounts and automatic blockhash updates when they change;

• tracking liquidity pool accounts (if the mode GRPC_ACCOUNT_MONITORING);

Options:

• URL — Yellowstone gRPC server address.

• (optional) X_TOKEN — authorization token if the server requires authentication.

Example:

# Real-time account updates streaming via Yellowstone gRPC protocol.
# Monitors: blockhash updates, payer account transactions, pool state changes
[GRPC]
# Yellowstone gRPC endpoint URL
URL = "https://solana-yellowstone-grpc.publicnode.com"
# Authentication token (optional)
X_TOKEN = ""

DEBUG.DISCORD

Description: The parameter Discord allows specifying the Webhook URLto which the system will send messages about transactions:

# Discord notifications for arbitrage results and alerts
[DEBUG.DISCORD]
# Send notifications about arbitrage execution
ENABLED = true
# Discord webhook URL
WEBHOOK = "https://discord.com/api/webhooks/..."

Notes:

• Backrun Strategy — in this mode all events are sent, including successful and failed (failed) transactions.

• Transaction Spam — only successful (successful) transactions.