---
id: 2020
title: "Version History"
section: version-history
category: "2020"
url: https://moonbot.pro/version-history?year=2020
locale: en
status: published
updated_at: 2026-08-17T23:09:59+03:00
---

# Version History

## 5.47

### 

- Latency fixed for cases when instantaneous execution is expected
- The built-in Telegram client was updated Attention! Might require a repeated logging into your Telegram account
- Some optimization of the MoonBot process priority.

### Binance Futures

- To motivate our community to participate in the upcoming trading tournament we are making the following changes:
  1. The maximum limit order for the Trial version is increased to 30$ (leverage not accounted for i.e. using the maximum leverage of x125, the maximum order amount becomes 30$x125 = 3750$ )
  2. The trial period for both modules will be reset two times. First reset will happen today, the second reset will happen on the day the tournament starts: April 10th.
  3. You can register for the tournament by following this link:https://www.binance.com — you must find the MoonTrader team and click the "Join" button.

## 5.46

### 

- With log level set to 5 the bot will not spam the log window anymore; service messages are written only into the log file
- API limits has been increased; its now correctly shown on the API load bar
- If you exeed the orders per minuite limit, the terminal will notify in the Telegram.

## 5.45

### 

- When using the HFT parameter, the bot will post CPU load in your Telegram channel.

### Binance Futures

- Fixed the "Gained USDT reports column
- Liquidations are not shown on all your bots anymore
- The MarkPrice filter
  - The MarkPrice filter is designed to avoid opening a position too far away from the mark price, which could lead to instant liquidation
  - The filter works with the MarkPrice delta, which is the percentile difference between the Market Price and the Mark Price. If the MarkPrice is above the market price, the difference will be negative and if it's below the market price, the difference will be positive
  - The filter is set with values from and to (MarkPriceMin, MarkPriceMax)
  - Example: MarkPriceMin=0 MarkPriceMax=1 - will choose all the coins where the MarkPrice is moved to the opposite side from the order by no more than 1%.(therefore, if mark price is 1% above the market price, no short orders will be placed; if the mark price is 1% below the market price, no long orders will be placed; in other cases, both short and long orders will be placed).

## 5.44

### 

- The parameter "Settings → Close charts in N minutes of inactivity" can be set to 0 (charts are closed in 10 seconds)
- New strategies parameter HFT(under the Buy Conditions chapter): determines the timeframe in milliseconds, during which the request to place an order (sent to the exchange) is valid. If 0 then not used (strategy works as previously). Read more in the bot, the News page ("Menu → News", under the discount chapter)
- The ping status string has now 2nd ping value: time, taken by Set Order commands. The exchange may execute API requests much slower then pure ping, that's why this timing is more important
- Binance Futures:
  - Liquidations are now show in the terminal's report.

## 5.43

### 

- The "Split" command hotkey (configure in the Settings → Hotkeys tab)
- The Split can be used in the UDP Trust Management
- Binance Futures:
  - The SamePosition filter now works in Telegram strategies
  - Separate colors for long and short liquidations on the chart
  - Max Leverage and margin type (cross/ isolated) are shown in the leverage dialog.

## 5.42

- Sell order split function (right-click on the order on market chart, select the "Split Order" menu).

## 5.41

### 

- Fixed bug when orders sometimes was missed in the report
- Added windows AutoLogon and autostart on windows startup settings (Menu → System Settings). Its recompensed to use them on vds as well as the "VDS mode" checkbox.