🦐Overview
Trading is a skill, sniping is an art...
General description
We will begin with a short description of every version available, then we will proceed to presenting the features.
MarksmanSwap runs as a dual application: the bot core (engine) and the user interface (GUI). The core is the heart, or better said... the brain! It is responsible for the entire logic implemented and it performs every action. On the other hand, the GUI is nothing more than a nice way to configure the parameters which govern the core. Therefore, they both must be running! If the core runs by itself - it can not be controlled. If the GUI runs by itself - it has nothing to control.
NOTE: Each and every change in the GUI is propagated to the core ONLY AND ONLY by pressing the Apply Configuration button. Without pressing the button, no change is taken into consideration. Example: after switching the chain, after switching from Hunter Mode to Mempool (don't worry, we'll describe modes later), etc.
NOTE: If the GUI does not start automatically when the executable is ran, please open a browser window (preferably Chrome) and type localhost:3000 .
The core is very much like a cmd where basic information about the current status is shown. For compatibility reasons, the GUI is based on Chrome, therefore it will run similar to a webpage which pairs with the core by listening to a port on the local host if the bot is run locally, or it can connect to your node if the bot runs in a remote manner, directly on the node (we shall discuss this further in this paper).
CORE:
GUI:
Supported Chains & DEXs
Currently, there are 4 chains available: BSC, ETH, POLY, FTM. Each requires its own connection to a node (endpoint) which acts as the means of communication between the bot and the blockchain. Communication is done by means of the web socket protocol.
The DEXs supported for the moment are the main ones for each chain: PancakeSwap, Uniswap, Quickswap, Spookyswap.
As you may notice, the network can be switched from the left-hand side bar: BSC, ETH, POLY, FTM. The selection gains a red outline. For example, in the picture below, BSC is selected.
MarksmanSwap modes and versions
Modes
Snipe On Liquidity Confirmed
Hunter Mode (Fast Buy & Fast Sell)
Snipe On Trading Enabled
Mempool Sniper
Versions
MarksmanSwap Basic
MarksmanSwap Pro
MarksmanSwap Ultra
MarksmanSwap Presale
Modes
Snipe On Liquidity Confirmed
Snipe On Liquidity Confirmed is the most simple mode to snipe a listing. The software is continuously interrogating the DEX in order to determine if any liquidity is present. When liquidity is detected in the DEX trading pair (already confirmed on the blockchain), the software will send a buy transaction. It can be used on any type of launch (DxSale, Unicrypt, BSCpad, Fairlaunch, etc), to buy dips, etc.
Hunter Mode (Fast Buy & Fast Sell)
Hunter Mode is a mode created mostly for stealth launches, but it can be nicely used for dips or for basic manual trades which are a lot faster than performing them through the DEX website. For stealth launches, one has to turn the software on, set any parameters as desired, Apply Configurations, press Confirm to verify the license and then WAIT for the token contract to be published. When the token contract is published, the only thing left is to copy-paste it, Apply Configurations and Fast Buy. 1 copy-paste and 2 clicks away from buying. Fast Sell is the tool used to manually sell really fast when desired: the price is crashing, DEX website not working, etc.
Snipe On Trading Enabled
Snipe On Trading Enabled is a mode implemented having in mind tokens which are launched on a DEX, but trading is DISABLED until the admins enable it. The core of this feature is the same as Snipe On Liquidity Confirmed, but instead of sending the buy transaction when it detects any liquidity, it will wait until the liquidity amount changes. Why it waits until the liquidity amount changes? The answer is quite intuitive: after a token is launched with trading disabled, a change in liquidity means that a buy was performed, therefore trading was enabled. Basically, instead of spamming transactions which are reverted because trading is disabled (wasting gas fees and risking to be blacklisted), the bot waits for someone else to buy and then it will also buy.
Mempool Sniper
Mempool Sniper is the universal mode to buy new listings using the mempool scanning technique. It supports all major launchpads (DxSale, Unicrypt, BSCpad and PinkSale) and fairlaunches.
What is the mempool? Well, when a transaction is sent to the blockchain, it is not instantly confirmed and neither it is instanly picked-up by a miner. Instead, the transaction is put in a priority queue and broadcasted from node to node, having the state as 'pending'. This priority queue is the mempool, or txpool, as it is also called. Miners pick up transactions from this queue based on GWEI: a miner receives the transaction fee for mining a transaction, so it will be stimulated to pick up transactions which pay more GWEI for taxes. Mempool can be interpreted as the list of transactions which are in pending state and waiting to be picked up by a miner.
Note: This list of pending transactions called mempool is different for every node. This is because node X might receive a transaction before node Y (remember, transactions are broadcasted by nodes to their neighbors). Node Y might never receive that transaction while it is in pending state, but it will surely receive it after it was already confirmed on the blockchain (we do not want our node to receive the transaction after it was already mined, we want our it in pending state). Simply said, we want our node to receive as many transactions in pending state as possible, ideally all of them (quite impossible).
After describing a little bit 'the mempool', let us now present how the Mempool Sniper is working. As we have already said, Mempool Sniper supports DxSale, Unicrypt, BSCpad, PinkSale, and fairlaunches. Why? Well, these types of listings add liquidity by transactions with some particular signatures (a little technical, do not bother too much understanding this). The bot scans the mempool (better said, the mempool of the node to which is connected) and looks up the transaction which adds liquidity to the targeted token. When this transaction is found, the bot sends a buy is sent, thus arriving in the same block as the liquidity arrives. Basically, the bot does not wait for the liquidity to be confirmed, it will send the buy when the liquidity is still in pending state.
Versions
MarksmanSwap Basic
MarksmanSwap Basic is the first version in our suite. It offers two modes: Snipe On Liquidity Confirmed and Hunter Mode.
MarksmanSwap Pro
MarksmanSwap Pro includes the following modes: Snipe On Liquidity Confirmed, Hunter Mode, Snipe On Trading Enabled, and Mempool Sniper. For this version, the Mempool Sniper mode is 50ms slower on average (25ms hardcoded and other 25ms on average resulting from the lack of some optimizations).
MarksmanSwap Ultra
MarksmanSwap Ultra is the most advanced version. It has all the modes available with the Mempool Sniper fully optimized.
Last updated
