161
General Discussion / Re: GUNBOT v3.1 - Release name: "x3"
« on: April 21, 2017, 10:00:37 AM »Hi Gun,No, it is enough to PM me again their existing api keys
Windows 2.0.4b users have to generate new API keys for 3.1 version?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hi Gun,No, it is enough to PM me again their existing api keys
Windows 2.0.4b users have to generate new API keys for 3.1 version?
WOW! great news! just 1 question: if I bought GUNBOT before April the 20th, how much is it for the polo license?l
Hi all :-) and Hi Gunthar :-)
First of all I want to say I really enjoy Gunbot and Gunthar's constant efforts to improve it !
Now from my experience and from what I read in the chat, the main problem remaining on Gunbot is when it buys at top price, leading to bag holdings for days (weeks... months...) before these alts recover
I have a suggestion for an option that would allow to minimize these situation
I already posted this idea twice on the Telegram group and it received very good feedback, but I'm sure many users missed it (sometimes hard to read 1000+ messages daily), and that's why I'm posting it here on the forum so everyone can see it and comment.
This options consists in an additional parameter that would be % of bolinger band where bot is allowed to buy
The bot would measure the distance between the lower and upper bolinger bands, and if the price is at a higher distance than set, the bot would not buy
We could set this parameter to 500% by default, with this setting the bot would behave exactly as it is doing now, and it would not bother those who don't want to use this feature.
This would be an additional filter that would be applied just before the bot buys, so it would not change at all the actual gunbot strategy, but only prevent buying too close to upper Bolinger Band if the feature is activated.
For those who want to use the feature, they could set this parameter to 50% for example in which case the bot would buy only if Buy Price is below or at 50% distance from lower bolinger band to upper bolinger band. Depending on each coin behavior the parametre could be set to 10%, 0%, or even -10%
In the picture below for example, the parameter is set at 50% and the bot would be allowed to buy only in the yellow range (sorry the drawing was quickly made and not perfect).
For myself if this was implemented I would use it a lot and set it between 20%~30% I think, but that must be adjustable differently for each pair according to their recent behavior.QuoteIn Spring, 2010, John Bollinger introduced three new indicators based on Bollinger Bands. They are BBImpulse, which measures price change as a function of the bands; percent bandwidth (%b), which normalizes the width of the bands over time; and bandwidth delta, which quantifies the changing width of the bands.
%b (pronounced "percent b") is derived from the formula for Stochastics and shows where price is in relation to the bands. %b equals 1 at the upper band and 0 at the lower band
So basically if we call BBSetParam this new parameter, we would have something like:Code: [Select]if (AllOtherConditionsOk && (%b*100 <= BBSetParam))
BotCanBuy=TRUE;
(Note: someone on the Telegram group said that it is useless because we have EMA's, but this is wrong. Bolinger Bands are really different indicators, and EMA's are useless in what I'd like to see because EMA's always tend to follow the upper Bolinger Band during pumps, and the lower Bolinger Band during dumps.)
I would like to hear everyone's opinion about this suggestion
Thanks for reading :-)
Ok, that means, the lower your buylevel is the bigger is the chance to stay in that pump. Advantage for kickass settings. But on the other hand in a dump the chances are also higher to buy although you actually don't want to buy. Right?
Gunthar, does the bot use the buylevels when buying again in a pump? Or are they ignored in that case?
QuoteIf you want to avoid this: raise the % to sell and the bot will not sell at the stop: it will continue with one buy and one sell.Raise LEVEL 1 and 2?
Good Gunthar, alway on top of thingsYes, even if it doesnt seem like it, i read everyone issues report. That's how our kiddo can grow. So keep posting and reporting!
Hey, I have this issue were sometimes GUNBOT buys so little of a currency that it cannot sell it afterwards.
I believe that it just should not be allowed to do so.
For example, it bought 0.00006166 BTC worth of AMP. Now it's trying to sell it but polo doesn't allow it.
=== ERROR ===statusCode 429
Temporary Ban from Exchange, because of too much API Requests by Bot.
- Reduce the Bot Wait Time and Error Wait Time in config File if you use many Coins to trade
- Open Less Coin-Pairs
//@version=2
study("GUNBOT by Gunthar", overlay=true)
// GUNBOT by Gunthar 29 Nov 2016
src = input(title="Data Array",type=source,defval=ohlc4)
prd1=input(title="Short MA period", type=integer,defval=10)
prd2=input(title="Long MA period",type=integer,defval=20)
AP = ema(src,2)
Fast = ema(AP,prd1)
Slow = ema(AP,prd2)
Bullish = Fast>Slow
Bearish = Fast<Slow
Green = Bullish and AP>Fast
Red = Bearish and AP<Fast
Yellow = Bullish and AP<Fast
Blue = Bearish and AP>Fast
//Long Signal
Buy = Green and Green[1]==0
Sell = Red and Red[1]==0
//Short Signal
Short = Red and Red[1]==0
Cover = Red[1] and Red==0
//Plot
l1=plot(Fast, linewidth=1,color=red)
l2=plot(Slow, linewidth=2,color=blue)
bcolor = Green ? red : Red ? lime : Yellow ? gray : Blue ? gray : white
barcolor(color=bcolor)
fill(l1,l2,bcolor)
When do you expect to release Bittrex and Kraken support? 1 day, 1 month? I'd like to know approximately when, so I can adjust account balances. J don't want to spend transaction fees moving from trex and kraken to polo, only to have to move funds right back to each for trading. An ballpark ETA is all I'm asking for.I posted yesterday ictures of last final 24h test. If everything is fine i will push them before easter.