Community. StockSharp

Seamless Setup: Installing Interactive Brokers IB Gateway on Linux with Easy-to-Follow Instructions

2024-03-19T01:24:32Z

FMZ platform now supports the integration of Interactive Brokers (IB). It's quite simple on Windows, so we won't explain how to install it here. For Linux users who generally rent servers without a graphical interface and only have SSH, the installation is more challenging. This article will explain how to install IB Gateway for quantitative trading. We usually choose to install IB Gateway instead of TWS client, because the TWS client shuts down periodically and is not suitable for quantitative trading. Here we take Debian as an example:

**Step 1: Install Desktop Services and VNC**

First, you need to install desktop services and a VNC server to enable remote desktop access. Here, we will use xfce and TightVNC as examples. Execute the following commands in the terminal to install:

```
sudo apt update
sudo apt install xfce4 xfce4-goodies dbus-x11
sudo apt install tightvncserver
tightvncserver
```
Please note that the maximum length for the password during installation is 8 characters. Please set a highly secure password. The default startup port for the first session is 5901.

**Step 2: Connect to VNC and Install IB Gateway**

The default address is ```vnc://IP Address:5901```, you can log in by entering the password. For Windows, please download and install the VNC client yourself.

Download page: https://www.interactiveb...ng/ibgateway-stable.php
Please use a tool similar to wget for downloading. If you can't find the corresponding version, please click on "Download for Other Operating Systems" on the page to search.

```
wget https://download2.intera...standalone-linux-x64.sh
```
If it's inconvenient to download within VNC, you can initiate a separate SSH download and then install it under the VNC desktop environment.

```
bash ibgateway-stable-standalone-linux-x64.sh
```
The interface can already be displayed here, you can manually run the installation directory directly by running ```./ibgateway```.
https://stocksharp.com/file/149319
After installation, log in and find the API option. Make sure to uncheck "Read-Only API". The port number is also in the settings. Please configure the exchange correctly according to this port number.
https://stocksharp.com/file/149320
The exchange is configured as follows: Client ID. If you have multiple robots that need to connect, this needs to be set to different IDs, as IB does not allow the same Client ID to connect simultaneously.
https://stocksharp.com/file/149321
It should be noted that localhost and 127.0.0.1 are not the same network address at the lower level of the Linux operating system, here we use localhost.

IB's market data requires a paid subscription. If you need real-time ticker and depth information, please subscribe for a fee, otherwise you can only receive delayed tickers.

From: https://blog.mathquant.c...teway-in-linux-bash.html

Harness the Power of FMZ Extended API: A Step-by-Step Guide to Batch Modify Bot Parameters with Ease

2024-03-18T08:56:55Z

How can I change the parameters of live tradings in batch on FMZ? When the number of live tradings exceeds dozens and reaches hundreds, it would be very inconvenient to configure live tradings one by one manually. At this time, we can use the FMZ extended API to complete these operations. So in this article, we will explore the group control of the bot, update some details of the parameters.

In the previous article, we solved the problem of how to use the FMZ extended API to monitor all the live tradings, group control live tradings, and send commands to the live tradings. And we still use the interface call code we encapsulated in the previous article as a basis, continue to write code to realize the batch modification of the parameters of the live trading.

Parameter settings:
https://stocksharp.com/file/149294
Strategy code:

```
// Global variable
var isLogMsg = true // Controls whether logs are printed or not
var isDebug = false // Debugging mode
var arrIndexDesc = ["all", "running", "stop"]
var descRobotStatusCode = ["Idle", "Running", "Stopping", "Exited", "Stopped", "There is an error in the strategy"]
var dicRobotStatusCode = {
"all" : -1,
"running" : 1,
"stop" : 4,
}

// Extended logging functions
function LogControl(...args) {
if (isLogMsg) {
Log(...args)
}
}

// FMZ extended API call functions
function callFmzExtAPI(accessKey, secretKey, funcName, ...args) {
var params = {
"version" : "1.0",
"access_key" : accessKey,
"method" : funcName,
"args" : JSON.stringify(args),
"nonce" : Math.floor(new Date().getTime())
}

var data = `${params["version"]}|${params["method"]}|${params["args"]}|${params["nonce"]}|${secretKey}`
params["sign"] = Encode("md5", "string", "hex", data)

var arrPairs = []
for (var k in params) {
var pair = `${k}=${params[k]}`
arrPairs.push(pair)
}
var query = arrPairs.join("&")

var ret = null
try {
LogControl("url:", baseAPI + "/api/v1?" + query)
ret = JSON.parse(HttpQuery(baseAPI + "/api/v1?" + query))
if (isDebug) {
LogControl("Debug:", ret)
}
} catch(e) {
LogControl("e.name:", e.name, "e.stack:", e.stack, "e.message:", e.message)
}
Sleep(100) // Control frequency
return ret
}

// Get information about all running bots for the specified strategy Id.
function getAllRobotByIdAndStatus(accessKey, secretKey, strategyId, robotStatusCode, maxRetry) {
var retryCounter = 0
var length = 100
var offset = 0
var arr = []

if (typeof(maxRetry) == "undefined") {
maxRetry = 10
}

while (true) {
if (retryCounter > maxRetry) {
LogControl("Maximum number of retries exceeded", maxRetry)
return null
}
var ret = callFmzExtAPI(accessKey, secretKey, "GetRobotList", offset, length, robotStatusCode)
if (!ret || ret["code"] != 0) {
Sleep(1000)
retryCounter++
continue
}

var robots = ret["data"]["result"]["robots"]
for (var i in robots) {
if (robots[i].strategy_id != strategyId) {
continue
}
arr.push(robots[i])
}

if (robots.length < length) {
break
}
offset += length
}

return arr
}
```
### Get to Know the RestartRobot Function of the FMZ Extended API First
When we need to batch modify the parameters of the live trading and then run it, there are 2 cases for this scenario to begin with.

- 1. Bot has been created
For a live trading that has already been created, it is natural to restart it using the RestartRobot function, which is an extended API interface to FMZ.
- 2. Bot has not been created
For the live trading has not been created, there is no need to "modify" the parameters of the live trading, that's the batch creation of the live trading to run, and we use FMZ extended API interface - NewRobot function.

But no matter what kind of method, the next idea as well as the operation are similar, so we will use the ```RestartRobot``` extended API function as an example to explain.

RestartRobot function is used in two ways:

- 1. Configuration with only live trading ID passed in, not the parameters of live trading
This approach keeps the parameter configuration unchanged when the live trading stopped, and restarts the live trading only.
- 2. Configuration with live trading ID and the parameters of live trading passed in
This approach starts the live trading running with the new parameter configuration.

The first approach is not useful for our demand scenario, because our own demand is to modify a large number of parameters of the live trading in bulk. So the question is, the configuration of the parameters of the live trading is very complex, there are exchange object configuration, strategy parameter configuration, K-line period settings and so on.

Do not worry, let's explore them one by one.

### Get the Information of the Live Trading You Want to Operate
On FMZ, if you want to modify the parameter configuration of a live trading, then it must be non-running. Because only a live trading that is not running can have its parameter configuration modified. A live trading that is not in the running state may be in:

- The strategy stopped.
- Strategy has errors, stopped.

So we need to get the live tradings for the specified strategy first, and these live tradings are in a **stopped state** or **have an error to stop**.

```
function main() {
var stopRobotList = getAllRobotByIdAndStatus(accessKey, secretKey, strategyId, 4)
var errorRobotList = getAllRobotByIdAndStatus(accessKey, secretKey, strategyId, 5)
var robotList = stopRobotList.concat(errorRobotList)
}
```
This gives us all the information about the live trading that we need to change the configuration of, next we will get the detailed configuration of the live trading.

### Modification of Live Trading Configuration Parameters
For example, the live trading strategy for which we need to modify the parameters is as follows (i.e., the strategy whose strategy ID is the strategyId variable):
https://stocksharp.com/file/149295
https://stocksharp.com/file/149296
The strategy has 3 parameters as a test.

Modify the strategy parameters for the live trading, but maybe we don't want to modify the strategy's exchange configuration, but for the Extended API interface RestartRobot function, either no parameters are specified (as is just start the live trading) or all parameter configurations must be specified.

That is to say, before we use the RestartRobot function to start the live trading, we must use the extended API interface GetRobotDetail function to get the current configuration of the live trading first, and then we replace the part of the parameters that need to be modified, to re-construct the configuration parameters for the start of the live trading (i.e., the parameters that will be used to call RestartRobot), and then restart the live trading.

So, next we traverse robotList, and get the current parameter configuration one by one, the ```/**/``` commented part of the following code is the live trading details, we need to deal with these data.

```
function main() {
var stopRobotList = getAllRobotByIdAndStatus(accessKey, secretKey, strategyId, 4)
var errorRobotList = getAllRobotByIdAndStatus(accessKey, secretKey, strategyId, 5)

var robotList = stopRobotList.concat(errorRobotList)
_.each(robotList, function(robotInfo) {
var robotDetail = callFmzExtAPI(accessKey, secretKey, "GetRobotDetail", robotInfo.id)

/*
{
"code": 0,
"data": {
"result": {
"robot": {
...
"id": 130350,
...
"name": "Test 1B",
"node_id": 3022561,
...
"robot_args": "[[\"pairs\",\"BTC_USDT,ETH_USDT,EOS_USDT,LTC_USDT\"],[\"col\",3],[\"htight\",300]]",
"start_time": "2023-11-19 21:16:12",
"status": 5,
"strategy_args": "[[\"pairs\",\"Currency list\",\"English comma spacing\",\"BTC_USDT,ETH_USDT,EOS_USDT,LTC_USDT\"],[\"col\",\"breadth\",\"Total width of the page is 12\",6],[\"htight\",\"height\",\"unit px\",600],[\"$$$__cmd__$$$coverSymbol\",\"close the position\",\"close out trading pairs\",\"\"]]",
"strategy_exchange_pairs": "[3600,[186193],[\"BTC_USD\"]]",
"strategy_id": 131242,
"strategy_last_modified": "2023-12-09 23:14:33",
"strategy_name": "Test 1",
...
}
},
"error": null
}
}
*/

// Parse the exchange configuration data
var exchangePairs = JSON.parse(robotDetail.data.result.robot.strategy_exchange_pairs)

// Get the exchange object index, trading pairs, these settings are not going to be changed
var arrExId = exchangePairs[1]
var arrSymbol = exchangePairs[2]

// Parse parameter configuration data
var params = JSON.parse(robotDetail.data.result.robot.robot_args)

// Update parameters
var dicParams = {
"pairs" : "AAA_BBB,CCC_DDD",
"col" : "999",
"htight" : "666"
}

var newParams = []
_.each(params, function(param) {
for (var k in dicParams) {
if (param[0] == k) {
newParams.push([k, dicParams[k]]) // Construct the strategy parameters and update the new parameter values
}
}
})

// Note that if there are spaces in the data you need to transcode it, otherwise the request will report an error
settings = {
"name": robotDetail.data.result.robot.name,
// Strategy parameter
"args": newParams,
// The strategy ID can be obtained by the GetStrategyList method.
"strategy": robotDetail.data.result.robot.strategy_id,
// K-period parameter, 60 means 60 seconds
"period": exchangePairs[0],
// Specifies which docker to run on; not writing this attribute means automatically assigning the run
"node" : robotDetail.data.result.robot.node_id,
"exchanges": []
}

for (var i = 0 ; i < arrExId.length ; i++) {
settings["exchanges"].push({"pid": arrExId[i], "pair": arrSymbol[i]})
}
Log(settings) // Test
var retRestart = callFmzExtAPI(accessKey, secretKey, "RestartRobot", robotInfo.id, settings)
Log("retRestart:", retRestart)
})
}
```
After running the batch parameter modification strategy, my live trading:

- Test 1A
- Test 1B

Batch modification of parameters was done with the configured exchange objects, trading pairs and K-line periods unchanged:

It was changed on the live trading page automatically:
https://stocksharp.com/file/149297
And start running. Because we specified the modified parameters in the code above:

```
// Update parameters
var dicParams = {
"pairs" : "AAA_BBB,CCC_DDD",
"col" : "999",
"htight" : "666"
}
```
### END
For dozens, hundreds of live trading batch modify parameters, this method is more convenient. In the example, the parameters are modified to a uniform, of course you can customize your own modification rules in the code to specify different parameter configurations for each live trading. Or specify different exchange objects, trading pairs and so on.

For the FMZ platform, these requirements are flexible and customizable to achieve. Feel free to leave a comment if you have any requirement ideas, we can discuss, research and learn from each other , and find the solution to the problem.

From: https://blog.mathquant.c...rameters-of-the-bot.html

Unlocking the Secrets of Perpetual Contract Grid Strategy Parameter Optimization with Python Backtesting

2024-03-18T05:23:38Z

The perpetual grid strategy is a popular classic strategy on FMZ platform. Compared with the spot grid, there is no need to have currencies, and leverage can be added, which is much more convenient than the spot grid. However, since it is not possible to backtest on the FMZ Quant Platform directly, it is not conducive to screening currencies and determining parameter optimization. In this article, we will introduce the complete Python backtesting process, including data collection, backtesting framework, backtesting functions, parameter optimization, etc. You can try it yourself in juypter notebook.

### Data Collection
Generally, it is enough to use K-line data. For accuracy, the smaller the K-line period, the better. However, to balance the backtest time and data volume, in this article, we use 5min of data from the past two years for backtesting. The final data volume exceeded 200,000 lines. We choose DYDX as the currency. Of course, the specific currency and K-line period can be selected according to your own interests.

```
import requests
from datetime import date,datetime
import time
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
import requests, zipfile, io
%matplotlib inline

def GetKlines(symbol='BTC',start='2020-8-10',end='2021-8-10',period='1h'):
Klines = []
start_time = int(time.mktime(datetime.strptime(start, "%Y-%m-%d").timetuple()))*1000
end_time = int(time.mktime(datetime.strptime(end, "%Y-%m-%d").timetuple()))*1000
while start_time < end_time:
res = requests.get('https://fapi.binance.com/fapi/v1/klines?symbol=%sUSDT&interval=%s&startTime=%s&limit=1000'%(symbol,period,start_time))
res_list = res.json()
Klines += res_list
start_time = res_list[-1][0]
return pd.DataFrame(Klines,columns=['time','open','high','low','close','amount','end_time','volume','count','buy_amount','buy_volume','null']).astype('float')

df = GetKlines(symbol='DYDX',start='2022-1-1',end='2023-12-7',period='5m')
df = df.drop_duplicates()
```
### Backtesting Framework
For backtesting, we continue to choose the commonly used framework that supports USDT perpetual contracts in multiple currencies, which is simple and easy to use.

```
class Exchange:

def __init__(self, trade_symbols, fee=0.0004, initial_balance=10000):
self.initial_balance = initial_balance #Initial assets
self.fee = fee
self.trade_symbols = trade_symbols
self.account = {'USDT':{'realised_profit':0, 'unrealised_profit':0, 'total':initial_balance, 'fee':0}}
for symbol in trade_symbols:
self.account[symbol] = {'amount':0, 'hold_price':0, 'value':0, 'price':0, 'realised_profit':0,'unrealised_profit':0,'fee':0}

def Trade(self, symbol, direction, price, amount):

cover_amount = 0 if direction*self.account[symbol]['amount'] >=0 else min(abs(self.account[symbol]['amount']), amount)
open_amount = amount - cover_amount
self.account['USDT']['realised_profit'] -= price*amount*self.fee #Deduction of handling fee
self.account['USDT']['fee'] += price*amount*self.fee
self.account[symbol]['fee'] += price*amount*self.fee

if cover_amount > 0: #Close the position first.
self.account['USDT']['realised_profit'] += -direction*(price - self.account[symbol]['hold_price'])*cover_amount #Profits
self.account[symbol]['realised_profit'] += -direction*(price - self.account[symbol]['hold_price'])*cover_amount

self.account[symbol]['amount'] -= -direction*cover_amount
self.account[symbol]['hold_price'] = 0 if self.account[symbol]['amount'] == 0 else self.account[symbol]['hold_price']

if open_amount > 0:
total_cost = self.account[symbol]['hold_price']*direction*self.account[symbol]['amount'] + price*open_amount
total_amount = direction*self.account[symbol]['amount']+open_amount

self.account[symbol]['hold_price'] = total_cost/total_amount
self.account[symbol]['amount'] += direction*open_amount

def Buy(self, symbol, price, amount):
self.Trade(symbol, 1, price, amount)

def Sell(self, symbol, price, amount):
self.Trade(symbol, -1, price, amount)

def Update(self, close_price): #Updating of assets
self.account['USDT']['unrealised_profit'] = 0
for symbol in self.trade_symbols:
self.account[symbol]['unrealised_profit'] = (close_price[symbol] - self.account[symbol]['hold_price'])*self.account[symbol]['amount']
self.account[symbol]['price'] = close_price[symbol]
self.account[symbol]['value'] = abs(self.account[symbol]['amount'])*close_price[symbol]
self.account['USDT']['unrealised_profit'] += self.account[symbol]['unrealised_profit']
self.account['USDT']['total'] = round(self.account['USDT']['realised_profit'] + self.initial_balance + self.account['USDT']['unrealised_profit'],6)
```
### Grid Backtest Function
The principle of the grid strategy is very simple. Sell when the price rises and buy when the price falls. It specifically involves three parameters: initial price, grid spacing, and trading value. The market of DYDX fluctuates greatly. It fell from the initial low of 8.6U to 1U, and then rose back to 3U in the recent bull market. The default initial price of the strategy is 8.6U, which is very unfavorable for the grid strategy, but the default parameters backtested a total profit of 9200U was made in two years, and a loss of 7500U was made during the period.
https://stocksharp.com/file/149291
```
symbol = 'DYDX'
value = 100
pct = 0.01

def Grid(fee=0.0002, value=100, pct=0.01, init = df.close[0]):
e = Exchange([symbol], fee=0.0002, initial_balance=10000)
init_price = init
res_list = [] #For storing intermediate results
for row in df.iterrows():
kline = row[1] #To backtest a K-line will only generate one buy order or one sell order, which is not particularly accurate.
buy_price = (value / pct - value) / ((value / pct) / init_price + e.account[symbol]['amount']) #The buy order price, as it is a pending order transaction, is also the final aggregated price
sell_price = (value / pct + value) / ((value / pct) / init_price + e.account[symbol]['amount'])
if kline.low < buy_price: #The lowest price of the K-line is lower than the current pending order price, the buy order is filled
e.Buy(symbol,buy_price,value/buy_price)
if kline.high > sell_price:
e.Sell(symbol,sell_price,value/sell_price)
e.Update({symbol:kline.close})
res_list.append([kline.time, kline.close, e.account[symbol]['amount'], e.account['USDT']['total']-e.initial_balance,e.account['USDT']['fee'] ])
res = pd.DataFrame(data=res_list, columns=['time','price','amount','profit', 'fee'])
res.index = pd.to_datetime(res.time,unit='ms')
return res
```
https://stocksharp.com/file/149292
### Initial Price Impact
The setting of the initial price affects the initial position of the strategy. The default initial price for the backtest just now is the initial price at startup, that is, no position is held at startup. And we know that the grid strategy will realize all profits when the price returns to the initial stage, so if the strategy can correctly predict the future market when it is launched, the income will be significantly improved. Here, we set the initial price to 3U and then backtest. In the end, the maximum drawdown was 9200U, and the final profit was 13372U. The final strategy does not hold positions. The profit is all the fluctuation profits, and the difference between the profits of the default parameters is the position loss caused by inaccurate judgment of the final price.

However, if the initial price is set to 3U, the strategy will go short at the beginning and hold a large number of short positions. In this example, a short order of 17,000 U is directly held, so it faces greater risks.
https://stocksharp.com/file/149293
### Grid Spacing Settings
The grid spacing determines the distance between pending orders. Obviously, the smaller the spacing, the more frequent the transactions, the lower the profit of a single transaction, and the higher the handling fee. However, it is worth noting that as the grid spacing becomes smaller and the grid value remains unchanged, when the price changes, the total positions will increase, and the risks faced are completely different. Therefore, to backtest the effect of grid spacing, it is necessary to convert the grid value.

Since the backtest uses 5m K-line data, and each K-line is only traded once, which is obviously unrealistic, especially since the volatility of digital currencies is very high. A smaller spacing will miss many transactions in backtesting compared with the live trading. Only a larger spacing will have reference value. In this backtesting mechanism, the conclusions drawn are not accurate. Through tick-level order flow data backtesting, the optimal grid spacing should be 0.005-0.01.

```
for p in [0.0005, 0.001 ,0.002 ,0.005, 0.01, 0.02, 0.05]:
res = Grid( fee=0.0002, value=value*p/0.01, pct=p, init =3)
print(p, round(min(res['profit']),0), round(res['profit'][-1],0), round(res['fee'][-1],0))

0.0005 -8378.0 144.0 237.0
0.001 -9323.0 1031.0 465.0
0.002 -9306.0 3606.0 738.0
0.005 -9267.0 9457.0 781.0
0.01 -9228.0 13375.0 550.0
0.02 -9183.0 15212.0 309.0
0.05 -9037.0 16263.0 131.0
```
### Grid Transaction Value
As mentioned before, when the fluctuations are the same, the greater the value of the holding, the risk is proportional. However, as long as there is no rapid decline, 1% of the total funds and 1% of the grid spacing should be able to cope with most market conditions. In this DYDX example, a drop of almost 90% also triggered a liquidation. However, it should be noted that DYDX mainly falls. When the grid strategy goes long when it falls, it will fall by 100% at most, while there is no limit on the rise, and the risk is much higher. Therefore, Grid Strategy recommends users to choose only the long position mode for currencies they believe have potential.

From: https://blog.mathquant.c...ameter-optimization.html

How to Exploit Brainless Selling Bots with a High-Frequency Strategy in 80 Lines of Code

2024-03-18T01:37:44Z

# How to Exploit Brainless Selling Bots with a High-Frequency Strategy in 80 Lines of Code

### Opportunity Observation
Recently, I found that Binance has a currency STORJ market is very strange unintentionally when I was watching the market, the trading volume is very large, and the trading frequency is very fast, the specific one-minute K-line of the following chart, we can see that the trading volume of each minute are consistent, and the minute K-line can be seen in a long lower shadow line.
https://stocksharp.com/file/149286
Observe with Binance 1-second K-line, I found out the end of the story, someone is marketed 10,000-20,000 STORJs every 5-7s, regardless of the cost, and smashing a small hole in the K-line directly, while the price recovers in the short term. This operation was obviously caused by a robot on an iceberg commission. This selling operation lasted for a very long time, totaling an estimated $10 million level, and in many cases caused slippage of up to 0.1%, which means that the executor of this strategy lost tens of thousands of dollars in slippage on the trade only. But with such a mechanical operation and active trading, there was a clear opportunity for market making scalping.
https://stocksharp.com/file/149288
A simple change to the original spot HF strategy, and in a few minutes I got this bot that specializes in exploiting this brainless sale of iceberg commissions.

### Strategy Idea
Since the market sells in market price every few seconds, we just need to find the 10k depth in the buy order book and hang the order in front of it. So that when the iceberg sells, a high probability that the market-making robot just can receive, and at this time the transaction is very active, the momentary price decline also triggered some buy orders. By the same token, hanging sell orders can be thrown in the trend, so repeated operations. The frequency of transactions is very high, even if each time the yield is not large, the total return is also quite substantial. Of course, the premise of everything is to have a low-fee account, if the buying and selling fees both are 0.1%, then the space is not enough to pay the fees.

### Strategy Performance
The strategy is performing as follows, at first, none of the profits were printing, so I changed it this afternoon, and print out the profits, the crazy selling robots have changed the volume to about 5000 at a time, so it's past the optimal time for arbitrage. I'm probably making 100-200U per hour at first, the key is risk free and low cost. On the flip side, the iceberg commission actually has a lot of skills, if you know how to write a strategy, you can spend ten minutes on FMZ to write the iceberg commission strategy that observes the depth of the buy order to decide the size and price of the order, observes the size of the active buy order to adjust the size of the pending order and take up the market monitoring and other characteristics, saving tens of thousands of dollars easily.
https://stocksharp.com/file/149289
### Strategy Source Code
The strategy code is very simple, only 80 lines, which is suitable for beginners, here are some of the parameters such as order precision and so on written fixed in the program, you can change the parameters as follows. It is recommended to save it, in case of any exchange trading pairs or the traders are out of control, you can fell free to charge them some interest at any time.
https://stocksharp.com/file/149290
```
function CancelPendingOrders() {
var orders = _C(exchange.GetOrders)
for (var j = 0; j < orders.length; j++) {
exchange.CancelOrder(orders[j].Id, orders[j])
}
}

function onexit(){
CancelPendingOrders()
}

function GetPrice(Type, Depth) {
var sumAmount = 0
var checkAmount = Type == "Buy" ? CheckBuyAmount : CheckSellAmount
var deep = Type == "Buy" ? Depth.Bids : Depth.Asks
for(var i = 0; i < Math.min(20, deep.length); i++) {
if(Type == "Buy" && deep[i].Price == lastBuyPrice && buyId){
sumAmount += deep[i].Amount - amountBuy //Subtract your own pending orders here
}else if(Type == "Sell" && deep[i].Price == lastSellPrice && sellId){
sumAmount += deep[i].Amount - amountSell
}else{
sumAmount += deep[i].Amount
}
if(sumAmount >= checkAmount){
return deep[i].Price
}
}
return deep[19].Price
}

function OnTick() {
var depth = _C(exchange.GetDepth)
var buyPrice = _N(Math.min(GetPrice("Buy", depth) + 0.0001, depth.Asks[0].Price-0.0001) , 4) //Guaranteed at the market
var sellPrice = _N(Math.max(GetPrice("Sell", depth) - 0.0001, depth.Bids[0].Price+0.0001), 4)
LogStatus('buy_price:'+buyPrice, ' sell price: '+sellPrice)
if ((sellPrice - buyPrice) < DiffPrice) {
buyPrice = 0
}
if(sellPrice != lastSellPrice && sellId){
exchange.CancelOrder(sellId);
sellId = 0
lastSellPrice = 0
}
if(buyPrice != lastBuyPrice && buyId){
exchange.CancelOrder(buyId);
buyId = 0
lastBuyPrice = 0
}
var acc = _C(exchange.GetAccount)
if(account.Stocks+account.FrozenStocks != acc.Stocks+acc.FrozenStocks){
LogProfit((acc.Stocks+acc.FrozenStocks)*depth.Bids[0].Price+acc.Balance+acc.FrozenBalance - 2000)
Log('free '+acc.Stocks, ' lock: '+ acc.FrozenStocks, ' total: ' , (acc.Stocks+acc.FrozenStocks)*depth.Bids[0].Price+acc.Balance+acc.FrozenBalance)
}
account = acc
amountBuy = _N(Math.min(account.Balance / buyPrice - 0.1, Amount), 0)
amountSell = _N(account.Stocks, 0)
if (sellPrice > 0 && amountSell > 40 && sellId == 0) {
sellId = exchange.Sell(_N(sellPrice,4), amountSell)
lastSellPrice = sellPrice
}
if (buyPrice>0 && amountBuy > 40 && buyId == 0) {
buyId = exchange.Buy(_N(buyPrice,4), amountBuy)
lastBuyPrice = buyPrice
}
Sleep(Interval)
}
var account = {Stocks:0, FrozenStocks:0, Balance:0, FrozenBalance:0}
var buyId = 0
var sellId = 0
var lastBuyPrice = 0
var lastSellPrice = 0
var amountSell = 0
var amountBuy = 0
var log_account_time = 0
function main() {
CancelPendingOrders()
while (true) {
OnTick()
}
}
```
From: https://blog.mathquant.c...in-80-lines-of-code.html

Release notes 3/16/2024

2024-03-16T07:51:10Z

Installer (v5.0.150):
Advise extra setup for MT and IBKR connectors.

An Analysis of Common Requirements Design Examples in the Cryptocurrency Market (II)

2024-03-15T06:42:30Z

# FMZ Quant: An Analysis of Common Requirements Design Examples in the Cryptocurrency Market (II)

In response to the comments from readers in the previous article, they requested a program example for monitoring contract account transfers. In this article, we will use Binance exchange as the test object to implement the requirement and learn how to design it together.

Cryptocurrency exchanges handle a large number of transactions every day, including the transfer of assets between different wallets. Monitoring these transfers in real time is crucial for traders and developers. In this article, we will explore a piece of JavaScript code designed to monitor recent asset transfers on a cryptocurrency exchange and discuss its key components.

### Analyze Requirements
I checked the documentation of Binance exchange and found that there is a transfer history interface that can query all transfer information. Since we are only monitoring transfer records that may occur, we do not need to obtain all transfer history. We only need to check recent transfer records within a certain range based on a certain frequency. If new transfer records are found, they will be updated and notified.

Use the interface:

```
// GET /sapi/v1/asset/transfer type, size : 100
```
So how to check the newly added transfer record? After reading Binance's documentation, I found that there is a timestamp in the data returned by this interface. It is very simple to judge by the timestamp. As long as there is a record larger than the maximum timestamp currently recorded, it means that a new transfer action has occurred. Just use this to trigger it.

The ```/sapi/v1/asset/transfer``` interface can request up to 100 pieces of data at a time. The detection will not cause problems for low-frequency transfers, unless the account has more than 100 transfer operations between the end of one detection and the start of the next detection. At this time, some new operation records may be missed, which is sufficient for general demand scenarios (generally, there will be no strategy to transfer funds crazily...).

Of course, there are many details in the actual design. For example, checking the documentation, we found that there are many transfer directions, so we need to monitor each transfer direction. The code is defined ```var dicType = {...}``` to manage all transfer directions.

In order to display the content better, we use a status bar table to output the last 5 transfer information in the strategy interface, so we constructed an object named ```monitor``` to record the data. Of course, you cannot record transfer information unlimitedly, so we only maintain 100 records for each transfer direction. If the number exceeds 100, we will delete premature records.

### Code Example
```
function getRecentTransferHistory(TransType, typeDesc) {
// GET /sapi/v1/asset/transfer type, size : 100

var rows = null
var ret = exchange.IO("api", "GET", "/sapi/v1/asset/transfer", `type=${TransType}&size=100`)
Log("/sapi/v1/asset/transfer" + `type=${TransType}&size=100`)
if (ret && typeof(ret.rows) != "undefined" && Array.isArray(ret.rows)) {
rows = ret.rows
} else if (ret && typeof(ret.total) != "undefined" && ret.total == 0) {
rows = []
} else {
Log(TransType, typeDesc, "inquiry failure", ret)
}

return rows
}

var monitor = {}
function monitorTransfers() {
var dicType = {
"MAIN_UMFUTURE": "Spot wallet --> U-based contract wallet",
"MAIN_CMFUTURE": "Spot wallet --> Currency-based contract wallet",
"UMFUTURE_MAIN": "U-based contract wallet --> Spot wallet",
"UMFUTURE_MARGIN": "U-based contract wallet --> Leveraged full position wallet",
"CMFUTURE_MAIN": "Currency-based contract wallet --> Spot wallet",
"MARGIN_UMFUTURE": "Leveraged full position wallet --> U-based contract wallet",
"MARGIN_CMFUTURE": "Leveraged full position wallet --> Currency-based contract wallet",
"CMFUTURE_MARGIN": "Currency-based contract wallet --> Leveraged full position wallet",
"FUNDING_UMFUTURE": "Funds wallet --> U-based contract wallet",
"UMFUTURE_FUNDING": "U-based contract wallet --> Funds wallet",
"FUNDING_CMFUTURE": "Funds wallet --> Currency-based contract wallet",
"CMFUTURE_FUNDING": "Currency-based contract wallet --> Funds wallet",
"UMFUTURE_OPTION": "U-based contract wallet --> Options wallet",
"OPTION_UMFUTURE": "Options wallet --> U-based contract wallet",
// integrated account
"MAIN_PORTFOLIO_MARGIN": "Spot wallet --> Unified accounts wallet",
"PORTFOLIO_MARGIN_MAIN": "Unified accounts wallet --> Spot wallet"
}

Log("start testing")
_.each(dicType, function(v, k) {
var rows = getRecentTransferHistory(k, v)
var maxTS = 0
_.each(rows, function(row) {
if (typeof(monitor[k]) == "undefined") {
monitor[k] = {"transType": k, "typeDesc": v, "recentRecords": [], "lastTS": 0}
}

if (row["timestamp"] > monitor[k]["lastTS"]) {
monitor[k]["recentRecords"].push(row)

if (monitor[k]["lastTS"] != 0) {
Log("New transfer records detected", k, v, row, "#FF0000")
}
}
maxTS = Math.max(maxTS, row["timestamp"])
})
if (rows && rows.length == 0) {
return
}
monitor[k]["lastTS"] = maxTS

var sortedArrayAscending = monitor[k]["recentRecords"].slice().sort((a, b) => a.timestamp - b.timestamp)
monitor[k]["recentRecords"] = sortedArrayAscending

if (monitor[k]["recentRecords"].length > 100) {
monitor[k]["recentRecords"].shift()
}
Sleep(1000)
})
Log("commencement and termination")
}

function main() {
LogReset()
while (true) {
monitorTransfers()

var tbls = []
_.each(monitor, function(v, k) {
var tbl = {
"type": "table",
"title": v["typeDesc"],
"cols": ["asset", "amount", "status", "tranId", "time"],
"rows": []
}

var arr = v["recentRecords"].slice().sort((a, b) => b.timestamp - a.timestamp)
for (var i = 0; i < arr.length; i++) {
if (i < 5) {
tbl["rows"].push([arr[i]["asset"], arr[i]["amount"], arr[i]["status"], arr[i]["tranId"], _D(arr[i]["timestamp"])])
}
}
tbls.push(tbl)
})

LogStatus(_D(), "\n", "`" + JSON.stringify(tbls) + "`")
Sleep(1000 * 30)
}
}
```
### Code Overview:
The provided JavaScript code includes several functions that build a system together for monitoring recent asset transfers. Let's analysis the main components:

- getRecentTransferHistory function:

Purpose: Obtain the recent asset transfer history from the exchange API according to the specified parameters.
Parameters: TransType (transfer type), typeDesc (type description).
API endpoint: /sapi/v1/asset/transfer.

- monitorTransfers function:

Purpose: Iterate over predefined transfer types, retrieve recent transfer history, and record any new transfers.
Use a dictionary (dicType) to map transfer types to human-readable descriptions.
Update the monitor object to track the latest transfers of each type.

- main function:

Purpose: Run an infinite loop that monitors transfers continuously and displays the latest data.
Use the monitorTransfers function regularly.
Generate a table for each transfer type, including columns such as asset, amount, status, transaction ID, and timestamp.

### Key Features:
- Dynamic transfer type mapping:

The code uses a dictionary (dicType) to map transfer types to descriptive names, providing a clear explanation of the nature of each transfer.

- Real-time monitoring:

The system checks for new transfers continuously, updates the monitor object and records any detected changes.

- Data presentation:

Use tables to present each type of transfer data, including relevant details such as assets, amounts, status, transaction IDs, and timestamps.

- Recent transfer history management:

Maintain a scrolling list of recent transfer records for each type, ensuring a concise and timely display.

### Bot Test
A transfer was made manually and the program detected the transfer operation.
https://stocksharp.com/file/149241
https://stocksharp.com/file/149242
### END:
The provided JavaScript code provides a powerful solution for monitoring recent asset transfers on cryptocurrency exchanges. Its dynamic and real-time nature makes it a valuable tool for traders and developers seeking to understand asset movements between different wallets. This code can be modified and customized to specific needs, providing a solid foundation for those looking to enhance their cryptocurrency trading strategies or develop additional monitoring capabilities.

This article throws some light on the topic and provides a design idea. May your cryptocurrency career be both informative and successful!

From: https://blog.mathquant.c...ocurrency-market-ii.html

An Analysis of Common Requirements Design Examples in the Cryptocurrency Market (I)

2024-03-15T01:17:45Z

In the cryptocurrency asset trading space, obtaining and analyzing market data, querying rates, and monitoring account asset movements are all critical operations. Below are code examples of implementations for some common requirements.

## 1. How do I write the code about getting the currency with the highest increase in 4 hours on Binance Spot?
When writing a quantitative trading strategy program on FMZ platform, the first thing you need to do when you encounter a requirement is to analyze it. So based on the requirements, we analyzed the following contents:

- Which programming language to use?
The plan is to use Javascript to implement it.
- Requires spot real-time quotes in all currencies
The first thing we did when we saw the requirement was to look up Binance API document to find out if there was any aggregated quotes (it's best to have aggregated quotes, it's a lot of work to look up one by one).
We found the aggregated quotes interface: ```GET https://api.binance.com/api/v3/ticker/price```.
On FMZ platform, use the ```HttpQuery``` function to access the exchange ticker interface (public interface that does not require a signature).
- Need to count data for a rolling window period of 4 hours
Conceptualize how to design the structure of the statistical program.
- Calculate price fluctuations and sort them
Thinking about the price fluctuations algorithm, is it: ```price fluctuations (%) = (current price - initial price) / initial price * 100``` in "%".

After figuring out the problem, as well as defining the program. We then got down to the business of designing the program.

### Code Design
```
var dictSymbolsPrice = {}

function main() {
while (true) {
// GET https://api.binance.com/api/v3/ticker/price
try {
var arr = JSON.parse(HttpQuery("https://api.binance.com/api/v3/ticker/price"))
if (!Array.isArray(arr)) {
Sleep(5000)
continue
}

var ts = new Date().getTime()
for (var i = 0; i < arr.length; i++) {
var symbolPriceInfo = arr[i]
var symbol = symbolPriceInfo.symbol
var price = symbolPriceInfo.price

if (typeof(dictSymbolsPrice[symbol]) == "undefined") {
dictSymbolsPrice[symbol] = {name: symbol, data: []}
}
dictSymbolsPrice[symbol].data.push({ts: ts, price: price})
}
} catch(e) {
Log("e.name:", e.name, "e.stack:", e.stack, "e.message:", e.message)
}

// Calculate price fluctuations
var tbl = {
type : "table",
title : "Price fluctuations",
cols : ["trading pair", "current price", "price 4 hours ago", "price fluctuations", "data length", "earliest data time", "latest data time"],
rows : []
}
for (var symbol in dictSymbolsPrice) {
var data = dictSymbolsPrice[symbol].data
if (data[data.length - 1].ts - data[0].ts > 1000 * 60 * 60 * 4) {
dictSymbolsPrice[symbol].data.shift()
}

data = dictSymbolsPrice[symbol].data
dictSymbolsPrice[symbol].percentageChange = (data[data.length - 1].price - data[0].price) / data[0].price * 100
}

var entries = Object.entries(dictSymbolsPrice)
entries.sort((a, b) => b[1].percentageChange - a[1].percentageChange)

for (var i = 0; i < entries.length; i++) {
if (i > 9) {
break
}
var name = entries[i][1].name
var data = entries[i][1].data
var percentageChange = entries[i][1].percentageChange
var currPrice = data[data.length - 1].price
var currTs = _D(data[data.length - 1].ts)
var prePrice = data[0].price
var preTs = _D(data[0].ts)
var dataLen = data.length

tbl.rows.push([name, currPrice, prePrice, percentageChange + "%", dataLen, preTs, currTs])
}

LogStatus(_D(), "\n", "`" + JSON.stringify(tbl) + "`")
Sleep(5000)
}
}
```
### Code Analysis
- 1. Data structure
```var dictSymbolsPrice = {}```: An empty object to store price information for each trading pair. The key is the symbol of the trading pair, and the value is an object containing the name of the trading pair, an array of price data, and information about the price fluctuations.
- 2. Main function main()
2.1. Infinite loop
```
while (true) {
// ...
}
```
The program continuously monitors the Binance API trading pair prices through an infinite loop.

2.2. Get price information
```
var arr = JSON.parse(HttpQuery("https://api.binance.com/api/v3/ticker/price"))
```
Get the current price information of the trading pair via Binance API. If the return is not an array, wait for 5 seconds and retry.

2.3. Update price data
```
for (var i = 0; i < arr.length; i++) {
// ...
}
```
Iterate through the array of obtained price information and update the data in dictSymbolsPrice. For each trading pair, add the current timestamp and price to the corresponding data array.

2.4. Exception processing
```
} catch(e) {
Log("e.name:", e.name, "e.stack:", e.stack, "e.message:", e.message)
}
```
Catch exceptions and log the exception information to ensure that the program can continue to execute.

2.5. Calculate the price fluctuations
```
for (var symbol in dictSymbolsPrice) {
// ...
}
```
Iterate through dictSymbolsPrice, calculate the price fluctuations of each trading pair, and remove the earliest data if it is longer than 4 hours.

2.6. Sort and generate tables
```
var entries = Object.entries(dictSymbolsPrice)
entries.sort((a, b) => b[1].percentageChange - a[1].percentageChange)

for (var i = 0; i < entries.length; i++) {
// ...
}
```
Sort the trading pairs in descending order of their price fluctuations and generate a table containing information about the trading pairs.

2.7. Log output and delay
```
LogStatus(_D(), "\n", "`" + JSON.stringify(tbl) + "`")
Sleep(5000)
```
Output the table and the current time in the form of a log and wait for 5 seconds to continue the next round of the loop.

The program obtains the real-time price information of the trading pair through Binance API, then calculates the price fluctuations, and outputs it to the log in the form of a table. The program is executed in a continuous loop to realize the function of real-time monitoring of the prices of trading pairs. Note that the program includes exception processing to ensure that the execution is not interrupted by exceptions when obtaining price information.

### Live Trading Running Test
https://stocksharp.com/file/149238
Since data can only be collected bit by bit at the beginning, it is not possible to calculate the price fluctuations on a rolling basis without collecting enough data for a 4-hour window. Therefore, the initial price is used as the base for calculation, and after collecting enough data for 4 hours, the oldest data will be eliminated in order to maintain the 4-hour window for calculating the price fluctuations.

## 2. Check the full variety of funding rates for Binance U-denominated contracts
Checking the funding rate is similar to the above code, first of all, we need to check the Binance API documentation to find the funding rate related interface. Binance has several interfaces that allow us to query the rate of funds, here we take the interface of the U-denominated contract as an example:

```
GET https://fapi.binance.com/fapi/v1/premiumIndex
```
### Code Implementation
Since there are so many contracts, we're exporting the top 10 largest funding rates here.

```
function main() {
while (true) {
// GET https://fapi.binance.com/fapi/v1/premiumIndex
try {
var arr = JSON.parse(HttpQuery("https://fapi.binance.com/fapi/v1/premiumIndex"))
if (!Array.isArray(arr)) {
Sleep(5000)
continue
}

arr.sort((a, b) => parseFloat(b.lastFundingRate) - parseFloat(a.lastFundingRate))
var tbl = {
type: "table",
title: "Top 10 funding rates for U-denominated contracts",
cols: ["contracts", "funding rate", "marked price", "index price", "current rate time", "next rate time"],
rows: []
}
for (var i = 0; i < 9; i++) {
var obj = arr[i]
tbl.rows.push([obj.symbol, obj.lastFundingRate, obj.markPrice, obj.indexPrice, _D(obj.time), _D(obj.nextFundingTime)])
}
LogStatus(_D(), "\n", "`" + JSON.stringify(tbl) + "`")
} catch(e) {
Log("e.name:", e.name, "e.stack:", e.stack, "e.message:", e.message)
}
Sleep(1000 * 10)
}
}
```
The returned data structure is as follows, and check the Binance documentation, it shows that lastFundingRate is the funding rate we want.

```
{
"symbol":"STMXUSDT",
"markPrice":"0.00883606",
"indexPrice":"0.00883074",
"estimatedSettlePrice":"0.00876933",
"lastFundingRate":"0.00026573",
"interestRate":"0.00005000",
"nextFundingTime":1702828800000,
"time":1702816229000
}
```
Live trading running test:
https://stocksharp.com/file/149239
### Getting OKX exchange contract funding rates of Python version
A user has asked for a Python version of the example, and it's for the OKX exchange. Here is an example:

The data returned by the interface ```https://www.okx.com/priapi/v5/public/funding-rate-all?currencyType=1```:
```
{
"code":"0",
"data":[
{
"fundingTime":1702828800000,
"fundingList":[
{
"instId":"BTC-USDT-SWAP",
"nextFundingRate":"0.0001102188733642",
"minFundingRate":"-0.00375",
"fundingRate":"0.0000821861465884",
"maxFundingRate":"0.00375"
} ...
```
Specific code:

```
import requests
import json
from time import sleep
from datetime import datetime

def main():
while True:
# https://www.okx.com/pria...rate-all?currencyType=1
try:
response = requests.get("https://www.okx.com/priapi/v5/public/funding-rate-all?currencyType=1")
arr = response.json()["data"][0]["fundingList"]
Log(arr)
if not isinstance(arr, list):
sleep(5)
continue

arr.sort(key=lambda x: float(x["fundingRate"]), reverse=True)

tbl = {
"type": "table",
"title": "Top 10 funding rates for U-denominated contracts",
"cols": ["contracts", "next rate", "minimum", "current", "maximum"],
"rows": []
}

for i in range(min(9, len(arr))):
obj = arr[i]
row = [
obj["instId"],
obj["nextFundingRate"],
obj["minFundingRate"],
obj["fundingRate"],
obj["maxFundingRate"]
]
tbl["rows"].append(row)

LogStatus(_D(), "\n", '`' + json.dumps(tbl) + '`')

except Exception as e:
Log(f"Error: {str(e)}")

sleep(10)
```
Live trading running test:
https://stocksharp.com/file/149240
### END
These examples provide basic design ideas and calling methods, the actual project may need to make appropriate changes and extensions based on the specific needs. Hopefully, these codes can help you better meet the various needs in cryptocurrency digital asset trading.
From: https://blog.mathquant.c...tocurrency-market-i.html

The Crucial Role of Efficient Quantitative Data Exploration Tools in Boosting Trading Success

2024-03-14T09:21:47Z

In today's fiercely competitive financial market, quantitative trading, as a trading strategy based on data analysis and algorithmic models, is becoming an increasingly favored choice for investors and traders. In the field of quantitative trading, the value of data is becoming increasingly prominent. Therefore, an efficient and reliable quantitative data exploration tool has become an indispensable key to achieving successful transactions.

In this era where data-driven decision-making is increasingly valued, the FMZ Quant data exploration module has emerged. As one of the essential tools in the field of quantitative trading, it is not only an ordinary data analysis software, but also a revolutionary innovation that provides investors with unique data analysis and mining functions, helping them seize opportunities and reduce risks in complex and ever-changing financial markets.

FMZ Quant, as a professional quantitative trading platform, is supported by numerous quantitative trading tools. At present, the "Data Exploration" module of the FMZ Quant Trading Platform has integrated the services of the datadata platform, giving users more advantages in multidimensional data analysis, mining visual data, exploring trading strategies, and other aspects. FMZ's self-developed datadata platform is a quantitative financial data platform. Using SQL queries to analyze massive amounts of data and configuring them through visual interfaces, generating various charts suitable for data analysis and sharing them with the team, allowing us to easily grasp market trends and seize investment opportunities!

FMZ Quant Data Exploration Module
First of all, let's familiarize with the FMZ Quant Data Exploration module, which is used just like on datadata. For each FMZ platform user, we don't need to register for the datadata platform again, and we can use all the features of the datadata platform directly.
https://stocksharp.com/file/149179
Data areas
The list on the left side shows the data content that has been supported on-line, currently supporting K-line data (OHLC) and Tick data of each exchange (platform). More types and dimensions of data will be supported in the future.
These data are updated continuously in real time, allowing us to always grasp the market dynamics.
For example, if we select OHLC and then select market->bitfinex_m1, we can see the field names in this table object after clicking Expand.
https://stocksharp.com/file/149180
Click on the table chart to preview some of the data.

The platform also supports uploading your own data by clicking the "Upload Data" button at the bottom of the list.

Uploading CSV files from your device to the server.
The file size should not exceed 10 MB, with a maximum of 10,000 rows and 128 columns.

SQL statement edit area
https://stocksharp.com/file/149181
Here is the edit box for writing a specific query statement, we will show two interesting examples later, let's understand the other features first.
https://stocksharp.com/file/149182
There are two control buttons here, the first one can be used to format the SQL statement easily. The second button is used to insert variables used in the SQL statement, similar to adding a parameter to the SQL query that can be modified in real time (without having to hard-code some of the query conditions into the SQL statement). For example:
https://stocksharp.com/file/149183
Input '1inch_usd' into the parameter test and click the "Execute" button on the right side, then you can query all the data of the variety 1inch_usd. The queried data can also be exported and downloaded locally:
https://stocksharp.com/file/149184
It supports JSON, CSV format.

If we want to save the SQL query, we can click the "Save" button in the upper right corner to record the SQL query in the resource list of the current FMZ account's "Data Exploration" (the resource list button is on the left side of the save button) for future use.

At present, the interface we see is simple and the functions are simple, but in practical use, we will experience the powerful use of this tool. Next, let's take a look at two more complex examples.

Volatility ranking
```
SELECT
UPPER(REPLACE(symbol, '_usdt.swap', '')) as symbol,
((MAX(high) - MIN(low)) / AVG((high + low) / 2)) AS volatility_percentage
FROM
market.futures_binance_d1
WHERE
timestamp >= CURRENT_DATE - INTERVAL '{{days}} day' and symbol like '%.swap'
GROUP BY
symbol
ORDER BY
volatility_percentage {{rank}}
LIMIT
{{limit}};
```
This SQL code is used to get the volatility percentage of the trading pair that meets the criteria from the table "market.futures_binance_d1" and sort and limit the quantity output by volatility percentage.

The explanation of this SQL is given below:

```
1. Two expressions were used for calculation, one was to replace the '_usdt.swap' in the 'symbol' column with an empty string and convert the result to uppercase, and the other was to calculate (MAX(high) - MIN(low)) / AVG((high+low) / 2).
The first expression uses the REPLACE function to replace strings that meet the criteria, and then uses the UPPER function to convert the result to uppercase.
The second expression calculates the difference between the highest and lowest prices divided by the average of the highest and lowest prices to calculate the percentage of volatility.

2. FROM clause:
The specified data table to be queried is "market.futures.binance_d1".

3. WHERE clause:
Two filter conditions are used: timestamp >= CURRENT_DATE - INTERVAL '{{days}} day' and symbol like '%.swap'.
The first condition filters out data within the last {{days}} days.
The second condition filters out trading pairs where the "symbol" column ends in '.swap'.

4. GROUP BY clause:
Group by the "symbol" column.

5. ORDER BY clause:
Sort by volatility percentage, either ascending (ASC) or descending (DESC), depending on the {{rank}} parameter.

6. LIMIT clause:
Limit the number of output results, which can be set according to the {{limit}} parameter.
```
https://stocksharp.com/file/149185
When we enter the parameters:
days: 10 , rank: DESC , limit: 10, click the "Execute" button to execute the SQL statement and query the result.

In addition to displaying data in the form of tables, it can also be displayed in a variety of visualization ways. After setting up some relevant settings for visualization, the data will be displayed in a richer and more vivid way.
https://stocksharp.com/file/149186
The created query can also generate URLs for easy sharing, and we can also modify the parameters to update the query (try modifying the parameters to update the query here in the article). Follwing is a chart of the real-time data generated:

volatility ranking
https://stocksharp.com/file/149187
In-depth Replay
Next we're going to study an example of studying a market micro-scenario, which is a wonderful tool for studying the details of high-frequency trading.

```
select * from market.binance where symbol = lower('{{symbol}}') order by timestamp desc limit 2000
```
Use the above SQL statement to query the tick level tick data for a particular species.
https://stocksharp.com/file/149188
The SQL query for this example is very simple, just querying the Tick data for a certain variety (specified by the parameter symbol) on the Binance exchange.

The point is to show the data in the form of a live trading replay, on a time series, with multiple charts:
https://stocksharp.com/file/149189
Is it convenient to study the details in the market?

Next, let's take a look at how to share our research. We can click on the share icon in the upper right corner.
https://stocksharp.com/file/149190
These shared codes, links, can be embedded in FMZ platform community posts, articles. They can be embedded in web pages and can be republished in other communities, forums, etc. It can also be shared directly to anyone.
https://stocksharp.com/file/149191
What are you waiting for with this powerful quantitative trading tool? Try to mine the data and analyze it.
From: https://blog.mathquant.c...-exploration-module.html

Release notes 3/12/2024

2024-03-12T13:00:32Z

Edu (v5.0.34):
Fix run backtests (no security lookup turn on by default).

Shell (v5.0.35):
Fix run backtests (no security lookup turn on by default).

Release notes 3/4/2024

2024-03-04T17:03:15Z

Installer (v5.0.149):
HtmlLabelEx -> ThemeHtmlLabel
Light/dark mode switch.
HtmlLabelEx

Release notes 2/23/2024

2024-02-23T18:54:03Z

Designer (v5.0.164):
Studio.Core removed dependency from Fix connector.

Release notes 2/22/2024

2024-02-22T21:31:41Z

Installer (v5.0.148):
Shows MT select folder dialog every time.
ISLR-36 Removed locked files checking. Auto-kill runner app without user request.
HyperlinkEx -> HyperlinkEdit usage.

Release notes 2/21/2024

2024-02-21T19:11:05Z

Installer (v5.0.147):
Return to main window after publish.
Product. UrlRelative, UrlAbsolute properties.
InstallerRepoProvider moved to Studio.Nuget.
WebApiHelper. IsAvailable, GetCurrency extensions.
Allow install schemas as standalone packages.

Release notes 2/21/2024

2024-02-21T19:05:02Z

API (v5.0.140):
Backtesting supports stop orders. Strategies can use local and server stop-orders.
IChart. Areas property type changed INotifyList -> IEnumerable

Release notes 2/21/2024

2024-02-21T19:04:59Z

MatLab (v5.0.154):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.
Backtesting supports stop orders. Strategies can use local and server stop-orders.
MyTrade. GetPosition extension returns non nullable decimal.

InteractiveBrokers connector (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

ASTSBridge (v5.0.161):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Plaza (v5.0.165):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Transaq (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

LMAX (v5.0.158):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

FIX (v5.0.173):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

FAST connector (v5.0.7):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

IQFeed (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

RSS (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

BarChart (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Rithmic (v5.0.161):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

TWIME (v5.0.160):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

SpbEX (v5.0.153):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

QuantFEED (v5.0.161):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

AlphaVantage (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

AlorHistory (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

DukasCopy (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Yahoo Finance (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Finam connector (v5.0.160):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

MFD (v5.0.159):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bibox (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Binance (v5.0.161):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bitalong (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bitbank (v5.0.157):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bitexbook (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bitfinex (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bithumb (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

BitMax (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bitmex (v5.0.158):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

BitStamp (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Bittrex (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

BitZ (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Btce (v5.0.155):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

BW (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Cex (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Coinbase (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

CoinBene (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

CoinCap (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Coincheck (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

CoinEx (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

CoinExchange (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

CoinHub (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Coinigy (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Cryptopia (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Deribit (v5.0.160):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Digifinex (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

DigitexFutures (v5.0.157):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Exmo (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

FatBtc (v5.0.155):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Gdax (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Gopax (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

HitBtc (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Hotbit (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

HTX connector (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Idax (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Kraken (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Kucoin (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Latoken (v5.0.155):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

LBank (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Liqui (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

LiveCoin (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Okcoin (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

OKX (v5.0.161):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Poloniex (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

PrizmBit (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Quoinex (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

TradeOgre (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Upbit (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Yobit (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Zaif (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

ZB (v5.0.156):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Terminal (v5.0.162):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.
Backtesting supports stop orders. Strategies can use local and server stop-orders.
MyTrade. GetPosition extension returns non nullable decimal.
IChart. Areas property type changed INotifyList -> IEnumerable
ProtectPositionDiagramElement. Can receive trades from multiple sources. Tracks own trades.
IChart refactoring.

Designer (v5.0.163):
Removed default min and max prices for backtesting.
DESIGNER-204 Fix publishing after prev canceled attempt.
Fix biding ribbon publish, export and delete buttons.
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.
Backtesting supports stop orders. Strategies can use local and server stop-orders.
MyTrade. GetPosition extension returns non nullable decimal.
IChart. Areas property type changed INotifyList -> IEnumerable
ProtectPositionDiagramElement. Can receive trades from multiple sources. Tracks own trades.
IChart refactoring.

Hydra (v5.0.166):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.
Backtesting supports stop orders. Strategies can use local and server stop-orders.
MyTrade. GetPosition extension returns non nullable decimal.
IChart. Areas property type changed INotifyList -> IEnumerable
ProtectPositionDiagramElement. Can receive trades from multiple sources. Tracks own trades.
IChart refactoring.

UDP Dumper (v5.0.133):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.
Backtesting supports stop orders. Strategies can use local and server stop-orders.
MyTrade. GetPosition extension returns non nullable decimal.
IChart. Areas property type changed INotifyList -> IEnumerable
ProtectPositionDiagramElement. Can receive trades from multiple sources. Tracks own trades.

Oanda (v5.0.158):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

UDPDumper.Console (v5.0.120):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

QUIK (v5.0.155):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

MT 4 (v5.0.151):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

MT 5 (v5.0.150):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

MOEX ISS (v5.0.32):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Runner (v5.0.21):
IChart. Areas property type changed INotifyList -> IEnumerable
IChart refactoring.
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.
Backtesting supports stop orders. Strategies can use local and server stop-orders.
MyTrade. GetPosition extension returns non nullable decimal.
ProtectPositionDiagramElement. Can receive trades from multiple sources. Tracks own trades.

Alor (v5.0.30):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Tinkoff (v5.0.30):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

PolygonIO (v5.0.21):
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Alpaca Markets (v5.0.1):
auto change StockFeed on iex for demo mode.
Unit. IsSet extension.
SecurityId. GetHashCode performance boost.

Release notes 2/14/2024

2024-02-14T21:23:02Z

MatLab (v5.0.153):
IIndicatorValue. GetValue accepts field.
AsyncMessageProcessor. Fix handling error request.

InteractiveBrokers connector (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

ASTSBridge (v5.0.160):
AsyncMessageProcessor. Fix handling error request.

Plaza (v5.0.164):
AsyncMessageProcessor. Fix handling error request.

Transaq (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

LMAX (v5.0.157):
AsyncMessageProcessor. Fix handling error request.

FIX (v5.0.172):
AsyncMessageProcessor. Fix handling error request.

FAST connector (v5.0.6):
AsyncMessageProcessor. Fix handling error request.

IQFeed (v5.0.155):
WithEnforcedCancellation usage.
AsyncMessageProcessor. Fix handling error request.

RSS (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

BarChart (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

Rithmic (v5.0.160):
AsyncMessageProcessor. Fix handling error request.

TWIME (v5.0.159):
AsyncMessageProcessor. Fix handling error request.

SpbEX (v5.0.152):
AsyncMessageProcessor. Fix handling error request.

QuantFEED (v5.0.160):
AsyncMessageProcessor. Fix handling error request.

AlphaVantage (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

AlorHistory (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

DukasCopy (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

Yahoo Finance (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

Finam connector (v5.0.159):
AsyncMessageProcessor. Fix handling error request.
Put runtime info into bug reports.

MFD (v5.0.158):
AsyncMessageProcessor. Fix handling error request.

Bibox (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Binance (v5.0.160):
AsyncMessageProcessor. Fix handling error request.

Bitalong (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Bitbank (v5.0.156):
AsyncMessageProcessor. Fix handling error request.

Bitexbook (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Bitfinex (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Bithumb (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

BitMax (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Bitmex (v5.0.157):
AsyncMessageProcessor. Fix handling error request.

BitStamp (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Bittrex (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

BitZ (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Btce (v5.0.154):
AsyncMessageProcessor. Fix handling error request.

BW (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Cex (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Coinbase (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

CoinBene (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

CoinCap (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Coincheck (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

CoinEx (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

CoinExchange (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

CoinHub (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Coinigy (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Cryptopia (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Deribit (v5.0.159):
AsyncMessageProcessor. Fix handling error request.

Digifinex (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

DigitexFutures (v5.0.156):
AsyncMessageProcessor. Fix handling error request.

Exmo (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

FatBtc (v5.0.154):
AsyncMessageProcessor. Fix handling error request.

Gdax (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Gopax (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

HitBtc (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Hotbit (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

HTX connector (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Idax (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Kraken (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Kucoin (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Latoken (v5.0.154):
AsyncMessageProcessor. Fix handling error request.

LBank (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Liqui (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

LiveCoin (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Okcoin (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

OKX (v5.0.160):
AsyncMessageProcessor. Fix handling error request.

Poloniex (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

PrizmBit (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Quoinex (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

TradeOgre (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Upbit (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Yobit (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Zaif (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

ZB (v5.0.155):
AsyncMessageProcessor. Fix handling error request.

Terminal (v5.0.160):
AsyncMessageProcessor. Fix handling error request.
IIndicatorValue. GetValue accepts field.
Put runtime info into bug reports.
IndicatorDiagramElement. Display Unit, date, time, enum properties.
Handle invalid image uri.

Designer (v5.0.161):
AsyncMessageProcessor. Fix handling error request.
IIndicatorValue. GetValue accepts field.
Put runtime info into bug reports.
IndicatorDiagramElement. Display Unit, date, time, enum properties.
Handle invalid image uri.

Hydra (v5.0.164):
AsyncMessageProcessor. Fix handling error request.
IIndicatorValue. GetValue accepts field.
Put runtime info into bug reports.
IndicatorDiagramElement. Display Unit, date, time, enum properties.
Handle invalid image uri.

UDP Dumper (v5.0.131):
IndicatorDiagramElement. Display Unit, date, time, enum properties.
IIndicatorValue. GetValue accepts field.
AsyncMessageProcessor. Fix handling error request.
Handle invalid image uri.

Oanda (v5.0.157):
AsyncMessageProcessor. Fix handling error request.

UDPDumper.Console (v5.0.119):
AsyncMessageProcessor. Fix handling error request.

QUIK (v5.0.154):
AsyncMessageProcessor. Fix handling error request.

MT 4 (v5.0.150):
AsyncMessageProcessor. Fix handling error request.

MT 5 (v5.0.149):
AsyncMessageProcessor. Fix handling error request.

MOEX ISS (v5.0.31):
AsyncMessageProcessor. Fix handling error request.

Runner (v5.0.19):
AsyncMessageProcessor. Fix handling error request.
IIndicatorValue. GetValue accepts field.
Put runtime info into bug reports.
IndicatorDiagramElement. Display Unit, date, time, enum properties.

Alor (v5.0.29):
AsyncMessageProcessor. Fix handling error request.

Tinkoff (v5.0.29):
AsyncMessageProcessor. Fix handling error request.

PolygonIO (v5.0.20):
WithEnforcedCancellation usage.
AsyncMessageProcessor. Fix handling error request.

Alpaca Markets (v5.0.0):
AsyncMessageProcessor. Fix handling error request.

Release notes 2/12/2024

2024-02-12T18:48:15Z

Terminal (v5.0.159):
MarketDataPanel. Fix saving changed while tf and dates range changed.
DESIGNER-203 Fix time out download from QUIK and memory issues.

Designer (v5.0.160):
MarketDataPanel. Fix saving changed while tf and dates range changed.
DESIGNER-203 Fix time out download from QUIK and memory issues.

Hydra (v5.0.163):
MarketDataPanel. Fix saving changed while tf and dates range changed.
DESIGNER-203 Fix time out download from QUIK and memory issues.

Release notes 2/12/2024

2024-02-12T17:03:38Z

MatLab (v5.0.152):
SS-302. AsyncMessageProcessor uses invariant culture.
BasketMarketDataStorage multi treading issue fix.
IOrderBookSource
Strategy. Security and Portfolio are optional.
Fix news subscribe.

InteractiveBrokers connector (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

ASTSBridge (v5.0.159):
SS-302. AsyncMessageProcessor uses invariant culture.

Plaza (v5.0.163):
SS-302. AsyncMessageProcessor uses invariant culture.

Transaq (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

LMAX (v5.0.156):
SS-302. AsyncMessageProcessor uses invariant culture.

FIX (v5.0.171):
SS-302. AsyncMessageProcessor uses invariant culture.

FAST connector (v5.0.5):
SS-302. AsyncMessageProcessor uses invariant culture.

IQFeed (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

RSS (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

BarChart (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

Rithmic (v5.0.159):
SS-302. AsyncMessageProcessor uses invariant culture.

TWIME (v5.0.158):
SS-302. AsyncMessageProcessor uses invariant culture.

SpbEX (v5.0.151):
SS-302. AsyncMessageProcessor uses invariant culture.

QuantFEED (v5.0.159):
SS-302. AsyncMessageProcessor uses invariant culture.

AlphaVantage (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

AlorHistory (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

DukasCopy (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

Yahoo Finance (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

Finam connector (v5.0.158):
SS-302. AsyncMessageProcessor uses invariant culture.
WebApiHelper. IsAvailable, GetCurrency extensions.

MFD (v5.0.157):
SS-302. AsyncMessageProcessor uses invariant culture.

Bibox (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Binance (v5.0.159):
SS-302. AsyncMessageProcessor uses invariant culture.

Bitalong (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Bitbank (v5.0.155):
SS-302. AsyncMessageProcessor uses invariant culture.

Bitexbook (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Bitfinex (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Bithumb (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

BitMax (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Bitmex (v5.0.156):
SS-302. AsyncMessageProcessor uses invariant culture.

BitStamp (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Bittrex (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

BitZ (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Btce (v5.0.153):
SS-302. AsyncMessageProcessor uses invariant culture.

BW (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Cex (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Coinbase (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

CoinBene (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

CoinCap (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Coincheck (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

CoinEx (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

CoinExchange (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

CoinHub (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Coinigy (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Cryptopia (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Deribit (v5.0.158):
SS-302. AsyncMessageProcessor uses invariant culture.

Digifinex (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

DigitexFutures (v5.0.155):
SS-302. AsyncMessageProcessor uses invariant culture.

Exmo (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

FatBtc (v5.0.153):
SS-302. AsyncMessageProcessor uses invariant culture.

Gdax (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Gopax (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

HitBtc (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Hotbit (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

HTX connector (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Idax (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Kraken (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Kucoin (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Latoken (v5.0.153):
SS-302. AsyncMessageProcessor uses invariant culture.

LBank (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Liqui (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

LiveCoin (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Okcoin (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

OKX (v5.0.159):
SS-302. AsyncMessageProcessor uses invariant culture.

Poloniex (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

PrizmBit (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Quoinex (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

TradeOgre (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Upbit (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Yobit (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Zaif (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

ZB (v5.0.154):
SS-302. AsyncMessageProcessor uses invariant culture.

Terminal (v5.0.158):
SS-302. AsyncMessageProcessor uses invariant culture.
logo updates.
Design time fixes.
SS-292 CandleSettingsEditor shows error message as red border.
TimeSpanEditor. MinValue, MaxValue properties added.
BasketMarketDataStorage multi treading issue fix.
IOrderBookSource
Strategy. Security and Portfolio are optional.
Fix news subscribe.
DESIGNER-199 MarketDepthPanelDiagramElement reverted back source selection
LoggedInCommand accepts Client arg.
WebApiHelper. IsAvailable, GetCurrency extensions.

Designer (v5.0.159):
Installing strategies from Gallery.
DESIGNER-199 MarketDepthPanelDiagramElement reverted back source selection
Strategy. Security and Portfolio are optional.
DESIGNER-200 Fix clear chart in live mode.
SS-302. AsyncMessageProcessor uses invariant culture.
logo updates.
Design time fixes.
SS-292 CandleSettingsEditor shows error message as red border.
TimeSpanEditor. MinValue, MaxValue properties added.
BasketMarketDataStorage multi treading issue fix.
IOrderBookSource
Fix news subscribe.
DESIGNER-201 Fix show menu items in designer.
LoggedInCommand accepts Client arg.
WebApiHelper. IsAvailable, GetCurrency extensions.
InstallerRepoProvider moved to Studio.Nuget.

Hydra (v5.0.162):
SS-302. AsyncMessageProcessor uses invariant culture.
logo updates.
Design time fixes.
SS-292 CandleSettingsEditor shows error message as red border.
TimeSpanEditor. MinValue, MaxValue properties added.
BasketMarketDataStorage multi treading issue fix.
IOrderBookSource
Strategy. Security and Portfolio are optional.
Fix news subscribe.
DESIGNER-199 MarketDepthPanelDiagramElement reverted back source selection
LoggedInCommand accepts Client arg.
WebApiHelper. IsAvailable, GetCurrency extensions.

UDP Dumper (v5.0.130):
SS-302. AsyncMessageProcessor uses invariant culture.
logo updates.
Design time fixes.
SS-292 CandleSettingsEditor shows error message as red border.
TimeSpanEditor. MinValue, MaxValue properties added.
BasketMarketDataStorage multi treading issue fix.
IOrderBookSource
Strategy. Security and Portfolio are optional.
Fix news subscribe.
DESIGNER-199 MarketDepthPanelDiagramElement reverted back source selection

Oanda (v5.0.156):
SS-302. AsyncMessageProcessor uses invariant culture.

UDPDumper.Console (v5.0.118):
SS-302. AsyncMessageProcessor uses invariant culture.

QUIK (v5.0.153):
Removed QUIK7 legacy code.
SS-302. AsyncMessageProcessor uses invariant culture.

MT 4 (v5.0.149):
SS-302. AsyncMessageProcessor uses invariant culture.

MT 5 (v5.0.148):
SS-302. AsyncMessageProcessor uses invariant culture.

MOEX ISS (v5.0.30):
SS-302. AsyncMessageProcessor uses invariant culture.

Runner (v5.0.18):
Strategy. Security and Portfolio are optional.
SS-302. AsyncMessageProcessor uses invariant culture.
BasketMarketDataStorage multi treading issue fix.
IOrderBookSource
Fix news subscribe.
LoggedInCommand accepts Client arg.
WebApiHelper. IsAvailable, GetCurrency extensions.
DESIGNER-199 MarketDepthPanelDiagramElement reverted back source selection

Alor (v5.0.28):
SS-302. AsyncMessageProcessor uses invariant culture.

Tinkoff (v5.0.28):
Fixes.
SS-302. AsyncMessageProcessor uses invariant culture.

PolygonIO (v5.0.19):
SS-302. AsyncMessageProcessor uses invariant culture.

Release notes 2/6/2024

2024-02-06T11:40:41Z

MatLab (v5.0.151):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.
SecurityCsvList multi-threading lookup fix.

InteractiveBrokers connector (v5.0.156):
v10.27.01 supported
API 10.27
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

ASTSBridge (v5.0.158):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Plaza (v5.0.162):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Transaq (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

LMAX (v5.0.155):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

FIX (v5.0.170):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

FAST connector (v5.0.4):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

IQFeed (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

RSS (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

BarChart (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Rithmic (v5.0.158):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

TWIME (v5.0.157):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

SpbEX (v5.0.150):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

QuantFEED (v5.0.158):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

AlphaVantage (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

AlorHistory (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

DukasCopy (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Yahoo Finance (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Finam connector (v5.0.157):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

MFD (v5.0.156):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bibox (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Binance (v5.0.158):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bitalong (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bitbank (v5.0.154):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bitexbook (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bitfinex (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bithumb (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

BitMax (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bitmex (v5.0.154):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

BitStamp (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Bittrex (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

BitZ (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Btce (v5.0.152):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

BW (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Cex (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Coinbase (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

CoinBene (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

CoinCap (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Coincheck (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

CoinEx (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

CoinExchange (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

CoinHub (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Coinigy (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Cryptopia (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Deribit (v5.0.157):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Digifinex (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

DigitexFutures (v5.0.154):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Exmo (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

FatBtc (v5.0.152):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Gdax (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Gopax (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

HitBtc (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Hotbit (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

HTX connector (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Idax (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Kraken (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Kucoin (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Latoken (v5.0.152):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

LBank (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Liqui (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

LiveCoin (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Okcoin (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

OKX (v5.0.158):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Poloniex (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

PrizmBit (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Quoinex (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

TradeOgre (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Upbit (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Yobit (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Zaif (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

ZB (v5.0.153):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Terminal (v5.0.157):
Hide Auto button in ConnectorWindow
DESIGNER-116 Fix expandable editors
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.
SecurityCsvList multi-threading lookup fix.
TRML-24 Fix show order book.

Designer (v5.0.158):
Optimizer supported nullable params.
DESIGNER-116 Fix expandable editors
Hide Auto button in ConnectorWindow
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.
SecurityCsvList multi-threading lookup fix.
TRML-24 Fix show order book.

Hydra (v5.0.161):
Subscriptions supports fill gaps mode.
Reduced info logs.
AsyncMessageAdapter. FaultDelay property.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
SecurityCsvList multi-threading lookup fix.
Hide Auto button in ConnectorWindow
DESIGNER-116 Fix expandable editors
TRML-24 Fix show order book.

UDP Dumper (v5.0.129):
Hide Auto button in ConnectorWindow
DESIGNER-116 Fix expandable editors
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.
SecurityCsvList multi-threading lookup fix.

Oanda (v5.0.155):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

UDPDumper.Console (v5.0.117):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

QUIK (v5.0.152):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

MT 4 (v5.0.148):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

MT 5 (v5.0.147):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

MOEX ISS (v5.0.29):
Subscriptions cancellation fixes.
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Runner (v5.0.17):
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.
SecurityCsvList multi-threading lookup fix.

Alor (v5.0.27):
Subscriptions cancellation fixes.
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Tinkoff (v5.0.27):
Subscriptions cancellation fixes.
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

PolygonIO (v5.0.18):
Subscriptions cancellation fixes.
Fix set security type for indexes.
AsyncMessageAdapter. FaultDelay property.
Subscriptions supports fill gaps mode.
AsyncMessageProcessor removed BaseLogReceiver inheritance.
AsyncMessageProcessor dispose logic added.
AsyncMessageAdapter. Fix unsubscribe requests.
HandleMessageException -> CreateErrorResponse.
PriorityQueue accepts subtractAbs arg.
MessageQueueItem. Removed Task info.
Reduced info logs.

Release notes 1/31/2024

2024-01-31T19:28:44Z

Installer (v5.0.144):
Removed legacy code.
removed custom priority initialization.
ISLR-25 Prevent to download system files.
Moved alls settings into single file
islr-66: fix binding warning
Dynamic language change.
Change language from settings.
ISLR-68 Show notification for new available products.