<![CDATA[Gekko Forum - Feature Requests]]> https://forum.gekko.wizb.it/ Wed, 29 Apr 2026 20:13:05 +0000 MyBB <![CDATA[Importing csv files to Gekko]]> https://forum.gekko.wizb.it/thread-58034.html Sun, 10 Nov 2019 16:31:28 +0000 https://forum.gekko.wizb.it/thread-58034.html
I wanted to ask if it is possible to feed historical data in csv format?

Thank you guys.]]>
I wanted to ask if it is possible to feed historical data in csv format?

Thank you guys.]]> <![CDATA[Can I use more than one stradegy in one Gekko?]]> https://forum.gekko.wizb.it/thread-58015.html Sun, 29 Sep 2019 02:03:09 +0000 https://forum.gekko.wizb.it/thread-58015.html <![CDATA[Gekko's plans for new features from Green Gekko mod]]> https://forum.gekko.wizb.it/thread-57914.html Wed, 08 May 2019 11:15:12 +0000 https://forum.gekko.wizb.it/thread-57914.html
I guess this question is more or less for Askmike and mark-sch..

Is there a plan to integrate some of the features added by mark-sch's mod to the native gekko? There are some really nice features he has added, but for example, if I want to use the green gekko now, I would need to migrate all of the existing sqllite db file to postgresql.. I would also need to modify many of my already existing strategies to take advantage of the new features below..

That's all fine at the moment, but from a maintainability perspective, when a new release of native gekko comes out, I don't want to be going back and forth between the two builds to figure out which one I'd like to use today..

So my question is, are any of the below features planned to be integrated in the next release of gekko?

  • Extended trading-strategy possibilities:
    • Heikin-Ashi candles core support, e.g. use candle.ha.close instead of candle.close inside your strategy
    • set trading amount while giving advice (e.g. buy with 50% of my portfolio)
    • allow market making or market taking order execution options
    • speedup in the internal event pipeline. Force undelayed advice execution by setting config.tradingAdvisor.fastAdviceEmit: true
    • receive "onCandle" events to allow developers building multi-timeframe strategies.
    • receive "onAdvice" events for plugin-to-plugin communication, e.g. notify the strategy with telegram initiated advices, or create containers with multiple strategies.
  • Core enhancements to write async trading strategies with new async tulip and talib wrappers. The new Green Gekko core is able to wait for async strategies without running into race conditions and allows developers to write multi-timeframe and multi-market strategies.
]]>
I guess this question is more or less for Askmike and mark-sch..

Is there a plan to integrate some of the features added by mark-sch's mod to the native gekko? There are some really nice features he has added, but for example, if I want to use the green gekko now, I would need to migrate all of the existing sqllite db file to postgresql.. I would also need to modify many of my already existing strategies to take advantage of the new features below..

That's all fine at the moment, but from a maintainability perspective, when a new release of native gekko comes out, I don't want to be going back and forth between the two builds to figure out which one I'd like to use today..

So my question is, are any of the below features planned to be integrated in the next release of gekko?

  • Extended trading-strategy possibilities:
    • Heikin-Ashi candles core support, e.g. use candle.ha.close instead of candle.close inside your strategy
    • set trading amount while giving advice (e.g. buy with 50% of my portfolio)
    • allow market making or market taking order execution options
    • speedup in the internal event pipeline. Force undelayed advice execution by setting config.tradingAdvisor.fastAdviceEmit: true
    • receive "onCandle" events to allow developers building multi-timeframe strategies.
    • receive "onAdvice" events for plugin-to-plugin communication, e.g. notify the strategy with telegram initiated advices, or create containers with multiple strategies.
  • Core enhancements to write async trading strategies with new async tulip and talib wrappers. The new Green Gekko core is able to wait for async strategies without running into race conditions and allows developers to write multi-timeframe and multi-market strategies.
]]> <![CDATA[Kraken WebSockets Public API Version 0.1.0]]> https://forum.gekko.wizb.it/thread-57837.html Wed, 23 Jan 2019 19:22:30 +0000 https://forum.gekko.wizb.it/thread-57837.html
I was wondering iif this could be interesting for Gekko, like for High-Frequency trading or so?

https://www.kraken.com/en-us/help/websocket-api

++]]>
I was wondering iif this could be interesting for Gekko, like for High-Frequency trading or so?

https://www.kraken.com/en-us/help/websocket-api

++]]> <![CDATA[A way to withdraw to and from hardware wallet]]> https://forum.gekko.wizb.it/thread-57799.html Thu, 20 Dec 2018 01:33:21 +0000 https://forum.gekko.wizb.it/thread-57799.html
Thank you Mike for this excellent program.]]>
Thank you Mike for this excellent program.]]> <![CDATA[Support for CoinSpot exchange]]> https://forum.gekko.wizb.it/thread-57767.html Thu, 15 Nov 2018 07:54:18 +0000 https://forum.gekko.wizb.it/thread-57767.html I need to request for my exchange of choice, CoinSpot, to be supported.

Thanks,
Lucas]]> I need to request for my exchange of choice, CoinSpot, to be supported.

Thanks,
Lucas]]> <![CDATA[Backtesting result no data display Please help]]> https://forum.gekko.wizb.it/thread-57711.html Wed, 10 Oct 2018 01:49:33 +0000 https://forum.gekko.wizb.it/thread-57711.html
[Image: Captura%2Bde%2Bpantalla_2018-10-09_11-42-30.png]
[Image: Captura%2Bde%2Bpantalla_2018-10-09_11-42-58.png]

.png   Captura de pantalla_2018-10-09_11-42-30.png (Size: 65.11 KB / Downloads: 7)

.png   Captura de pantalla_2018-10-09_11-42-58.png (Size: 53.49 KB / Downloads: 7) ]]>
[Image: Captura%2Bde%2Bpantalla_2018-10-09_11-42-30.png]
[Image: Captura%2Bde%2Bpantalla_2018-10-09_11-42-58.png]

.png   Captura de pantalla_2018-10-09_11-42-30.png (Size: 65.11 KB / Downloads: 7)

.png   Captura de pantalla_2018-10-09_11-42-58.png (Size: 53.49 KB / Downloads: 7) ]]> <![CDATA[Running more than one tradebot per exchange.]]> https://forum.gekko.wizb.it/thread-57695.html Sat, 29 Sep 2018 19:04:41 +0000 https://forum.gekko.wizb.it/thread-57695.html
Why we not able to run more than 1 tradebot per exchange? I believe there should be a technical obstacle in this matter.. Could someone please explain the obstacle, lets try to implement this Smile]]>
Why we not able to run more than 1 tradebot per exchange? I believe there should be a technical obstacle in this matter.. Could someone please explain the obstacle, lets try to implement this Smile]]> <![CDATA[add indodax exchange]]> https://forum.gekko.wizb.it/thread-57641.html Wed, 12 Sep 2018 10:55:34 +0000 https://forum.gekko.wizb.it/thread-57641.html thank you]]> thank you]]> <![CDATA[Trade multiple pairs with common currency]]> https://forum.gekko.wizb.it/thread-57624.html Thu, 06 Sep 2018 20:28:47 +0000 https://forum.gekko.wizb.it/thread-57624.html Would it be possible to trade simultaneously more than one pairs that share common currency for example USDT/BTC and USDT/ETH on the same exchange ?

The documentation states "If your strategy signal a long advice Gekko will try to buy as much "asset" as it can get with all your "currency"" so i guess if a 'long' advice is generated for BTC all USDT will be used for this buy and no more will be left to buy ETH.

I guess one workaround is to traid the second pair on a defferent exchange right?]]> Would it be possible to trade simultaneously more than one pairs that share common currency for example USDT/BTC and USDT/ETH on the same exchange ?

The documentation states "If your strategy signal a long advice Gekko will try to buy as much "asset" as it can get with all your "currency"" so i guess if a 'long' advice is generated for BTC all USDT will be used for this buy and no more will be left to buy ETH.

I guess one workaround is to traid the second pair on a defferent exchange right?]]> <![CDATA[Automate strategies]]> https://forum.gekko.wizb.it/thread-57505.html Sun, 05 Aug 2018 08:12:32 +0000 https://forum.gekko.wizb.it/thread-57505.html
I've got a question about the backtest api. 
I was trying to post to the backtest api, using Postman, but I got a lot of Internal Server Errors.

I want to try all methods automatically, with different settings, by using the backtest api. 

Is there already something like this, if not, I would like to request this as a feature!

Kind regards


[EDIT: I think this post thread belongs to the Technical Support, not feature requests.]]]>
I've got a question about the backtest api. 
I was trying to post to the backtest api, using Postman, but I got a lot of Internal Server Errors.

I want to try all methods automatically, with different settings, by using the backtest api. 

Is there already something like this, if not, I would like to request this as a feature!

Kind regards


[EDIT: I think this post thread belongs to the Technical Support, not feature requests.]]]> <![CDATA[Backtest multiple date ranges with GekkoGA]]> https://forum.gekko.wizb.it/thread-57173.html Wed, 16 May 2018 20:32:13 +0000 https://forum.gekko.wizb.it/thread-57173.html
I'd like to be able to have gekkoga do multiple date-ranges like it does multiple parameters for other parts of the config; i.e. I imagine it would be done like this (and maybe it already can do this and I'm just not doing it right? let me know):
Instead of this:
Code:
daterange: {
  from: '2018-02-13 05:54:00',
  to: ' 2018-02-25 04:12:00'
  },
Do this:

Code:
daterange: {
  from: ('2018-02-13 05:54:00', '2018-02-13 05:56:00', '2018-02-13 05:58:00', '2018-02-13 06:01'),
  to: ' 2018-02-25 04:12:00'
  },

It might look pointless, but I think sometimes the difference between a bot started at 5:04pm and a bot started at 5:08pm can be huge, and that by backtesting like this, you could determine where the "starting points" are that work well for your strategy for a given data set. It might be that your strategy always does better when started right on the hour, or 11 minutes after the hour, or 16 minutes after the hour, etc. -- I think that it's totally possible that "lining it up" by checking different start times could make a huge difference in performance.

What do you guys think?

Attached photo is two bots with identical config, 11 minute candles, one performing better than the other, seems to have caught the right cycle, while the other one missed the timing, and so took bigger losses. One started just a few minutes before the other.

.png   Screenshot_2018-05-16_16-30-15.png (Size: 292.93 KB / Downloads: 11) ]]>
I'd like to be able to have gekkoga do multiple date-ranges like it does multiple parameters for other parts of the config; i.e. I imagine it would be done like this (and maybe it already can do this and I'm just not doing it right? let me know):
Instead of this:
Code:
daterange: {
  from: '2018-02-13 05:54:00',
  to: ' 2018-02-25 04:12:00'
  },
Do this:

Code:
daterange: {
  from: ('2018-02-13 05:54:00', '2018-02-13 05:56:00', '2018-02-13 05:58:00', '2018-02-13 06:01'),
  to: ' 2018-02-25 04:12:00'
  },

It might look pointless, but I think sometimes the difference between a bot started at 5:04pm and a bot started at 5:08pm can be huge, and that by backtesting like this, you could determine where the "starting points" are that work well for your strategy for a given data set. It might be that your strategy always does better when started right on the hour, or 11 minutes after the hour, or 16 minutes after the hour, etc. -- I think that it's totally possible that "lining it up" by checking different start times could make a huge difference in performance.

What do you guys think?

Attached photo is two bots with identical config, 11 minute candles, one performing better than the other, seems to have caught the right cycle, while the other one missed the timing, and so took bigger losses. One started just a few minutes before the other.

.png   Screenshot_2018-05-16_16-30-15.png (Size: 292.93 KB / Downloads: 11) ]]> <![CDATA[Gekko Buy/sell starting position]]> https://forum.gekko.wizb.it/thread-57171.html Wed, 16 May 2018 13:27:49 +0000 https://forum.gekko.wizb.it/thread-57171.html
One feature i think is needed is the ability for gekko to decide if long or short is the 1st trade to use, when you fire up gekko, currently it chooses to short each time you fire it up even when there is nothing to short.

Having gekko check if the balance is in favor of the asset or currency on start up then adjust the 1st trade would be ideal.

Thanks]]>
One feature i think is needed is the ability for gekko to decide if long or short is the 1st trade to use, when you fire up gekko, currently it chooses to short each time you fire it up even when there is nothing to short.

Having gekko check if the balance is in favor of the asset or currency on start up then adjust the 1st trade would be ideal.

Thanks]]> <![CDATA[Remote manual override]]> https://forum.gekko.wizb.it/thread-57167.html Tue, 15 May 2018 18:46:56 +0000 https://forum.gekko.wizb.it/thread-57167.html
1. Send buy advice to my trader
2. Send sell advice to my trader
3. Pause my trader, but keep watching the market
4. Restart my trader from a paused state

With my (lack of) skills, I'd probably have the trader watching an email address like complexpassword@gmail.com for instructions, but I'm sure there's a more crypto-savvy way of implementing this.

Trading on based on charts is better than guessing, but sometimes you see a shift in the fundamentals (block reward halving, for example) and want to manually take action or prevent buying into a bull trap, etc.

I'd put up a bounty, but I have a new baby on the way in 4 weeks...   Big Grin]]>
1. Send buy advice to my trader
2. Send sell advice to my trader
3. Pause my trader, but keep watching the market
4. Restart my trader from a paused state

With my (lack of) skills, I'd probably have the trader watching an email address like complexpassword@gmail.com for instructions, but I'm sure there's a more crypto-savvy way of implementing this.

Trading on based on charts is better than guessing, but sometimes you see a shift in the fundamentals (block reward halving, for example) and want to manually take action or prevent buying into a bull trap, etc.

I'd put up a bounty, but I have a new baby on the way in 4 weeks...   Big Grin]]> <![CDATA[ask - last price balance]]> https://forum.gekko.wizb.it/thread-57133.html Wed, 09 May 2018 14:25:09 +0000 https://forum.gekko.wizb.it/thread-57133.html
Quote:Understand ask_last_balance

ask_last_balance sets the bidding price. Value 0.0 will use ask price, 1.0 will use the last price and values between those interpolate between ask and last price. Using ask price will guarantee quick success in bid, but bot will also end up paying more then would probably have been necessary.


I would be using this in gekko.]]>
Quote:Understand ask_last_balance

ask_last_balance sets the bidding price. Value 0.0 will use ask price, 1.0 will use the last price and values between those interpolate between ask and last price. Using ask price will guarantee quick success in bid, but bot will also end up paying more then would probably have been necessary.


I would be using this in gekko.]]> <![CDATA[Balance Display]]> https://forum.gekko.wizb.it/thread-56896.html Mon, 23 Apr 2018 22:44:33 +0000 https://forum.gekko.wizb.it/thread-56896.html
One feature i would like to see is a display of current balance of an assets on the exchange or a csv output of trades for people to manipulate, Gryphon created one which worked a treat till Trade class was introduced. Something similar or integration of this would be perfect for those who use multiple exchanges and find logging in a ball ache to check balances.]]>
One feature i would like to see is a display of current balance of an assets on the exchange or a csv output of trades for people to manipulate, Gryphon created one which worked a treat till Trade class was introduced. Something similar or integration of this would be perfect for those who use multiple exchanges and find logging in a ball ache to check balances.]]> <![CDATA[Integrate CCXT lib to Gekko?]]> https://forum.gekko.wizb.it/thread-56864.html Sat, 21 Apr 2018 22:40:43 +0000 https://forum.gekko.wizb.it/thread-56864.html
Are there any plans on integrating ccxt lib to gekko?

https://github.com/ccxt/ccxt

It seems it already supports more complex order types and advanced parameterization (like order amount etc.), and communication with many exchanges.

See here for details.

Thanks.]]>
Are there any plans on integrating ccxt lib to gekko?

https://github.com/ccxt/ccxt

It seems it already supports more complex order types and advanced parameterization (like order amount etc.), and communication with many exchanges.

See here for details.

Thanks.]]> <![CDATA[Gekko's most wanted features]]> https://forum.gekko.wizb.it/thread-56680.html Sun, 08 Apr 2018 11:30:52 +0000 https://forum.gekko.wizb.it/thread-56680.html
If your favorite is not in the list, please name it in the comments below.]]>
If your favorite is not in the list, please name it in the comments below.]]> <![CDATA[Improved profit and loss reporting]]> https://forum.gekko.wizb.it/thread-56679.html Sun, 08 Apr 2018 09:02:38 +0000 https://forum.gekko.wizb.it/thread-56679.html
This thread is to continue the discussion of the suggested proposal here.

As an example of this implementation, a stand alone cli-application is available here.

What  do we want PnL reporting in Gekko to look like in the future? Please share your views here, what is the best way forward?]]>
This thread is to continue the discussion of the suggested proposal here.

As an example of this implementation, a stand alone cli-application is available here.

What  do we want PnL reporting in Gekko to look like in the future? Please share your views here, what is the best way forward?]]> <![CDATA[Ability to long/short multiple shares]]> https://forum.gekko.wizb.it/thread-56660.html Wed, 04 Apr 2018 18:15:34 +0000 https://forum.gekko.wizb.it/thread-56660.html