Skip to content

v1.0.0-alpha - Staked Helius Transactions!
Compare
Choose a tag to compare
@AlexRubik AlexRubik released this 31 May 20:01
· 24 commits to main since this release
v1.0.0-alpha
26bc19e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Any paid Helius plan can now use their staked connection to send heavily prioritized transactions.

Newly required files in this zip (don't try to put the new executable in your older version directories).

Using a staked connection does not improve execution speed!
It only makes your transaction more likely to be included in a block (fail or success)!
Helius requires expensive priority fees (10k lamports minimum) for this feature which the bot calculates automatically (read below).
If you don't have an optimal setup, you can lose a lot due to these high priority fees.
If you are not targeting large profit or large trade sizes, you can lose a lot due to these high priority fees.

  • Put your Helius API key value in the new .env variable: HELIUS_API_KEY=X

  • In baseConfig.json you now have 2 new properties:
    "useHeliusTxn": true,
    "heliusPriorityLevel": "MEDIUM"

  • When useHeliusTxn = true, if the bot uses a helius rpc in any way for sending txns, it will send it with priority to their staked connection.

  • heliusPriorityLevel can be "LOW" , "MEDIUM", or "HIGH" . This determines the size of helius txn priority fee. They suggest MEDIUM.

  • A Helius transaction will always use more than 10k lamports priority fee

  • If you are using the spam .env variables, they will work as normal. They won't use the large priority fee even if you have useHeliusTxn = true

  • useHeliusTxn = true does not make the worker send only Helius transactions when using spam feature. If you are spamming, the worker will send normal transactions to your non Helius rpcs with the min/maxFeeLamports as the priority fee

  • Try using MAX_RETRIES=0 (in .env) and duplicating RPCs in your rpcs.json

  • A worker with jitoProfitPerc > 0 will still only send jito bundles. The new Helius properties/variables don't affect that. Bundles are prioritized in this condition.

Get started! https://rude-bot-org.gitbook.io/rude-solana-arbitrage-bot/bot-setup-instructions

Official Website: https://www.solanaarbitrage.com/

Assets 4
Loading