# Moonshot ## Nodes select node list that will parse all info ( node should support all type of requests )\ if you want to use node with geyser you should import it in this format: http;ws;geyser *** ## NodesToken select node that will monitor balance change on your wallet and monitor price of the token *** ## NodesTX select node list that will send buy and sell transactions *** ## Proxy list choose your proxy list ( it is Necessary ) *** ## Wallet select your wallet *** ## Wallet JITO select any wallet from which you will pay JITO tips ( now you don't need to whitelist your wallet ) *** ## Proxy JITO select proxies that will be used to with JITO *** ## 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 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 **LAMPORTS** {% 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 JITO TIP transaction. ``` {% endcode %} Tips for Fee buy field: 
If you are using a regular node to send transactions, you can use this table to calculate how much SOL you will spend to buy and sell a coin.

Also, 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.

If you use JITO, the fee calculation is different. To determine how much you will spend, please use this website.

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.
*** ## input amount input amount of **Token in** that you want to swap ( USE WSOL ) *** ## 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: 
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.
*** ## Min,max % Bought Of Tokens % of token supply that owner bought when he was creating token ( example: 3,10.5 ) *** ## Compute Unites Leave empty if you don't understand how it works( if you leave empty the value in the field will be 200000 ) *** ## Slippage Buy this is the maximum deviation from the original purchase price that bot can buy. Input value in % *** ## Ticker BlackList input names of tokens that always rugs , bot will skip them ( input in format token,token,token) *** ## Creator blacklist input wallets that always rugs , bot will skip them ( input in format wallet,wallet,wallet ) *** ## Creators Whitelist If you want to snipe token from exact creator , just input his wallet *** ## Tickers Whitelist If you want to snipe token with exact ticker, just fill this ticker *** ## Socials If you want to snipe exact token and you know twitter/telegram/site of this token , just input it( you can fill it one by one seperated by comma. Example: Social,Social,Social,Social) *** ## Min,max Creator Balance Min,Max sol balance on the wallet that created token *** ## Token Out This field is used to swap a token that already exists on Moonshot. {% code overflow="wrap" %} ``` Input contract address of the token. Make sure that token didn't migrate to Raydium or Meteora and still trading on Moonshot. ``` {% endcode %} *** ## 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 empty. ``` *** ## JITO buy ON: Bot will buy tokens using JITO OFF: bot will send tx via your node that you selected in node section ## Nextblock Enabled: Bot will send transactions via Nextblock plugin ( *** ## Smart Bl ON - enable vision smart black list system *** ## 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 **turn ON** if you want to switch bot to sell mode after successful swap ( you will get estimated amount of **Token In** in status field ) press on banknote when you want to sell \ **Turn OFF** if you want just to buy token with bot and then sell manually ( not via bot , bot will stop task when he bought token ) *** ## 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 price updates in status of the task *** ## 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.
*** ## 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

Example:20,30,50
20: When the token price drops by 20%, the bot will sell X% of your tokens (as specified in the "sell % of tokens after SL" field).
30: When the token price drops by 30%, the bot will sell another X% of your tokens.
50: When the token price drops by 50%, the bot will sell the remaining X% of the tokens.
*** ## Fee sell 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 **LAMPORTS** {% 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 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 JITO TIP transaction. ``` {% endcode %} Tips for Fee buy field: 
If you are using a regular node to send transactions, you can use this table to calculate how much SOL you will spend to buy and sell a coin.

Also, 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.

If you use JITO, the fee calculation is different. To determine how much you will spend, please use this website.

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.
*** ## 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 The bot will sell **x%** of the tokens after reaching the value that you input as the Stop Loss. {% code overflow="wrap" %} ``` You should input the percentage to sell for every Stop Loss. Example:50,80,100 Sell 50% of the tokens when the first SL is reached. Sell 80% of the remaining tokens when the second SL is reached. Sell 100% when the third SL is reached. If you need only one SL and more than one TP, you can input this SL multiple times to match the number of TP levels, and for each SL, input 100 to sell 100% at each level. ``` {% endcode %} 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 buy in MS Bot will send Sell TX after X MS after buying tokens ( put 1000 and bot will sell tokens in 1000 ms after buying ) *** ## Delay token delay to monitor your balance for token that you bought ( when bot sends Buy TXs it starts to monitor your balance for this token , so in past this value was 1000 ms , now you can customize it ) *** ## 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 %} *** ## Trailing Stop Loss 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. *** ## 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. ``` *** ## 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 *** ## Desc bot will buy token that has at list one social in description *** ## 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 *** ## JITO sell ON: Bot will sell tokens using JITO ( if you want to use JITO you should [fill their form ](https://visionaio-guide.gitbook.io/visionaio-guide-eng/solana-shitcoins/shitcoins-sniping-modules/jito)and select this wallet in wallet JITO field ) OFF: bot will send tx via your node that you selected in node section *** ## 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 %} [^1]: [^2]: [^3]: