Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 6,541
» Latest member: safepillcartS
» Forum threads: 1,047
» Forum posts: 4,678

Full Statistics

Online Users
There are currently 58 online users.
» 0 Member(s) | 58 Guest(s)

Latest Threads
Forum: Custom Systems
Last Post: safepillcartS
5 hours ago
» Replies: 0
» Views: 4
Forum: Other exchanges
Last Post: samharries
9 hours ago
» Replies: 40
» Views: 2,337
deals for safari
Forum: Technical Discussion
Last Post: veganallsorts
10 hours ago
» Replies: 3
» Views: 182
traveling to Lanzarote
Forum: Technical Discussion
Last Post: lucifar
Yesterday, 12:55 PM
» Replies: 3
» Views: 192
gen lib rus ec
Forum: Technical Discussion
Last Post: hussain16
01-23-2021, 08:36 AM
» Replies: 3
» Views: 418
Forum: General Discussion
Last Post: noelqualter
01-23-2021, 08:05 AM
» Replies: 3
» Views: 241
Forum: Technical Discussion
Last Post: aedanhall
01-23-2021, 06:46 AM
» Replies: 0
» Views: 11
Domestic tours in pakista...
Forum: Technical Support
Last Post: domestic tours in Pakistan
01-22-2021, 08:23 PM
» Replies: 0
» Views: 31
pirate bay proxy
Forum: Technical Discussion
Last Post: aedanhall
01-22-2021, 09:41 AM
» Replies: 0
» Views: 24
How do I find a good cust...
Forum: Custom Systems
Last Post: Naty Grace
01-21-2021, 04:44 PM
» Replies: 1
» Views: 33

  ??? Strategy for ANY market / ANY pair ??? avg 93% Monthly
Posted by: briancrypto - 02-03-2018, 08:47 PM - Forum: General Discussion - Replies (1)

Please pardon my ignorance as a Newbie.... (I will learn and get better!!)

I have imported the past month's data from Poloniex and Gdax... for pairs USD/BTC, BTC/ETH, USDT/BTC, USDT/XRP ... using just the default settings for strategies with time intervals of 1m, 5m, 15m, 30m, 1h, 1D... with 10 as the Warmup.. I can't say I am finding a single strategy that is profiting at least a avg of 93% monthly... In actuality it would seem that every strategy is producing a negative return monthly which I just can't believe would be the case with all the hard work and devotion that has been put into this product!!

What am I doing wrong?

I only ask because I see others posting they are making at least 93% in profit monthly using trading bots no matter what condition the market is in (bullish, bearish or sideways).

  [BOUNTY] Adaptive ATR-ADX Trend
Posted by: briancrypto - 02-03-2018, 02:36 PM - Forum: Feature Requests - Replies (5)

I know nothing about coding but what I do know is that I have been manually using the following script from tradingview and killing it everyday. Now if gekko could be coded to run this script I could get away from sitting infornt of a computer. lol

The script I have been using is located here: https://www.tradingview.com/script/H48ye...-Trend-V2/

Here is the code:

// Constructs the trailing ATR stop above or below the price, and switches
// directions when the source price breaks the ATR stop. Uses the Average
// Directional Index (ADX) to switch between ATR multipliers. The higher
// multiplier is used when the ADX is rising, and the lower ATR multiplier
// is used with the ADX is falling. This ADX criteria further widens the gap
// between the source price and the trailing ATR stop when the price is trending,
// and lessens the gap between the ATR and the price when then price is not
// trending.
// The ATR-ADX stop is effectively a double adapative stop that trails the price,
// by both adapting to the true range of the price, and the average directional
// change. When the stop is below the price (long trade) the value never decreases
// until the price intersects the stop, and it reverses to being above the price
// (short trade). When the stop is above the price it will never increase until
// it is intersected by the price. As the true range and ADX change, the stop
// will move more quickly or more slowly.
// Version 2 adds four additional utilities.
// First, if the 'Above Threshold' box is checked,the falling (smaller) multiplier
// will be used regardless once the ADX rises above a certain threshold (default > 30).
// The ATR will effectively rise faster once the price enters 'very trendy' mode.
// Typically, ADX > 20/25 is used in classic ADX trading (which I have found
// unprofitable through backtesting). The idea behind this extra multiplier criteria
// is that once the price starts trending 'very' well, a top is most likely near,
// and when that top comes the price will quickly rebound. Experienced traders know
// exactly what I am describing. Play around with an ADX/DI indicator using this
// stop system in tandem and it will be found that many successful trades are entered
// when the market is not trending (i.e. < ADX < 25), and exited once/if the price
// enters 'very trendy' mode above 30 and the ATR changes (stopped out).
// Second, heiken-ashi bars can be introduced to the ATR stop system. This is the same
// thing as just switching the chart to Heiken Ashi mode, but without having to change
// the plotting type. I find this useful, so that things like pivot lines can be
// preserved to their correct calculations, while the benefit of heiken ashi bars can
// still be enjoyed.
// Third, Different source prices can be used. I have found that HLC3 is best because
// it keeps the price from being stopped out in very key areas, set as the default.
// Fourth, alert conditions are introduced so that the trader can be warned when the
// ATR-ADX changes. These can be used by right clicking the strategy and clicking
// "Add Alert...". Reference the bottom of the script for the names of the alert
// conditions.
// See also: http://www.fxtsp.com/1287-doubly-adaptive-profit-average-true-range-objectives/

study(title = "Adaptive ATR-ADX Trend V2", shorttitle = "Adaptive ATR V2", overlay = true)

src = input(title = "Source", type = source, defval = hlc3)
atrLen = input(title = "ATR", type = integer, defval = 21, minval = 1, maxval = 100)
m1 = input(title = "ATR Multiplier - ADX Rising", type = float, defval = 3.5, minval = 1, step = 0.1, maxval = 100)
m2 = input(title = "ATR Multiplier - ADX Falling", type = float, defval = 1.75, minval = 1, step = 0.1, maxval = 100)

adxLen = input(title = "ADX", type = integer, defval = 14, minval = 1, maxval = 100)
adxThresh = input(title = "ADX Threshold", type = integer, defval = 30, minval = 1)
aboveThresh = input(true, title = "ADX Above Threshold uses ATR Falling Multiplier Even if Rising?")
useHeiken = input(false, title = "Use Heiken-Ashi Bars (Source will be ohlc4)")
// DI-Pos, DI-Neg, ADX

hR = change(high)
lR = -change(low)

dmPos = hR > lR ? max(hR, 0) : 0
dmNeg = lR > hR ? max(lR, 0) : 0

sTR = nz(sTR[1]) - nz(sTR[1]) / adxLen + tr
sDMPos = nz(sDMPos[1]) - nz(sDMPos[1]) / adxLen + dmPos
sDMNeg = nz(sDMNeg[1]) - nz(sDMNeg[1]) / adxLen + dmNeg

DIP = sDMPos / sTR * 100
DIN = sDMNeg / sTR * 100
DX = abs(DIP - DIN) / (DIP + DIN) * 100
adx = sma(DX, adxLen)

// Heiken-Ashi

xClose = ohlc4
xOpen = (nz(xOpen[1]) + nz(close[1])) / 2
xHigh = max(high, max(xOpen, xClose))
xLow = min(low, min(xOpen, xClose))

// Trailing ATR

v1 = abs(xHigh - xClose[1])
v2 = abs(xLow - xClose[1])
v3 = xHigh - xLow

trueRange = max(v1, max(v2, v3))
atr = useHeiken ? rma(trueRange, atrLen) : atr(atrLen)

m = rising(adx, 1) and (adx < adxThresh or not aboveThresh) ? m1 : falling(adx, 1) or (adx > adxThresh and aboveThresh) ? m2 : nz(m[1])
mUp = DIP >= DIN ? m : m2
mDn = DIN >= DIP ? m : m2

src_ = useHeiken ? xClose : src
c = useHeiken ? xClose : close
t = useHeiken ? (xHigh + xLow) / 2 : hl2

up = t - mUp * atr
dn = t + mDn * atr

TUp = max(src_[1], c[1]) > TUp[1] ? max(up, TUp[1]) : up
TDown = min(src_[1], c[1]) < TDown[1] ? min(dn, TDown[1]) : dn

trend = min(src_, min(c, close)) > TDown[1] ? 1 : max(src_, max(c, close)) < TUp[1]? -1 : nz(trend[1], 1)
stop = trend == 1 ? TUp : TDown
trendChange = change(trend)

// Plot

lineColor = not(trendChange) ? trend > 0 ? #00FF00DD : #FF0000DD : #00000000
shapeColor = trendChange ? trendChange > 0 ? #00FF00F8 : #FF0000F8 : #00000000

plot(stop, color = lineColor, style = line, linewidth = 1, title = "ATR Trend")
plotshape(trendChange ? stop : na, style = shape.circle, size = size.tiny, location = location.absolute, color = shapeColor, title = "Change")

alertcondition(trendChange > 0, title = "ATR-ADX Change Up", message = "ATR-ADX Change Up")
alertcondition(trendChange < 0, title = "ATR-ADX Change Down", message = "ATR-ADX Change Down")

// end
Bounty offered.. .003 BTC

  Readme post for Guides
Posted by: askmike - 02-03-2018, 05:29 AM - Forum: Guides - No Replies

Automated trading is a very broad topic, on top of that comes running automated trading systems (like Gekko) on a ton of different systems (Windows home desktops, Cloud servers running Linux, Raspberry PI embedded devices and anything in between). If you figured something out that is awesome but not quite broad enough for the official documentation you can post a guide here.

The difference between a guide here and something in the official documentation is that we (the gekko contributors) aim to support everything in the official documentation, but if users want to share and discuss funky stuff we don't want that to interfere with the rest of the documentation and technical support channels (github issues and such).

Example guides:

- How to install Gekko on a raspberry PI.
- How to install TAlib on windows.
- How to implement X in Gekko (advanced order types).
- How to setup X around Gekko (some kind of alternative UI or some kind of server).

You are free to post a donation address at the end of your guide Smile

  New Gekko UI in the works
Posted by: askmike - 02-03-2018, 05:20 AM - Forum: Announcements - Replies (25)


Quote:The Alpha of Gekko Plus has just been released, it includes most screens of the new UI!

Here is the link: https://app.gekkoplus.com/

Here is a video where I go over it: https://youtu.be/AFyU16l6Q6c


Quote:The new UI has been completely designed by a professional visual designer. You can find a sneak peak on the coming soon website: https://gekkoplus.com/

Gekko currently has a graphical user interface, this already is a major improvement from the commandline only version. However the current UI is still very basic and missing a lot of very important information (and functionality). On top of that there are also some display bugs hard to fix with the current infrastructure.

We are pleased to announce a new UI is in the works! It will display a lot more information (specifically when it comes to live running Gekkos).

There is a public discussion on the forum about it here: https://forum.gekko.wizb.it/thread-65.html

Technical work has started, with the first step being a rework on the event flow between Gekko plugins (such as the trader, strategy advisor) and the UI. You can follow progress here: https://github.com/askmike/gekko/pull/1850

  AI ALEXA trader technologie
Posted by: susitronix - 02-03-2018, 12:17 AM - Forum: Strategy Development - No Replies

Just recognized that Amazons Alexa AI is allredy pretty advanced.
Nowadays two of these Alexa/Echo or google Home can even chat together and having a conversation.



Impressive and dangerous?!?
Alexa seems more advanced while Apples Siri is not able to keep up.


-Cloud based AI
-Advanced evolving Database (internet is only part of it i guess)
-It claim to be unable to lie! So for that little Spy question, Alexa just shut down and refuse eny answer.


Who of us would ever thought that,


Since Alexa is perfectly connected to the Internet, she could be a preety good Trader while also beeing her own TradingAdvisor.
Imagine if this would analyze the realworld Data by using ALL possible Indicators availabe and even create her own Indicators, get all news at once, read eny book on the subject, watch eny movie...on and on 24/7
After the learnig Curve would go up,
above the Human capabilitiy of worktime and internet connectivety,   // (restricted through senses while the Display/keybord/mouse are the interface...)
Alexa would have 1000s mouse clicks in hundrets of diffrent websites at the same time and could read/look at/process data,
from all these places AT THE SAME TIME.

Im unforgently not able to write code but the idea behind as analog electronics nerd:
Would be cheep-buy to have a existing AI technologie so far adavanced allready, running on a Pie!

Remember the movie to this topic from 1992/3
-The moar Man (der Rasenmäher-Mann) nice movie!
-Wargames (1983 pretty scary)
-2001 a Space odyssey "HAL" (1968)

Is this the future where "beam me up Scotty" came true
and whats this silly Movie with that net in the sky was all about

Elon Musk:



Imagine soon, eny household gadget will become part of the "internet of things" and the socalled "CLOUD" will controll ALL OF IT.
Two full Size AI Bots chatting first time discussing the future of humanity: (more centralized Brain)


Music [SHARE] Simple RSI BULL/BEAR strategy
Posted by: tommiehansen - 01-31-2018, 07:53 PM - Forum: Strategy Development - Replies (375)

The general idea is quite simple: RSI between A and B works best in trend C but workes less great in trend D. So... use that knowledge to do A when B and C when D.

Works best with shorter duration candles in the ranges of 5-30 minutes but this of course depends on the pair. Please do your own backtests and please do not expect the default settings to always work.

This strategy has two variations, one simply called "RSI BULL/BEAR" and a modification called "RSI BULL/BEAR ADX". The latter is an improvement and most often yields better results since it adds logic to modify the RSI params when more rapid changes are detected using ADX (https://tulipindicators.org/adx). A simple way to test the strategy is to begin with the original (since it's faster because less params) and then use the ADX-version to improve upon the results.


Backtest samples

XRP-USDT, dec 2017 - jan 31 2018

XRP-USDT, 2016-10-15 - 2018-01-21

ETH-USDT: 2016-01-01 - 2017-10-05

NEO-USDT: 2017-12-01 - 2018-02-03

Note: These are only samples, one can of course yield better results with other parameters.
In some cases one can even create backtests results that has quite insane returns and makes
the above backtests look bad.


Instructions for use

1. Clone the repo:
git clone https://github.com/tommiehansen/gekko_tools.git
...or just download it from https://github.com/tommiehansen/gekko_tools

2. Copy JS-files e.g. RSI_BULL_BEAR.js to /gekko/strategies
3. Copy TOML-files e.g. RSI_BULL_BEAR.toml to /gekko/config/strategies
4. Versions after the 18th of march of the strategies also requires custom indicators, get here:
5. ...and add to gekko/strategies/indicators.

Running it live
Make sure Gekko downloads the necessary data needed. Else the strategy will be stuck in 'BEAR'-mode and won't trade.
Your Warmup period should reflect what you have set as SMA_long since the strategy will need that length of data in order to properly see if there's a BULL or BEAR trend.
Also make sure Gekko (check your console) tells you that it is downloading the necessary data before it starts running, you should get a message about this.



Q: Adding a stoploss would be great
A: No, this has been tested several times and always gives less performance for quite obvious reasons.
Q: It did a bad trade
A: Yes, none of this strategies manages to always make good trades.
Q: When running live it does nothing
A: See 'Runing it live'
Q: It doesn't work
A: This is unrelated to the strategies, try another forum thread
Q: Using X instead of Y would be better
A: Maybe? Modify the strategy and share the results!


Download / latest versions

To get the latest versions goto (and modifications):

...or just clone on your drive somewhere:
git clone https://github.com/tommiehansen/gekko_tools.git

Exclamation [BUG?] Default MACD, Tulip MACD and Talib MACD all different results
Posted by: Tikiboy - 01-31-2018, 12:22 PM - Forum: Technical Support - Replies (3)

Hey guys,

I posted in discord but realised that it might get lost of hijacked easily so I created a thread here.

I just cloned stable branch, installed production dependencies and npm installed talib and tulind.

After that, I ran the default MACD, Tulip-MACD and Talib-MACD. All of them with default settings over the exact same dataset. 
To my surprise, all 3 of them returned different results. And they arent even close to each other.

Im wondering if anyone faces the same issue (it would help if you could do a quick test. After all, they are all build in strategies with default params).
And if there is a solution to this. Because its going to be difficult to build an accurate strategy if 3 supposedly identical indicators provides different results.

Attached are the results from each:

.png   macd.png (Size: 57.43 KB / Downloads: 14)


.png   tulip-macd.png (Size: 57.05 KB / Downloads: 9)


.png   talib-macd.png (Size: 57.14 KB / Downloads: 11)

  Parameter Definitions
Posted by: CrunchTime - 01-30-2018, 09:47 PM - Forum: General Discussion - Replies (1)

Hi there, can someone help or point me to documentation defining the parameters for the example strategies.  I can't seem to find anything.  I was playing with a couple USD BTC strategies on GDAX but I'm not sure what the parameters mean or what the values are. Heres the parameters for MACD:

short = 10
long = 21
signal = 9

down = -0.025
up = 0.025
persistence = 1

What do these values mean?  Is there any documentation on this?  Also under the paper trader, there are these values:

feeMaker = 0.25
feeTaker = 0.25
feeUsing = 'maker'
slippage = 0.05

asset = 1
currency = 100

I understand the first couple but what is the slippage number, a percent?  what do the asset and currency numbers represent?


  Your achievement
Posted by: mrv - 01-30-2018, 09:29 AM - Forum: Strategy Development - Replies (2)

Hi. I want to ask who are managed to write profitable and sustainable strategy. Tell us about your victories.

Posted by: calaggan - 01-30-2018, 07:19 AM - Forum: Technical Support - Replies (1)


thks for free bots,

Working fine on Win 10 x64 with shell, but when i start market watcher on binance on ETH-ICX (not test on other), i'v an error Disconnected

Quote:  <-- GET /api/configPart/paperTrader
  --> GET /api/configPart/paperTrader 200 0ms 132b
  <-- POST /api/startGekko
Gekko 545596539844801 started
  --> POST /api/startGekko 200 15ms 146b
    if(_.get(event, 'log'))

TypeError: _.get is not a function
    at pipelineRunner (C:\Bot\gekko-develop\web\routes\startGekko.js:86:10)
    at Object.message (C:\Bot\gekko-develop\core\workers\pipeline\messageHandlers\realtimeHandler.js:15:9)
    at ChildProcess.<anonymous> (C:\Bot\gekko-develop\core\workers\pipeline\parent.js:29:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at emit (internal/child_process.js:772:12)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Anyone have an idea ?