Skip to content
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

additional feature for Altrank script #137

Open
bonjo75 opened this issue Aug 13, 2022 · 7 comments
Open

additional feature for Altrank script #137

bonjo75 opened this issue Aug 13, 2022 · 7 comments
Assignees
Labels
enhancement New feature or request

Comments

@bonjo75
Copy link

bonjo75 commented Aug 13, 2022

would like to ask if possible to add additional criteria of coin selecting for Altrank from Lunarcrush, like select the first X coins but also taking in considration other parameter offered by LC as Market volatility and/or market Cap, etc.
Is that would be possible

Thanks

@bonjo75 bonjo75 added the enhancement New feature or request label Aug 13, 2022
@dangalv
Copy link
Contributor

dangalv commented Nov 1, 2022

Selecting the first coins can be done with the botassistexplorer script, but unfortunately no script allows you to use lunar rank and volatility at the same time
I hope guys @amargedon @brhahlen @cyberjunky can implement these two conditions that can be used simultaneously.
In botassistexplorer script, for example, the possibility of choosing 2 or more lists could be implemented, ex: altrank + volatility range.
🙌
This will greatly improve coin selection refinement :)

@amargedon
Copy link
Collaborator

@bonjo75 @dangalv There could be good news coming. I'm currently working on a Marketcollector script which I intend as replacement for CoinMarketCap, Altrank/GalaxyScore/LunarCrush, BotAssistExplorer scripts and merge it in one. Result will be a combined database with all the collected data from different sources.

A second script, the Botupdater, will use the data from that database to update the bots at 3Commas. The configuration of the Botupdater contains several options to filter the data. For example Altrank rank 1 - 10 and within CoinMarketCap rank 1 - 250 and price change over the last 24h between 0% and 25%.

For now it's work in progress, but in the back of my mind I knew there was somewhere a request. So, that's the update for now.

@dangalv
Copy link
Contributor

dangalv commented Nov 10, 2022

There could be good news coming. I'm currently working on a Marketcollector script which I intend as replacement for CoinMarketCap, Altrank/GalaxyScore/LunarCrush, BotAssistExplorer scripts and merge it in one. Result will be a combined database with all the collected data from different sources.

A second script, the Botupdater, will use the data from that database to update the bots at 3Commas. The configuration of the Botupdater contains several options to filter the data. For example Altrank rank 1 - 10 and within CoinMarketCap rank 1 - 250 and price change over the last 24h between 0% and 25%.

For now it's work in progress, but in the back of my mind I knew there was somewhere a request. So, that's the update for now.

Sounds great, I hope it turns out as expected. TY!
If I have any idea to improve trading I let you know, I was looking at some metric that can also be used to do short trading more safely since I can't find anything reliable that helps me for these bots. I was seeing the LC metric of "bearish sentiment", but it fluctuates with very different values between currency and currency, so I'll keep watching.

One thing that I forgot is the volatility meter. I modified it manually, but not in a very neat way, I just inverted the signs and something else. It is to give the option if the volatility is greater or less than such value, since the one that comes by default allows it to be only less than specific value and not greater. I also made modifications to allow a specific range of altrank and galaxyscore, although I stopped using this but it can also serve as an option and as I said maybe not in a very neat way that's why I didn't dare to upload it.

@amargedon
Copy link
Collaborator

There could be good news coming. I'm currently working on a Marketcollector script which I intend as replacement for CoinMarketCap, Altrank/GalaxyScore/LunarCrush, BotAssistExplorer scripts and merge it in one. Result will be a combined database with all the collected data from different sources.
A second script, the Botupdater, will use the data from that database to update the bots at 3Commas. The configuration of the Botupdater contains several options to filter the data. For example Altrank rank 1 - 10 and within CoinMarketCap rank 1 - 250 and price change over the last 24h between 0% and 25%.
For now it's work in progress, but in the back of my mind I knew there was somewhere a request. So, that's the update for now.

Sounds great, I hope it turns out as expected. TY! If I have any idea to improve trading I let you know, I was looking at some metric that can also be used to do short trading more safely since I can't find anything reliable that helps me for these bots. I was seeing the LC metric of "bearish sentiment", but it fluctuates with very different values between currency and currency, so I'll keep watching.

One thing that I forgot is the volatility meter. I modified it manually, but not in a very neat way, I just inverted the signs and something else. It is to give the option if the volatility is greater or less than such value, since the one that comes by default allows it to be only less than specific value and not greater. I also made modifications to allow a specific range of altrank and galaxyscore, although I stopped using this but it can also serve as an option and as I said maybe not in a very neat way that's why I didn't dare to upload it.

You mean the percent change as currently is in the coinmarketcap script? In the new Botupdater script you can specify a range, so for example percent 1h change between 1.0% and 5.0%. Or, if you want to take more risk between 9.0% and 100.0% ;)

The same for Altrank and Galaxyscore, you can select the range instead of only a threshold value.

@dangalv
Copy link
Contributor

dangalv commented Nov 11, 2022

There could be good news coming. I'm currently working on a Marketcollector script which I intend as replacement for CoinMarketCap, Altrank/GalaxyScore/LunarCrush, BotAssistExplorer scripts and merge it in one. Result will be a combined database with all the collected data from different sources.
A second script, the Botupdater, will use the data from that database to update the bots at 3Commas. The configuration of the Botupdater contains several options to filter the data. For example Altrank rank 1 - 10 and within CoinMarketCap rank 1 - 250 and price change over the last 24h between 0% and 25%.
For now it's work in progress, but in the back of my mind I knew there was somewhere a request. So, that's the update for now.

Sounds great, I hope it turns out as expected. TY! If I have any idea to improve trading I let you know, I was looking at some metric that can also be used to do short trading more safely since I can't find anything reliable that helps me for these bots. I was seeing the LC metric of "bearish sentiment", but it fluctuates with very different values between currency and currency, so I'll keep watching.
One thing that I forgot is the volatility meter. I modified it manually, but not in a very neat way, I just inverted the signs and something else. It is to give the option if the volatility is greater or less than such value, since the one that comes by default allows it to be only less than specific value and not greater. I also made modifications to allow a specific range of altrank and galaxyscore, although I stopped using this but it can also serve as an option and as I said maybe not in a very neat way that's why I didn't dare to upload it.

You mean the percent change as currently is in the coinmarketcap script? In the new Botupdater script you can specify a range, so for example percent 1h change between 1.0% and 5.0%. Or, if you want to take more risk between 9.0% and 100.0% ;)

The same for Altrank and Galaxyscore, you can select the range instead of only a threshold value.

E D I T:
Excuse me mate, I thought you had confirmed that such functions existed in the current scripts. But now I realize that you mean the new update of the scripts that you are about to do. Leave all that dribbling that I said aside 🤣🤣

And yes, it is exactly what you are saying, I mean volatility ranges or volatility minimums values so that the bot takes more moved coins


Another good but surely tricky strategy is to use a total bot shutdown signal when bitcoin might crash. For example, I use some script that turns the bot on or off, the problem is that this script would turn on the bot even when it received the shutdown signal from tradingview, making it impossible to have the "allowbotstopstart" command turned on.
So I don't know if the script could read if the bot received a power on command or not so that the bot could turn the bot on and off as it pleased as long as the start trigger signal from tradingview was received.

I think it is an interesting strategy to add a layer of security to our bot and safeguard against a possible strong fall like the one we have suffered this week.

Combining signals with tradingview without being harmed by the script would be the icing on the cake.

Excuse me for rambling lol

@dangalv
Copy link
Contributor

dangalv commented Nov 12, 2022

@amargedon Speaking of the last part of my post, I found a bug in the BAE script that doesn't allow to put neither "allowmaxdealchange" nor "allowbotstopstart" in "false" condition when I want to use a list of winners or volatility from 3c-tool since I had planned to turn off the bot only with a TV signal and not from the script. Perhaps it necessarily needs to be "true", for logical reasons and it is because of this gap that I find that it should allow reading if it received a tradingview signal to turn the bot on and off at will

@amargedon
Copy link
Collaborator

@amargedon Speaking of the last part of my post, I found a bug in the BAE script that doesn't allow to put neither "allowmaxdealchange" nor "allowbotstopstart" in "false" condition when I want to use a list of winners or volatility from 3c-tool since I had planned to turn off the bot only with a TV signal and not from the script. Perhaps it necessarily needs to be "true", for logical reasons and it is because of this gap that I find that it should allow reading if it received a tradingview signal to turn the bot on and off at will

Our scripts are not connected to TV, so not sure how we can 'know' the bot has been stopped by somebody else? There is no indication, unless we start to keep some administration.

As other good news; I've just merged the MarketCollector and BotUpdater scripts to this main repo! This means you will get access to better filtering options as request in the very first message of this discussion. Also Wiki has been updated to reflect on the changes and, hopefully, provide enough to get you all started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants