Skip to content

v1.2.0-alpha - maxTxnAge, useHeliusFee, REUP_NATIVE_ENABLED, SLOT_DATA_ENABLED, WRITE_TO_CSV
Compare
Choose a tag to compare
@AlexRubik AlexRubik released this 25 Jun 21:32
· 19 commits to main since this release
v1.2.0-alpha
50c5bad

New baseConfig.json properties: maxTxnAge, useHeliusFee, inDexes, outDexes

  • inDexes, outDexes, useInDexes, useOutDexes: the variables that start with "use" can take true or false as their values depending on if you want to use them. For in/outDexes, you can provide a list of the dexes you want to restrict your in and out swaps to (read here to see what those swaps look like).
    You can find all the valid dex names here.

Example values:
"useInDexes": true,
"inDexes": ["Orca V1", "Orca V2", "Phoenix", "Meteora", "Lifinity V2", "Raydium CLMM", "Meteora DLMM", "Raydium"]

Don't use these maxTxn params for now. There might be value to them in the future.

  • maxTxnAge: approximate max age for your transaction measured in blocks. For example, if you only want transactions to land within 5 blocks then make this value = 5. In this example, if the bot finds an arb opportunity at block number ~100 and you have a processing time <400ms then the transaction will only land up to block ~105. A validator will not attempt to land your transaction later. Doesn't make since to use this for Jito txns so only test this with native txns. In theory, this should greatly reduce your amount of failed transactions once you find an optimal number.
  • useMaxTxnAge: boolean (true/false) for maxTxnAge mentioned above^
  • useHeliusFee: set this to true if you want to use Helius's suggested fees for all your normal transactions. You still need to have a Helius API key set in the .env file for this to work.

New .env variables: RANDOM_JITO..., REUP_NATIVE_ENABLED, SLOT_DATA_ENABLED, WRITE_TO_CSV

  • REUP_NATIVE_ENABLED: you can now disable/enable this feature
  • SLOT_DATA_ENABLED: set this to true to see what slots you attempt to send your txns
  • WRITE_TO_CSV: set this to true to write significant arb data to a csv inside the csvs folder. The naming format for the csvs is txns_{unix time of when bot was started}.csv
  • RANDOM_JITO_URLS: set this to true if you want to randomly use a jito url from BLOCK_ENGINE_URL.
  • RANDOM_JITO_URLS_COUNT: the number of jito urls you want to send each arb transaction to. For example, if this value is 2 then it will send every arb opportunity to 2 random jito urls. To reduce rate limits, you should have this number set to 1.
Assets 3
Loading