Also described on the “Autodetection” page. This method is giving a signal on the price drop for a specified percentage. Using this strategy you can configure different bot behavior depending on the daily trading volume on the coin, on the specific coins listed in the whitelist, and adjust for the different levels of buy price, sell price and stops.

DropsMaxTime: Period to analyze, in seconds. Based on this parameter, all the parameters are estimated below. Example: set to 100 seconds, bot estimates price change in the last 100 seconds, ie, every new second(tick) is a new last 100 seconds interval.

DropsPriceMA: Interval to calculate Moving Average. The bot is getting 2-seconds price ticks, so for example If you set this to 10 seconds, then every 5 prices will be averaged. The bot then takes maximum average price and compares it to the last price. If you do not want to average prices you can set this parameter to less than 2.

DropsLastPriceMA: Ticks to calculate last price average value. If you set this to 1, then the last price will be taken as is. The more this value the less detection sensitivity for fast drops. If set to 0, then any sharp drop, bigger than the DropsPriceDelta value will trigger a detect.

DropsPriceDelta: Price drop during the analysis period, percentage. Is calculated as: (Highest price/ Lowest price - 1) * 100.

DropsPriceIsLow: If YES, then in addition to the above-described conditions, the current market price has to be the hourly low.

Example: If the current market price is 2% lower than the highest price, the strategy will be triggered (e.g.: the highest price was 102$, the current price is 100$. The drop is equal to (102/100 - 1) * 100 ) = 2%

This method reveals coins with a large volume of buy orders for a long time (support). The example in Fig. below:

Configure parameters to specify a period to check how long the support was there; the bot checks it by 5-m candles. It recommended to set stoploss to a small level behind the wall, and to check manually news for the coin on twitter and so on. Usually, such walls followed by good news ensure that the coin is going to raise high.

Parameters

WallsMaxTime: Time to check the wall was there, seconds. The bot uses 5m candles to detect if the price had not dropped below the wall level.

WallsPriceDelta: Difference between minimum and maximum of 5m candles minimums. The objective is to determine how long the purchase wall is in place with a minimum of her movements.

WallBuyVolDeep: The distance between the price and wall inside the orderbook (in %). This parameter we specify within what distance from the current market price, we will check the presence of the volume of the wall.

WallBuyVolume: The volume of the tested walls in BTC (at least).

WallBuyVolToDailyVol: The volume of the wall is not less than the percentage of the volume of daily trades on the coin (in %). If the volume of the wall is 10BTC, and the daily trading volume is 100BTC, the strategy will work if the parameter is equal to 10/100 = 10% or less of it.

WallSellVolToBuy: Volume of the sell wall in % to buy wall. Its volume should not exceed X% of the volume of the buy wall.

WallSellVolDeep: How deep to look for sell orders in % to the current price

Example of the Walls strategy for Bittrex: copy the text below and paste it to the bot (Strategies form, the button “paste”)

##Begin_Strategy

Active=-1

StrategyName=Walls Test

Comment=

SignalType=WallsDetection

ChannelName=

ChannelKey=

SilentNoCharts=NO

ReportToTelegram=YES

CoinsWhiteList=

CoinsBlackList=TRX,NBT

MinVolume=10

MaxVolume=500

AutoBuy=NO

MaxActiveOrders=10

AutoCancelBuy=180

BuyType=Buy

OrderSize=0.00000000

buyPrice=-3.00000000

SellPrice=4.00000000

UseStopLoss=NO

StopLoss=1.00000000

PanicSellSpread=0.10000000

AllowedDrop=0.00000000

UseTrailing=YES

TrailingPersent=-1.00000000

UseTakeProfit=YES

TakeProfit=2.50000000

DropsMaxTime=600

DropsPriceMA=1

DropsLastPriceMA=1

DropsPriceDelta=1.00000000

DropsPriceIsLow=NO

WallsMaxTime=3600

WallsPriceDelta=4.00000000

WallBuyVolDeep=2.00000000

WallBuyVolume=10

WallBuyVolToDailyVol=10.00000000

WallSellVolToBuy=75.00000000

WallSellVolDeep=15.00000000

##End_Strategy#

Fast detecting of executed buy orders (market history). Example: (false detection by the way, look warning below)

The thin green candle is a pack of buy orders executed in a second. (Actually, that was 1 buyer which bought plenty of MANA for 11 BTC).

Parameters

PumpPriceInterval: Interval to measure price raise, choose from: 60s, 30s, 15s, 4s

PumpPriceRaise: Price raised during last PumpPriceInterval seconds, %

PumpBuysPerSec: The number of purchases per second (green crosses on the graph). EMA (Executed buy orders)

PumpVolPerSec: Purchase volume per second, in BTC (the lower the value, the greater the likelihood of false detects)(Buy volume), in BTC

PumpBuyersPerSecMin: The number of customers in the given interval (at least). For different scenarios, this value might be different. Some pumps should be detected, making sure several people are already in or vice versa, you can detect only actions form a single person. (if 0 – then ignored)

PumpBuyersPerSecMax: Buyers count in the specified interval, not more then (If 0, then ignored)

PumpVolEMA: The interval for calculating the volume of purchases EMA (default is 2 seconds, may be a fraction), i.e. the averaging interval of volume purchases.

PumpBuyersInterval: Interval to calculate Buyers count (1 second by default)

PumpMoveTimer: Time to move the sell order (If 0 then never). The order is moved only once.

PumpMovePercent: Percentage of [distance from peak price to buy price], to which move the sell order. Example: PumpMoveTimer=5sec, PumpMovePercent=50%. The bot has detected a pump, bought a coin at 1000 sat, in next 5 seconds the price has further raised to 1200 sat. Initial sell was placed at 1300 sat. This case the bot will replace the sell to (50% from (1200 – 1000) = 1100 sat (half of the peak price in the other words).

PumpUsePrevBuyPrice: Use 2-seconds old price for calculating BuyPrice (unless specified using price 30 seconds ago). Enabled by default. This setting protects against buying at the very top of the spike. Before this parameter was added to the settings, it was always enabled programmatically, so when disabled, the strategy behavior will change!

Currently, only 1 PumpsDetection strategy can be active despite you can configure many of them.

It’s recommended to use Pump Detection only for known in advance pumps when you know exact pump time. Turn it ON 15 seconds before the pump announcement and turn OFF immediately after.

WARNING! There is a high risk of false detection! Despite you can configure many parameters to avoid them, it is still possible that some market activity could be taken as a pump. look the example of MANA above.

Recommended parameters values for Binance pump detection on the example of Mega Pump Group actual pumps (https://t.me/mega_pump_group):

PumpPriceRaise:=7; – 7% Price increase for the last 30 seconds. The more this value, the less chance of false detection, on the other hand, you might want to detect a pump as soon as possible when the price is not very high yet.

PumpBuysPerSec:=20;

PumpVolPerSec:=0.8; The volume added by the very first buyers. (usually admins and privileged members of the discord group). The more this value, the less chance of false detection

PumpBuyersPerSecMax:=4; The goal is to detect the pump at the very beginning when no more than 2-4 ppl already bought the coin.

PumpBuyersPerSecMin:=2; Reject a case when there is only 1 buyer occasionally bought some coin not related to the pump

The strategy puts buy orders and automatically replace them in order to catch spikes. (look picture below) Initially, the order is placed at a price below the market price on MShotPrice (in the example below 3%). With a further price drop to MShotPriceMin (in the example of 2%), the order is replaced on MShotPrice from the current market price. If the price increases, the order moves up. Thus, the order price is always in the range from MShotPrice to MShotPriceMin.

Using the delay (MShotReplaceDelay) you can slow order’s replacing on downtrend; this is riskier but gives more actual trades. If MShotReplaceDelay=0 then the order will catch only spikes like in the picture above; this is less risky but happens less often.

Use delay on price raise (MShotRaiseWait) to avoid moving order up on fast pumps (which is very risky). Also, protect from the catch on dumps by using strategy daily volume filters (flash pumps could happen only on coins with low daily vol.)

With a relatively rapid drop in prices, it makes sense to use the MShotReplaceDelay delay to swap the buy order; In this case, the probability of a transaction increases, but the risk also increases.

Important

At partial execution greater than min. lot (0.001 BTC) the order will be immediately canceled and the sell will be set up regardless of the settings for partial cancellation (since there is no point in waiting for full execution after spike has happened)

At the moment, the internal limit for max. active orders for the MoonShot is 10. In addition, MShotPriceMin should be greater than 0.5 and MShotPrice should be greater then MShotPriceMin+0.5. The restriction is due to the exchange’s API limit.

Charts for this strategy are not opened automatically to reduce API requests. You can open them manually through the list of orders.

Parameters

MShotPrice: Price in % to current market to keep buy order at (always a positive value, the order is below market price at this value).

MShotPriceMin: Min, price in % to current market price, after which the order will be replaced to MShotPrice again. So that the order is always between MShotPrice and MShotPriceMin.

MShotMinusSatoshi: If YES, then buy orders will be placed not closer then 2 satoshi from current ASK price. Useful for coins with price 100sat or less, which have price step more than 1%.

MShotAdd3hDelta: For each percent of the 3-hour Delta add X% to the value of MShotPrice

MShotAddHourlyDelta: For each percent of hourly price delta add MShotAddHourlyDelta percent to price range [MShotPrice .. MShotPriceMin]. Example: If the coin rose/fell by 10% in last hour, and MShotAddHourlyDelta=0.1, then 1% will be added to both parameters [MShotPrice .. MShotPriceMin]. The more the price deviation the more the distance to your order.

MShotAdd15minDelta: For each percent of 15-minute Delta percentage add X% to the value of MShotPrice.

MShotAddMarketDelta: For each percent of the hourly Market Delta add X% to the value of MShotPrice.

MShotAddBTCDelta: For each percent of the hourly BTC Delta add X% to the value of MShotPrice.

MShotAddBTC5mDelta: To adjust price range by BTC 5-minutes delta. The delta is calculated as difference (percentage) between min and max rates during last 5 minutes (hence it always positive)

MShotAddDistance: The expansion coefficient for MShotPrice (percentage relatively to MShotPriceMin depending on deltas; If AddDelta values added X% to MShotPriceMin, then MShotPrice will be adjusted by X * (1 + MShotAddDistance/100)%. Example: MShotAddDistance = 100, MShotPriceMin is adjusted by AddDeltas by 1%, then MShotPrice is adjusted by 2%. Default 0 – dont adjust (works as before).

MShotAddPriceBug: A parameter modifier dependent on PriceBug. The recommended value of this parameter is 0.2, to be used when the exchange is lagging in order to buy further from the current price.

MShotSellAtLastPrice: After Buy has happened put a sell order at a price equal to the maximum price of the strategy (the sell price) and the last price (4-sec-old, that was, before the spike happened) ASK price, taking into account the MShotSellPriceAdjust (see below).

MShotSellPriceAdjust: If the previous option is YES, then substitutes MShotSellPriceAdjust percent from the previous market price. Example: at the moment of a spike market price was 1000 sat. MShotSellPriceAdjust = 1. Then you order will be placed at higher of 2 prices: strategy settings sell price and 1000sat – 1% = 990sat. Explanation: after a spike, the price often goes back to where it was just before the spike, so its good idea to sell a bit lower.

MShotReplaceDelay: Delay to replace the buy upon price drops to MShotPriceMin.

MShotRaiseWait: Delay to replace the buy upon price raise.

MShotSortBy: Sorting of coins that the bot selects for the operation. LastNhDelta - based on the 1-, 2-, 3-hourly deltas. DVolToHVolAsc - based on the horly to daily volume ratio ascending. DVolToHVolDesc - based on the horly to daily volume ratio descending. OrderBook (only for MoonStrike owners) - by the orderbook ((coins with the thinnest orderbook are taken first of all), DailyVol - by day. volume, MinuteVol - by minute volume. Accordingly, the coin with the highest value will have the highest priority.

MShotUsePrice: Can be “ASK” (default), “BID” or “Trade” – use the last trade price for calculation of the MoonShot price corridor. Determines what price (ASK or BID) should be used to calculate MoonShot price corridor

MShotRepeatAfterBuy: This parameter is part of the Extension Package for auto-trading, the description to it can be read there.

MShotRepeatIfProfit: This parameter is part of the Extension Package for auto-trading, the description to it can be read there.

MShotRepeatWait: This parameter is part of the Extension Package for auto-trading, the description to it can be read there.

MShotRepeatDelay: This parameter is part of the Extension Package for auto-trading, the description to it can be read there.

The detector uses 4 intervals to check that the average prices and volumes grew from previous to next interval. Growth is set in percent. If you set 0 percent, then the condition turns into “price (volume) did not fall.” To disable checking for price/volume growth for a specific interval, you should set a large negative value for a parameter that would allow passing the verification for this condition, i.e. the verification for the condition on the set interval will always take place (except for the times when a real fall in price/volume that was less than the set value has happened).

Picture to illustrate: P – Prices, V – Volumes

Parameters

VLiteT0: The interval in seconds.

VLiteT1: The interval in seconds.

VLiteT2: The interval in seconds.

VLiteT3: The interval in seconds.

VLiteP1: The price increase from the previous to the subsequent interval of not less than (in %).

VLiteP2: The price increase from the previous to the subsequent interval of not less than (in %).

VLiteP3: The price increase from the previous to the subsequent interval of not less than (in %).

VLiteMaxP: Each increase by no more than (in%).

VLitePDelta1: Comparison of rising prices between themselves (in %).

VLitePDelta2: Comparison of rising prices between themselves (in %).

VLiteDelta0: Price change at the zero interval. (The difference between the max. And min. Price within a range of zero percent).

VLiteMaxSpike: The maximum difference between the max. price and average price within the specified interval, no more than (in %). It is necessary to eliminate mini-pumps.

VLiteV1: Growth from the previous to the subsequent interval (%).

VLiteV2: Growth from the previous to the subsequent interval (%).

VLiteV3: Growth from the previous to the subsequent interval (%).

VLiteWeightedAvg: The method of calculating average prices: if YES, it is considered to be the weighted average by volume in the interval, if NO, the average of the count of transactions in the interval.

VLiteReducedVolumes: If YES, then count the amount per minute. If NO then the full amount of the interval.(in case of long intervals)

The essence of the method is in the detection of volumes. Two intervals are set: “short” and “long” and the volumes are calculated at both intervals. The volume on a long interval is considered reduced to a minute, i.e. volume per minute. For example, if the long interval is set to 300 seconds (5 minutes), the volume in 5 minutes was 10 BTC, then the volume per minute would be 2 BTC. In a short interval, the volume is taken as is.

All ratios of volumes are given as numbers “how many times one is bigger than the other”, not percentages!

When the conditions for volumes are triggered, the orderbooks are checked as the second step:

filling the glass with BIDs (green) on 2 levels.

Min level prices at a short interval.Level max. prices at a short interval.

Filling the BIDs orderbook to a predetermined depth from the current ASK price.

Comparing the volume in the BIDs(green) orderbook at a given depth with the volume of ASKs (red) at a given height.

Determining the dynamics of filling the green orderbook from the moment of detection at the 1st step to the moment of placing the order (the bot waits for checking no more than 20 sec if the conditions did not work, no order is placed)

Parameters

VolShortInterval: The short interval in seconds.

VolShortPriseRaise: Price increase over the short interval (it is possible to set 0).

VolLongInterval: Long interval in seconds.

VolBvShortToLong: The ratio of the volume of purchases (BV) on the Short interval to the total volume on the Long period (how many times bigger than the other one).

VolBvLongToHourlyMin: The ratio of the volume on the long interval to the hourly volume, at least.

VolBvLongToHourlyMax: The ratio of the volume on the long interval to the hourly volume, not more.

VolBvLongToDailyMin: The ratio of the volume on the long interval to the daily volume, at least.

VolBvLongToDailyMax: The ratio of the volume on the long interval to the daily volume, not more.

VolBvToSvShort: BV to SV ratio on the short interval.

VolBvShort: BV on the short interval (in BTC).

VolBuyersShort: The number of buyers on the short interval is not less than. (single flash spikes can be filtered out by this line)

VolSvLong: Sell volume over the long interval, excluding the short interval volume, not more than (in BTC).

VolTakeLongMaxP: Whether to take MaxPrice rates at the long interval (useful in the case of a false rebound after a drop).

VolAtMinP: The volume in the green orderbook at min. prices for a short interval (in BTC).

VolAtMaxP: The volume in the green orderbook at max. prices for a short interval (in BTC).

VolDeltaAtMaxP: Dynamics(Delta) in the green orderbook at max. prices on the short interval after the detection until placing the order (bot waiting for not more than 20 seconds to check if the condition has not been met, the order is not placed), (in BTC).

VolDeltaAtMinP: Dynamics(Delta) in the green orderbook at min. prices for the short interval.

volBidsDeep: The depth at which to watch green orderbook, a percentage of current ASK.

volBids: Volume in the green orderbook at the specified depth (in BTC).

volAsksDeep: The height at which to watch the red orderbook, the percentage of the current ASK.

volBidsToAsks: The ratio BIDs ASKs volume to volume at the specified depths, not less than (in BTC).

The idea is the same as Volumes Lite: The detect uses 4 intervals to check prices and volumes deviation from previous to next interval. Unlike VolumesLite, negative parameter means that the value has dropped, positive means the value has raised, zero parameters will be ignored.

Parameters: P – Prices, V – Volumes

WavesT0: The interval in seconds.

WavesT1: The interval in seconds.

WavesT2: The interval in seconds.

WavesT3: The interval in seconds.

WavesP1: Price change from the previous to the next interval (in %). If you set a positive value, growth is checked. If you specify a negative value, verified drop. If zero, the parameter is ignored.

WavesP2: Price change from the previous to the next interval (in %). If you set a positive value, growth is checked. If you specify a negative value, verified drop. If zero, the parameter is ignored.

WavesP3: Price change from the previous to the next interval (in %). If you set a positive value, growth is checked. If you specify a negative value, verified drop. If zero, the parameter is ignored.

WavesDelta0: Price change at the zero interval (T0). (The difference between the max. and min. price within the T0 interval percent). If you set a positive value, growth is checked (measured delta is bigger than the one specified). If a negative value is set, then no growth is verified (delta measured is not greater than the predetermined. For example, “-1” means that the fluctuation was not more than 1%). If zero, the parameter is ignored.

WavesMaxSpike: The maximum difference between the max. price range and on average (not more than, in%). It is necessary to eliminate lumbago.

WavesV1: Growth of volumes from a previous to the subsequent interval. If you set a positive value, growth is checked. If you specify a negative value, verified drop. If zero, the parameter is ignored.

WavesV2: Growth of volumes from a previous to the subsequent interval. If you set a positive value, growth is checked. If you specify a negative value, verified drop. If zero, the parameter is ignored.

WavesV3: Growth of volumes from a previous to the subsequent interval. If you set a positive value, growth is checked. If you specify a negative value, verified drop. If zero, the parameter is ignored.

WavesWeightedAvg: The method of calculating average prices: if YES, it is considered to be the weighted average by volume in the interval, if NO, the average of the count of transactions in the interval.

WavesReducedVolumes: If YES, then count the volume per minute. If NO then the full amount on the interval.

Logic: We take a long interval of the last 100 seconds (as an idea, all parameters are adjustable) and a short window of 10 seconds. On each tick we run this 10-second window through the 100-second interval and calculate the minimum and maximum price averaged over the window. We get DeltaPrice in the last 100 seconds – the degree of movement of the coin.

We consider the total volume for the last 100 seconds and the previous 100 seconds and compare how much% the volume has grown.

We look at the last 10 seconds and count the number of deals and the change in the average price in the last 10 seconds compared to the average price in the last 100 seconds.

Parameters

DeltaInterval: Interval analysis of price and volume changes (long).

DeltaShortInterval: Interval of averaging prices and analysis of the dynamics of transactions (short).

DeltaPrice: Price change (delta) in the long interval (at least). It is considered as a percentage deviation between min. price and max. price based on prices averaging over short intervals.

DeltaVol: The total volume (BV + SV) on the long interval (at least, in BTC).

DeltaVolRaise: The total volume on the long interval is greater than the volume at the same previous interval for the given percentage (at least).

DeltaVolSec: The volume per second, averaged and thus delayed. The last seconds before the detect have more weight, single pump spikes are avoided with the averaging. If you put 0, it is ignored.

DeltaBuyers: The number of transactions (buyers + sellers) on the last short-range.

DeltaLastPrice: The average price on the last short interval increased or decreased by a predetermined percentage of the average price for a long interval. If the value is positive, then growth checked. If the value is negative, drop is checked. When 0, the parameter is ignored.

The following strategy is used for trusted management through the UDP protocol.

TMBuyPriceLimit: percent value.

TM strategy protection against purchases at excessive price: the TMBuyPriceLimit parameter sets the maximum value for the buy price (in percent based on the current market price). 

E.g.: If TMBuyPriceLimit = 5%, and a Buy command is received at a price of +10%, such command will be ignored.

More details about Trusted Management can be found here:

Trusted Management High-Frequency trading via UDP port

Trusted Management

The task of the strategy is to detect a spike down(similar to what Moonshot is waiting for) and place an order as quickly as possible in order to have time to buy something. Estimated mechanics – the spike itself in most of the cases will not be caught but it triggers stop loss orders of other market players as well as other stop-limit orders, therefore (and also because of the delay in the execution) the idea does NOT ALWAYS work. Following trades will not happen every time.

It makes sense to run on a VPS in Japan, it also makes sense to increase the priority of the MoonBot application (in new versions, when started, the admin priority “above average” is set automatically).

Description of parameters:

MStrikeDepth: Depth of the spike as a percentage (10% by default, you can set 0.1% or higher). How is measured:

1. LastBidEMA (4 ticks) is considered using the next Formula: If on the next-to-last tick, the bid is less than LastBidEMA, then LastBidEMA is taken to be the same to the bid on the last-to-last tick (i.e., if the price falls, LastBidEMA will be equal to the bid in the orderbook 2 seconds ago) If on the next-to-last tick, the bid is larger than LastBidEMA, then the normal EMA (4) is considered Thus, when the price falls, the lastbid will always be minimal, with growth it will grow smoothly

2. Read the depth from LastBidEMA to the bottom of the spike at the time of the detection.

Note1: catches also “up-and-down” situation (for an exception, you should probably consider the EMA from bids, on the other hand, it will lead to catching slow drops like dropsdetect, but this is not interesting)

Note2: trades from the exchange arrive in turn, i.e. Spike begins to draw from top to bottom not instantly. Because of this, at some point (when the spike has become lower than MStrikeDepth, a detection will occur, in the meantime, the trades can go even lower. To override, see below MStrikeBuyDelay)

MStrikeVolume: The volume of spike at the time of detection is not less than.

MStrikeLastBidEMA: still in development.

MStrikeAddHourlyDelta: Similar to Moonshots, add% to MStrikeDepth for each percent of the hourly delta.

MStrikeAdd15minDelta: Similarly to above.

MStrikeAddMarketDelta: Similarly to above.

MStrikeAddBTCDelta: Similarly to above.

MStrikeBuyDelay: Delay in placing buy orders in milliseconds. It seems to be contrary to the idea of the strategy, but in a situation where trades after detection continue to draw the spike even lower, it can help. A delay is inserted between the detect and placing an order, during which the spike measurement continues.

Important:

The general parameters SellPrice and BuyPrice are REMOVED from this strategy! Instead, the parameters MStrikeBuyLevel and MStrikeSellLevel are introduced.

MStrikeBuyLevel – If 0, then we try to buy at the very bottom, if the value is 50.00 we try to buy 50% of the detected Strike depth, i.e. in the middle of it. Please note, that following trades from the same spike may arrive AFTER the detect has happened, simply because there is a delay between your Moonbot and the exchange server, that is sending you trades one by one, you need to make sure your strategy setting do not detect too early, otherwise, it is considered you are doing it intentionally and accept the risk.

MStrikeBuyRelative – If YES, it is counted as described in MStrikeBuyLevel. If NO, then the purchase order will be set at the specified percentage of the price at the moment of the detect. Example: MStrikeBuyRelative = YES, MStrikeBuyLevel = 5 – put a buy order 5% higher than the lowest point of the spike at the moment of the detect. MStrikeBuyRelative = NO, MStrikeBuyLevel = -5 – put a buy order at -5% from the price BEFORE the spike.

MStrikeSellLevel – percentage of the depth of the spike (and not the purchase price). For example, a spike 10% deep, SellPrice = 80% – in this case we sell 80% from 10% = +8% above the lowest detected price of the spike.

Order size must be specified, indication 0 will not take ordersize from the slider off the main screen.

MStrikeDirection - has 3 values for placing orders: Both (symmetrically in both directions), OnlyLong (only long orders), OnlyShort (only short orders). Both and OnlyShort options are available for Futures trading only.

MStrikeWaitDip: Wait until a trade appears with a price higher (or for a short - lower) than the previous one. (in any direction, i.e. for a long: a spike from sell orders, then a buy or sell appears with a price higher = detection). Wait no more than 10 seconds, if suddenly the trade did not appear, then the order is not placed

The log messages consist of:

LastBidEMA value according to the formula above;

Min detected price of the spike at the time of placing the order

Spike depth in percent

The volume of the spike

Buy price

Pre-calculated selling price

For example:

04:13:00.097 BCD: MoonStrike LastBID: 0.00029700 min.Price: 0.00029500 Depth: 0.7% StrikeVol: 0.295 BTC  BuyPrice: 0.00029500 sell +0.7% SellPrice: 0.00029699

The strategy is available only If you tick the “I agree to send the results of my transactions to the server” (“Settings – Login”) on all your bots and keep the check mark on for at least a week before using the strategy.

A strategy for fast automatic purchase and sale of new coins on the listing.

Working Principle:

If you want to buy a coin on the listing, you create one NewListing strategy, or several if you have the "Multiorder" module connected, with a fixed price in absolute value (parameter BuyPriceAbsolute=YES), or in percentage of listing price (parameter BuyPriceAbsolute=NO). As soon as the trading starts, the bot will immediately place an order to buy a new coin according to the set parameters.

If you need to quickly sell the coins that you received before the listing and they are on your balance, then specify that you need to sell coins from the balance (SellFromAssets=YES), specify at what price to sell (SellPriceAbsolute=YES at absolute price or SellPriceAbsolute=NO as a percentage of ASK price), specify the number of coins to sell from the balance (SellQuantity=1000 - sell 1000 coins, if SellQuantity=0, then sell all coins). As soon as trading starts, the bot will immediately sell the required number of coins at the specified parameters.

The strategy does not have a separate Strategy setting tab, but when you create it, special parameters appear in the general tabs.

In the Buy conditions tab:

buyPriceAbsolute: NO/YES (default is NO),

If NO, then buyPrice is calculated as a percentage of the market price (for example 1%), if YES, then buyPrice is calculated as an absolute value (for example $1).

In the Sell order tab:

SellPriceAbsolute: NO/YES (default is NO),

if NO, SellPrice is considered a percentage of the ASK price (for example 1%), if YES, SellPrice is considered an absolute value (for example $1).

SellFromAssets: NO/YES (default is NO),

If NO, then strategy will not sell coins from balance, if YES, then strategy will sell coins from balance.

SellQuantity: the number of coins to sell from the balance (e.g. 1000 coins), if set to "0", then all coins must be sold.

Combo is a pair of 2 strategies(“Start” + “End”), which works together: after the first strategy “Start” has signaled, the bot starts to wait for the second strategy “End” for the specified time. If the “End” strategy has signaled during the waiting period, the bot will buy the coin and use Combo strategy settings to trade it. Otherwise, the bot waits for the “Start” strategy again.

Note: autobuy should be turned off in both “Start” and “End” strategy!

All 3 strategies must be active.

Parameters:

ComboStart: The first strategy

ComboEnd: The second strategy

ComboDelayMin: Time between 1st and 2nd strategy signals, not less than, seconds

ComboDelayMax: Time between 1st and 2nd strategy signals, not more than, seconds

The TopMarket strategy is automatically created on first launch and is active by default. If you want to disable it, click on the "Remove selection" button. 

The TopMarket strategy signals a detection for the coins with the highest 15m delta. 

DeltaMin: percent value (0 or any positive value).

The lower threshold for a coin’s delta to trigger a detect.

TMSameDirection: YES / NO (default = YES)

Opens a position based on the trend or against it, the direction of the trend is determined by comparing the average price over the last hour with the current price on a specific coin.

а) TMSameDirection = YES (position will open following the trend, if it was a long position, it will open long)

b) TMSameDirection = NO (position will open against the trend, if it was a long, it will open a short position)

Note that with both TMSameDirection = YES and TMSameDirection = NO, the TopMarket strategy can accrue both long and short positions. If you want to accumulate positions only in one direction that you need, then do it through triggers: you define a strategy TopMarket as a MASTER strategy without buying, which triggers SLAVE strategy (for example EMA), which then buys in the desired direction (only short or only long), regardless of the trend direction.

The TopMarket strategy is one of the core strategies and can be used both for auto-trading and coin detection during manual trading sessions.

For more flexible settings for manual trading, there is a special strategy type “Manual”. To start using it, create one or more strategies of this type, don’t mark them with checkboxes and don’t start them. Unlike other strategies, “Manual” is turned by using the main menu, “Use Manual strategy” (look picture below). If you have more then 1 manual strategy, you may switch them by clicking on the caption with strategy name.

Note: when using manual strategy, its filters are applied when you click to set buy order; If you don’t need filters, put in the strategy loose high values: for coin’s Delta 0..1000, for BTC and markets delta -100..+100

The strategy is based on detecting liquidations and setting long or short orders depending on the type of liquidated orders.

This strategy is part of the “Binance Futures” module and is available to all who have activated the module (including the trial period).

Concept: for a given period of time, liquidations are being checked, their number, total volume (in USDT) and direction (long or short positions liquidated).

If LiqWaitTime > 0, then the lack of new liquidations for a set time period is also checked (in ms). Depending on the LiqDirection, the strategy can execute on both unique detections for a LiqTime time period and also check for combinations of consecutive detections (the minimum time between detections is set in the NextDetectPenalty filter, the maximum time is not limited): liquidations (short, long), (long, short), (short, short), (long, long). Example: the LiqDetection Twice strategy will execute only if two detections of the same type will occur (either short or long) in a row, with a minimum time interval between them equal to NextDetectPenalty; the time interval for the detections is set by LiqTime.

Parameter descriptions

LiqTime: time interval between counting liquidations, seconds;

LiqCount: number of liquidations within an interval (if null, is disregarded)

LiqVolumeMin: minimum volume of liquidations within a set interval, in USDT (if null, is disregarded)

LiqVolumeMax: maximum volume of liquidations within a set interval, in USDT (if null, is disregarded)

LiqWaitTime: time waiting after a detection for lack of new liquidations, millisec.;

LiqWithinTime: time since last liquidation is less than, millisec., (if null, is disregarded);

LiqDirection: the direction of liquidated positions (Both – any direction, OnlyShort – counting only short positions, OnlyLong – counting only long positions, Combo – two oposite positions in a row, Twice – two similar positions in a row);

LiqSameDirection: sets an order in the same direction or in the oposite direction, YES – the set order will repeat the direction of the liquidation, NO – the set order will be in the oposite direction;

Liq_BV_SV_Time: time for calculating volumes, in milliseconds;

Liq_BV_SV_Filter: threshold value bv sv, (if 0, then ignored).

This parameter is part of the Extension Package for auto-trading, the description of its parameters can be read there.

This parameter is part of the Extension Package for auto-trading, the description of its parameters can be read there.

The following strategy is only available for PRO version users who are registered with our cash-back program.

This strategy detects fast price drops and places a buy order that then fluctuates within a price range, similar to the moon-shot, awaiting a repeated shot.

Both the price range and the initial position of the order is linearly dependent on the actual detect. The "swiftness" of the price drop is determined by the

HookTimeFram parameter (a time-frame to be analyzed). The strategy was developed to catch shots (HookTimeFrame = 2 sec.), but larger time frames

can also be used (up to 40 sec.)

Note:

1. In light of the inner workings of the strategy, the repeated detect is only possible after HookTimeFrame seconds (subject to discussions) (in abscence of this penalty, a spam of detects might occur).
2. The strategy calculates the detect conditions once every 0.5 seconds.
3. BuyModifier, unlike other strategies, affects only the width and depth of the price range in this strategy.

How it works: when a detect occurs, the deltas are recorded. Then, if the deltas start increasing, the difference of the current deltas and the

recorded ones are multiplied by their corresponding coefficient and affect the upper and lower limits of the price range.

Example:

BuyModifier = -3 (must be negative!)

coefficient Add3hDelta = 0.05

3hDelta at detect time = 10

later, the 3hDelta starts to grow rapidly = 50

Difference = 40

if at detect time, the price range was -2%, -3%, then at the time when the delta was = 50 (difference = 40) the price range will equal:

Upper Limit = -2+(40*0.05*(-3)/2)=-5%

Lower Limit = -3+(40*0.05*(-3))=-9%

Note! The upper limit increases twice slower thatn the Lower limit! In this way, a widening of the price range is achieved!

Parameter description

BuyOrderReduce: sets the interval (in ms) used to calculate the average trade volume. The strategy will place an order of size not larger than the average volume. By default = 100ms. Volume calculation: sum of all trades (buy and sell) over the TimeInterval interval, divided by BuyOrderReduce. Examlple: if TimeInterval = 5 sec (5000 ms), BuyOrderReduce = 100ms, the volume over 5 sec was 10 000$, the average volume over 100ms will equal 10000/5000ms*100ms=200$. In this case the strategy will place an order not larger than 200$.Alternatively, knowing the average volume over 100 / 10/ 5 ms, this will be the maximum order size of the strategyBuyOrderReduce=0 – parameter is turned offThe work of the order reduction function can be seen in the following inscription:IOTA: [1] (40) Buy order reduced: 1000.00$ => 23.32$ (Vol: 23.32$)In this log, the OrderSize in the strategy was 1000$, but the average volume over 100ms was just 23$, thus, the strategy has placed an order of 23$.

MinReducedSize: If after using BuyOrderReduce the order size becomes lower than the set size (in USDT), the order is not placed (and the corresponding detect will not exist). Default value = 0(not applied).

HookTimeFrame: time frame set for analysis.

HookDetectDepth: the depth of the detect.

HookDetectDepthMax: the maximum detect depth value for a shot. If 0, is ignored.

HookAntiPump parameter: If YES, it takes the average price before the detection to calculate the depth of detection, which helps filter out spikes right after a quick pump.

HookPriceRollBack: percentage of price roll back in percentage points relative to the general depth, 33% would mean a roll back by one third of the entire price movement

HookPriceRollBackMax: The rollback limit is no more than. If 0 (default), has no effect.

HookRollBackWait: The time during which the price stays above the RollBack (milliseconds). The recommended value of 100ms will cut off situations when the price immediately drops after detection. You can set more, but the entire event of a spike, rollback and waiting for a rollback must keep within the HookTimeFrame sec.

HookDropMin, HookDropMax: price decrease prior to the detect over the last 2 minutes, before and after. Is calculated in percentage points relative to the recorded depth of the shot.

Example: Take a 10% shot. But the price of the coin has allready been falling for 2 minutes before the shot and has already fallen by 20%.

In this case, the HookDrop = 20 / 10 * 100 = 200% (i.e the previous decrease in price is 200% larger than the shot itself). If 0, is ignored.

HookDirection: search for Long or Short detects or both.

HookOppositeOrder: place an order in the opposite direction (when an arrow is detected, put a short instead of a long)

HookInterpolate:

- If 0, the strategy will place an order from the uppermost price to the shot.

- If 1, the strategy will place an order from the rollback following the shot

- If 2, the HookInitialPrice parameter will be prioritized

- If 3, calculates the initial price and the corridor from current price, based on spike depth

- If 4, is based on rollback depth

If it contradicts the price range, the upper limit of the range will be moved up by half the distance between your order and the current price. If this is impossible, the detect will not execute.

Applying the same logic, the lower limit will be lowered.

The logic is the same for both short and long orders.

If HookInterpolate is set to 0, then the BuyModifier is not applied.

HookPriceDistance: the width of the price range. Set in percentage points relative to the general detect depth. For example: if a 5% fall was detected, a HookPriceDistance = 10% will mean that the order can move within the following limits -- upper limit HookPriceDistance = 5-5/100*10=4,5%, lower limit 5+5/100*10=5,5% from the current price. Just like the MoonShot, it will be moved when the price will come close to one of the limits. If 0, the order is not move like in case of MoonShot, will remain static until execution or cancellation.

HookPartFilledDelay: Delay for canceling a buy order after partial filling (milliseconds). If 0, there is no delay, the partially filled order is immediately canceled (as in moonshots)

HookSellLevel: replaces SellPrice. Is set in percent of the detect depth.

For example: SellPrice = 75% would mean that it should sell in the upper quarter of the shot. SellPrice = 100% would mean selling at the upmost point, at the start of the shot.

HookSellFixed: always calculate sell as (HookSellLevel * depth) percent, regardless of the buy price

HookReplaceDelay: Delay to replace the buy upon price drops

HookRaiseWait: Delay to replace the buy upon price raise

HookRepeatAfterSell: repeat buy order after the sell is executed

HookRepeatIfProfit: %, repeat if the sale closed with such or a large profit.

BuyOrderReduce: (the parameter has migrated from the Spread strategy and has similar values). Sets a time frame (in ms) for which the average tradin vaolume is calculated. The strategy will then place an order not larger than the average volume. Default value = 100 (ms). Volume is calculated as follows: all trades volume is sumed up (buy and sell) for the HookTimeFrame period and is devided by BuyOrderReduce.

For example: if HookTimeFrame = 5 sec (5000 ms), BuyOrderReduce = 100ms, the volume over 5 sec was 10000$, the average volume for 100ms will equal10000/5000ms*100ms=200$. In this case the strategy will place an order of no more than 200$.

In other words, we monitor the average volume over the last 100ms/10ms/5ms, that will be our maximum order size used by the strategy.

BuyOrderReduce=0 - parameter is turned off

The order reduction function execution can be observed in the log, in the following format:

IOTA: [1] (40) Buy order reduced: 1000.00$ => 23.32$ (Vol: 23.32$)

In this log, the OrderSize of the strategy was 1000$, while the average trading volume over 100ms was only 23$, thus the startegy has placed a

buy order of 23$.