Different between current and highest price. #67

BramFr · 2021-03-31T05:07:55Z

Is your proposal related to a problem?

Not a problem like software issue more frustration.

Describe the solution you'd like

When a Coin drops within a few minutes with 15% (current price vs highest price and between the candles interval) but still higher then the buy/lowest counter it can be interesting to buy
When the current price >15% vs highest price buy coins.
When the current price <15% vs highest price do nothing
When the Trigger Sell price < Highest price dont buy

Describe alternatives you've considered

Doing manual.

chrisleekr · 2021-03-31T09:23:08Z

Hey @BramFr, this is interesting strategy.

When a Coin drops within a few minutes with 15% (current price vs highest price and between the candles interval) but still higher then the buy/lowest counter it can be interesting to buy

So when there is a sharp drop, you would like to place a trailing buy order, right?

When the current price >15% vs highest price buy coins.

Confusing. So place a trailing buy order when the current price is higher than 15% down of the highest price?

When the current price <15% vs highest price do nothing

Confusing again. If the current price dropped more than 15% of the highest price, don't buy?

When the Trigger Sell price < Highest price dont buy

What do you mean by this step?

I think I kind of understand what you are trying to do, but would be able to give a detailed scenario using the price numbers?
So I understand 100% of your strategy?

BramFr · 2021-03-31T11:14:23Z

Hey @BramFr, this is interesting strategy.

When a Coin drops within a few minutes with 15% (current price vs highest price and between the candles interval) but still higher then the buy/lowest counter it can be interesting to buy

So when there is a sharp drop, you would like to place a trailing buy order, right?

Indeed. When a sharp drop > 15 % its interesting to buy. Even when the current price still higher than the lower/trigger price.
Example
Highest price: 100
Dropping to: 85 >= 15% this will hit a buy order
trigger price: 80

Its possible that this never hit the trigger price.
You can consider a option that the drop of 15% must be within a timestamp of 1hour?

When the current price >15% vs highest price buy coins.

When the current price <15% vs highest price do nothing
Indeed very confusing sorry for my bad English.

Almost the same as the example above but then without the drop (drop timestamp) and looking for longer information.
Highest price: 120
current value to: 100 (20% different then highest price with a 15% sell profit value) buy coins.
trigger price: 80

When you have a sell value of 15% and the difference between the highest value and current value > 20% (because you want to have a marge between these values). It can be interesting buy.

When the Trigger Sell price < Highest price dont buy

What do you mean by this step?

example:
When you have a flat line with a 1h candle with 100 interval and this will hit the trigger price.
Its not interesting to buy any coins when the highest value within 4h candle with 200 interval isn't higer x% then the current value.

1h candle with 100 interval
Trigger price 100

4h candle with 200 interval
highest price 105

This will indicate a profit of 5% but when you have a sell value of 15%. Its possible that this coin will never hit this 15% of profit or you have to wait a very long time to hit this value. There must be a option to disable / enable this feature.

I think I kind of understand what you are trying to do, but would be able to give a detailed scenario using the price numbers?
So I understand 100% of your strategy?

I`ll hope i make this clear :)

chrisleekr · 2021-04-02T11:58:16Z

Hi @BramFr

I was considering your strategy, however, I don't think I will add that strategy to buy signal.

I mean, if you want to target sharp drop, you may change the candle number to a small number of candles. Then, the lowest price will be close to the current price. If there is a sharp drop that reaches the lowest price, the bot will follow the drop and buy at the lowest price.

And we have Buy Trigger Percentage that you can set to give some buffer for buying. (Thanks to @Maxoos suggestion #18).

Hm, others may think differently.

Let me keep this issue open to see how others think.

4KJuegos · 2021-04-07T08:21:12Z

May be interesting, because the trigger with minimum sometimes doesn't work. An option to try the trigger minimum or the drop percentage may be interesting. Cryptos works different one of the other. The funcionality is the same as the sell, when drops below the percentage, it will start to set the stop-loss to buy. Can you add also a STOP-LOSS? It's impossible to add it directly because the bot remove it from binance. And you can also add an option to link this stop-loss to the last buy price. With this, if the price falls, the stop-loss will sell and with trigger percentage that BramFr says, you go to buy on best price ever.

The idea is that if price fall below your buy, you can stop losing and then, buy again to a better price.

BramFr · 2021-04-07T09:37:32Z

I mean, if you want to target sharp drop, you may change the candle number to a small number of candles. Then, the lowest price will be close to the current price. If there is a sharp drop that reaches the lowest price, the bot will follow the drop and buy at the lowest price.

The problem with this is you have to adjust the candle number al the time...
When you dont have any dorp you would have a candle 1h with 100 interval. To play save

When there is a drop you want something like 30m with 30 interval.
Highst value = 1
current drop value = 0.8 (this is a drop of 20%. When your "sell trigger percent" has a value of: 1.10 its interesting to buy)
trigger value = 0.5

Highst value = 1
current drop value = 0.8 (this is a drop of 20%. When your "sell trigger percent" has a value of: 1.30 its not interesting to buy because the coin have may not reach the "sell trigger percent" value.)
trigger value = 0.5

chrisleekr · 2021-04-07T12:55:49Z

@4KJuegos

May be interesting

I do agree this is a very interesting strategy.

With this, if the price falls, the stop-loss will sell and with trigger percentage that BramFr says, you go to buy on best price ever.

However, I don't think this is a good strategy. Let me try to give an example.

Let say, current market & configuration are like below:

Highest & current price: $120
Lowest price within 1h period: $80
Drop buy percentage: 15%
Drop buy trigger price: $102
Stop Loss percentage: 0.95 (5%)

In the next 30 mins, if the price drops to $102 and I place a BUY order for the coin and immediately place STOP-LOSS order as you mentioned

Current price: $102
Stop Loss order: $96.9

In the next few minutes, if the price drops to $96.9, then the STOP-LOSS order will be executed, but the current price is still in the range of Drop buy percentage (less than $102). The bot will think it's in range, so buy again. And if drops another 5% (Stop Loss percentage), then it will sell again. So you keep losing the money.

I may be able to overcome this issue by checking not to place multiple BUY order within Drop buy trigger price.

But the actual problem goes below the situation: (Mind for copy and paste above example, I highlighted the difference.)

Let say, current market & configuration are like below:

Highest & current price: $120
- Lowest price within 1h period: $100
Drop buy percentage: 15%
Drop buy trigger price: $102
Stop Loss percentage: 0.95 (5%)

In the next 30 mins, if the price drops to $102 and I place a BUY order for the coin and immediately place STOP-LOSS order as you mentioned

Current price: $102
Stop Loss order: $96.9

In the next few minutes, if the price drops to $96.9, then the STOP-LOSS order will be executed.
But the current market is like this:

Current price: $96.9
Lowest price: $96.9

Then the bot will purchase the coin again because it is reached the lowest price.

So you will have to choose either using sharp drop strategy or the lowest price buy strategy.

Hm, I wrote too long, hope what I said is making sense.

chrisleekr · 2021-04-07T13:09:21Z

@BramFr

Highst value = 1
current drop value = 0.8 (this is a drop of 20%. When your "sell trigger percent" has a value of: 1.10 its interesting to buy)
trigger value = 0.5

Highst value = 1
current drop value = 0.8 (this is a drop of 20%. When your "sell trigger percent" has a value of: 1.30 its not interesting to buy because the coin have may not reach the "sell trigger percent" value.)
trigger value = 0.5

I assume you meant "Buy trigger percentage".

I think the above reply would have answered the issue with the sharp drop buy.

4KJuegos · 2021-04-07T14:11:40Z

@4KJuegos

May be interesting

I do agree this is a very interesting strategy.

With this, if the price falls, the stop-loss will sell and with trigger percentage that BramFr says, you go to buy on best price ever.

However, I don't think this is a good strategy. Let me try to give an example.

Let say, current market & configuration are like below:

Highest & current price: $120

Lowest price within 1h period: $80

Drop buy percentage: 15%

Drop buy trigger price: $102

Stop Loss percentage: 0.95 (5%)

In the next 30 mins, if the price drops to $102 and I place a BUY order for the coin and immediately place STOP-LOSS order as you mentioned

Current price: $102

Stop Loss order: $96.9

In the next few minutes, if the price drops to $96.9, then the STOP-LOSS order will be executed, but the current price is still in the range of Drop buy percentage (less than $102). The bot will think it's in range, so buy again. And if drops another 5% (Stop Loss percentage), then it will sell again. So you keep losing the money.

I may be able to overcome this issue by checking not to place multiple BUY order within Drop buy trigger price.

But the actual problem goes below the situation: (Mind for copy and paste above example, I highlighted the difference.)

Let say, current market & configuration are like below:

Highest & current price: $120
- Lowest price within 1h period: $100

Drop buy percentage: 15%

Drop buy trigger price: $102

Stop Loss percentage: 0.95 (5%)

In the next 30 mins, if the price drops to $102 and I place a BUY order for the coin and immediately place STOP-LOSS order as you mentioned

Current price: $102

Stop Loss order: $96.9

In the next few minutes, if the price drops to $96.9, then the STOP-LOSS order will be executed.
But the current market is like this:

Current price: $96.9

Lowest price: $96.9

Then the bot will purchase the coin again because it is reached the lowest price.

So you will have to choose either using sharp drop strategy or the lowest price buy strategy.

Hm, I wrote too long, hope what I said is making sense.

Yeah, you are right! Sorry, I forgot to thank you for your work! This bot is the best I tried!

BramFr · 2021-04-07T14:40:57Z

@BramFr

Highst value = 1
current drop value = 0.8 (this is a drop of 20%. When your "sell trigger percent" has a value of: 1.10 its interesting to buy)
trigger value = 0.5
Highst value = 1
current drop value = 0.8 (this is a drop of 20%. When your "sell trigger percent" has a value of: 1.30 its not interesting to buy because the coin have may not reach the "sell trigger percent" value.)
trigger value = 0.5

I assume you meant "Buy trigger percentage".

I think the above reply would have answered the issue with the sharp drop buy.

sorry for my bad english :).

Nope i do mean "sell trigger percent"
Example:

At this example this coin will never hit his Lowest Value because this coin has a nice increase value.
Highest value: 23.430
current Value: 19.920
LowestValue: 16.550
Buy Trigger price (0.00%): 16.550
Sell Trigger price (10.00%): ???

At this point the difference between current and Highest value +/- 17%
because 17 is much higher then my Sell Trigger price (10.00%) it can be intresting to buy.

You can make a fail safe option like:
% difference between H/C = 1.15 (15%)
Candle counts = 5 1h

summary:
Within the first 5 candle the price drop from: 23.430 - 15% "% difference between H/C" = 19.9155

Highest value: 23.430
current Value: 19.9155
"% difference between H/C": 1.15 (this value is most likely higher then "Sell Trigger price") AND Candle counts = 5 1h
Lowest Value: 16.550
Buy Trigger price (0.00%): 16.550
Sell Trigger price (10.00%): ???

Make a buy order

chrisleekr · 2021-04-09T03:30:59Z

Ah, I see what you mean now. So you mean we can use Sell trigger percentage for buying.

Let me re-summarise what I understood from your summary to make sure I understood correctly:

Highest price within candles: 23.430
Current price: 19.9155 (15% less than the highest price)
Lowest price: 16.550
Sell trigger price of the highest price(10%): 21.087
Number of monitoring candles for the sudden drop: 5 candles

If the current price drops within 5 candles to less than Sell trigger price (10%): 21.087 of the highest price, then place a buy STOP-LOSS-LIMIT order.
So above case will place a buy STOP-LOSS-LIMIT order.

Am I understanding correctly?

BramFr · 2021-04-09T06:18:39Z

Ah, I see what you mean now. So you mean we can use Sell trigger percentage for buying.

Let me re-summarise what I understood from your summary to make sure I understood correctly:

Highest price within candles: 23.430

Current price: 19.9155 (15% less than the highest price)

Lowest price: 16.550

Sell trigger price of the highest price(10%): 21.087

Number of monitoring candles for the sudden drop: 5 candles

If the current price drops within 5 candles to less than Sell trigger price (10%): 21.087 of the highest price, then place a buy STOP-LOSS-LIMIT order.
So above case will place a buy STOP-LOSS-LIMIT order.

Am I understanding correctly?

Indeed. 👍
This will work.

ill consider extra option to make sure you will hit the Sell trigger price just for certainty

% difference between H/C = 1.15 (15%)
Sell trigger price of the highest price(10%)

The difference between current en High must be >15% to make sure you will hit the 10% sell trigger price.

But your example will do the job also.

ggloveswp · 2021-04-09T09:01:31Z

@BramFr out of curiosity, what amount of candles/interval have you currently set the bot at?

Asking just because Im trying to follow the same trading logic, partially: looking to place buy orders in sudden -5% (within last X(1-9) hours) drops and selling back at +5% with no specific timeframe, no matter if I hodl those coins forever.

Im currently confused about the candles amount and interval needed for my scope.

BramFr · 2021-04-09T10:55:26Z

@BramFr out of curiosity, what amount of candles/interval have you currently set the bot at?

Asking just because Im trying to follow the same trading logic, partially: looking to place buy orders in sudden -5% (within last X(1-9) hours) drops and selling back at +5% with no specific timeframe, no matter if I hodl those coins forever.

Im currently confused about the candles amount and interval needed for my scope.

I don't recommend any settings its still at your own risk..
When coin has a stable or i dont have any time ill used something like 2h with 80 interval with buy percent 1. Just to play safe

But when i know there is a sharp dorp for some coins ill change it to 30m with 30interval with buy percent 1 ore something but you have to look at everycoin if this settings possible.

im still experimenting with this :)

chrisleekr · 2021-04-09T11:13:26Z

@BramFr

% difference between H/C = 1.15 (15%)

Sell trigger price of the highest price(10%)

When you say H/C, it stands for Highest Candle? or Highest Price?

Either way, this strategy could be implemented. Although I will need reasonable option names to make understanding easier.
And detailed example strategy.

Just note I am still testing #77 which was massive refactoring.
I won't add more features until that is stable.
So this change may be delayed.

BramFr · 2021-04-09T11:28:13Z

@BramFr

% difference between H/C = 1.15 (15%)

Sell trigger price of the highest price(10%)

When you say H/C, it stands for Highest Candle? or Highest Price?

% difference between H/C = 1.15 (15%)
H = Highest Price
C = Current Price

@d0x2f

# Binance Trading Bot [![Stand With Ukraine](https://raw.githubusercontent.com/vshymanskyy/StandWithUkraine/main/banner2-direct.svg)](https://war.ukraine.ua) [![GitHub version](https://img.shields.io/github/package-json/v/chrisleekr/binance-trading-bot)](https://github.com/chrisleekr/binance-trading-bot/releases) [![Build](https://github.com/chrisleekr/binance-trading-bot/workflows/Push/badge.svg)](https://github.com/chrisleekr/binance-trading-bot/actions?query=workflow%3APush) [![CodeCov](https://codecov.io/gh/chrisleekr/binance-trading-bot/branch/master/graph/badge.svg)](https://codecov.io/gh/chrisleekr/binance-trading-bot) [![Docker pull](https://img.shields.io/docker/pulls/chrisleekr/binance-trading-bot)](https://hub.docker.com/r/chrisleekr/binance-trading-bot) [![GitHub contributors](https://img.shields.io/github/contributors/chrisleekr/binance-trading-bot)](https://github.com/chrisleekr/binance-trading-bot/graphs/contributors) [![MIT License](https://img.shields.io/github/license/chrisleekr/binance-trading-bot)](https://github.com/chrisleekr/binance-trading-bot/blob/master/LICENSE) > Automated Binance trading bot with trailing buy/sell strategy --- [![ko](https://img.shields.io/badge/lang-한국어-brightgreen.svg)](https://github.com/chrisleekr/binance-trading-bot/blob/master/README.ko.md) [![中文](https://img.shields.io/badge/lang-中文-blue.svg)](https://github.com/chrisleekr/binance-trading-bot/blob/master/README.zh-cn.md) This is a test project. I am just testing my code. ## Warnings **I cannot guarantee whether you can make money or not.** **So use it at your own risk! I have no responsibility for any loss or hardship incurred directly or indirectly by using this code. Read [disclaimer](#disclaimer) before using this code.** **Before updating the bot, make sure to record the last buy price in the note. It may lose the configuration or last buy price records.** ## How it works ### Trailing Grid Trade Buy/Sell Bot This bot is using the concept of trailing buy/sell order which allows following the price fall/rise. > Trailing Stop Orders > About Trailing Stop Orders Concept you can find at [Binance Official document](https://www.binance.com/en/support/faq/360042299292) > > TL;DR > Place orders at a fixed value or percentage when the price changes. Using this feature you can buy at the lowest possible price when buying down and sell at the highest possible price when selling up. - The bot supports multiple buy/sell orders based on the configuration. - The bot can monitor multiple symbols. All symbols will be monitored per second. - The bot is using MongoDB to provide a persistence database. However, it does not use the latest MongoDB to support Raspberry Pi 32bit. Used MongoDB version is 3.2.20, which is provided by [apcheamitru](https://hub.docker.com/r/apcheamitru/arm32v7-mongo). - The bot is tested/working with Linux and Raspberry Pi 4 32bit. Other platforms are not tested. #### Buy Signal The bot will continuously monitor the coin based on the grid trade configuration. For grid trade #1, the bot will place a STOP-LOSS-LIMIT order to buy when the current price reaches the lowest price. If the current price continuously falls, then the bot will cancel the previous order and re-place the new STOP-LOSS-LIMIT order with the new price. After grid trade #1, the bot will monitor the COIN based on the last buy price. - The bot will not place a buy order of the grid trade #1 if has enough coin (typically over $10 worth) to sell when reaches the trigger price for selling. - The bot will remove the last buy price if the estimated value is less than the last buy price removal threshold. ##### Buy Scenario Let say, if the buy grid trade configurations are set as below: - Number of grids: 2 - Grids | No# | Trigger Percentage | Stop Price Percentage | Limit price percentage | USDT | | --- | ------------------- | --------------------- | ---------------------- | ---- | | 1 | 1 | 1.05 | 1.051 | 50 | | 2 | 0.8 | 1.03 | 1.031 | 100 | To make it easier to understand, I will use `$` as a USDT symbol. For the simple calculation, I do not take an account for the commission. In real trading, the quantity may be different. Your 1st grid trading for buying is configured as below: - Grid No#: 1 - Trigger percentage: 1 - Stop percentage: 1.05 (5.00%) - Limit percentage: 1.051 (5.10%) - Max purchase amount: $50 And the market is as below: - Current price: $105 - Lowest price: $100 - Trigger price: $100 When the current price is falling to the lowest price ($100) and lower than ATH(All-Time High) restricted price if enabled, the bot will place new STOP-LOSS-LIMIT order for buying. - Stop price: $100 * 1.05 = $105 - Limit price: $100 * 1.051 = $105.1 - Quantity: 0.47573 Let's assume the market changes as below: - Current price: $95 Then the bot will follow the price fall and place new STOP-LOSS-LIMIT order as below: - Stop price: $95 * 1.05 = $99.75 - Limit price: $95 * 1.051 = $99.845 - Quantity: 0.5 Let's assume the market changes as below: - Current price: $100 Then the bot will execute 1st purchase for the coin. The last buy price will be recorded as `$99.845`. The purchased quantity will be `0.5`. Once the coin is purchased, the bot will start monitoring the sell signal and at the same time, monitor the next grid trading for buying. Your 2nd grid trading for buying is configured as below: - Grid#: 2 - Current last buy price: $99.845 - Trigger percentage: 0.8 (20%) - Stop percentage: 1.03 (3.00%) - Limit percentage: 1.031 (3.10%) - Max purchase amount: $100 And if the current price is continuously falling to `$79.876` (20% lower), then the bot will place new STOP-LOSS-LIMIT order for the 2nd grid trading for the coin. Let's assume the market changes as below: - Current price: $75 Then the bot will follow the price fall and place new STOP-LOSS-LIMT order as below: - Stop price: $75 * 1.03 = $77.25 - Limit price: $75 * 1.031 = $77.325 - Quantity: 1.29 Let's assume the market changes as below: - Current price: $78 Then the bot will execute 2nd purchase for the coin. The last buy price will be automatically re-calculated as below: - Final last buy price: ($50 + $100)/(0.5 COIN + 1.29 COIN) = $83.80 ##### In-depth Buy Configuration in-depth The detailed document for buy configuration available here. [https://github.com/chrisleekr/binance-trading-bot/wiki/Buy-Scenario](https://github.com/chrisleekr/binance-trading-bot/wiki/Buy-Scenario) ### Sell Signal If there is enough balance for selling and the last buy price is recorded in the bot, then the bot will start monitoring the sell signal of the grid trade #1. Once the current price reaches the trigger price of the grid trade #1, then the bot will place a STOP-LOSS-LIMIT order to sell. If the current price continuously rises, then the bot will cancel the previous order and re-place the new STOP-LOSS-LIMIT order with the new price. - If the bot does not have a record for the last buy price, the bot will not sell the coin. - If the coin is worth less than the last buy price removal threshold, then the bot will remove the last buy price. - If the coin is not worth than the minimum notional value, then the bot will not place an order. #### Sell Scenario Let say, if the sell grid trade configurations are set as below: - Number of grids: 2 - Grids | No# | Trigger Percentage | Stop Price Percentage | Limit price percentage | Sell Quantity Percentage | | --- | ------------------- | --------------------- | ---------------------- |------------------------- | | 1st | 1.05 | 0.97 | 0.969 | 0.5 | | 2nd | 1.08 | 0.95 | 0.949 | 1 | Unlike buy, the sell configuration will use the percentage of a quantity. If you want to sell all of your coin quantity, then simply configure it as `1` (100%). From the last buy actions, you now have the following balances: - Current quantity: 1.79 - Current last buy price: $83.80 Your 1st grid trading for selling is configured as below: - Grid No# 1 - Trigger percentage: 1.05 - Stop price percentage: 0.97 - Limit price percentage: 0.969 - Sell amount percentage: 0.5 Let's assume the market changes as below: - Current price: $88 As the current price is higher than the sell trigger price($87.99), then the bot will place new STOP-LOSS-LIMIT order for selling. - Stop price: $88 * 0.97 = $85.36 - Limit price: $88 * 0.969 = $85.272 - Quantity: 0.895 Let's assume the market changes as below: - Current price: $90 Then the bot will follow the price rise and place new STOP-LOSS-LIMIT order as below: - Stop price: $90 * 0.97 = $87.30 - Limit price: $90 * 0.969 = $87.21 - Quantity: 0.895 Let's assume the market changes as below: - Current price: $87 Then the bot will execute 1st sell for the coin. Then the bot will now wait for 2nd selling trigger price ($83.80 * 1.08 = $90.504). - Current quantity: 0.895 - Current last buy price: $83.80 Let's assume the market changes as below: - Current price: $91 Then the current price($91) is higher than 2nd selling trigger price ($90.504), the bot will place new STOP-LOSS-LIMIT order as below: - Stop price: $91 * 0.95 = $86.45 - Limit price: $91 * 0.949 = $86.359 - Quantity: 0.895 Let's assume the market changes as below: - Current price: $100 Then the bot will follow the price rise and place new STOP-LOSS-LIMT order as below: - Stop price: $100 * 0.95 = $95 - Limit price: $100 * 0.949 = $94.9 - Quantity: 0.895 Let's assume the market changes as below: - Current price: $94 Then the bot will execute 2nd sell for the coin. The final profit would be - 1st sell: $94.9 * 0.895 = $84.9355 - 2nd sell: $87.21 * 0.895 = $78.05295 - Final profit: $162 (8% profit) ##### In-depth Sell Configuration The detailed document for buy configuration available here. [https://github.com/chrisleekr/binance-trading-bot/wiki/Sell-Scenario](https://github.com/chrisleekr/binance-trading-bot/wiki/Sell-Scenario) ### [Features](https://github.com/chrisleekr/binance-trading-bot/wiki/Features) - Manual trade - Convert small balances to BNB - Trade all symbols - Monitoring multiple coins simultaneously - Stop-Loss - Restrict buying with ATH price - Grid Trade for buy/sell - Integrated with TradingView Technical Analysis ### Frontend + WebSocket React.js based frontend communicating via Web Socket: - List monitoring coins with buy/sell signals/open orders - View account balances - View open/closed trades - Manage global/symbol settings - Delete caches that are not monitored - Link to public URL - Support Add to Home Screen - Secure frontend ## Environment Parameters Use environment parameters to adjust parameters. Check `/config/custom-environment-variables.json` to see list of available environment parameters. Or use the frontend to adjust configurations after launching the application. ## How to use 1. Create `.env` file based on `.env.dist`. | Environment Key | Description | Sample Value | | ------------------------------ | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | BINANCE_LIVE_API_KEY | Binance API key for live | (from [Binance](https://binance.zendesk.com/hc/en-us/articles/360002502072-How-to-create-API)) | | BINANCE_LIVE_SECRET_KEY | Binance API secret for live | (from [Binance](https://binance.zendesk.com/hc/en-us/articles/360002502072-How-to-create-API)) | | BINANCE_TEST_API_KEY | Binance API key for test | (from [Binance Spot Test Network](https://testnet.binance.vision/)) | | BINANCE_TEST_SECRET_KEY | Binance API secret for test | (from [Binance Spot Test Network](https://testnet.binance.vision/)) | | BINANCE_SLACK_ENABLED | Slack enable/disable | true | | BINANCE_SLACK_WEBHOOK_URL | Slack webhook URL | (from [Slack](https://slack.com/intl/en-au/help/articles/115005265063-Incoming-webhooks-for-Slack)) | | BINANCE_SLACK_CHANNEL | Slack channel | "#binance" | | BINANCE_SLACK_USERNAME | Slack username | Chris | | BINANCE_LOCAL_TUNNEL_ENABLED | Enable/Disable [local tunnel](https://github.com/localtunnel/localtunnel) | true | | BINANCE_LOCAL_TUNNEL_SUBDOMAIN | Local tunnel public URL subdomain | binance | | BINANCE_AUTHENTICATION_ENABLED | Enable/Disable frontend authentication | true | | BINANCE_AUTHENTICATION_PASSWORD | Frontend password | 123456 | | BINANCE_LOG_LEVEL | Logging level. [Possible values described on `bunyan` docs.](https://www.npmjs.com/package/bunyan#levels) | ERROR | *A local tunnel makes the bot accessible from the outside. Please set the subdomain of the local tunnel as a subdomain that only you can remember.* *You must change the authentication password; otherwise, it will be configured as the default password.* 2. Launch/Update the bot with docker-compose Pull latest code first: ```bash git pull ``` If want production/live mode, then use the latest build image from DockerHub: ```bash docker-compose -f docker-compose.server.yml pull docker-compose -f docker-compose.server.yml up -d ``` Or if want development/test mode, then run below commands: ```bash docker-compose up -d --build ``` 3. Open browser `http://0.0.0.0:8080` to see the frontend - When launching the application, it will notify public URL to the Slack. - If you have any issue with the bot, you can check the log to find out what happened with the bot. Please take a look [Troubleshooting](https://github.com/chrisleekr/binance-trading-bot/wiki/Troubleshooting) ### Install via Stackfile 1. In [Portainer](https://www.portainer.io/) create new Stack 2. Copy content of `docker-stack.yml` or upload the file 3. Set environment keys for `binance-bot` in the `docker-stack.yml` 4. Launch and open browser `http://0.0.0.0:8080` to see the frontend ## Screenshots | Password Protected | Frontend Mobile | | ------------------ | --------------- | | ![Password Protected](https://user-images.githubusercontent.com/5715919/133920104-49d1b590-c2ba-46d7-a294-eb6b24b459f5.png) | ![Frontend Mobile](https://user-images.githubusercontent.com/5715919/137472107-4059fcdf-5174-4282-81af-80cea5b269a0.png) | | Setting | Manual Trade | | ------- | ------------ | | ![Setting](https://user-images.githubusercontent.com/5715919/127318581-4e422ac9-b145-4e83-a90d-5c05c61d6e2f.png) | ![Manual Trade](https://user-images.githubusercontent.com/5715919/127318630-f2180e1b-3feb-48fa-a083-4cb7f90f743f.png) | | Frontend Desktop | Closed Trades | | ----------------- | ------------- | | ![Frontend Desktop](https://user-images.githubusercontent.com/5715919/137472148-7be1e19b-3ce5-4d5a-aa28-18c55b3b48aa.png) | ![Closed Trades](https://user-images.githubusercontent.com/5715919/137472190-a4c6ef0f-3399-44bb-852f-eedb7c67d629.png) | ### Sample Trade | Chart | Buy Orders | Sell Orders | | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | ![Chart](https://user-images.githubusercontent.com/5715919/111027391-192db300-8444-11eb-8df4-91c98d0c835b.png) | ![Buy Orders](https://user-images.githubusercontent.com/5715919/111027403-36628180-8444-11eb-91dc-f3cdabc5a79e.png) | ![Sell Orders](https://user-images.githubusercontent.com/5715919/111027411-4b3f1500-8444-11eb-8525-37f02a63de25.png) | ## Changes & Todo Please refer [CHANGELOG.md](https://github.com/chrisleekr/binance-trading-bot/blob/master/CHANGELOG.md) to view the past changes. - [ ] Develop simple setup screen for secrets - [ ] Allow to execute stop-loss before buy action - [#299](chrisleekr/binance-trading-bot#299) - [ ] Improve sell strategy with conditional stop price percentage based on the profit percentage - [#94](chrisleekr/binance-trading-bot#94) - [ ] Add sudden drop buy strategy - [#67](chrisleekr/binance-trading-bot#67) - [ ] Manage setting profiles (save/change/load?/export?) - [#151](chrisleekr/binance-trading-bot#151) - [ ] Improve notifications by supporting Apprise - [#106](chrisleekr/binance-trading-bot#106) - [ ] Support cool time after hitting the lowest price before buy - [#105](chrisleekr/binance-trading-bot#105) - [ ] Reset global configuration to initial configuration - [#97](chrisleekr/binance-trading-bot#97) - [ ] Support multilingual frontend - [#56](chrisleekr/binance-trading-bot#56) - [ ] Non linear stop price and chase function - [#246](chrisleekr/binance-trading-bot#246) - [ ] Support STOP-LOSS configuration per grid trade for selling - [#261](chrisleekr/binance-trading-bot#261) ## Donations If you find this project helpful, feel free to make a small [donation](https://github.com/chrisleekr/binance-trading-bot/blob/master/DONATIONS.md) to the developer. ## Acknowledgments - [@d0x2f](https://github.com/d0x2f) - And many others! Thanks guys! ## Contributors Thanks to all contributors ❤️ [Click to see our heroes](https://github.com/chrisleekr/binance-trading-bot/graphs/contributors) ## Disclaimer I give no warranty and accepts no responsibility or liability for the accuracy or the completeness of the information and materials contained in this project. Under no circumstances will I be held responsible or liable in any way for any claims, damages, losses, expenses, costs or liabilities whatsoever (including, without limitation, any direct or indirect damages for loss of profits, business interruption or loss of information) resulting from or arising directly or indirectly from your use of or inability to use this code or any code linked to it, or from your reliance on the information and material on this code, even if I have been advised of the possibility of such damages in advance. **So use it at your own risk!**

BramFr added the enhancement New feature or request label Mar 31, 2021

chrisleekr added the help wanted Extra attention is needed label Apr 2, 2021

BramFr mentioned this issue Apr 20, 2021

Buy Trigger Price Negative value #105

Open

chrisleekr mentioned this issue May 17, 2021

What will be the next feature? #166

Closed

chrisleekr mentioned this issue Jun 5, 2021

Dip Detection Strategy #219

Open

pedrohusky mentioned this issue Jul 6, 2021

feat: Customise the last buy price removing threshold #206

Merged

zxramozx mentioned this issue Jul 20, 2024

Update README.md BinanceAPItest/Binance-api-doc#7

Open

11 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Different between current and highest price. #67

Different between current and highest price. #67

BramFr commented Mar 31, 2021 •

edited

Loading

chrisleekr commented Mar 31, 2021

BramFr commented Mar 31, 2021

chrisleekr commented Apr 2, 2021

4KJuegos commented Apr 7, 2021

BramFr commented Apr 7, 2021

chrisleekr commented Apr 7, 2021 •

edited

Loading

chrisleekr commented Apr 7, 2021 •

edited

Loading

4KJuegos commented Apr 7, 2021

BramFr commented Apr 7, 2021 •

edited

Loading

chrisleekr commented Apr 9, 2021 •

edited

Loading

BramFr commented Apr 9, 2021 •

edited

Loading

ggloveswp commented Apr 9, 2021

BramFr commented Apr 9, 2021

chrisleekr commented Apr 9, 2021

BramFr commented Apr 9, 2021

Different between current and highest price. #67

Different between current and highest price. #67

Comments

BramFr commented Mar 31, 2021 • edited Loading

Is your proposal related to a problem?

Describe the solution you'd like

Describe alternatives you've considered

chrisleekr commented Mar 31, 2021

BramFr commented Mar 31, 2021

chrisleekr commented Apr 2, 2021

4KJuegos commented Apr 7, 2021

BramFr commented Apr 7, 2021

chrisleekr commented Apr 7, 2021 • edited Loading

chrisleekr commented Apr 7, 2021 • edited Loading

4KJuegos commented Apr 7, 2021

BramFr commented Apr 7, 2021 • edited Loading

chrisleekr commented Apr 9, 2021 • edited Loading

BramFr commented Apr 9, 2021 • edited Loading

ggloveswp commented Apr 9, 2021

BramFr commented Apr 9, 2021

chrisleekr commented Apr 9, 2021

BramFr commented Apr 9, 2021

BramFr commented Mar 31, 2021 •

edited

Loading

chrisleekr commented Apr 7, 2021 •

edited

Loading

chrisleekr commented Apr 7, 2021 •

edited

Loading

BramFr commented Apr 7, 2021 •

edited

Loading

chrisleekr commented Apr 9, 2021 •

edited

Loading

BramFr commented Apr 9, 2021 •

edited

Loading