When a price continues to rise the bot will purchase further orders of a single symbol. This is recorded correctly in the current-orders.json but when it comes to selling it does not appear to process all orders.

Suggested behaviour: when a stop loss is triggered for a symbol then all current orders for that symbol should be closed, not just the first on the list.

When there is a long period where nothing happens it can be hard to keep track of the executions. It might be helpful to add a timestamp to the output to make it clearer what is happening and when.

[2021/05/18 18:05:02] No coin has risen more than 5% in the last 5 minutes
[2021/05/18 18:05:02] MATICUSDT price has hit SL threshold
[2021/05/18 18:05:03] The asset MATICUSDT has been sold sucessfully at the profit of -5.72% and recorded in sold-assets.json
[2021/05/18 18:05:03] Wait for the bot to gather data to check price volatility...

Also, outputting the console to a .log file would help with troubleshooting. This might need to be configured with some form of log rotation.

Receiving the following warning is very scary

Error in executing buying volatiles function: "Error in executing buy function: {\"code\":-2010,\"msg\":\"Account has insufficient balance for requested action.\"}"

Maybe this can be caught and replaced with something friendlier?

Tried to buy but there was not enough funds available

• The sell_at key is returned as a text when it should be numeric
• The profit key is a text with the % symbol. Should this be a simple numeric and leave the text formatting to the front end

SAFE MODE description: To avoid the rapid ups and immediate downs within the next interval, after an asset is bought, the bot scan to check the asset price every 1 minute (1 is the default value, you can change the SCAN_INTERVAL in the config.env file). If the asset price hits SL threshold during that 1 minute, the bot will proceed to sell the asset.

Every time an asset hits the TP, the bot doesn't sell it immediately. The SL and TP threshold of that asset is increased. If an asset hits the SL, we sell (In fact, we just sell at SL).

For example, BTCUSDT is bought at 100. TP is 106 (6%) and SL is 97 (3%). When it hits 106, the TP is adjusted to ~106 and SL is ~103. Whenever it hits SL (97 or 103...), the bot sells.

{ BNBUSDT: { price: '488.00000000', time: 1630134032907 }, BTCUSDT: { price: '48960.73000000', time: 1630134032907 }, ETHUSDT: { price: '900.00000000', time: 1630134032907 }, LTCUSDT: { price: '172.55000000', time: 1630134032908 }, TRXUSDT: { price: '0.08478000', time: 1630134032908 }, XRPUSDT: { price: '0.99990000', time: 1630134032908 } } i like to have all prices from pair USDT (>=220 assets)

[6/7/2021, 11:04:49 AM] Error in executing buying volatiles function: "Error in calculating quantity: "Current portfolio value exceeds the initial quantity, waiting for the current asset(s) to be sold first...""

I'm seeing some double entries at the same time stamp which appears to be the INTERVAL script and the safe mode script running at the same time. See 11:16 on the following logs. The price increase calculations seem to be adding together as well.

Purchased at: 0.3496 Max during ownership: 0.3850 (gain of 10.1%)

[26/05/2021, 11:11:34] The price of RAMPUSDT has increased 6.78% within last 5 minutes... [26/05/2021, 11:11:34] Successfully place an order: {"symbol":"RAMPUSDT","quantity":142.93,"orderId":36363922,"bought_at":0.3496,"TP_Threshold":0.360088,"SL_Threshold":0.339112,"purchase_time":"26/05/2021, 11:11:34","purchase_time_unix":1622023894804,"updated_at":"26/05/2021, 11:11:34"} [26/05/2021, 11:12:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:13:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:14:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:15:33] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:16:33] The price of RAMPUSDT has increased 7.15% within last 5 minutes... [26/05/2021, 11:16:33] Error in executing buying volatiles function: "Error in calculating quantity: "Current portfolio value exceeds the initial quantity, waiting for the current asset(s) to be sold first..."" [26/05/2021, 11:16:33] The RAMPUSDT has hit TP threshold and we continue to hold as TRAILING MODE activated [26/05/2021, 11:16:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:16:34] The price of RAMPUSDT has increased 11.33% within last 5 minutes... [26/05/2021, 11:16:34] RAMPUSDT price hasn't hit SL or TP threshold, continue to wait... [26/05/2021, 11:16:34] Error in executing buying volatiles function: "Error in calculating quantity: "Current portfolio value exceeds the initial quantity, waiting for the current asset(s) to be sold first..."" [26/05/2021, 11:17:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:18:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:19:33] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:20:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:21:33] Wait for the bot to gather data to check price volatility... [26/05/2021, 11:21:34] RAMPUSDT price hasn't hit SL threshold during this scan and the asset is kept [26/05/2021, 11:21:34] RAMPUSDT price hasn't hit SL or TP threshold, continue to wait... [26/05/2021, 11:24:11] RAMPUSDT price has hit SL threshold [26/05/2021, 11:24:11] The asset RAMPUSDT has been sold sucessfully at the profit of 0.94% and recorded in sold-assets.json [26/05/2021, 11:24:11] RAMPUSDT price hasn hit SL threshold during this scan and the asset is sold [26/05/2021, 11:24:12] Error in scanning Error in selling asset when it hits SL threshold: Error in selling 142.93 of RAMPUSDT: {"code":-2010,"msg":"Account has insufficient balance for requested action."}

Issue: When a symbol's price is rapidly falling it can go far below the SL_Threshold before the script is run again and value is lost. This is worse if a longer interval is set.

Possible fix: Use the Binance API to set a stop loss limit at the SL_Threshold.

1. Initial SL limit is set when the order is placed
2. After Interval the order status is checked. If it has been filled the order is moved from current to sold with the price data set
3. If the order has not been filled the script runs as normal
4. If the TP_Threshold has been reached the SL order is cancelled and a new one is sent for the newly calculated SL_Threshold

Challenges:

• This might require a separate table for the stop loss orders?
• This might make the bot too responsive when a delay for the interval would allow the price to bounce back above the SL

When an order is sold the action goes through correctly but the order is not removed from current-orders.json. This results in the bot trying to repeatedly sell the item but not being able to as the Binance wallet no longer has the item to sell.