Releases

PreviousTrouble shooting NextFAQ

Last updated 10 days ago

Release 1.3.34

Use base64 for jito encoding.

Release 1.3.33

Switch kamino to use main market.

Release 1.3.30

Update jup to

Release 1.3.27

Added param under BASE_MINT.

Release 1.3.26

Update jup to

Release 1.3.25

Remove INTERMEDIUM_MINT_COUNT_FROM_JUPITER_TRENDING as jupiter no longer provide the api for it.
Ignore MAX_TIP when it's set to 0(default)
Fixed a bug where SKIP_SAME_OPPORTUNITY only works when ENABLE_FIXED_SIZE_OPTIMIZATION is set to true. Now it will work in either case.

Release 1.3.24

Update jup to

Release 1.3.23

Fixed a JITO override bug with fixed-range params

Release 1.3.22

Added a new param. You can use this to manually select which ips to use for jito.
Added , , . You can use them to send to multiple regions for a provider.
Small improvements on logs.

Release 1.3.21

Added two new jito : static-list, fixed-range
Added build in support for multiple ip. Added a new config

Release 1.3.20

Update jup to
Added a version.txt for easier automation support.

Release 1.3.19

Fix a ledger bug for new account.

Release 1.3.18

Add proper ledger account recovery when bot started.

Release 1.3.17

Fixed a bug where jito tip transfer may not show up correctly when using separate tip wallet.
Updated fee accounts

Release 1.3.16

Fix the bug where fixed strategy doesn't work well with static
Added additional safe guard to prevent future bugs

Release 1.3.14

Added a new flag . See the link for details
Small bug fixes for validations.

Release 1.3.13

Update jup to
Cleanup some logs and validation
Added new BLOXROUTE_REGION : amsterdam

Release 1.3.12

Added support for third party Jupiter API
- Added new config . If your provider uses x-api-key in the header, you can set it with this. E.g. Shyft
- Added new config . Some provider does not expose their /tokens Jupiter api call, in such case you can set this to true to get around it. E.g. Shyft
- Added new config . If your provider uses url params for api key, you can set it with this. E.g. apikey=123456

Release 1.3.11

Fix a bug for backrun, where if you don't put in base mint as intermedium, it will not fetch the correct markets.
Cleanup some log

Release 1.3.10

Handle tx too large error gracefully

Release 1.3.9

Removes a hard trade size cap for backrun

Release 1.3.8

Fix a jito bug where the profit may not cover the basic gas
Fast key is deprecated, you should use CIRCULAR_API_KEY now if you are using the priority queue of Fast to send.

Release 1.3.7

Upgrade default jup to
now also accept urls. You can now use custom endpoints more easily. For example, you can use for the official ny endpoint now instead of ny

Release 1.3.5

Added a new config
Optimize memo instruction.

Release 1.3.3

Bug fix that sometimes may quoting from the same pool twice

Release 1.3.1

Improve how bot create ledger account on first time start.

Release 1.3.0

Updated to use a new onchain program. Now an account will be created the first time you run the bot, which will cost ~0.001 SOL. The bot will no longer creating a temp account in every tx. This also brings some nice optimization and reduced the overall size of the transaction.
New flashloan provider: . There is no fee for kamino flashloan, so you can go as high as the kamino vault allows. All three base mints SOL/USDC/USDT are supported. This does increase the CU by about 80,000, and may generate too large of a tx if you are using direct only false. Example tx:
Update the script to support http://127.0.0.1 as the local jupiter url.
Support SolFi for backrun
Added new config , which takes a list of files and merge the mints in them
Added new config , which is just a list of mints. You no longer need to create a file if you just want to run a few mints manually selected.
Bug fixes

Release 1.2.3

Added a new config FIXED_SIZE to backrun TRADE_CONFIGS. Example:

TRADE_CONFIGS:
  - FIXED_SIZE: 1_000_000_000
  - FIXED_SIZE: 10_000_000_000

Release 1.2.2

Improved market fetching logic. Now it should be very fast.
Fixed a bug that sometimes unnecessary instruction may be added to tx.

Release 1.2.1

Upgrade default jup to
Added a new config . This can be handle when the network is super congested.
Added more integration with Circular()
- Added a new config CIRCULAR_API_KEY
- Updated params in INTERMEDIUM_MINT_FROM_CIRCULAR
- Added a new config ENABLE_CIRCULAR_MARKET_CACHE under Jupiter.
Removed rate limit for NextBlock and Bloxroute with your own key
Bug fix for USDC base mint

Release 1.2.0

Bot now uses 8 different fee wallet instead of 1. Each transaction will pick a random one to send fee.
Update temporal to adopt their new fee addresses. Also updated the regions that is available to temporal. Supported regions now: pit1 ,ams1, fra2 ,ewr1

Release 1.1.8

Fix a bug with token 2022 mints

Release 1.1.7

Added a new supported region germany to
Added a new
Small bug fixes

Release 1.1.6

Fix a bug with
Added a new config , note you can only set one of INCLUDED_DEXES and EXCLUDED_DEXES not both.

Release 1.1.5

Fixed a bug with token-2022 mints

Release 1.1.3

Added support of la/tokyo region for BLOXROUTE_REGION.
Fix a bug with
Improved the speed of market updates for backrun strategy.
Added a new supported backrun strategy DEXES_TO_MONITOR: LifinityV2

Release 1.1.2

./run.sh now can take a param as the config you use. This can make it easier to switch between different configs. example: ./run.sh config.jito.yaml
Added a new config . This is only useful when you connect to a remote Jupiter. Example usage is running multiple bot with the same Jupiter server.
Added a new option to only send through jito for several sending venders:
Add support for sending through Jito GRPC. You should only look into this if you have a Jito GRPC key. See for more detail.
Bug fixes

Release 1.1.0

Update how static/fixed tip strategy work when USE_SEPARATE_TIP_ACCOUNT is enabled to better prepare for jito's update. It's now static tipping when you use static/fixed tip strategy with USE_SEPARATE_TIP_ACCOUNT
Upgrade the default jupiter version to
Small bug fixes

Release 1.0.26

Fix a bug with run-jup.sh not respecting AUTO_RESTART

Release 1.0.25

Fixed a bug with MIN_COMPUTE_UNIT_PRICE
Fixed a bug with max trade size when using TRADE_SIZES
Added a new param .
Update how the default compute unit limit is calculated.
Added a new TRADE_RANGE_STRATEGY: exponential. For example for range 10-1000, with a count 5, it will generate the following trade sizes: [10, 77, 315, 668, 1000]

Release 1.0.24

Added config to hide vender failure logs. TEMPORAL_SHOW_SENDING_ERROR, NEXTBLOCK_SHOW_SENDING_ERROR, FAST_SHOW_SENDING_ERROR
Added config to set max fee for venders. BLOXROUTE_MAX_DYNAMIC_FEE, TEMPORAL_MAX_DYNAMIC_FEE, FAST_MAX_DYNAMIC_FEE, NEXTBLOCK_MAX_DYNAMIC_FEE
Bug fixes

Release 1.0.23

Fix a bug with memo for Fast transactions

Release 1.0.22

Added a new sending vender . See the config for how to set it up. Visit their discord to obtain a key.

Release 1.0.21

Fixed some small issue introduced with 1.0.20

Release 1.0.20

Optimize jupiter quote time, you should see at least 10% improvement on the quote time.
Added a new config to config how many workers(thread) to use for fetching from Jupiter.
Optimize 3hop quote logic, you should see a much better quote time now compare to previously.

Release 1.0.19

Fixed a bug with JITO/SPAM override
Fixed a bug with max tip not applied for static tip
Optimized compute unit
Added a new config

Release 1.0.18

Added a new feature . This is useful when you run multiple machines and want to use different mints for them.

Release 1.0.17

Added a new experimental feature . If your server has multiple public ips you can set it with the config to have more jito rate limit, do remember to use this together with
You can now set the fee paid to sending venders BloXRoute/NextBlock/Temporal based on your projected profit. Check the according config docs
- ,
- ,
- ,
Added a new script so you can upgrade/downgrade jupiter versions as you wish.
If you have API key from circular.bot, you can now directly use their api with the bot. See
Bug fixes

Release 1.0.16

Support a new 3rd party send transaction provider . Check config doc for more details.

Release 1.0.15

Fixed a bug of displaying the wrong number for opportunities.
Added option under JUPITER. See docs for more detail

Release 1.0.14

More jupiter optimization. Should see less RPC calls and slightly faster speed for jupiter quote.

Release 1.0.13

The failed intermedium mints feature is now not enabled by default. You can turn it on by setting .

Release 1.0.12

Update Jup to
Optimization for tx instructions

Release 1.0.11

Fix a bug with default value for ROUTE_TYPES

Release 1.0.10

Handle ata fetch error gracefully

Release 1.0.9

The bot will now remove intermedium mints that keep failing to quote for 50 times in a row.
A new config for BLIND_QUOTE_STRATEGY is added. This allows similar routes like setting to false, but with a much faster quote time. Read the doc for more details and example.
Fix a bug with helius where it shouldn't fetch when it's not enabled

Release 1.0.8

Starting from 1.0.8 the bot will encrypt your private key into a file called ENCRYPT_PRIVATE_KEY on your first run, and ask you to remove your private key config once it's created. Though this is not 100% bullet proof but it does make it harder for hackers to get access to your key on the vps. You can disable this behavior by setting the to false.

Release 1.0.7

Support custom BloXRoute key. You can now set to use your own key with no rate limit.
Support a new 3rd party send transaction provider . Check config doc for more details.

Release 1.0.6

Fix a bug for how max trade size is loaded.
Fix a bug for kill-jup.sh script that it does not load the correct local port.
Fix a bug for how intermedium mints are loaded for backrun strategy.
BloXRoute rate limit is now set to 10/s, as we have more and more people using it.

Release 1.0.5

Fix a bug introduce with 1.0.4 for blockhash

Release 1.0.4

Cleanup logs
Fix a bug that may ocassionally cause jito fail to send

Release 1.0.3

Fix a bug with max trade size
Some log improvements

Release 1.0.2

Add validation for TRADE_SIZES, which was TRADE_SIZE in 0.3.x versions.
Update example to reflact the latest changes.

Release 1.0.1

Fixed a bug that will crash the bot with INVALID_URL when YELLOWSTONE_URL is not set
Make helius error more clear
Small bug fixes

Release 1.0.0

This is a big release with multiple breaking changes. Please read the release note here carefully before upgrading. You can use the example config inside page or the config.yaml.example file come with the bot as a reference.

1.0.0 introduced a new strategy , which introduces a whole new way to find opportunities. The is landed with this new strategy. Read the docs on the strategy to learn more.

The old way of running the bot is now renamed into .

Changes to old config

is now moved under
and is now moved to
BIRDEYE_API_KEY is deprecated. You no longer need it to get birdeye tokens.
is moved to under
MAX_PRIORITY_FEE is moved to SPAM and renamed to MAX_COMPUTE_UNIT_PRICE
MIN_PROFIT is renamed to
SKIP_SAME_OPPORTUNITY is now moved under
TRADE_SIZE is rename to TRADE_SIZES

Other changes with the release

Update jupiter api to
Improved how jupiter quote works to slightly speed up the quote latency
Added a new field . You now need to specifically set which strategy you use similar to jito tip.
Added a new field inside . You can now increase the BloXRoute fee you pay
Added a new field inside . You can now turn off the sending logs in your output.
Added a new field inside . This will override the MEMO under BOT.

Release 0.3.14

Added and param to get around the rpcs that does not support transaction history. You can use a free helius plan now for this.
Cleanup some logs.

Release 0.3.13

Update jupiter api to
Added three JUPITER config: , ,

Release 0.3.12

Added a new way to fetch intermedium tokens . You do not need birdeye api to fetch this, this is fetched from bot's own backend. This list has new mints faster than the original birdeye 24h volume list.

Release 0.3.11

Update jupiter api to

Release 0.3.10

Added a new field to JITO config. Together with as a new param. Read the configuration doc for more details.
Breaking: JITO_TIP_BP is now renamed to . JITO_TIP_BP will still work for now, but changing the name is recommended.
Fix some config override bug with JITO_UUID and BLOCK_ENGINE.
Cleanup some logs

Release 0.3.9

Update jupiter api to . market mode europa may finally be possible to run.
Fixed a bug with USE_DIFFERENT_TX_FOR_SENDERS + flashloan.
MEMO now also works for flashloan enabled tx
Added a new config . When enabled, for SOL base mint, bot will pay the jito tip/bot fee using your profit. This will allow catching bigger opportunitiese even when you don't have enough SOL balance to pay for jito tip.

Release 0.3.8

Fixed a bug with USE_DIFFERENT_TIP_ACCOUNT_FOR_BLOCK_ENGINES, where jito will fail to send if this is enabled.
Cleanup some debug logs.

Release 0.3.7

Added feature to ./upgrade.sh. You can now upgrade/downgrade to a specific version by running it with the version number. If you want to download version 0.3.3, you can run ./upgrade.sh 0.3.3
Added a new jito config USE_DIFFERENT_TIP_ACCOUNT_FOR_BLOCK_ENGINES. This will use different tip account for different block engines, in theory increase your chance to land.
Small bug fixes

Release 0.3.6

Fixed a bug with COMPUTE_UNIT_PRICE not being set when simulation is on.

Release 0.3.5

Fix a bug with some spam configs not taking effect correctly
Change the default COMPUTE_UNIT_PRICE value to 0
Move ENABLE_JITO_RPC to bot config
Added a yaml config format checker on start
Increase compute unit price when retrying wrap sol to increase the success rate during congested time.

Release 0.3.4

Breaking: Changed format of , now it takes an additional param MAX_MINT_COUNT, See for more details. This will allow more targeted strategy like only try to arb the mints with the most arbs possible.

INTERMEDIUM_MINT_FROM_ADDRESSES:
  MAX_MINT_COUNT: 0 # 0 is no maximum, 
  ADDRESSES:
    - ADDRESS: 'benRLpbWCL8P8t51ufYt522419hGF5zif3CqgWGbEUm'
      TX_COUNT_PER_ADDRESS: 100 # Number of latest transactions to check on start
      SUCCESSFUL_ONLY: false # Only consider successful transactions
      MAX_MINT_COUNT: 0 # 0 is no maximum
    - ADDRESS: 'bobCPc5nqVoX7r8gKzCMPLrKjFidjnSCrAdcYGCH2Ye'
      TX_COUNT_PER_ADDRESS: 100
      SUCCESSFUL_ONLY: false
      MAX_MINT_COUNT: 0 # 0 is no maximum

USE_DIFFERENT_TX_FOR_BLOCK_ENGINES is now deprecated. Bot will always send different tx to different block engines.
Added a new JITO config
Added a new JITO config . Note this is NOT sharing the jito rate limit as using JITO_TIP_BP, and can be config together with JITO_TIP_BP or alone by itself.
Fix a bug with that some address failed to load.
Optimize the logic for . Note can only return ~20-30 mints at maximum due to their limitation on the api.
Show log for run-jup.sh script.
Added a new capability to override JITO/SPAM config within BASE_MINT, see for more details. This basically allows you to override the global value for each base mint you define. Here's an example that override the JITO_TIP_BP value for this specific base mint config.

BASE_MINTS:
  - MINT: So11111111111111111111111111111111111111112 # Wrapped SOL
    TRADE_RANGE:
      FROM: 1_000_000_000
      TO: 2_000_000_000
    TRADE_RANGE_COUNT: 5 # Number of trade sizes within the range
    TRADE_RANGE_STRATEGY: 'linear' # Strategy for distributing trade sizes
    JITO:
      JITO_TIP_BP: 9000

Release 0.3.3

Fixed a bug for migrating TRADE_SIZE
Fixed a bug with INTERMEDIUM_MINT_COUNT_FROM_GECKO

Release 0.3.2

Fixed a bug with starting jupiter.

Release 0.3.1

Change to some default values so the config values are more consistent: ENABLE_JITO now default to false. INTERMEDIUM_MINT_COUNT_FROM_BIRDEYE now default to 0.
Cleanup some logs.

Release 0.3.0

Upgrade Jupiter api to
Breaking: deprecate .env and base-mint.json. Now all configs goes into config.yaml. As the bot evolves the old way to config settings are messy and not scalable. The introduction of this new config format allows more structured config file, comments in the example, better readability for lamports, and more flexibility in the future. Now every possible configs are in config.yaml.example with the default value visible to users so it's easier to know what is configurable at first glance. For easier migration the bot provides a new binary you can run ./migrate, which will generate a config.yaml file for you based on your old .env and base-mint.json. See the updated page for more details.
Breaking: New INTERMEDIUM_MINTS config. This consolidate some of the old configs under one umbrella for better understanding. Now instead of a given name for intermedium-mints.json and exclude-mints.json, you have to specifically set a file name for the same purpose. More details see .
Added a new way to fetch INTERMEDIUM_MINTS : INTERMEDIUM_MINT_FROM_ADDRESSES. This allow you to copy trade other top players' mints for their most recent transactions. More details see
Breaking: BIRDEYE_API_KEY no longer has a default value. You have to use your own now.
Breaking: INTERMEDIUM_MINT_COUNT_FROM_NEW_TOKENS is renamed to

Release 0.2.22

Update run-jup.sh to incorporate the latest logic to start jupiter server.

Release 0.2.21

Fixed a bug with USE_SEPARATE_TIP_ACCOUNT

Release 0.2.20

Fixed a bug with MARKET_MODE. Also change the default value for it to remote.
Cleanup some log on start.
Update how USE_SEPARATE_TIP_ACCOUNT works so it can now work on smaller profits.

Release 0.2.19

Upgrade jupiter to . Specifically now newly streamed markets will also be added to jup if it's in your mint list.
Added a new env MARKET_MODE. Default value europa. Note the default behavior here will stream new markets for your mint list to Jupiter, but it can be very heavy for some RPC to handle. You can change it to remote to disable this behavior.

Release 0.2.18

Added a new .env config USE_SEPARATE_TIP_ACCOUNT. When this is enabled, a new solana address will be used to send tip in its own tx instead of sending to jito directly for every jito transaction. Jito currently is rate limiting bundles based on the accounts in the tx that does the tip. This is useful when you have machines in multiple locations but still trying to use the same wallet to run the bot. Example transaction: Note: this is an experimental feature and I'm still testing how good this is to get around the jito limitation. Please report in discord if you run into any issues.

Release 0.2.17

Remove minimum SOL requirement for flashloan
Remove marginfi as a provider

Release 0.2.16

Remove USE_SHARED_INTERMEDIUM_ACCOUNTS as it's not a working config.

Release 0.2.15

Add a new .env config SHOW_JITO_LOGS, default to false. When enabled, it will show the response for the jito bundle requests. This is helpful if you are trying to see how often you are hitting the jito's rate limit.

Release 0.2.14

Fixed a bug in run.sh

Release 0.2.13

Upgrade Jupiter api to . The old Jupiter versions will no longer be updated with new mints and markets. So make sure you upgrade to this asap.
BREAKING: EXCLUDED_DEXES now need to be the address of the market instead of the name. If you didn't modify this in your .env you can ignore this.
BREAKING: USE_LOCAL_MARKET_CACHE now has a different format and url, if you are using it make sure you download from the new link. Otherwise you can ignore this.

Release 0.2.12

Added a new param JITO_UUID. If you get a custom uuid from jito, you can set it here to have a higher rate limit. The default rate limit is 5/s/ip
The Jito rate limit for all bot users are reverted unfortunately, Jito has a bug on their end that caused the uuid to cap on all usage instead of per ip. This unfortunately set back the rate limit back to 5/s for jito. But old versions have a worse performance now due to this issue.

Release 0.2.11

Fixed a bug that introduced by Jupiter which will cause all quotes to fail with WARN tower_http::trace::on_failure: response failed classification=Status code: 500 Internal Server Error latency=0 ms
Fixed a bug in .env.example

Release 0.2.10

Fix a bug with opportunity count
Fix a typo with base-mint example

Release 0.2.9

Added a .env config USE_SHARED_INTERMEDIUM_ACCOUNTS. Default to false. When enabled, it will not create intermedium token accounts in your wallet, instead it will use a shared one provided by jupiter. This is very useful if you don't want to have hundreds of token accounts opened in your wallet. Note this may slightly reduce your landing rate as if the token is very popular the shared accounts may be locked by other Jupiter users
Fixed a bug with SKIP_SAME_OPPORTUNITY
Cleanup some logs

Release 0.2.8

Added a .env config SKIP_SAME_OPPORTUNITY, when enabled and you are using fixed trade size(either using tradeSize or tradeRange with linear strategy), the bot will check if it's the same as last time and not generate a new opportunity for it if it's the same.
Raise bloXroute rate limit to 20/s
Due to a recent change of Jito's SendTransaction endpoint, the bot now only send through SendBundle, which will lead to a reduced rate limit of jito to 25 tx/s
Upgrade jupiter-swap-api to
Some log improvements

Release 0.2.7(Rolled back)

Now when you use fixed trade size(either using tradeSize or tradeRange with linear strategy), the bot will check if it's the same as last time and not generate a new opportunity for it if it's the same.
Raise bloXroute rate limit to 10/s
Upgrade jupiter-swap-api to

Release 0.2.6

Remove JUPITER_TOKEN_COUNT param.

Release 0.2.5

Update jupiter-swap-api to

Release 0.2.4

Fix a bug where COMPUTE_UNIT_PRICE may not work for spam mode.

Release 0.2.3

Jito rate limit raised to 50/s/ip!
Added a new .env config USE_DIFFERENT_TX_FOR_BLOCK_ENGINES, default to true. When it's enabled it will send a different tx for each jito block engine
Optimize compute unit limit for jito transactions. FIXED_COMPUTE_UNIT_LIMIT now also affects jito transactions. When it's set to 0, a more accurate estimation algorithm will be used. When simulation is enabled, the value from the simulation value +20% buffer will be used.

Release 0.2.2

Add new jito region slc(salt lake city)

Release 0.2.1

Hide Jupiter log with run.sh
Cleanup some logs

Release 0.2.0

Added a new .env config SPAM_RESTRICT_LEVEL. Default to 0. Valid values are 0,1,2,3,4,5. This config will try to limit how long a tx land compares to when you send it when using spam. 0 is no restriction, the same behavior as before. 5 is maximum restriction and will only allow the tx to land within ~1-2 slots. Note the exact restriction time for each level can be affected by your RPC's latency and performance. Read the doc for more details about this config.
Added a new config in base-mint.json. spamFeeBps . This allows you to set a fixed percentage of your projected profit as your gas fee. Read the doc for more details.
Now if you enable simulation, the Compute Unit will be set based on simulation result with a 15% buffer. This will help to reduce the Compute Unit Limit number and improve landing rate.
Now when you set minProfit = 0 in your base-mint.json file, no profit check will be performed. This is useful when using super spam strategy.
Added a new .env config PULL_BLOCKHASH_WITH_YELLOWSTONE , when enabled, will use your Yellowstone to pull blockhash instead of RPC. This can save you a lot of RPC credits.
Added a new .env config BLOCK_ENGINES, default to ny,amsterdam,frankfurt,tokyo You should not change this unless you know what you are doing. This is list of block engines the bot will send to when using Jito.
The bot now show full compute time, you can have a better how long your jupiter quote takes to help you optimize your bot.
Added a new .env config MAX_COMPUTE_TIME. You can set a value and when the bot will not send out tx if the compute time for an opportunity is higher than the value.
Added new .env configs ENABLE_BLOXROUTE, and BLOXROUTE_REGION. This is useful when you don't have a good rpc for sending when using spam mode. BloXroute will always use staked connection.
Added a new .env config ENABLE_JITO_RPC. If you have a Jito RPC this can give you a better estimation of the profit when running simulation.
Added a lot of new logs
MEMO config now will NOT add anything to your tx by default. It will only be added when you set a value for it.
Now the bot will NOT call jupiter simulation to get a compute unit limit, instead bot uses a new algorithm to calculate an estimation.
Fix a small bug that may slow down super spam strategy.
Update jupiter-swap-api to
Bug fixes

Release 0.1.8

Fix version number

Release 0.1.7

Fix a bug that jito tip for USDC may not be calculated correctly sometimes
Change the output level for run-jup.sh

Release 0.1.6

Update jupiter-swap-api to
Added a new param LOCAL_JUPITER_PORT, default to 18080. This is for advanced usage, normal user can ignore this change.

Release 0.1.5

Fixed a bug with the upgrade.sh script. If you are upgrading from 0.1.4 make sure you run the upgrade.sh twice.

Release 0.1.4

Fixed a bug with trade range. If you see a low jup success rate with trade range, this release should fix it.
Added a new script upgrade.sh that you can run to upgrade to the latest version.

Release 0.1.3

Removed an unnecessary Jup rpc call. This should save you a lot of rpc credits, and speed up jup quote slightly.

Release 0.1.2

Added a new config ENABLE_LANDING_LOG, default to false. When this is enabled, it will output an additional WIN log when a transaction is landed like in previous version. Though if you turn this on while having ENABLE_SIMULATION=false, it may consume a lot of your RPC credits, as for each transaction you send, this will call a getTransaction for it to confirm landing.

Release 0.1.1

Fixed a bug with run.sh script, now it won't kill your jupiter when you have DISABLE_LOCAL_JUPITER=true

Release 0.1.0

ENABLE_JITO_TRANSACTION config is now removed. Instead bot will utilize sendTransaction from Jito to send bundles, which will raise the limit of 5/s to 10/s for sending transactions with Jito.
Added a few more optimization tips
Changed fee collecting address
Small bug fixes.

Release 0.0.27

This release focus on improvements around ENABLE_SPAM mode.

New config MAX_RETRIES, default to 0. This is a config for RPC method, Maximum number of times for the RPC node to retry sending the transaction to the leader. The higher this number, the more chance your tx can land, but also lead to high chance of failure, as retried tx is likely too late for the opportunity.
New config HELIUS_API_KEY, this is used for fetching lated priority fee. You can get one for free by register an account on .
New config PRIORITY_FEE_UPDATE_INTERVAL , default to 60. Unit in seconds. This controls how often the priority fee is updated.
Two new fields for base-mint.json
- priorityFeePercentile, value from 0 to 100(you can set higher than 100 but not recommended). Automatically set COMPUTE_UNIT_PRICE based on current priority fee level. You need to set HELIUS_API_KEY in order to use this. The bot utilize helius's , to fetch the latest priority fee levels. The response is something like the following from the api, value map to the response, aka 0 means min, 25 means low, 50 means medium, 75 means high, 100 means veryHigh. If the current response looks like below, and you set 30 as the value for priorityFeePercentile, the auto generated COMPUTE_UNIT_PRICE would be 10000 + (60082 - 10000) * ((30 - 25) / 25) = 20016. Note the value for each level will change all the time as market moves. When this is set, it will override the COMPUTE_UNIT_PRICE value in .env file.
```
"min": 0,
"low": 10000,
"medium": 60082,
"high": 1230000,
"veryHigh": 5000000
```
- maxPriorityFee. The max COMPUTE_UNIT_PRICE you are willing to set. This is helpful to prevent setting a huge priority fee as market moves.
Example usage of the config

[
  { "mint": "So11111111111111111111111111111111111111112",
    "tradeSize": [1210000000, 2410000000],
    "minProfit": 2000000,
    "priorityFeePercentile": 50,
    "maxPriorityFee": 100000
  }
]

Improved how transaction is sent, should see slightly better landing rate.
Added a new script run-jup.sh, this will only start the Jupiter API and not running the bot. Useful when you want to run Jupiter API on one machine and bots on other machines.

Release 0.0.26

Added a new config USE_LOCAL_MARKET_CACHE for Jupiter API. When this is set to true, it will load the market cache from the local file mainnet.json. This is useful when you run jup and it's very slow to start, or even fail with error reading a body from connection. You can update the local file with wget https://cache.jup.ag/markets?v=3 -O mainnet.json

Release 0.0.25

Fix a bug where wrap/unwrap and balance check is not working in 0.0.24
Fix a bug where in some corner cases the bot will send an empty tx

Release 0.0.24

Update the format of base-mint.json to support defining the same base mint for different strategy. Please check for the new format. The old one will continue to work but if you want to define multiple strategy for the same mint you have to use the new format.
Introducing for base-mint.json. Make it easier to customize your strategy. And now you can use random trade size with trade range!
Small bug fixes
Added more logs on bot start

Release 0.0.23

Added a new optional config file exclude-mints.json. It's in the same format as intermedium-mints.json, the tokens in the file will be excluded from jup api and intermedium mints. This is useful if your RPC is under a lot of load and couldn't catch up, you can remove USDC/USDT and just run SOL with alt tokens as a different strategy. You may see this error if you exclude USDC, it can be safely ignored: price_tracker.update_prices failed with: missing decimals for USDC
[Experimental] Added a new experimental config INTERMEDIUM_MINT_COUNT_FROM_NEW_TOKENS, which will fetch new pools opened through geckoterminal and extract the mints used in the pool. This config is still in development. If you want to set this you can try to set it up to 200. One way to use this is with only SOL base mint with no birdeye intermedium tokens/no jupiter_token_count, or use exclude-mints.json to exclude USDC/USDT for better performance. Default to 0, which means this is not enabled.
[Experimental] Added a new experimental config FILTER_GECKO_POOLS_FROM_RAYDIUM, default to true. This config is specifically used together with INTERMEDIUM_MINT_COUNT_FROM_NEW_TOKENS, when set to false, it will extract all tokens that has a new pool opened, but a lot of them may only have one amm on raydium, which means there's no arb opportunities for them. When set to true you would probably see around 10-20 new tokens fetched at most.
Update jupiter-swap-api to v6.0.18

Release 0.0.22

Added a new config DISABLE_LOCAL_JUPITER, when set to true, it will not start the Jupiter API locally. This is useful when you want to run multiple bots on the same machine.
Cleanup some logs