81
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 30, 2017, 09:48:28 PM »
Thanks to all of you that contribute testing adn reporting, we move to the 3.3 bugs tracker now
~Gun
~Gun
Show Posts
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.
82
General Discussion / Gunbot 3.3 - SMART edition: Windows/Linux/MacOs/armv6/armv7 - Release name "Sato
« on: May 30, 2017, 09:24:51 PM »Gunbot 3.3 - SMART edition: Windows/Linux/MacOs/armv6/armv7 - Release name "Satoshi Nakamoto"
A tribute to the person that changed our lifes. Namasté GM Satoshi Nakamoto.
Changelogs:
Fix ALLPAIRS priority and HotReconfig functions: ALLPAIR overrides CONFIG correctly now and have priority 0
Introducing early stages of machine learning on "price to sell" and BB calculation: the best price to sell is now automatically picked up by the bot, based on the strategy you using, compared to GAIN (which acts like a safety level to not sell at loss). One of the pros of this: if you restart the bot, you dont need to wait for your BB to be recalculated, they are now dynamically used as long as they update over time.
Introducing dynamic levels for stepgain: now the bot takes in consideration 3 levels to buy and sell instead of 2 and using the "SMART" function (enabled by default) it can now use all 3 levels as a fallback chain if the price fails to reach desired level. Basically: in the previous stepgain strategies we only used 2 levels effectively: now all levels are taken in consideration. Pros of this change: you dont have to set buylvl or selllvl anymore: the bot updates the level dynamically as long as the price swings up and down
Introducing early stages of machine learning for price to buy: the best price to buy is automatically picked by the bot comparing BB and BUY_LEVEL, Pros: if you restart the bot, you dont need to wait hours before BB recalculation is done and used.
Actually deleting all open orders (buy and sell) if security margin is reached;
Fix "waiting to sell 0": it comes from the hack that handles "multiple buys";
Fix "Missing boughtPrice!!!" error, which is more than a fix: implementing manual trades: you can now buy manually and the bot would know the last price you bought. Same with manual sell orders: the bot switches to buy loop if you sell manually what it bought.
Deleting both BUY and SELL orders if they get unfilled and the price/volume moves away from previous trading opportunity: the bot will find new home at actual market conditions.
Embedding both color and debig console in windows, so unexperienced users can understand better what is going on
Initial commit of "Start all pairs": when you first start the GUI it will ask if you want to start all pairs. NB: DO NOT DO IT AT VERY FIRST START OF THIS EDITION. Instructions will follow on forums.
Some refactor of GUI layout to avoid exceeding borders if too many pairs are open
Instructions:
How to start from a fresh install:
Double click on GUNBOT.EXE
Change coin names and exchange (Kraken failed the test protocol, please use only polo and bittrex: in the next 24 hours i will push kraken in this release and update this note)
Push SAVE SETTINGS button
Push START button
WAIT for both debug and color consoles to show up and the Alert box to automatically close
Repeat for every new coin you want to trade
How to migrate from v3.2:
Make a new folder and copy/paste all your save.json file from old bot to new one
Start GUNBOT.EXE
Change coin names and exchange, following the save.json files you copy/pasted. Example: if you have poloniex-BTC_ETH-save.json, change coin names and market in the GUI to BTC/ETH/Poloniex
Push SAVE SETTINGS button
Push START button
WAIT for both debug and colo consoles to show up and the Alert box to automatically close
Repeat for each save.json file
How to start again after the first install start:
Push LOAD SETTINGS button: in the new window, select the pair worker you want to use
Push START button
WAIT for both debug and colo consoles to show up and the Alert box to automatically close
Repeat for each worker file you previously saved with V3.3 ONLY !!!! (workers from previous versions are not compatible)
How to use the START ALL PAIR function:
Please i'm still tuning the delay time and waiting for kraken tests to complete, so use this with a max of 4-5 coins. If you use this with 50 pairs, you get only errors 429. When i will push kraken in the next 24 hours you will be able to start all pairs. I will update this note.
Start GUNBOT.EXE
Your bot will ask if you want to start all previously saved pairs: answer yes
WAIT for all consoles (both debug and color) to start and for all Alert messageboxes to close automatically. If after a few minutes you see some Alert messageboxes not closing, you can push the RETRY button: the connection timedout and the retry function will kick your pair to start: all fine!
TODO (in the next 2 days):
Push kraken in the release
Tuning delay times
Include legacy strategies and Best Currencies in the release: for now you can use v3.2 if you want those old strategies.
Please report any bug immediately!!!
Thanks!
~Gun
83
Beginners & Help / Re: GUNBOT...the way i run it!
« on: May 24, 2017, 02:39:40 PM »Today my bot on strategy Stepgain bought crypto higher then BB and higher than each EMA. Previously bot works about 10 hours.
How can it be?
miracles do not happen against the laws of nature but against what we think to know about nature...
You obvously trading with a bot on your computer but then you are looking at poloniex ema and BB instead to look at your bot ema and bb...check those in the moment your bot bought and tell me those values.
84
Beginners & Help / Re: GUNBOT...the way i run it!
« on: May 22, 2017, 10:34:30 PM »Hi @Gunthar,
referring to new stepgainHow does it work? You specify 2 levels of buy and 2 levels of sell (buy below EMA and sell above the price you bought). Say you set buy level 1 to 2% and buy level 2 to 5%: the bot will try to reach the level you set in "Level to use for buy orders" (1 or 2: in the example above would be 2% or 5%). If the price fails to reach that level, the bot will buy on the higher level you set or better price. Same happen with the sell part of it: say you set Sell level 1 to 3% and sell level 2 to 10%, the bot will try to reach 10% or better and if it fails, it will sell between 3% and 10%. In the Legacy-Stepgain strategy, there were 3 levels: now the third level is the BB. So basically let's make some examples:can you please elaborate on theQuoteIf the price fails to reach that levelpart?
what does it mean if it fail? for how long is it supposed to fail? by how far? Does the algo tries more than once?
thanks
Doc
nothing wizard: the trend watcher is our friend. If it reverses before to reach the desired level then....blah blah blah.
85
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 20, 2017, 02:28:43 PM »~snip
Unfortunately we cant do anything against error 522: poloniex server issues. Just be patient and let the bot run until it gets good cycles and start to update again
86
Beginners & Help / GUNBOT...the way i run it!
« on: May 20, 2017, 03:24:48 AM »GUNBOT...the way i run it.
Ok, first of all, this is an announcement: GUNBOT v3.2 GUI edition is out!
So why this disguised announcement? Because before you get your hands on this piece of software, I want you to think: all past months have been exciting, entertaining and you have been a part of it! Together, we built this bot, we discussed, we shared ideas, we pondered every single option, price, setting: until now. It has been a win-win: I have coded our common ideas and sold licenses, you have used all previous versions and patches and your BTC balance makes you smile now. Some of you posted on this forum their results, some didn't: I want to thank you all, announcing this is not the end: this is our "start". The software is considered now out of beta and by now, we are ready to make serious money with it.
That's why, I want to share with you the way I run it, the way I configure it, and the way I take profits out of it.
Let's start:
How to install GUNBOT v3.2 GUI edition
You have been provided a download link: it is a zip file, double click on it and unzip it on your desktop or any other folder you want. Navigate to the unzipped folder and double click on "GUNBOT.EXE", the following screen would appear:
This is the place to put your API keys and SECRET. I'm sure you know where to get those, but for newcomers, here are the links:
Poloniex > https://poloniex.com/apiKeys
Kraken > https://www.kraken.com/u/settings/api
Bittrex > https://bittrex.com/Manage#sectionApi
When you create a new API key, everything needs to be enabled but withdrawal and deposit: as long as you don't enable those 2 options, you are safe using the bot, none will ever be able to access your account and move your assets out of the exchanges. It is a good idea tho, to never share your "secret" key with anyone, me included: if you post your secret key in my PM and I get hacked, someone could steal them. If you realize you sent me your secret key, please delete that API/secret and generate a new one.
If you press "CONTINUE" button on the GUI, your bot saves your API/secret for all markets locally on your computer, so you will not have to type them again. Notice: it is not needed to change your API keys every day
the bot handles all nonce errors and any other kind of thing that screwed API keys in the past. So, kindly...stop asking to "add" new API keys to your license 
Let's move on the next screen that GUNBOT V3.2 will show you:
There are 4 Tabs in the configurator, each one is useful for a set of strategies: the "Legacy-STEPGAIN", "1000trades" and "Russian Roulette" are from v1 and v2 editions and I ported them in v3 because people still like them as they are still very profitable. Please read the main topic of this thread about those strategies. We will talk about the "x4 Edition" tab:
How to configure GUNBOT v3.2 GUI Edition
The "Markets Settings" section is very important: this is the place you select what pairs you are going to trade with GUNBOT and in what exchange. Actually Poloniex, Bittrex, and Kraken are available, but we are going to implement any serious exchange out there. Each exchange is a separated license you can purchase, their cost is 0.1BTC each one, but if you buy more than 1 license, you get 50% discount off on the second and third license: 0.05BTC each one.
You don't have to worry about the spell of the altcoins: write BTC for bitcoin on all exchanges, without worrying about Kraken calling it XBT or another exchange calling it differently: the bot does that internally and when you write BTC or ETC, your GUNBOT knows what to call it on the different exchanges. Take into consideration the primary coins issue tho: i.e at poloniex there are 4 primary coins: BTC/ETH/XMR/USDT. If you want to trade BTC against USD Theter you need to respect what poloniex tradable assets are: they call it USDT/BTC and not BTC/USDT. Also: when you first start to trade a pair, you need to have a balance in the primary coin and possibly no balance on the "altcoin" (please note that in the case of USDT/BTC, bitcoin si considered altcoin). So: if you want to trade USDT/BTC, you need to have Theter Dollars on your balance.
Fill the coins pair and the market in the Markets Section and press "Save settings" button: a confirmation message will appear if everything went smooth.
Let's talk about the "Strategy Settings" now:
There are 4 available strategies in the x4 Edition: Bollinger Band, New STEPGAIN, GAIN, and PINGPONG. Here is the place to select which one to use:
There is a combo box to select one of the 4 strategies for each order set: you can decide to use Bollinger Band (BB) to buy and Stepgain to sell, or you can buy at a fixed price (or better) using PINGPONG and you can sell at a fixed % using GAIN strategy. And so on: any possible mix of those 4 strategies is possible on both buy and sell orders. You can run difference strategies on the same coin too: do it with different balances tho (aka subaccounts). Which one is more profitable? I run pure BB only
(BB strategy on buy and BB strategy on sell) so...think about it...The GAIN section allows you to set a % for both buy and sell orders: the bot will buy x% below the lowest EMA (or better price) and will sell at x% above the price you bought (or better). These settings are very important to set even if you are not using the GAIN strategy: this values, indeed, are "safe" values the bot will never sell or buy above or below this. I.e.: if you are using Bollinger Band strategy, sometimes the Bollinger Band are too tiny (or not completely calculated yet). In those cases, the bot would use a safety price to sell, which is the GAIN setting: it will never sell at less than that. Be sure to have the correct value for it!
The next section is my favorite: the Bollinger Band.
What is this? Do yu remember this post of mine https://bitcointalk.org/index.php?topic=1715214.msg17180517#msg17180517
Well...a lot have changed since that post and we developed the Bollinger Band as a strategy. You can set % values in Low BB and in High BB: the bot will buy only when the price goes x% above the lowest BB (or better price) and will sell only when the price will go x% below the highest BB (or better price. Easy like that...I run this
you been warned...The PINGPONG section is interesting too: if you see a coin doing side moving and reaching the same price up and down repeatedly (DOGE ?) this could give you good profits: set a price to buy and a price to sell and the bot will keep buying/selling at that price (or better).
I'm not a big fan of the next section because the natural evolution of STEPGAIN has been Bollinger Band. But I see reputable members of the GUNBOT community that are doing huge profit with this strategy. Criptonauta and CryptokeeperCanada, for example, they offer a service for their customers of custom settings over this strategy and I always seen impressive profits from them!
How does it work? You specify 2 levels of buy and 2 levels of sell (buy below EMA and sell above the price you bought). Say you set buy level 1 to 2% and buy level 2 to 5%: the bot will try to reach the level you set in "Level to use for buy orders" (1 or 2: in the example above would be 2% or 5%). If the price fails to reach that level, the bot will buy on the higher level you set or better price. Same happen with the sell part of it: say you set Sell level 1 to 3% and sell level 2 to 10%, the bot will try to reach 10% or better and if it fails, it will sell between 3% and 10%. In the Legacy-Stepgain strategy, there were 3 levels: now the third level is the BB. So basically let's make some examples:
Buy Level 1 to 3% - Buy Level 2 to 5% > Level to use 1 > the bot will buy between 3% and Lowest Bollinger Band
Buy Level 1 to 3% - Buy Level 2 to 5% > Level to use 2 > the bot will buy between 5% and Lowest Bollinger Band: if it fails, it will buy at 3% or better
For sales:
Sell Level 1 to 2% - Sell Level 2 to 7% > Level to use 1 > the bot will sell when the price will go between 2% above price you bought and Highest Bollinger Band
Sell Level 1 to 2% - Sell Level 2 to 7% > Level to use 2 > the bot will sell when the price will go between 7% above the price you bought and Highest Bollinger Band: if it fails it will buy at 2% or better.
Confused? Use Bollinger Band
: it is a natural extension of all of this that lets you explore from GAIN setting to BB or better (but I will not take this strategy off until Criptonauta and CryptoKeeperCanada and their customers will tell me they moved to pure BB.Let's see the Balance Settings Section:
Max Balance to trade is the amount of BTC (or primary coin) you want to use per each trade: in this case, it will buy 0.01 BTC worth of altcoin and will sell them at profit, using your strategy. If you are afraid of falling coins, you can protect your balance using the Security Margin: in this case, the bot would sell all your bought altcoins, if the price reaches 60% down the price you bought. You can play with this limit: there are people running GUNBOT with a very small margin, so they sell the bought coins at a loss if they go down after they bought them and the bot moves on to look new entry points: it is a way to not hold bags! Please use this setting with caution: the bot sells at a loss when the security margin is reached!
Let's see the Indicators section now:
GUNBOT uses different indicators in the different strategies:
- EMA indicators (short and long EMA) which are used in GAIN and STEPGAIN in the buy orders (the bot will buy at a % below lowest EMA) and in BB strategy in the SELL orders: the bot will never sell lower than highest EMA or lower than GAIN % from bought price (the best of the 2) in case the Bollinger Band are too tiny to give you a profit. The 0.02 and 0.04 values are a reversed engineered formula to calculate EMA1 and EMA2 very similar to Poloniex periods of 2 and 4 hours with a candlesticks period of 15 minutes. This is the only setting that is backtested with good results: if you use a different period of hours or use a different candlesticks period, the bot will not behave as its creator coded it: it would become too rushy with candlesticks lower than 15 minutes and/or ema1/ema2 lower than 2/4 hours, or too dormant with candlesticks period and/or Ema period higher than what suggested...by the moment you purchased the bot, tho, that's your bot, it is not mine anymore, so you can play with those values but you have been warned...
- Max latest prices indicators: there are 2 of them, max latest prices and max latest prices trend. The first one is used to store prices and calculate Bollinger Band. Unfortunately, poloniex/bittrex/Kraken don't send us Bollinger Band, Ema, Candlesticks back with their API: we need do to maths by ourselves using prices. While the exchange gets one price at every microsecond as long as their order book gets updated, we are limited to the API calls limits to gather prices: one every x seconds you set bot delay time. This is the reason why you will always see different values of indicators than the exchanges. Is ok tho: we are fine, we gather our own statistics and we do it better
TheMax latest prices for BB calculation are fine to 300: you can play with that number and compare results with exchanges.
The Max latest prices for trend watcher is interesting too: using the trend watcher, GUNBOT can see downtrends and uptrends. It will follow downtrends for the buy orders and despite any strategy you use, it will always try to get a better price: when a downtrend is over it is time to buy!
Same happens with uptrend: the bot follows them and when the uptrend is over (the price trend reverses), it is time to sell! Using 30 latest prices is fine if you increase that number the bot would become less reactive, if you decrease that number, the bot would become more reactive.
The Bot Timing section is nice too:
There are 3 bot timings: bot delay, bot on fail and need faster/slower. You can play with the first 2 of them in this section. Consider all exchanges have an API call limit in seconds: i.e. on poloniex, you can't send more than 6 API calls per second. If you are trading a lot of pairs and you have Time delay time and bot on fail time too short, you risk being banned. The Time delay time is a number of seconds the bot will wait before to update prices and statistics. The Bot of Fail delay is used if an API call fails: it will retry after x seconds you set in that config value. A reasonable timing for up to 10 pairs is 60/30 in this couple. For over 10 pairs up to 20-25 pair, is reasonable to double those values to 120/60. If you go higher than 20-25 pairs, I suggest you use 2 or more different API keys: you don't have to pay for it, you can generate new API keys and send them to me to be added to your license. Beware tho: do not abuse exchanges limits, we are welcome at exchanges with our bots because we generate fees, but the system needs to be workable for everyone. Any abuse of API calls made with GUNBOT is highly discouraged and if it happens to you and you don't stop your bot and use reasonable bot timing, I may suspend your license until you comply with the exchange's limits.
The Best currencies section (aka Statistics button)
It is hard to select the right coins to trade. You have 2 ways to do it: go with the highest volume on exchanges, or use this tool. Select a minimum volume and a minimum 24 hours variation you want (for example coins with at least 200 of volume and 3% of variation in the last 24 hours and press the STATISTICS button: a new tab would open to list all currencies at poloniex that are above those values in any market (BTC/USDT/ETH/XMR). Of course, you can use another method to decide what coin to trade: your skills and your knowledge
So...we are done with settings...what's next?
It is time to start our bot! This is the correct procedure:
- After you are sure of your settings, press "SAVE SETTINGS"
A confirmation message would appear saying the settings have been successfully saved. Next: press START GUNBOT.
Again a confirmation message would appear asking you to wait sometime and give the bot its time to collect everything it needs to start trading and connect to the desired exchange. Please do not close the alert message and patiently wait for your console to appear:
The confirmation message above says the bot is starting to trade on the desired exchange: please do not close/abort this message and patiently wait for your bot to go LIVE like the picture below:
So what does your console says?
These are the basic information about the exchange we are trading, the coin pairs we are using in this instance and their available balances to trade: in this case, we will use those BTC to buy and we will have to sell those ETH.
You can always see a TimeStamp about the last time the bot updated prices and statistics at the exchange:
In the picture below you can see LowBB and HighBB values the bot calculated:
Here you can see prices: the Last market price, the maximum price the bot would buy (but it will try to get a better one) based on the strategy and settings you using, the minimum price the bot would sell (but it will try to get a better price) based on the strategy and settings you using, the price you bought in your last buy order and the price for the security margin.
Now, try to play a bit with your bot and see how those prices would change if you change settings. But how to change settings? Go back to the configuration tab (the X4 Edition tab), change the coin name and the market (polo, rex, Krak) you are trading that pair and press the LOAD SETTINGS. It will load the settings you previously saved for that pair: now change i.e. the BUY LEVEL in the GAIN section and press SAVE SETTINGS. Go back to the trading pair tab and observe the Price to buy: it changed following the % you just changed. You can play with any settings and observe the console reacting to your changes LIVE.
The picture below shows an important part of the GUNBOT core: the trading.
It shows you the last trading attempt timestamp and indicates the results: in this case, it is saying that it is waiting for a good price to sell but it can sell yet because the last price is too low. It also indicates that it doesn't need to be faster and it doesn't need to be slower. This is an important concept: when the price gets closer to the target price to buy or the target price to sell, we need to move faster! We did talk about the API call limits: if you set a bot timing too short, you may get banned. Don't do it: let the bot do the job for you. When it is needed, the bot knows how to speed: it does it in the correct way, without exceeding the API call limits and it does it only for that pair and only for the time it is needed. For example, the price is getting close to the target price to sell: we need to be fast or we may risk to lose the price and not able to sell. In this case, if you have a bot timing very high because you are trading a lot of pairs, the bot ignores all of that and uses its own timing, in the right way, respecting the exchange rules and being fast enough internally to not lose the ride
The section below shows your trading results: the last buy order description, the last sell order description and the total profit you got in the actual session. When you decide to close the bot, you can withdraw that amount from the exchange! If you leave that profit on your balance tho, the bot will reinvest it the next time you start.
The last part of the console shows all actual settings for that pair so you always know what settings you are using, without having to go back to the configurator and "load settings".
Well, this is all...what's next? Oh right....the way I run it....
Ok, do this: use pure BB, you will have time to speculate and study your own strategy. Set lowBB and highBB to values between 20 and 35 (for example lowBB 21 and highBB 29 or lowBB 24 and highBB 27 or any other value you wish. Make a selection of at least 10-15 coins and start them all with those settings on pureBB. In 1 week, come back here and post your results!
These are mines since 11 of May at night (basically 1 week):
https://docs.google.com/spreadsheets/d/1CVJzkVQzkkaslDgVcfEVVi54WwLZXgfbaqAdKzcLH5A/pubhtml
~Gun
87
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 18, 2017, 03:03:48 PM »Looks like on 3.2, at least on Kraken (the only 3.2 I'm running at the moment), when it gets a 502 error, the bot is dumping the HTML response to the console instead of catching it and just reporting the 502.Code: [Select][ --2017/05/18 07:33:33--kraken--BTC_DASH -- Gunbot v3.2 cycle #213 --------------- ]
::::: collecting market data...
2017/05/18 07:33:35 Error: Could not understand response from server: <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]> <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]> <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>
<meta http-equiv="set-cookie" content="cf_use_ob=0; expires=Thu, 18-May-17 12:34:05 GMT; path=/">
<title>api.kraken.com | 502: Bad gateway</title>
<meta charset="UTF-8"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1"/>
<meta name="robots" content="noindex, nofollow"/>
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1"/>
<link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" type="text/css" media="screen,projection"/>
<!--[if lt IE 9]><link rel="stylesheet" id='cf_styles-ie-css' href="/cdn-cgi/styles/cf.errors.ie.css" type="text/css" media="screen,projection" /><![endif]-->
<style type="text/css">body{margin:0;padding:0}</style>
<!--[if lte IE 9]><script type="text/javascript" src="/cdn-cgi/scripts/jquery.min.js"></script><![endif]-->
<!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/zepto.min.js"></script><!--<![endif]-->
<script type="text/javascript" src="/cdn-cgi/scripts/cf.common.js"></script>
</head>
<body>
<div id="cf-wrapper">
<div id="cf-error-details" class="cf-error-details-wrapper">
<div class="cf-wrapper cf-error-overview">
<h1>
<span class="cf-error-type" data-translate="error">Error</span>
<span class="cf-error-code">502</span>
<small class="heading-ray-id">Ray ID: 360ed87d7f50583d • 2017-05-18 12:33:35 UTC</small>
</h1>
<h2 class="cf-subheadline" data-translate="error_desc">Bad gateway</h2>
</div>
<div class="cf-section cf-highlight cf-status-display">
<div class="cf-wrapper">
<div class="cf-columns cols-3">
<div id="cf-browser-status" class="cf-column cf-status-item cf-browser-status ">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-browser"></i>
<i class="cf-icon-status cf-icon-ok"></i>
</div>
<span class="cf-status-desc" data-translate="browser_desc">You</span>
<h3 class="cf-status-name" data-translate="browser_label">Browser</h3>
<span class="cf-status-label" data-translate="browser_status_label">Working</span>
</div>
<div id="cf-cloudflare-status" class="cf-column cf-status-item cf-cloudflare-status ">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-cloud"></i>
<i class="cf-icon-status cf-icon-ok"></i>
</div>
<span class="cf-status-desc" data-translate="cloud_desc">Location</span>
<h3 class="cf-status-name" data-translate="cloud_label">Cloudflare</h3>
<span class="cf-status-label" data-translate="cloud_status_label">Working</span>
</div>
<div id="cf-host-status" class="cf-column cf-status-item cf-host-status cf-error-source">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-server"></i>
<i class="cf-icon-status cf-icon-error"></i>
</div>
<span class="cf-status-desc" data-translate="server_desc">api.kraken.com</span>
<h3 class="cf-status-name" data-translate="server_label">Host</h3>
<span class="cf-status-label" data-translate="server_status_label">Error</span>
</div>
</div>
</div>
</div>
<div class="cf-section cf-wrapper">
<div class="cf-columns two">
<div class="cf-column">
<h2 data-translate="what_happened">What happened?</h2>
<p>The web server reported a bad gateway error.</p>
</div>
<div class="cf-column">
<h2 data-translate="what_can_i_do">What can I do?</h2>
<p data-translate="try_again_in_a_few">Please try again in a few minutes.</p>
</div>
</div>
</div>
<div class="cf-error-footer cf-wrapper">
<p>
<span class="cf-footer-item">Cloudflare Ray ID: <strong>360ed87d7f50583d</strong></span>
<span class="cf-footer-separator">•</span>
<span class="cf-footer-item"><span data-translate="your_ip">Your IP</span>: x.x.x.x</span>
<span class="cf-footer-separator">•</span>
<span class="cf-footer-item"><span data-translate="performance_security_by">Performance & security by</span> <a data-orig-proto="https" data-orig-ref="www.cloudflare.com/5xx-error-landing?utm_source=error_footer" id="brand_link" target="_blank">Cloudflare</a></span>
</p>
</div>
</div>
</div>
!!! Cycle 214 failed. Will repeat in 102.9763402239914s
Seems that maybe this should be caught by gunbot and just reported as a 502 or whatever.
Yes, since the last weeks mitigation of ddos attacks on multiple exchanges i added (err, data) to the err. I'll move that to err logs: i needed to see wtf was going on...
88
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 17, 2017, 09:29:15 PM »@OutOfSync to me it looks like 3.2 BB needs 3 cycles to calculate its values!? but I might be wrong and the values showing up are ...?.. something else!
It shows BB values after 3 cycles because you need at least 3 values to calculate standard deviation. However, until stats are calculated (300 cycles with default settings) the bot does not use BB strategy but the GAIN value (2% as default). 300 cycles with default delay of 120 s is 10 hours untils BB stats are done. This is just quite long if you have to e.g. update the binary and hotconfig is therefore not possible...
A trick if you know you are going to do a quick restart: save your save.json file in another folder > start yor bot > copy/paste yoru old save.json file while the bot is already running. Dont do that if you stop yrou bot for long time tho: you will get weird standard deviation
89
Technical Support & Development / Re: Problem: Gunbot buying too many. (Patch Fixes #2021 - v3.2 )
« on: May 17, 2017, 02:42:13 AM »
fixed in patch 2022
91
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 15, 2017, 10:05:30 PM »
~snip
You "think" the bot doesnt: 6e-9 are 0.000000006 BTC on your balance at Kraken which are 0.00000 BTC displayed on kraken balances (roundings is worse than polo at kraken: 5 digits only)
92
Technical Support & Development / Back to old STEPGAIN?
« on: May 15, 2017, 10:00:34 PM »
I see some people are confused with the new STEPGAIN logic. Do you guys want me to port back the old STEPGAIN strategy on 3.2?
Let me know,
Thanks!
Let me know,
Thanks!
93
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 15, 2017, 09:24:29 PM »gbot complains about "Missing boughtPrice" since it cannot find a record of this altcoin balance.
MissingBoughtPrice comes because you didnt port the save.json file: basically wasnt the bot to place that sell order.
Please do not use manual orders, they are nto implemented nor they help.
95
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 15, 2017, 05:26:39 PM »~snip
Thanks for reporting this!
96
Technical Support & Development / Re: Other pairs on hold while one pair has a pending (untouched) order
« on: May 14, 2017, 08:02:34 PM »When one Pair places an order that is not yet executed, all the rest of the pairs pretend to have the same order for their currency.fixed in patch 2020
This holds all the other pairs to proceed normally
Settings:
Gunbot v3.2, win headless, Buy strategy: BB, 25%; sell strategy: GAIN 3%, bot delay: 60s
Details:
Gunbot placed a buy order for LTC that was processed with a delay of some minutes by Kraken.
Meanwhile, all the rest of the pairs that were about to proceeed with a buy/sell had the same message:
2017/05/12 00:40:10 Waiting for orders: 370.248 XLTC , for LTC
2017/05/12 00:26:33 Waiting for orders: 370.248 XXLM , for XLM
2017/05/12 00:26:07 Waiting for orders: 370.248 XETC , for ETC
etc. etc.
Thanks for reporting!
97
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 14, 2017, 08:01:14 PM »Tripple an quadruple buys on Patch 2019!statuscode 502, 429, 422 from poloniex caused this. Please apply patch 2020 to mitigate about 99% of these issues.
"BB" strategy, poloniex!
All pairs are set to "BTC_TRADING_LIMIT: 0.035"
98
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 14, 2017, 08:00:13 PM »2 issues to report:
1) "Altcoin on orders" is reported incorrectly in kraken market (did not check other markets):
Situation: I have some ETH that I manually placed a selling order for. Now I started a different pair in kraken from scratch with brand new config and no save file. The ETH on orders is now reported as "balance on order" for the newly started pair and the bot is confused because it thinks we have altcoins but no boughtPrice. This could be mitigated if the "balance on order" is reported correctly for the pair the bot is running.
2) I cannot find the Low BB and High BB values in the "-save.json" file.
Saving these important values would make it easy to write a GUI that reports them over time. I am thinking along the lines of an InfluxDB database with Grafana dashboard tracking all parameters. Would be really nice to tweak the bot.
Thanks Gunthar for an awesome update!
Solved both in patch 2020
Thanks for reporting!
99
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 12, 2017, 06:40:15 PM »~snip
~snip
Please apply patch #1029_ i moved kraken to limit market
100
Technical Support & Development / Re: Market Buy/Sell Orders lead to losses
« on: May 12, 2017, 05:57:38 PM »When the time to buy has come, gunbot puts market order to buy to a price that is in reality incorrect.
Settings:
gunbot v3.2, buy strategy: BB, 25%; sell strategy: GAIN3%5%, bot delay time: 60s
Description:
Having lower 'bought price' leads to inappropriate calculations of the GAIN % (sell strategy is GAIN). Afterwards, because sell orders are also market the result is unpredictable and at least in my case all trades lead to losses.
The problem is fixed in patch 2019: moved to limit. Apparently the issue is that we dont get "market" price from their api, we get "average" price. Reference: https://support.kraken.com/hc/en-us/articles/203325783-Market-and-Limit-Orders