# Pump.fun bonding sniper ## ## This module can be used for bonding sniper and filtering token for many params , sniping CA in telegram/discord/twitter. To use tg/ds/twitter scrapper you need to download libraries from this site [\ https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
](https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/) ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ *** ## BUY SETTINGS *** ### **Nodes** Select node with geyser that will be used in this task *** ### NodesToken Select node that will Monitor the price of the token {% hint style="warning" %} We don't use WebSocket or Geyser for monitoring because some nodes are unstable, so we send a simple GetProgram request to the node to receive the actual price of your position. {% endhint %} *** ### NodesTX Select node that will send buy transactionsProxy JITO select proxies that will be used to with JITO *** ### NodeGPA Select node that can handle heavy requests like GPA *** ### Proxy list choose your proxy list *** ### Proxy JITO select proxies that will be used to with JITO *** ### **wallet** select your wallets *** ### Buy tx Amount of transaction that bot will send to buy coin. Buy TX input explanation: {% code overflow="wrap" %} ``` In Buy TX, you can input only two values, separated by a comma. The first value is the number of transactions the bot will send during your initial attempt to buy a token. The second value is the number of transactions the bot will send in subsequent attempts to buy the token again, if the first attempt fails. If you have more than one retry attempt, all subsequent attempts will use the number of transactions specified by the second value of #BuyTX. Example:50,35 50: The number of transactions the bot will send for the first attempt to buy. 35: The number of transactions the bot will send for the second and any further attempts. If you need only one attempt to buy a coin, you should input a single value representing the number of transactions the bot will send to buy the coin. Example:50 50: The number of transactions the bot will send to buy coin. ``` {% endcode %} Tips for Buy TX field: 
f you are using a Node, always check its TPS (Transactions Per Second) and avoid overusing it, as this can result in getting rate-limited.

The number of transactions depends on your fees, and you have several options here:

1.Lower fees and a high number of transactions (to spam the block with your transactions) with SAME TX disabled.
2.High fees and a low number of transactions with SAME TX disabled.
3.High fees and a high number of transactions with SAME TX enabled.

Each of these strategies has advantages and disadvantages depending on the module you are using:

Spamming with SAME TX disabled tends to result in better transaction landing compared to SAME TX enabled.
However, with SAME TX enabled, you can significantly increase your fee and the number of transactions you send.
The best approach is to test and choose the option that works best for your specific scenario.
*** ### Delay buy This is the time that the bot waits before sending the next transaction, measured in milliseconds. Delay buy input explanation: {% code overflow="wrap" %} ``` In Delay Buy, you can input only two values, separated by a comma. The first value is the delay between transactions during your first attempt to buy a token. The second value is the delay between transactions during your next attempts to buy the token again, if your first attempt fails. The second value is intended for use in #buyTX after a failed transaction. If you have more than one retry attempt, all subsequent attempts will use the delay specified by the second value of #Delay Buy. Example:1,3 1: The delay between transactions for the first attempt (First value in buyTX). 3: The delay between transactions for the second and any subsequent attempts (Second value in buyTX). ``` {% endcode %} Tips for delay buy: {% code overflow="wrap" %} ``` If you use a regular node, the optimal delay between transactions is 1 ms. This means that before sending each transaction, the bot will wait 1 millisecond, allowing you to spam within a single block and increase your chances of a successful transaction. If you use JITO, the recommended delay is 200 ms. However, you can also choose a random location for JITO in the settings and try to reduce your delay further. Test your setup to find the best delay that avoids rate limits. ``` {% endcode %} *** ### Fee buy in sol A fee in Solana is a small amount in SOL tokens that users pay for conducting and confirming transactions on the Solana blockchain. Input in this field fee in SOL {% code overflow="wrap" %} ``` In Fee Buy, you can input only one value. The fee that you input will be used for the main attempt to buy (for the first value in the Delay Buy and Buy TX fields) and for subsequent attempts to buy the coin again (for the second value in Delay Buy and Buy TX fields) if the first attempt fails. You can also use this field as the fee for sending a JITO TIP. If you enable JITO BUY and fill in the JITO TIP field, you can also fill in the Fee Buy field, and this value will be used as the fee to send the swap transaction. ``` {% endcode %} Tips for Fee buy field: {% code overflow="wrap" %} ``` if you use the SAME TX for buying or selling, it reduces costs because you avoid failed transactions, with only one successful buy. This allows you to significantly increase your fees. However, keep in mind that spamming with unique transactions is generally more effective than repeating the same transaction multiple times. Therefore, if you choose to use SAME TX, always increase your fees to improve your chances. ``` {% endcode %} *** ### Tip Buy sol Jito / nextblock / temporal will be sent with fee in SOL that you input in this filed {% code overflow="wrap" %} ``` Also you can send buy transaction using usual node and jito bundle to use this input fee in sol in fee buy/sell field(s) Usual fee will be in swap transaction ``` {% endcode %} {% code overflow="wrap" %} ``` Additionally, your fees should depend on which module you are using. If you experience unsuccessful transactions in 99% of cases, it's likely due to low fees, low Buy/Sell TXs, or large delays between transactions. ``` {% endcode %} *** ### **Compute units** Compute Units in Solana measure the computational resources consumed by a transaction. The more units used, the higher the transaction cost. ``` 70000 - if precreate ata disabled 35000 - if precreate ata enabled ( check guide on precreate ata pls ) ``` *** ### Slippage Absolute **Slippage absolute** is the minimum number of tokens you will receive after a purchase. If the amount is less than what you specified, the transaction will fail. *** ### Slippage Percent **Slippage percent** is the maximum token amount deviation you’ll accept. If it’s exceeded, the trade won’t go through. Because our contract uses a fixed price for the trade, this affects the token amount you will receive. {% code overflow="wrap" %} ``` Example: 10 You send a transaction expecting to receive 1 million tokens. While it’s processing, someone makes a whale buy, and now you only receive 700k tokens. The transaction fails because the token amount deviation exceeds 10%. ``` {% endcode %} *** ### Buy amount Amount of sol that you want to spend to buy token *** ### Slot Difference Enter the maximum number of slots the transaction should go through; otherwise, the transaction will fail. *** ### Retries Buy This field is used to specify the number of attempts to buy a coin again if the initial attempt fails. Attempt - amount of transactions from [#buy-tx](#buy-tx "mention") and delay between them from [#delay-buy](#delay-buy "mention") Retries Buy input explanation: {% code overflow="wrap" %} ``` In Retries Buy, you can input only one value. This value represents the number of attempts to buy the coin again, using the second value from #BuyTX and #DelayBuy. Example:3 This means that the bot will make 3 attempts to buy the coin again if your main attempt fails (the main attempt refers to the first value from #BuyTX and #DelayBuy). The retries will occur if the main attempt does not go through within the time specified by the first value in #RetriesDelay (in milliseconds). ``` {% endcode %} {% code overflow="wrap" %} ``` If you don't need Retry attempt you can leave this field empty. ``` {% endcode %} *** ### Retries delay This field is used to specify the delay between attempts to buy coin. Retries Delay input explanation: {% code overflow="wrap" %} ``` In Retries Delay, you can input only two values in milliseconds, separated by a comma. If you have more than 1 retry attempt, you should input 2 values: Example:10000,20000 The first value is the delay between your main attempt and the first retry attempt. The second value is the delay between subsequent retry attempts. ``` {% endcode %} ``` If you have only 1 attempt, you should input input 1 value. Example:10000 It will be delay between your main attempt and retry attempt. ``` ``` If you don't need Retry attempt you can leave this field ``` *** ### Max Tokens Atm Maximum number of tokens that the bot can buy and monitor at one time *** ### Snipe initials **Enabled** - Vision will only snipe new tokens on PF **Disabled** - Module will work as usual *** ### Allow retry if you want to have an ability to buy same token more than 1 time - Enable this toggle. If you leave disabled and bot will attempt to buy token second time, transaction will fail. *** ### Only Buy Enable if you want to buy a token and not sell via vision sell tab ( token will not appear there ). *** ### **Send Separate** Works only if you have enabled multiple token-buying services (e.g., Jito, Nextblock, Temporal anti-MEV). When enabled, each service sends a unique transaction. You are charged only for the successful transaction. For any failed transactions (only the Jito, Temporal, and Nextblock toggles may fail; anti-MEV cannot), you pay only the **Fee buy in SOL** — the **Tip Buy SOL** is not charged on failed transactions. When disabled, you will send every service that you enabled in one transaction and pay Tip Buy SOL for each service.

Disabled

*** ### 0Slot Enabled - bot will buy tokens using 0Slot service without mev protection. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### **JITO** Enabled - bot will buy tokens using Jito without mev protection. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### JITO 95% Tip Enabled - bot will send transaction via JITO with 95% chance of successful landing. It will be dynamic TIP that bot requests from JITO API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable JITO or JITO anti-mev toggle to send tx with mev protection or without and after that enable JITO 95% TIP. JITO API: {% endhint %} *** ### JITO 99% Tip Enabled - bot will send transaction via JITO with 99% chance of successful landing. It will be dynamic TIP that bot requests from JITO API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable JITO or JITO anti-mev toggle to send tx with mev protection or without and after that enable JITO 99% TIP. JITO API: {% endhint %} *** ### Jito Anti-mev Enabled - bot will send jito bundle with mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Jito Only bundle If you want to use this toggle **enable JITO toggle.** Enabled - bot will send jito bundle without mev protection. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### NextBlock Enabled - Bot will buy tokens using Nextblock without mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} Mininmum TIP is 0.001 sol {% endhint %} Docs: *** ### Nextblock Anti-mev Enabled - Bot will buy tokens using Nextblock with mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} Mininmum TIP is 0.001 sol {% endhint %} Docs: *** ### Temporal Enabled - Bot will buy tokens using Temporal without mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Temporal 95% Tip Enabled - bot will send transaction via Temporal with 95% chance of successful landing. It will be dynamic TIP that bot requests from Temporal API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable Temporal or Temporal anti-mev toggle to send tx with mev protection or without and after that enable Temporal 95% TIP. Temporal API: {% endhint %} *** ### Temporal 99% Tip Enabled - bot will send transaction via Temporal with 99% chance of successful landing. It will be dynamic TIP that bot requests from Temporal API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable Temporal or Temporal anti-mev toggle to send tx with mev protection or without and after that enable Temporal 99% TIP. Temporal API: {% endhint %} *** ### Temporal Anti-mev Enabled - Bot will buy tokens using Temporal with mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Normal TX Use this toggle if you enabled multiple sending transaction services( jito, nextblock, temporal ) Enabled - bot will send usual transaction via node that you selected in NodeTX with other services that you enabled, Disabled - Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Same TX This toggle is used to switch between sending unique and non-unique transactions. Explanation: {% code overflow="wrap" %} ``` Disabled Toggle: This means that you will send unique transactions. In this case, 1 transaction will be successful, and the other transactions will fail. You will need to pay a fee for each transaction that is landed on the chain. Enabled Toggle: This means that you will send 1 transaction X times, as specified in #BuyTX. With this option, you will have only 1 transaction on the chain and no failures. ``` {% endcode %} How you can use this: {% code overflow="wrap" %} ``` For buying, you can use either unique or non-unique transactions, depending on your setup. In some cases, spamming with unique transactions may be more effective, but it really depends on your specific situation. With non-unique transactions, you can spam 100 million lamports and pay only 0.007 SOL (if your CU = 70,000) while avoiding failed transactions. For selling, it's generally better to use non-unique transactions (Enabled SAME TX), as this allows you to sell less than 50% of the tokens without any issues. However, if you need to sell tokens instantly and want to sell 100% of them, it's better to spam with unique transactions (Disabled SAME TX). ``` {% endcode %} *** ## SELL SETTINGS *** ### Delay sell This is the time that the bot waits before sending the next transaction, measured in milliseconds. Delay sell input explanation: {% code overflow="wrap" %} ``` In Delay sell, you can input only two values, separated by a comma. The first value is the delay between transactions during your first attempt to sell a token. The second value is the delay between transactions during your next attempts to sell the token again, if your first attempt fails. The second value is intended for use in #sellTX after a failed transaction. If you have more than one retry attempt, all subsequent attempts will use the delay specified by the second value of #sell delay. Example:1,3 1: The delay between transactions for the first attempt (First value in sellTX). 3: The delay between transactions for the second and any subsequent attempts (Second value in sellTX). ``` {% endcode %} Tips for delay sell: {% code overflow="wrap" %} ``` If you use a regular node, the optimal delay between transactions is 1 ms. This means that before sending each transaction, the bot will wait 1 millisecond, allowing you to spam within a single block and increase your chances of a successful transaction. If you use JITO, the recommended delay is 200 ms. However, you can also choose a random location for JITO in the settings and try to reduce your delay further. Test your setup to find the best delay that avoids rate limits. ``` {% endcode %} *** ### **delay price** delay between Sending requests to receive your position price {% hint style="success" %} This field will use node from NodesToken {% endhint %} *** ### Sell tx Amount of transaction that bot will send to sell coin. sell TX input explanation: {% code overflow="wrap" %} ``` In sell TX, you can input only two values, separated by a comma. The first value is the number of transactions the bot will send during your initial attempt to sell a token. The second value is the number of transactions the bot will send in subsequent attempts to sell the token again, if the first attempt fails. If you have more than one retry attempt, all subsequent attempts will use the number of transactions specified by the second value of #sellTX. Example:50,35 50: The number of transactions the bot will send for the first attempt to sell. 35: The number of transactions the bot will send for the second and any further attempts. If you need only one attempt to sell a coin, you should input a single value representing the number of transactions the bot will send to buy the coin. Example:50 50: The number of transactions the bot will send to sell coin. ``` {% endcode %} Tips for sell TX field: 
if you are using a Node, always check its TPS (Transactions Per Second) and avoid overusing it, as this can result in getting rate-limited.

The number of transactions depends on your fees, and you have several options here:

1.Lower fees and a high number of transactions (to spam the block with your transactions) with SAME TX disabled.
2.High fees and a low number of transactions with SAME TX disabled.
3.High fees and a high number of transactions with SAME TX enabled.

Each of these strategies has advantages and disadvantages depending on the module you are using:

Spamming with SAME TX disabled tends to result in better transaction landing compared to SAME TX enabled.
However, with SAME TX enabled, you can significantly increase your fee and the number of transactions you send.
The best approach is to test and choose the option that works best for your specific scenario.
*** ### Fee sell SOL A fee in Solana is a small amount in SOL tokens that users pay for conducting and confirming transactions on the Solana blockchain. Input in this field fee in SOL 
In Fee Buy, you can input only one value.

The fee that you input will be used for the main attempt to sell (for the first value in the Delay Sell and Sell TX fields) and for subsequent attempts to sell the coin again (for the second value in Delay Sell and Sell TX fields) if the first attempt fails.

You can also use this field as the fee for sending a JITO TIP. If you enable JITO SELL and fill in the JITO TIP field, you can also fill in the Fee Sell field, and this value will be used as the fee to send the swap transaction.
Tips for Fee buy field: {% code overflow="wrap" %} ``` if you use the SAME TX for buying or selling, it reduces costs because you avoid failed transactions, with only one successful buy. This allows you to significantly increase your fees. However, keep in mind that spamming with unique transactions is generally more effective than repeating the same transaction multiple times. Therefore, if you choose to use SAME TX, always increase your fees to improve your chances. ``` {% endcode %} *** ### **Delay token** Right after vision started to send transactions to buy token, vision will also start to send requests to detects if it bought the token or not Input value in **milliseconds** {% hint style="success" %} delay by default - 1000 ms This field will use node from NodesToken {% endhint %} *** ### Slippage Percent **Slippage percent** is the maximum sol amount deviation you’ll accept. If it’s exceeded, the trade won’t go through. {% code overflow="wrap" %} ``` Example: 10 You send a transaction expecting to receive 1 sol. While it’s processing, someone makes a whale buy, and now you only receive 0.8 sol. The transaction fails because the sol amount deviation exceeds 10%. ``` {% endcode %} *** ### Slot Difference Enter the maximum number of slots the transaction should go through; otherwise, the transaction will fail. *** ### Tip Sell Sol Jito bundle will be sent with fee in SOL that you input in this filed {% code overflow="wrap" %} ``` Also you can send buy transaction using usual node and jito bundle to use this input fee in sol in fee buy/sell field(s) Usual fee will be in swap transaction ``` {% endcode %} 
Additionally, your fees should depend on which module you are using. If you experience unsuccessful transactions in 99% of cases, it's likely due to low fees, low Buy/Sell TXs, or large delays between transactions.
*** ### Retries Sell This field is used to specify the number of attempts to Sell a coin again if the initial attempt fails. Attempt - amount of transactions from [#sell-tx](#sell-tx "mention") and delay between them from [#delay-sell](#delay-sell "mention") Retries sell input explanation: {% code overflow="wrap" %} ``` In Retries sell, you can input only one value. This value represents the number of attempts to sell the coin again, using the second value from #sellTX and #DelaySell. Example:3 This means that the bot will make 3 attempts to sell the coin again if your main attempt fails (the main attempt refers to the first value from #SellTX and #DelaySell). The retries will occur if the main attempt does not go through within the time specified by the first value in #RetriesDelay (in milliseconds). ``` {% endcode %} {% code overflow="wrap" %} ``` If you don't need Retry attempt you can leave this field empty. ``` {% endcode %} *** ### Retries delay This field is used to specify the delay between attempts to sell coin. Retries Delay input explanation: {% code overflow="wrap" %} ``` In Retries Delay, you can input only two values in milliseconds, separated by a comma. If you have more than 1 retry attempt, you should input 2 values: Example:10000,20000 The first value is the delay between your main attempt and the first retry attempt. The second value is the delay between subsequent retry attempts. ``` {% endcode %} ``` If you have only 1 attempt, you should input input 1 value. Example:10000 It will be delay between your main attempt and retry attempt. ``` ``` If you don't need Retry attempt you can leave this field empty. ``` *** ### **Send Separate** Works only if you have enabled multiple token-buying services (e.g., Jito, Nextblock, Temporal anti-MEV). When enabled, each service sends a unique transaction. You are charged only for the successful transaction. For any failed transactions (only the Jito, Temporal, and Nextblock toggles may fail; anti-MEV cannot), you pay only the **Fee buy in SOL** — the **Tip Buy SOL** is not charged on failed transactions. When disabled, you will send every service that you enabled in one transaction and pay Tip Buy SOL for each service.

Disabled

*** ### 0Slot Enabled - bot will buy tokens using 0Slot service without mev protection. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### **JITO** Enabled - bot will buy tokens using Jito without mev protection. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### JITO 95% Tip Enabled - bot will send transaction via JITO with 95% chance of successful landing. It will be dynamic TIP that bot requests from JITO API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable JITO or JITO anti-mev toggle to send tx with mev protection or without and after that enable JITO 95% TIP. JITO API: {% endhint %} *** ### JITO 99% Tip Enabled - bot will send transaction via JITO with 99% chance of successful landing. It will be dynamic TIP that bot requests from JITO API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable JITO or JITO anti-mev toggle to send tx with mev protection or without and after that enable JITO 99% TIP. JITO API: {% endhint %} *** *** ### Jito Anti-mev Enabled - bot will send jito bundle with mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Jito Only bundle If you want to use this toggle **enable JITO toggle.** Enabled - bot will send jito bundle without mev protection. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### NextBlock Enabled - Bot will buy tokens using Nextblock without mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} Mininmum TIP is 0.001 sol {% endhint %} Docs: *** ### Nextblock Anti-mev Enabled - Bot will buy tokens using Nextblock with mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} Mininmum TIP is 0.001 sol {% endhint %} Docs: *** ### Temporal Enabled - Bot will buy tokens using Temporal without mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Temporal 95% Tip Enabled - bot will send transaction via Temporal with 95% chance of successful landing. It will be dynamic TIP that bot requests from Temporal API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable Temporal or Temporal anti-mev toggle to send tx with mev protection or without and after that enable Temporal 95% TIP. Temporal API: {% endhint %} *** ### Temporal 99% Tip Enabled - bot will send transaction via Temporal with 99% chance of successful landing. It will be dynamic TIP that bot requests from Temporal API. Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. {% hint style="danger" %} You have to firstly enable Temporal or Temporal anti-mev toggle to send tx with mev protection or without and after that enable Temporal 99% TIP. Temporal API: {% endhint %} *** ### Temporal Anti-mev Enabled - Bot will buy tokens using Temporal with mev protection Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Normal TX Use this toggle if you enabled multiple sending transaction services( jito, nextblock, temporal ) Enabled - bot will send usual transaction via node that you selected in NodeTX with other services that you enabled, Disabled - Disabled - bot will send tx via your node that you selected in NodesTX or via other services that you selected. *** ### Same TX This toggle is used to switch between sending unique and non-unique transactions. Explanation: {% code overflow="wrap" %} ``` Disabled Toggle: This means that you will send unique transactions. In this case, 1 transaction will be successful, and the other transactions will fail. You will need to pay a fee for each transaction that is landed on the chain. Enabled Toggle: This means that you will send 1 transaction X times, as specified in #BuyTX. With this option, you will have only 1 transaction on the chain and no failures. ``` {% endcode %} How you can use this: {% code overflow="wrap" %} ``` For buying, you can use either unique or non-unique transactions, depending on your setup. In some cases, spamming with unique transactions may be more effective, but it really depends on your specific situation. With non-unique transactions, you can spam 100 million lamports and pay only 0.007 SOL (if your CU = 70,000) while avoiding failed transactions. For selling, it's generally better to use non-unique transactions (Enabled SAME TX), as this allows you to sell less than 50% of the tokens without any issues. However, if you need to sell tokens instantly and want to sell 100% of them, it's better to spam with unique transactions (Disabled SAME TX). ``` {% endcode %} *** ## SELL STRATEGY *** ### Take profit at Input the value of token growth in % that will be used as the Take Profit. The bot will sell **X** amount of the tokens when this percentage is reached. {% code overflow="wrap" %} ``` You can specify multiple TP levels, separated by commas. For each TP level, you must provide an equal number of "sell % of tokens after TP" values. For example, if you have 3 TP levels, you need 3 corresponding "sell % of tokens after TP" values. You must also specify an equal number of Stop Losses (SL). Otherwise, the task will not start. (If you do not need SL, just input 1000 for every level.) Example:40,60,100 40: When the token reaches 40% growth, the bot will sell X% of your tokens (as specified in the "sell % of tokens after TP" field). 60: When the token reaches 60% growth, the bot will sell another X% of your tokens. 100: When the token reaches 100% growth, the bot will sell the remaining X% of your tokens. ``` {% endcode %} *** ### Stop loss Input value of token decrease in % that will be used as Stop loss and bot will sell X amount of token when this % reached 
You must have equal amount of SL and TP levels ( otherwise task you won't be able to run task )

If you need only 1 SL, you can input it in every level and input in Sell "% of tokens after TP" 100 in each level

If you don't need SL, but you have TP you can simply input 1000 for each level
*** ### Sell % of tokens after TP Enter the token growth value in % that will be used as the take profit, and the bot will sell X amount of the token when this percentage is reached. {% code overflow="wrap" %} ``` You can use multiple take profit (TP) levels separated by commas. For each TP level, you must specify an equal number of 'sell % of tokens after TP' values. For example, 3 TP levels require 3 corresponding 'sell % of tokens after TP' values. You must also provide an equal number of stop losses (SL). Otherwise, the task will not start. (If you don't need an SL, simply input 1000 for every level.) Example:50,80,100 Sell 50% of the tokens when the first TP is reached. Sell 80% of the remaining tokens when the second TP is reached. Sell 100% when the third TP is reached. ``` {% endcode %} *** ### Sell % of tokens after SL bot will sell x % of token after reaching value that you input in Stop Loss 
You should input % to sell for every Stop loss 

Example:50,80,100 
50 % tokens when 1 SL reached 
80 % rest of the tokens when 2 SL reached 
100 % when 3 SL reached

If you need only 1 SL and more than 1 TP, you can input this SL few times that will be equal to the TP levels and for each SL input 100 to sell 100% on each level
Example for 1 SL and more than 1 TP levels\ ![Example for 1 SL and more than 1 TP](https://788737236-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV5oxHMkkXARv6Kg798Uu%2Fuploads%2FUkp574iGvam7C7ZVDNda%2Fimage.png?alt=media\&token=a9757ead-b64b-4de0-aa31-b4b87512efda) *** ### **Sell After Ms** Bot will send sell transactions after X MS after token bought {% code overflow="wrap" %} ``` input 1000 and bot will sell tokens in 1000 ms after token bought ``` {% endcode %} *** ### Sell on Dev Bot will sell tokens when detect that dev sold his tokens ( input min,max value ) if you fill 50,100 and dev will sell 30% of his tokens , bot will not sell *** ### Bonding,Milliseconds input value of bonding and milliseconds seperated by comma this field used for some type of AFK sniping. If token not reaching bonding that you input in x milliseconds, bot will sell tokens. If token reaches bonding in x ms , bot will not sell tokens and continue to monitor token. *** ### Trailing SL A trailing stop is a modification of a typical Stop Loss that can be set at a defined percentage. The Bot will remember every ATH of your position and if price drops for x% that you input from ATH bot will sell. *** ### Sell % after trail % of position to sell after Trailing SL level reached *** ### Price movement This field is used to sell the token if the price does not move by **X%** within **X** milliseconds. Input explanation: {% code overflow="wrap" %} ``` You need to input 3 values in this field: %move,ms,%sell %move: The value representing the percentage of price movement of the token. If the token does not move higher than this percentage, the bot will sell the token. (Input the value without the % sign.) ms: The value in milliseconds that the bot will wait before deciding whether to sell or not, depending on the price movement during this time period. %sell: The percentage of tokens you wish to sell if the price does not move higher than %move. Example:20,10000,100 If the price does not move higher than 20% (either positive or negative) within 10000 ms (10 seconds), the bot will sell 100% of your position. ``` {% endcode %} *** ### Migration Sell % Amount of tokens in % that you want to auto-sell right after migration *** ### TP bonding Turn on: bot will sell tokens on some % of bonding progress that you should write in Take Profit At field ( input value without % , just number ) Turn off: bot will use take profit at field as usual *** ## Token filter *** ### Min TXs in block this field is working in pair with Max bundle count field to detect bundled coins. You can set here your own parameters to mark coin as bundled or not ( if coin bundled, bot will not buy ) {% code overflow="wrap" %} ``` Input minimum amount of transactions in 1 block ( slot ) while token was trading to mark token as bundled ``` {% endcode %} *** ### Max bundle count input minimum amount of blocks that will have X amount of transactions that you include in field above {% code overflow="wrap" %} ``` Example: Min TXs in block - 5 Max bundle count - 3 if token that you trying to buy has minimum 3 blocks with minimum 5 transactions in it ( buy and sell ) - this token will be skipped ``` {% endcode %} *** ### Min bought for bundle Specify min purchase amount to filter it as a bundle ( use this filter with max bundle count and min txs in block). {% code overflow="wrap" %} ``` Example: 1 only more than 1 sol purchases will be marked as bundled ( if it also satisfy 2 more filters, that i mentioned above ) ``` {% endcode %} *** ### Tip difference Enter number in percentage. Bot will check every transaction, which tip is similar to another transactions. Specify this difference in TIPs in percentage in this field {% code overflow="wrap" %} ``` Example: 0.1 Bot will check all transaction that sent with TIPs and if the difference of amounts of this tips is lower than 0.1%, bot will start to check them on next filters. ``` {% endcode %} *** ### Fee difference Enter number in percentage. Bot will check every transaction, which fee is similar to another transactions. Specify this difference in fee's in percentage in this field {% code overflow="wrap" %} ``` Example: 0.1 Bot will check all transaction that sent with fee's and if the difference of amounts of this fee's is lower than 0.1%, bot will start to check them on next filters. ``` {% endcode %} *** ### Min TIP Equals Enter minimum number of transactions with TIPs difference lower than value you entered in TIP difference to mark this token as bundled. *** ### Min fee equals Enter minimum number of transactions with FEE's difference lower than value you entered in Fee difference to mark this token as bundled. *** ### Min bought for TIP/fee Specify min purchase amount to filter it as a bundle ( use this filter with TIP/fee difference and min Min TIP/fee equals). *** ### Min,Max % Bonding Input the minimum and maximum bonding curve progress in % of the token that the bot should snipe. **Example:** `50,80` *** ### Min,max % Creator The percentage of the token supply that the owner holds at the moment you buy the token. **Example:** `3,10.5` *** ### Samefund cache bot caches all information about samefund wallets for some time. With this field you can manage this time. We recommend to use value from 10 to 30 mins. Important note: input value in ms: 10 mins = 600000 , 30 mins = 1800000 *** ### Skip percent due to a fact that bot parse a lot of tx for each token node can not handle all this amount of requests and will return you error on some transactions. This field is used to limit failed parsed transactions. If amount of failed parsed transaction is more than some % ( you should input this value without % ) bot will skip this token , if less bot will buy. what transactions bot parses? - 20 transactions of every 20 top holders to find wallets that funded from same wallet , 100 transaction of owner to find wallet that funded this wallet. Also checks all buy txs of top20 holders and owner to check how many signers in each tx and many more to prevent rugs. *** ### Samefund Whitelist input whitelisted addresses that can fund wallets from top 20 holders ( wallets of binance , bybit and other CEXs ). if you input in same fund 0,1 ( thats means that top20 holders funded from different wallets ) , but there some wallets that funded from one of wallet bellow , bot will still buy this token 9Wzu7fjoQSKU6tosKJvUQDeVtFtM94m6mdPDHpgayxXD,GdYwdbjRB1Ds2z9WH7FjZscqTnLRsLVqcPcyNX4tZbVg,5VCwKtCXgCJ6kit5FybXjvriW3xELsFDhYrPSqtJNmcD,9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM,5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9,2ojv9BAiHUrvsm9gxDe7fJSzbNZSJcxZvf8dqmWGHG8S,DRpbCBMxVnDK7maPM5tGv6MvB3v1sRMC86PZ8okm21hy,H8sMJSCQxfKiFTCfDR3DUMLPwcRbM61LGFJ8N4dK3WjS,2AQdpHJ2JpcEgPiATUXjQxA8QmafFegfQwSLWSprPicm,GJRs4FwHtemZ5ZE9x3FNvJ8TMwitKTh21yxdRPqn7npE,AC5RDfQFmDS1deWZos921JfqscXdByf8BKHs5ACWjtW2,5Q544fKrFoe6tsEbD7S8EmxGTJYAKtTVhAW5Q5pge4j1,FWznbcNXWQuHTawe9RxvQ2LdCENssh12dsznf4RiouN5,FLiPggWYQyKVTULFWMQjAk26JfK5XRCajfyTmD5weaZ7,Habp5bncMSsBC3vkChyebepym5dcTNRYeg2LVG464E96,u6PJ8DtQuPFnfmwHbGFULQ4u4EgjDiyYKjVEsynXq2w,5ndLnEYqSFiA5yUFHo6LVZ1eWc6Rhh11K5CfJNkoHEPs,5VCwKtCXgCJ6kit5FybXjvriW3xELsFDhYrPSqtJNmcD,A77HErqtfN1hLLpvZ9pCtu66FEtM8BveoaKbbMoZ4RiR,ASTyfSima4LLAdDgoFGkgqoKowG1LZFDr9fAQrg7iaJZ,AaZkwhkiDStDcgrU37XAj9fpNLrD8Erz5PNkdm4k5hjy,8mowmVCEewZ9W2cEaQyQeQEeSxhGr1hvRviLwozwNtBt,96gYZGLnJYVFmbjzopPSU6QiEV5fGqZNyN9nmNhvrZU5,HFqU5x63VTqvQss8hp11i4wVV8bD44PvwucfZ2bU7gRe,Cw8CFyM9FkoMi7K7Crf6HNQqf4uEMzpKw6QNghXLvLkY,ADaUMid9yfUytqMBgopwjb2DTLSokTSzL1zt6iGPaS49,DfXygSm4jCyNCybVYYK6DwvWqjKee8pbDmJGcLWNDXjh,ADuUkR4vqLUMWXxW9gh6D6L8pMSawimctcNZ5pGwDcEt,DttWaMuVvTiduZRnguLF7jNxTgiMBZ1hyAumKUiL2KRL,3AVi9Tg9Uo68tJfuvoKvqKNWKkC5wPdSSdeBnizKZ6jT,GZctHpWXmsZC1YHACTGGcHhYxjdRqQvTpYkb9LMvxDib,9eZbWiHsPRsxLSiHxzg2pkXsAuQMwAjQrda7C7e21Fw6,4R3gSG8BpU4t19KYj8CfnbtRpnT8gtk4dvTHxVRwc2r7,T1pyyaTNZsKv2WcRAB8oVnk93mLJw2XzjtVYqCsaHqt *** ### Mini Cache this field is used to limit parsing some token for some time. When bot detects some buy on token that he didnt parse before that , bot will parse all info on it and then bot detects again a new buy on this token in 300 ms later , most likely nothing changed in this token and it won't match with your filters and it will be skipped again , but he need to parse all info again , it is really big load on the node , so you can use this field to skip some tokens for some time after bot checked it first time. We recommend to use value about 1000-3000 milliseconds *** ### Initial Bought min and max amount of sol that owner spend to buy token when he was creating it ( example: 0,5 - owner bought from 0 sol to 5 sol max ) and you can choose how many last txs bot will parse to find funding wallet and check if it is blacklisted or not \ \ example: 0,5,50 - owner bought from 0 sol to 5 sol max , 50 - lasts txs bot will parse *** ### Min,max % Koh input minimum and maximum King of the hill progress in % of the token that bot should snipe ( example: 50,80 ) *** ### Min,max % Holders input minimum and maximum value that wallet can hold tokens from all supply in % ( bot parsing top 10 holders , but you can specify this number in holders count) ( example: 0,10 ) *** ### Marketcap If you want to filter token by marketcap, enter min and max value in $. ``` Example: 100000,500000 ``` ### Created Time Vision will buy tokens that were created in some period of time {% code overflow="wrap" %} ``` Input two values in milliseconds separated by comma: First value - Mininmum amount of time from token creation to current time ( in milliseconds ) Second value - maximum amount of time from token creation to current time ( in milliseconds ) Example:60000,3600000 6000 - if token was created less than 1 minute, vision will not buy 3600000 - if token was created more than 1 hour ago, vision will not buy every token that was created in this period is eligble for buying ``` {% endcode %} *** ### Bought Specify the minimum and maximum amount of SOL that someone should spend when you buy the token. The module works by parsing all buy transactions on **pump.fun**. When the bot detects a purchase of a token, it checks the transaction, and if it meets your filter criteria, the bot buys the token. Some scammers ("ruggers") may start buying tokens for **30+ SOL**, causing the token to pump artificially. This results in you buying the token, and then the scammer immediately sells it after you purchase. With this filter, you can prevent situations where you buy during a fake pump. **Example:** `0, 8` — minimum buy is **0** SOL, and maximum buy is **8** SOL. *** ### Same fund min and max amount of sol that owner spend to buy token when he was creating it. example: 0,5 - owner bought from 0 sol to 5 sol max \ \ You can choose how many last txs bot will parse to find funding wallet and check if it is blacklisted or not example: 0,5,50 - owner bought from 0 sol to 5 sol max , 50 - lasts txs bot will parse from dev wallet.\ \ This can be useful when dev using his wallet to bump token so on this caise he do meny transaction (tx), bot will able to check more tx if you setup it. *** ### Dev bundle whitelist If you enable Dev bundle toggle, you can specify wallets that bot will not mark them as a bundlers. Enter wallets deviding by comma without spaces. *** ### Signers input min and max amount of signers that could be in one transaction bot will parse top 20 holders buys and last 25 buy tx in this token if in one transaction amount of signers ( wallets that buying token ) more than in your filter , bot will skip this token *** ### Holders Count Minimum and maximum amount of token holders input explanation: {% code overflow="wrap" %} ``` Three values: [Minimum holders, Maximum holders, Number to parse] Example: 20,100,15 Parses from the top holder based on amount. Setting fewer holders to parse helps avoid rate limits. Two values: [Minimum holders, Maximum holders] Example: 20,100 Summary: Define minimum and maximum token holders. Use three values to specify holders to parse. Two values set min and max holders only. ``` {% endcode %} *** ### Transfer ON - if dev trasfered tokens on other wallet , bot will skip this token OFF - bot will buy any token *** ### Dev bundle Enabled - bot will not buy token if someone bought in same block with dev initial purchase. Disabled - bot will not filter this. *** ### Skip zero tips Enabled - bot will skip all tokens that purchased with usual fee and without jito, nextblock , temporal and etc *** ### Smart blacklist **Enabled -** If a token does not match your token filters, Vision will record its ticker, token name, and token creator to add them to a blacklist. Consequently, if a token is later deployed with the same ticker or name, or if the creator issues another token, Vision will not purchase it. **Disabled -** Vision will not collect any information and will purchase every token. *** ## SOCIAL FILTERS *** ### Socials Enter link on social media that token should have to be purchased. You can leave this field empty. *** ### Description Enabled - bot will skip all tokens that don't have any social media in onchain description Disabled - bot will not filter *** ### Socials Turn on: bot will snipe tokens that have twitter/tg/site Turn off: bot will snipe tokens with socials and with out them *** ### Telegram bot will buy tokens only with telegram *** ### Twitter bot will buy tokens only with twitter *** ### Website bot will buy tokens only with website *** ### Profile Enabled - bot will only buy tokens with paid profile page in DexScreener Disabled - bot will buy any token *** ### ADS Enabled - bot will only buy tokens with paid promo in Dexscreener Disabled - bot will buy any token *** ### CTO Enabled - bot will buy tokens with Community take over Disabled - bot will buy any token > ![](https://788737236-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV5oxHMkkXARv6Kg798Uu%2Fuploads%2FP2TxzjCmsggijLcTfDOc%2Fimage.png?alt=media\&token=db20de91-37e6-454f-a414-5cc52a3f2aae) *** ## SCRAPPERS *** ### Profile list select profile with your telegram/discord/twitter account *** ### Whitelist Keywords input keywords seperated by comma. Bot will check message and if it not contains this word , bot will skip it If you want to snipe calls with a role tag and your wl kw should be a role or roles, you need to input role id ( just numbers and thats all ). If you need few roles just separate them by comma Example: 1181578863059423304,1181547561526497360,buy *** ### Chat Whitelist For Telegram: input chat id with '-' before it. Example:-1001560620044 for discord: input chat id. Example:1001560620044 for twitter input twitter id ( [ \ https://twiteridfinder.com/](https://twiteridfinder.com/) ) *** ### Blacklist keywords input keywords seperated by comma. Bot will check message and if it contains this word , bot will skip it *** ### Twitter delay Delay between refreshing twitter page for a new tweets ``` Delay by default - 5000 ( if you leave this field empty ) ``` {% hint style="danger" %} Twitter ratelimits a lot, so use as many profiles as you can {% endhint %} *** ### Wl Authors If you use this module to parse calls in discord, you can WL people, whos calls you will follow So if someone post CA in channel that you parse and this person not whitelisted in this field - bot will skip this call ``` Input discord ID of person or few ID's separated by comma example:ID,ID,ID ``` *** ### API call port {% hint style="danger" %} Please read about API call port and API call in discord in channel "[telegram multi channel guide"](https://discord.com/channels/977026877447360512/1341128976252272761/1341136156045213787) {% endhint %} *** ### Find any WL Enabled - bot will find any equals in message Disabled - bot will find only whole words *** ### Find any BL Enabled - bot will find any equals in message Disabled - bot will find only whole words *** ### API call {% hint style="danger" %} Please read about API call port and API call in discord in channel "[telegram multi channel guide"](https://discord.com/channels/977026877447360512/1341128976252272761/1341136156045213787) {% endhint %} *** ### Clipboard Feature that allows to buy token immediatly once you copied token contract {% code overflow="wrap" %} ``` Enabled - Vision will only parse your Clipboard, once token contract will appear there, it will buy immediatly ( only tokens that are from raydium ) Disabled - Vision will work as usual ``` {% endcode %} {% code overflow="wrap" %} ``` Can be really useful, if you prefer to search coins manually, just copy token ca and vision will buy it. Also you can use all filters that included in module to analize token. Bot will do it in less than 1 second and you won't spend your time to analyze manually. ``` {% endcode %} *** ## APIs ### AlphaChain Blacklist to enable Alphachain you should enter their access key in settings. Check bottom of the [important settings](https://visionaio-guide.gitbook.io/visionaio-guide-eng/get-started/important-settings#alphachain-api) *** ### Alphachain Whitelist to enable Alphachain you should enter their access key in settings. Check bottom of the [important settings](https://visionaio-guide.gitbook.io/visionaio-guide-eng/get-started/important-settings#alphachain-api) *** ### PumpIT Blacklist To enable PumpIT you should enter their access key in settings. Check bottom of the [important settings](https://visionaio-guide.gitbook.io/visionaio-guide-eng/get-started/important-settings#pumpitpro-blacklist-whitelist) *** ### PumpIT Whitelist To enable PumpIT you should enter their access key in settings. Check bottom of the [important settings](https://visionaio-guide.gitbook.io/visionaio-guide-eng/get-started/important-settings#pumpitpro-blacklist-whitelist) *** ## Test settings ### Initial Balance Enter start balance in SOL to check how profitable your strategy on distance. ### Test Mode Enabled - activates Test mode and don't spend your sol on trades. Disabled - usual trades with sol spending. [^1]: