Hi all,

using tradebot in a market BTC-USDT on Binance, Gekko worked well if I have BTC funds and 0 USDT (it starts to sell, than buy, etc.)
If I start with 100 USDT (for example) and 0 BTC it should buy BTC as first step but it won't buy anything.
Do Gekko only works if it starts with BTC funds? (So i should manually buy BTC and then start gekko??)

Thank you

Edit: I should to wait due to stategy... sorry!

Attached Files

  gekkolog.txt (Size: 13.63 KB / Downloads: 5)

Instead of using APIs like fetch_ohlcv from exchange interfaces?

Synthesized candle works fine in realtime trader, speed is OK there, but it becomes an issue when backtesting with imported history data. I tried to import half a year's data from bitfinex and it took a whole night to complete. I guess it'll be slower if the rate limit is low for an exchange.

Could anyone explain what advantage it has to use synthesized candle from trades?

I am building new start using some talib indicators . but i couldn't find the complete parameters for RSI .

I want to use upper band at 80 and lower band at 20 with 5 length. but what i found in talib parameters is only optInTimePeriod

i tried adding 2  optInTimePeriod but it didn't work . also how can i add different length. how can i calculate rsi values using upper and lower band with my length ?

I noticed that the bot gets a lot of time on syncing private data. It's normal?

Today the bot runs in docker with mongodb database.

Attached Files

  print-log.png (Size: 25.72 KB / Downloads: 1)

They ruin my strategy. Is there a way to just place normal limit orders at the exact price the strategy calls for without trying to be on top of order book and cancel when limit orders don’t fill? In fact, is there a way to issue your own limit orders at specified price as opposed to just waiting for candle to close?

All,

I forked Gekko and modded it from a trading bot into a dollar cost averaging bot. 

https://github.com/crypto49er/gekko-DCA

I also made a video about it if you want to know which files I had to modify. Honestly, it was 3 files (including the config file) and adding a DCA strategy. But if you want to explore modifying your strategies with the ideas I describe below, it's worth a watch.

https://youtu.be/h2MEVp9lBqQ

I know dollar cost average might not be something that's interesting to members of this forum. But you can expand upon this in multiple ways (you still need to use Gekko to do the following, not Gekko-DCA):
-Set a limit on how much your bot trades (ex: you have $200 but only want the bot to trade $100)
-Layer your buys and sells (ex: Use 50% of your portfolio to buy at price A, and 50% to buy at price B, Sell 25% when the price hits your 1st target, sell the remaining 75% when it hits your 2nd target)
-Run multiple bots using one exchange API keys by locking each bot to a specific amount (add code in your strat to adjust the amount based on profit/losses so the bot always have a full balance to work with)

Those are just some of the ideas that I can think of off the top of my head, I'm sure there are plenty others. Love to hear what you guys think.

hi,

everything works fine for me so far 

but i have just a question because my gekko doesnt use the whole amount of currency or asset.

for example i have 1000usd and gekko buys xrp but not for the whole 1000usd, so there is always 35-40usd rest.
or when selling back from xrp to usd gekko doesn't sell all xrp, so like about 90 xrp will stay.

is this maybe misconfiguration by me or it is like some security margin so gekko can be sure the amount is big enough so the order will not be canceled or something? 

thanks

Hello guys.

I am trying to adapt the native traling stop loss into some open source neural net based strategies, but the same problem described at https://steemit.com/gekko/@crypto49er/ge...esn-t-work happens. I mean, when the stop loss is triggered, the conditions to buy are satisfied, and the strategy advice to buy again.

In order to avoid that, I am trying to figure out how to put an extra condition, using timeout or any other kind of logic, in order to avoid the strategy to buy again.

The problem is that I am not able to find how to register my code to be notified when the trigger loss got triggered.

Can someone please provide me some sample code for this?

The strategy I am trying to adapt right now is this one https://github.com/zschro/gekko-neuralnet

Currently, my go long advice is defined as follows:




      if ('buy' !== this.prevAction && signal === false  && meanAlpha > this.settings.threshold_buy )
      {

        log.debug("");
        log.debug("**** Buy - Predicted variation: ",meanAlpha);
        if (!this.settings.stoploss_enabled) {
          return this.advice('long');
        } else {
          return this.advice({
            direction: 'long',
            trigger: {
              type: 'trailingStop',
              trailPercentage: this.settings.stoploss_trailPercentage
            }
          });
        }
      }

Thank you

I have been creating videos on the Gekko Trading Bot since the beginning of this year. I covered everything from installing it on Windows, Mac, Linux, Docker, and backtesting, running various plugins like Telegram and Twitter. I'm sure some of you have watched some of my videos. I figured I probably should have a playlist of all the videos here so you can reference them at your leisure. 

https://www.youtube.com/playlist?list=PL...lPyy9Qa3aY

In addition, I get asked what Gekko topics I should cover next. I don't always respond to PMs (sorry, my inbox is inundated) so it might be better to leave a comment here and I will let you know if that is something that I will cover in a future video.

This is more a share of the method I'm using for candle batching than of the strategy, but as Tommies RSI strat is rather excellent and so widely known it seemed a good demonstrator.

This strategy runs on 1 minute candles and batches them in the update function. 
The less obvious bit is that instead of keeping one copy of each indicator, it keeps an array of each indicator as long as the candle size for that indicator. Each new minute candle, the next indicator in the array is updated and read. 
The upshot of this is that each minute there is an up to date result of the longer term indicator, allowing far more accurate entry and exit points checked every minute, instead of every 5, 10, 30, 60 etc minutes. This also makes a strategy less sensitive to start time - although it still makes more of a difference than I'd expect!

The timeframe for each indicator is also independent so different candle sizes can be used for bear and bull market indicators - however the indicator candle size and indicator period do become a little interchangeable as they're both changing the amount of time that the indicator is watching the market over.

Other benefits of running at 1 minute is that any stop losses or take profits that you might add can be checked that much more frequently, so are that much more useful at catching quick market movements.

Downsides:
> As with any strategy running on very short timeframes trying to tune it with GA style optimisers can results in huge profits with hundreds of trades per day that will perform absolutely miserably if ran live as the orders simply can't be filled. Tuning requires a little more understanding of what the strategy is doing and inputting sensible parameters.
> Gekko currently has a limitation on the number of candles it can pre-seed a strategy with of around 4000. When running at 1 minute, this is 2.7 days of history so you need to shrink those long SMAs


So - here's a quick example backtest from 6 months history on an alt, with Tommie's original strategy first, candlebatched second. Both have exactly the same parameters, as in the TOML file below.

Original:


Candlebatched:

Paper trading settings are at their defaults. These two are purely intended as a relative comparison. I obviously can't promise any results but hope it shows that there is potential!


I'm sharing this under the same CC-BY-SA 4.0 license that Tommie shared his under - I learnt a lot from that bit of code, so hopefully giving a little back.
Run the strategy in 1 minute candles in gekko and specify the candle sizes you want each indicator to run at with the timeframe parameter in the TOML.

TOML: Github