JITO Strategy Settings
Last updated
Last updated
If using the JITO strategy, you can configure your bot to send opportunities it finds through the JITO block engines. They currently have 5 mainnet engine locations in New York City (USA) , Salt Lake City (USA), Frankfurt (Germany), Amsterdam (Netherlands), and Tokyo (Japan).
For more JITO information, visit their
[[jito]]
(Required if using Jito)enabled
: Toggle Jito dispatching.
http_enabled
: enables http sending (default true)
grpc_enabled
: enables grpc sending (default false)
url
: Endpoint for Jito block engine.
New York:
Salt Lake City:
Frankfurt:
Amsterdam:
Tokyo:
http_timeout_ms
: Timeout for Jito HTTP requests.
http_pool_max_size
: Maximum HTTP connections.
Keep this the same as your JITO RPS limit.
requests_per_second
: Rate limit for Jito requests.
The default by JITO is 5 requests per second (RPS)
You can request to increase your limit by filling out their
queue_timeout_ms
: Timeout for queuing requests.
always_queue
: Force queuing for transactions.
proxy_*
: Proxy settings if needed.
You can have your opportunities sent to certain locations or all if you'd like.
Using the proxy settings allows you to use other IPs and bypass the Jito default limit of 5 requests per second.
Below is an example of setting up a proxy for Amsterdam:
proxy_wallet = true/false
: uses tips with a "proxy" wallet (default false)
proxy_host = ""
: Put the address or ip from your proxy provider
proxy_port = 8002
: Put the port number from your proxy provider
Proxy user = ""
: Put the username from your proxy provider
proxy_password = ""
: Put the password from your proxy provider
priority_queue
: enables priority queuing by estimated opportunity profit (default true)
bind_ip
: binds outgoing connections to a system ip address (default none)
UNDER CONSTRUCTION