sthewissen / Mynt

An Azure Functions-based crypto currency trading bot; featuring 10 exchanges, 25 indicators, custom strategy support, backtester and more

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Provide a buying strategy

kitcoun opened this issue · comments

Anderson Strategy . Every time the price is down,2 times the Number of purchase loss

$18 buys 20 EOS and $17 buys 40 EOS.
-1=1820/20-17. 0.333=(1820+17*40)/60-17

-1 = 18 x 20 / 20-17。0.333 =(18 x 20 + 17 * 40)/ 60-17

I don't entirely follow how this strategy works yet. Also since the current bot only looks at candle data and has no context of previous trades at that point I'm not sure if it is possible in the current setup. I would like to hear more about it though. Perhaps you have a link to an explanation of the strategy? Most of the stuff I'm finding is related to the ProfitTrailer bot.

https://www.jianshu.com/p/ad4503310036

This strategy requires a lot of money

As long as there is no big floating drop, they are all profitable.

Not all historical transactions can be obtained from API?

So I'm curious about why you need to use the database

usd 1140

price Purchase quantity Existing quantity Surplus usd

18 10 10 960

17 20 30 620

16 60 90 0
sell 1 440=16*90
.....Continue the cycle

still have a question. Is this program submitted for sale after the purchase is completed?

Please forgive my laziness ^_ ^

Not all historical transactions can be obtained from API?
So I'm curious about why you need to use the database

Oh it's definitely possible. All the parts are there, just not together :)

Is this program submitted for sale after the purchase is completed?

This question I don't quite understand, sorry :(

Hope to support the Huobi exchange.

This should be easy.

Update the ExchangeSharp .

Add the Huobi request API code to the market summary.(They are different)

image

SqlServerData cannot use the native login, and the account password must be required.

There will be bugs using SqlServerData. Maybe the reason why I run locally?

Made separate issues for those last 2 points.