[EDIT]
0.6 is OUT! Get the release here
[/EDIT]

Gekko 0.6.0 is a major upgrade of the Gekko project, you can find some background information here.

The release of 0.6.0 is now finally ready for testing! Note that this release only includes:

- rewritten core & event logic.
- rewritten core plugins such as baseStrategy, performanceAnalyzer, paperTrader and (live) trader.
- Addition of the Gekko Broker library for live order execution.

LIMITATIONS:

- It does not support all exchanges previously supported by Gekko, see here for a list: https://github.com/askmike/gekko/blob/de....md#status


To test the 0.6 pre release:

- Update Gekko to the latest release.
- Make sure you run a new Node version (minimum is updated from 6.0 to 8.11.2)
- Besides the usual installation, please also install Gekko Broker dependencies, see here: https://github.com/askmike/gekko/blob/pr...pendencies

If you find any issue with the new release please open an issue on github (or open a new thread on the forum).

Let's say I have a stock trading at $100. If it gets to $120 I want to have a trailing stop limit order initiated with a trailing amount of $1 let's say.
I only want the trailing stop limit to take effect once the stock reaches $120.
How to create an strategy to automate this process?

Let's say I have a stock trading at $100. If it gets to $120 I want to have a trailing stop limit order initiated with a trailing amount of $1 let's say.
I only want the trailing stop limit to take effect once the stock reaches $120.
How to create an strategy to automate this process?

I had run --import to load initial data of over 5000 mintues using CLI.

I found the postgresql database loaded with some records successfully (with 6718 records).

Live paper trader was successfully run with slow moving average indicator loaded with 1000 x 5 min candles.

I did make sure config.candleWriter = { enabled: true }

I supposed new candle data will be inserted to database for all the subsequent ticker update. However, I found the number of records did not increased.

After a day of running, I restarted gekko live trader using the same config file. Datasets were not stitched with following log...

---- DEBUG LOG ----
The trading method requests 5000 minutes of historic data. Checking availablity..
Available local data:
from: 5000 minutes ago
to: 1176 minutes ago
Usable local data available, trying to match with exchange data..
Preventing Gekko from requesting 1191 minutes of history.
Fetching exchange data since 240 minutes ago
Available exchange data:
from: 240 minutes ago
to: 180 minutes ago
Unable to stitch datasets.
Not seeding locally available data to the trading method.
The exchange does not return enough data. 0 minutes are still missing.
---- END OF LOG ----

It seems like that 1176 minutes running of live paper trader did not save candle data into database but only in memory. Therefore that period of data was lost after gekko restarted.

I also don't understand why gekko fetch exchange data from 240 min to 180 min? I have seen this happened many times before.

Since it doesn't make sense to wait for a 5000 minutes warmup, my workaround is to run --import using CLI again to load the data after every gekko restart.

Does anyone know if this is a constraint of did I miss anything in the configuration for gekko to save live data into the database?

Thanks for advice.

for the CLI-gekko (terminal gekko) we must set up the sample-config.js.

our strategie has its "my_strategie.toml" file, but in the config IT MUST BE AS JSON-style CODE.

if you do not use the backtest Machine from xFFFFF,
you can simply use an online tool that makes the conversation for you.
this is very easy and never makes an error.!!!

go to this page:
toml-json convertor

here simply copie paste your .toml code

Hi all,

I know Gemini isn't a popular exchange (at least not talked about much in this forum). I'm trying to set it because I want to have a "set it and forget it" place to let Gekko do its thing and I will just check once a month on the performance of the strat.

So I just started live trading on Gekko CLI on Gemini the other day and I'm getting this error message. Anyone else experience this error message before? Any fixes? I will share my solution if I find it. Thanks.

hi

2018-06-17 04:42:26 (INFO): Trader
2018-06-17 04:42:26 (INFO): Follows the advice and create real orders.
2018-06-17 04:42:26 (DEBUG): portfolioManager : getting balance & fee from binance
2018-06-17 04:42:26 (INFO):

2018-06-17 04:42:27 (DEBUG): [binance.js] entering "getTicker" callback after api call, err: null data: 357 symbols
2018-06-17 04:42:28 (DEBUG): [binance.js] entering "setBalance" callback after api call, err: null data: {"makerCommission":10,"takerCommission":10,"buyerCommission":0,"sellerCommission":0,"canTrade":true,"canWithdraw":true,"canDeposit":true,"updateTime":1529199170532,"balances"

1-Why does this error come in

[b]2-canWithdraw:true  (why true)?[/b]



[b]gekko v0.5.14[/b]

Hi all, 

I've downloaded two datasets for Binance, BTC:ALL and ETH:ALL. They both have the same name, but it seems that gekko only recognised the one named exactly "binance_0.1.db". 

Is there something specific I need to do to allow the use of both datasets at the same time?

Thanks!

Hello there,

I wonder about these things. Maybe it is technically not feasable at this point .. I don't know.

1. History strorage convention
Right now I have separate *db-files (i.e. poloniex_0.1.db). The importer and the mimic to join segments is working for me, but sometimes very slow and unstable. I saw a thread offering history data, that will speed things up and not everyone would need to do the same time consuming thing.

Wouldn't it be nice, if the naming convention would identify a db file by trading plattform (exchange), currency and asset?
poloniex_USDT-BTC.db for example. This is only a question up to discussion.


2. Something like "Hot-Start"
History data is mandatory for technical indicators, no way around this.
But, is it already possible, to start (Paper- or Live-Trading) with any given size of history, which is not aggregated continuesly from reading new coming data, but by retrieving all the needed history size from the past before the start of the strategy? So basically an importing - process.
When all missing candles were collected/imported to join a complete history of the demanded size to the actual point in time, the strategy would then be allowed to make trades. 

Regards,
Rainer