-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different between current and highest price. #67
Comments
Hey @BramFr, this is interesting strategy.
So when there is a sharp drop, you would like to place a trailing buy order, right?
Confusing. So place a trailing buy order when the current price is higher than 15% down of the highest price?
Confusing again. If the current price dropped more than 15% of the highest price, don't 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? |
Indeed. When a sharp drop > 15 % its interesting to buy. Even when the current price still higher than the lower/trigger price. Its possible that this never hit the trigger price.
Almost the same as the example above but then without the drop (drop timestamp) and looking for longer information. 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.
example: 1h candle with 100 interval 4h candle with 200 interval 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`ll hope i make this clear :) |
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 Hm, others may think differently. Let me keep this issue open to see how others think. |
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. |
The problem with this is you have to adjust the candle number al the time... When there is a drop you want something like 30m with 30 interval. Highst value = 1 |
I do agree this is a very interesting strategy.
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:
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
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:
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
In the next few minutes, if the price drops to $96.9, then the STOP-LOSS order will be executed.
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. |
I assume you meant "Buy trigger percentage". I think the above reply would have answered the issue with the sharp drop buy. |
Yeah, you are right! Sorry, I forgot to thank you for your work! This bot is the best I tried! |
Ah, I see what you mean now. So you mean we can use Let me re-summarise what I understood from your summary to make sure I understood correctly:
If the current price drops within 5 candles to less than Am I understanding correctly? |
Indeed. 👍 ill consider extra option to make sure you will hit the
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. |
@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.. 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 :) |
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. Just note I am still testing #77 which was massive refactoring. |
% difference between H/C = 1.15 (15%) |
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.
The text was updated successfully, but these errors were encountered: