Misc settings

Various extra strategy options.

Miscellaneous settings parameters

These strategy settings allow you to control your stop limit and other uncategorized features.

Stop Limit

Sets a stop limit to sell a coin at a calculated loss.

After a stop limit sell order has been placed, the bot will go into buying mode after TRADES_TIMEOUT has passed and will buy again when market conditions meet your buying strategy.

Setting a stop limit at 60 would make sure that all holdings for a coin are sold when 60% value is lost, compared to the averaged bought price. E.g. average bought price is 100, stop limit is executed at 40 and all assets are sold.

With margin trading, the stop limit is set as a ROE value. Setting it to 1 will lead to the stop limit triggering when ROE reaches -1. Use a value that includes your leverage.

It's recommended to use STOP_BUY / STOP_SELL instead, when possible.These are placed at the same time as the position is opened.

SL Disable Buy

When set to true, buy orders will be disabled after a pair hits STOP_LIMIT.

For margin trading, buy orders will be disabled when a long position hits STOP_LIMIT.

SL Disable Sell

When set to true, sell orders will be disabled after a short position hits STOP_LIMIT.

Specific to margin trading.

Panic Sell

When set to true, all quote will be sold at market value as soon as possible. This may incur losses!

You should only enable this when you want to sell your current holdings immediately.

For margin trading, this setting will delete any open orders and close any position as soon as possible. Pairs are not automatically disabled afterwards.

Trades Timeout

Sets a timeout between two trades for a single pair, in this time no trades will be placed.

Count Sell

Sets a maximum number of sell orders before automatically disabling a pair.

Setting this to 5 disables the pair after 5 strategy sell orders took place (not including RT). No further trades will happen until you re-enable the pair. The COUNT_SELL counter gets reset after a pair is re-enabled.

This parameter is irrelevant for margin trading.

Maker Fees

Futures platforms: When set to true, limit orders will placed as post only orders. If the order can be (partially) filled immediately, it will get cancelled by the exchange. Using PRE_ORDER you can configure how far from bid/ask the order gets placed, you must use a negative value for PRE_ORDER_GAP for post only orders.

Other exchanges: When set to true, limit buy orders are placed at bid, limit sell orders are placed at ask. This increases the likelyhood that the trade is executed with maker fees.

Ignore Trades Before

Optional parameter to force Gunbot to not consider any trades before the set timestamp.

Only ever use this when you know exactly what you are accomplishing, and for example want to prevent RT from being started on a pair where the last sell order resulted in a loss.

Use https://currentmillis.com/ to convert human readable time to unix timestamps, make sure to use the timestamp in milliseconds.

Bought price

Exchanges often don't provide order information anymore on trades that happened longer ago. This parameter exists to manually specify a reference price per unit that Gunbot should consider when selling an asset for which no bought price is provided by the exchange.

This parameter should only be used as an override.

The override is only valid when no bought price can be retrieved from the exchange. In case you want to forcefully override an available bought price, you can apply IGNORE_TRADES_BEFORE and remove the pairs state json file after doing so.

This parameter is irrelevant for margin trading

Liquidity maker

Use any strategy as a liquidity provider on spot markets, by using a simple staggered orders strategy that places orders at many positions in the order book.

Liquidity maker

Enables a staggered orders strategy variant that continuously places up to 9 orders on the bid side of the order book. If there is enough quote balance, up to 9 orders are placed on the ask side as well. You profit from the spread between bid and ask, provided the spread is higher than your trading fees.

Each order is in value of 1x TRADING_LIMIT. Potentially it can use your whole balance.

This works in addition to your regular strategy. You can disable the regular strategy by setting both buy and sell enabled to "false".

Liquidity taker

In addition to maker orders, use taker orders when reaching your targets or to DCA.

When GAIN is reached, every round a market sell order of 1x TRADING_LIMIT gets fired to reduce your position in profit.

When price drops below the average bought price, every round a market buy order of 1x TRADING_LIMIT gets fired to bring down the average price per unit.

Liquidity gain

Option to enforce sell orders to be placed at or above break-even. Disable this to provide pure liquidity.

Max invested base

Limits the total position size for liquidity maker and taker orders. When the maximum value is reached, no more liquidity maker or taker orders that would add to the position are placed .

Order type settings

On exchanges that support market orders, you can select which types of orders should be sent as limit or market.

Not all exchanges support market orders

Test if your market orders execute before leaving your strategy run unattended.

Market Buy

When set to true, strategy buy/long orders will be placed as market order.

Market Sell

When set to true, strategy sell/short orders will be placed as market order.

Market RT Buy

When set to true, RT_BUY orders will be placed as market order.

Market RT Sell

When set to true, RT_SELL orders will be placed as market order.

Market Buyback

When set to true, RT Buyback orders will be placed as market order.

Market DU

When set to true, DU orders will be placed as market order.

Market Close

When set to true, position close orders at Bitmex will be placed as market order.

Market Stop

When set to true, position stop orders at Bitmex will be placed as market order.

Market FOK

When set to true, FOK orders will be placed as market order. This refers to orders placed within CANCEL_ORDERS_CYCLE_CAP.

PreviousTrailMe NextConfig marketplace

Last updated 4 years ago

Was this helpful?