41
Technical Support & Development / Bugs/Issues tracker v4.0.3 patched
« on: August 15, 2017, 12:55:30 PM »
Bumping up this to v4.0.3
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.
42
General Discussion / MOVED: Gunfigurator - Gunbot 4.0.2 Configuration File Generator
« on: August 14, 2017, 10:14:35 PM »43
Technical Support & Development / Bugs/Issues tracker v4.0.1_patched
« on: August 12, 2017, 10:15:19 PM »
Updated bug tracker for patched v4.0.1
Thanks!
~Gun
Thanks!
~Gun
44
Technical Support & Development / Constructive ideas for TA use in Gunbot
« on: August 11, 2017, 01:43:54 AM »
Please if you have a REAL and tested strategy to implement in Gunbot using TA lib, post it here, we will discuss togheter and implement it.
Example: "SMA5 crossing SMA10 and SMA20 as buy/sell signals IF Stochastic RSI is between 30/70 and changes direction"
Thanks!
~Gun
Example: "SMA5 crossing SMA10 and SMA20 as buy/sell signals IF Stochastic RSI is between 30/70 and changes direction"
Thanks!
~Gun
45
Technical Support & Development / Bugs/Issues tracker v4.0.1
« on: August 11, 2017, 01:39:30 AM »
I'm going to read this user-generated tracker every 5 minutes.
Thanks!
~Gun
Thanks!
~Gun
46
General Discussion / Release Candidate v.4.0.1_core - All oS - Poloniex/Bittrex/Kraken/Cryptopia - Co
« on: August 11, 2017, 01:37:41 AM »Release Candidate v.4.0.1_core - All oS - Poloniex/Bittrex/Kraken/Cryptopia - Code name "2nite"
@GuntharDeNiro GuntharDeNiro and @RaffaeleDonadono released this 3 minutes ago
Changelogs:
-Fix all reported bugs of v3.3.5
-Bump Kraken to 4.0.1
-Implement Cryptopia exchange
-Implement all v3.x strategies: BB,Gain,StepGain (v2.0.4 style), PingPong
-Implement Stop-loss
-Allowing users to disable BUY orders
-Implementing MIN_VOLUME_TO_BUY and MIN_VOLUME_TO_SELL to handle dust (if ever happens)
-If we have altcoin balance lower than minimum allowed amount: we buy
-Implementing a new trend watcher using TA lib
-Implementing new averaged buy price based on @BeerK0in formula. Thanks Beer K0in!
Config.js explanations and instructions:
Pairs format per exchange:
-poloniex: BTC_ETH, ETH_XMR, XMR_ETC, USDT_BTC
-Kraken: EOSXBT, DASHXBT, GNOXBT, BCHXBT all others are XLTCXXBT. Fiat are ZEURXXBT.
-Bittrex: BTC-ETH, ETH-LTC
-Cryptopia: SIGT_BTC, ETH_BTC, CHC_BTC
Possible strategies (format is buysell for mixed strategies and strategyname for pure strategies):
-bb (for Bollinger Band in both buy and sell)
-gain (for GAIN strategy in both buy and sell)
-stepgain (for SG strategy in both buy and sell)
-pp (for PingPong strategy in both buy and sell)
-bbgain (buy with BB and sell with gain)
-gainbb (buy with gain and sell with BB)
-bbstepgain (buy with bb and sell with stepgain)
-stepgainbb (buy with stepgain and sell with bb)
-bbpp (buy with BB and sell with PingPong)
-ppbb (buy with PingPong and sell with BB)
-gainstepgain (buy with gain and sell with stepgain)
-stepgaingain (buy with stepgain and sell with gain)
-gainpp (buy with gain and sell with PingPong)
-ppgain (buy with PingPong and sell with gain)
-stepgainpp (buy with stepgain and sell with PingPong)
-ppstepgain (buy with PingPong and sell with stepgain)
New Trend watcher (former supergun trend):
-it is active only in StepGain
-it is in a very short timeframe: looks at very latest 5 to 8 x 15 minutes candles
-It uses -DM and +DM from TA
-It is very useful to spot pumps (limited to the StepGain levels)
-It will be configurable after a short period of test from GBU clerks
Some example of configuration settings and their meaning:
Code: [Select]
"bb": {
"BTC_TRADING_LIMIT": 0.01,
"PERIOD": 15,
"BUY_LEVEL": 0.1,
"GAIN": 0.1,
"HIGH_BB": 40,
"LOW_BB": 40,
"PANIC_SELL": false, //set this to true to sell all your altcoin at market price (set BUY_ENABLED: false)
"DOUBLE_UP": true, //set this to false if you dont want to use the average down feature
"STOP_LIMIT": 60, //In this case it will sell all your altcoins if the price reaches -60% from bought price
"BUY_ENABLED": true, //set this to false to disable buy orders
"MIN_VOLUME_TO_BUY": 0.001, //if you have dust, set this higher than your dust
"MIN_VOLUME_TO_SELL": 0.001 //if you have dust, set this higher than your dust
}Provided config.js file must stay untouched: do not delete variables (even if you think they are not useful), do not change names of variable. Just add yoru pairs and change your values. Everything in "Strategies" section can go in "Override" of the single pair.
To verify the validity of your config.js use this tool https://jsonlint.com/
SUGGESTED STRATEGY AND SETTINGS: once again the best performances (unless you are in GBU) come with pure BB at 40/40 or even better at 45/45 with or without DOUBLE_UP.
Thanks to @raffaeledonadono for his precious code contribution. Thanks to all users that patiently tested and reported bugs of previous versions.
Please report any bug immediately!!!
Thanks!
~Gun
47
General Discussion / Release Candidate v3.3.5 AllOs_x64 - Code name: "Emotionless Fork"
« on: July 31, 2017, 05:19:33 PM »
Release Candidate v3.3.5 AllOs_x64 - Code name: "Emotionless Fork"
@GuntharDeNiro GuntharDeNiro released this just now
Changelogs:
Fixed bugs reported in v3.3.4
Processing only pairs with trading signals
CPU/RAM improved performances
Implemented "bought price" for deposited coins: if you deposit a coin from another exchange, move "BOUGHT_PRICE" setting in "override" and GUNBOT will know the price you originally bought it
Instructions:
Dont stop it on 1st August. The bot is ready to take any direction of the market and help us to take advantage of altcoins reaction to the BTC fork. We waited patiently till now with all our bags: shutting down right now is something i don't suggest, we are not quitters!
Tested configurations to face up the fork:
LowBB/HighBB 40/40
GAIN: 0.6
DOUBLE_UP: true
Let it run 24/7 and watch charts and wallets at exchanges: you'll never know what would happen!
Wish you all Happy Fork!
Please report any bug immediately!
Thanks!
~Gun
@GuntharDeNiro GuntharDeNiro released this just now
Changelogs:
Fixed bugs reported in v3.3.4
Processing only pairs with trading signals
CPU/RAM improved performances
Implemented "bought price" for deposited coins: if you deposit a coin from another exchange, move "BOUGHT_PRICE" setting in "override" and GUNBOT will know the price you originally bought it
Instructions:
Dont stop it on 1st August. The bot is ready to take any direction of the market and help us to take advantage of altcoins reaction to the BTC fork. We waited patiently till now with all our bags: shutting down right now is something i don't suggest, we are not quitters!
Tested configurations to face up the fork:
LowBB/HighBB 40/40
GAIN: 0.6
DOUBLE_UP: true
Let it run 24/7 and watch charts and wallets at exchanges: you'll never know what would happen!
Wish you all Happy Fork!
Please report any bug immediately!
Thanks!
~Gun
48
General Discussion / Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"
« on: July 25, 2017, 05:58:39 PM »
Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"
@GuntharDeNiro GuntharDeNiro released this 11 minutes ago
This is a major release introducing new concepts both in core and strategies. Starting by this release, Gunbot devs family is now bigger: @raffaeledonadono is now caring about the "core-engine" while i am focused on the "strategies" part of the code. This new devs structure will allow us to stay focused on the different parts of the code while double checking each other code with doubled security and coding accuracy.
Please: continue to forward all support requests to me, tho, thank you.
The final release will aim to:
Make Gunbot able to run as many pairs and as many exchanges as you want in one single process using a very low amount of RAM and CPU
Solve all past reported bugs
Give new Technical Analysis instruments for an advanced trading experience
Give a real cross-platform package including GUI for *nix/OSX/arm
Give Gunbot real-data from exchanges with no limit to "bot timing"
Give 3rd parties devs a Websocket API to build plugins
Give Gunbot capability to work as a live data-hub for 3rd parties software
Give end-users capability to build their own strategies based on TA indicators
This Release Candidate aims to:
Give existing customers a tool to liquidate their altcoin holdings with profit and give new liquidity to their Gunbot to continue trading at new price levels (healing from recent cripto-crashes)
Give a preview and receive feedbacks for a community-driven final release
This Release Candidate is able to:
Run all your pairs in one single console for Poloniex and Bittrex exchanges
Average down your "bought price" from existing "bags" and sell them at profit in 24/48 hours
Continue to trade all your pairs without creating "bags" or liquidating them at lower levels (with profit) if the value of the altcoin dropped below the bought price.
Fetching real data from Poloniex and Bittrex exchanges: you can now see the same values than exchanges for indicators (BB, EMA, etc). If Gunbot restarts, the indicators data will NOT be lost.
Trade all your pairs with a real and effective BB and GAIN strategy (SG and other strategies to be completed in a patch)
Deprecate bot timing: we are now "live" on the exchange and we run following microseconds tickers updates from exchanges
Fix all bugs reported in v3.3.2: double buys, wrong indicators, wrong priceToBuy/priceToSell calculations
included all 422 errors, stuck instances etc
Added TA indicators capability
Added "watch mode only" and "panic sell" mode: first mode would run gunbot without trading, second one would sell all altcoin at actual market price (WARNING: it might be at loss).
How to run v3.3.3 from existing v3.x
Disclaimer: v3.3.3 is backward compatible with any existing trades/balances. - v3.3.3 config files are NOT backward compatible
Step-by-Step instructions:
The concept: one of the main issues of Gunbot old versions, was to be unable to follow the price flow during up and down levels swings. If BB and EMA moved to new low levels and you bought during the previous price level timeframe, you would end with the unfamous "bags" in your portfolio. Despite we all "luv" bags because they represent cheap coins we were able to buy, if market conditions keep being bearish, "bags" would engulf our portfolio with unsold coins, hence missed trades because of low primary coin liquidity. The v3.3.3 "Autopilot" version, solves this issue with a simple wise move: averaging down your bought price and selling all "bags" at a profit in a short-term time frame, giving so new liquidity to your Gunbot and making it able to continue its profitable strategy on the new market level.
How it works: the leading indicators are still BB. Now we use live data from exchange so we can trick BB at a reliable value, same than exchanges. I tested this strategy with SMA: it triggers the average-buy order TOO EARLY, do not use SMA for this strategy!!
See the following scenario:
Your last buy order for coin X was at 0.001;
HighBB was at 0.0014;
Bear come in the scene and price drops to 0.00083 and now HighBB is at 0.00094;
Because HighBB value (0.00094) dropped below your last bought price (0.001), Gunbot buys again SAME AMOUNT OF COIN X
We have now a new "bought price" at (0.001+0.00083)/2=0.00091 with an HighBB at 0.00094: WE CAN SELL AT PROFIT VERY SOON!!!
What you need to do to autostart this on your existing bags?
The Release Candidate is already configured to start this automatically on your existing bags. The only thing you need to configure are pairs you want to run on this. Let's see some config file format:
We are still without GUI so you will need to understand how the config file is structured: it is a json file
Sections in the config.js file need their synthax:
Exchanges/Pair section
"pairs": {
"poloniex": {
"BTC_XMR": {
"strategy": "bb",
"override": {}
},
"BTC_ETH": {
"strategy": "bb",
"override": {}
},
"BTC_ETC": {
"strategy": "bb",
"override": {}
}
},
"bittrex": {
"BTC-LTC": {
"strategy": "bb",
"override": {}
},
"BTC-PIVX": {
"strategy": "bb",
"override": {}
}
}
},
As you can see it is a simple json file but we need to respect commas, quotes and parenthesis format inside it. The tree is like this:
PAIR SECTION > EXCHANGE > PAIR LIST
If you have any doubt you can contact me for assistance about the right synthax to use or you can open config.js file with Notepad++ using its embedded code highlight feature.
Strategies section
The strategy section is preconfigured to start averaging down when it is needed and sell pretty much immediately with 0.6% of profit: if follows BB in buy (unless TRAILING STOP enters the scene) and then sells at 0.6% with GAIN (notice the highBB setting is at 60 to not override GAIN). Start like this to get rid of your bags and let it run for 1 or 2 days. You will see your bot coming back to life on your poloniex/bittrex trading history (and balance). When you are satisfied of your bags recovering, switch highBB setting at 40 or below at desired levels: you will meet a new GUNBOT: emotionless, continuosly profitable, despite the coins swings.
Example of strategy to get rid of bags
"strategies": {
"bb": {
"PERIOD": 15,
"BUY_LEVEL": 0.1,
"GAIN": 0.6,
"HIGH_BB": 60,
"LOW_BB": 40,
"PANIC_SELL": false
}
Change to this configuration once you got rid of your bags
"strategies": {
"bb": {
"PERIOD": 15,
"BUY_LEVEL": 0.1,
"GAIN": 0.6,
"HIGH_BB": 40,
"LOW_BB": 40,
"PANIC_SELL": false
}
Disclaimer: you need capital to average down. Rather you are able to deposit more bitcoin at your exchange account or you need some immediate liquidity from existing bags. How much capital or how much liquidity you need to start using this strategy? Same amount in BTC (or primary coin) of one of your bags: say you have a list of 10 bags > deposit BTC (or primary coin) amount equal to ONE OF YOUR BAGS HOLDING VALUE IN BTC (i.e. if one of your bags is ETH and its value in BTC is 0.02BTC: deposit 0.02BTC), or sell one of your bags (any of your choice) at market price so to give your account an immediate liquidity, if you are unable to deposit more BTC (or primary coin). You dont need to deposit a lot of BTC (or primary coin) to average down your bags: it is enough to cover just one bag only and your GUNBOT will start a chain of bags-recovering, getting liquidity as it sells your bags. Keep this in mind by now on when you use GUNBOT: dont use all your capital, GUNBOT will need a reserve in case averaging down is needed because market conditions.
How to start GUNBOT
Windows: compile the config.js file and double click on gunthy.exe
Linux/MacOs: compile config.js file and run ./gunthy
I'm pretty sure a lot of questions will come out and i'm looking forward to all of you bugging me 24/7 on forums and Telegram...but this is why we love GUNBOT!
Please report any bag immediately!!!
Thanks!
~Gun
@GuntharDeNiro GuntharDeNiro released this 11 minutes ago
This is a major release introducing new concepts both in core and strategies. Starting by this release, Gunbot devs family is now bigger: @raffaeledonadono is now caring about the "core-engine" while i am focused on the "strategies" part of the code. This new devs structure will allow us to stay focused on the different parts of the code while double checking each other code with doubled security and coding accuracy.
Please: continue to forward all support requests to me, tho, thank you.
The final release will aim to:
Make Gunbot able to run as many pairs and as many exchanges as you want in one single process using a very low amount of RAM and CPU
Solve all past reported bugs
Give new Technical Analysis instruments for an advanced trading experience
Give a real cross-platform package including GUI for *nix/OSX/arm
Give Gunbot real-data from exchanges with no limit to "bot timing"
Give 3rd parties devs a Websocket API to build plugins
Give Gunbot capability to work as a live data-hub for 3rd parties software
Give end-users capability to build their own strategies based on TA indicators
This Release Candidate aims to:
Give existing customers a tool to liquidate their altcoin holdings with profit and give new liquidity to their Gunbot to continue trading at new price levels (healing from recent cripto-crashes)
Give a preview and receive feedbacks for a community-driven final release
This Release Candidate is able to:
Run all your pairs in one single console for Poloniex and Bittrex exchanges
Average down your "bought price" from existing "bags" and sell them at profit in 24/48 hours
Continue to trade all your pairs without creating "bags" or liquidating them at lower levels (with profit) if the value of the altcoin dropped below the bought price.
Fetching real data from Poloniex and Bittrex exchanges: you can now see the same values than exchanges for indicators (BB, EMA, etc). If Gunbot restarts, the indicators data will NOT be lost.
Trade all your pairs with a real and effective BB and GAIN strategy (SG and other strategies to be completed in a patch)
Deprecate bot timing: we are now "live" on the exchange and we run following microseconds tickers updates from exchanges
Fix all bugs reported in v3.3.2: double buys, wrong indicators, wrong priceToBuy/priceToSell calculations
included all 422 errors, stuck instances etc
Added TA indicators capability
Added "watch mode only" and "panic sell" mode: first mode would run gunbot without trading, second one would sell all altcoin at actual market price (WARNING: it might be at loss).
How to run v3.3.3 from existing v3.x
Disclaimer: v3.3.3 is backward compatible with any existing trades/balances. - v3.3.3 config files are NOT backward compatible
Step-by-Step instructions:
The concept: one of the main issues of Gunbot old versions, was to be unable to follow the price flow during up and down levels swings. If BB and EMA moved to new low levels and you bought during the previous price level timeframe, you would end with the unfamous "bags" in your portfolio. Despite we all "luv" bags because they represent cheap coins we were able to buy, if market conditions keep being bearish, "bags" would engulf our portfolio with unsold coins, hence missed trades because of low primary coin liquidity. The v3.3.3 "Autopilot" version, solves this issue with a simple wise move: averaging down your bought price and selling all "bags" at a profit in a short-term time frame, giving so new liquidity to your Gunbot and making it able to continue its profitable strategy on the new market level.
How it works: the leading indicators are still BB. Now we use live data from exchange so we can trick BB at a reliable value, same than exchanges. I tested this strategy with SMA: it triggers the average-buy order TOO EARLY, do not use SMA for this strategy!!
See the following scenario:
Your last buy order for coin X was at 0.001;
HighBB was at 0.0014;
Bear come in the scene and price drops to 0.00083 and now HighBB is at 0.00094;
Because HighBB value (0.00094) dropped below your last bought price (0.001), Gunbot buys again SAME AMOUNT OF COIN X
We have now a new "bought price" at (0.001+0.00083)/2=0.00091 with an HighBB at 0.00094: WE CAN SELL AT PROFIT VERY SOON!!!
What you need to do to autostart this on your existing bags?
The Release Candidate is already configured to start this automatically on your existing bags. The only thing you need to configure are pairs you want to run on this. Let's see some config file format:
We are still without GUI so you will need to understand how the config file is structured: it is a json file
Sections in the config.js file need their synthax:
Exchanges/Pair section
"pairs": {
"poloniex": {
"BTC_XMR": {
"strategy": "bb",
"override": {}
},
"BTC_ETH": {
"strategy": "bb",
"override": {}
},
"BTC_ETC": {
"strategy": "bb",
"override": {}
}
},
"bittrex": {
"BTC-LTC": {
"strategy": "bb",
"override": {}
},
"BTC-PIVX": {
"strategy": "bb",
"override": {}
}
}
},
As you can see it is a simple json file but we need to respect commas, quotes and parenthesis format inside it. The tree is like this:
PAIR SECTION > EXCHANGE > PAIR LIST
If you have any doubt you can contact me for assistance about the right synthax to use or you can open config.js file with Notepad++ using its embedded code highlight feature.
Strategies section
The strategy section is preconfigured to start averaging down when it is needed and sell pretty much immediately with 0.6% of profit: if follows BB in buy (unless TRAILING STOP enters the scene) and then sells at 0.6% with GAIN (notice the highBB setting is at 60 to not override GAIN). Start like this to get rid of your bags and let it run for 1 or 2 days. You will see your bot coming back to life on your poloniex/bittrex trading history (and balance). When you are satisfied of your bags recovering, switch highBB setting at 40 or below at desired levels: you will meet a new GUNBOT: emotionless, continuosly profitable, despite the coins swings.
Example of strategy to get rid of bags
"strategies": {
"bb": {
"PERIOD": 15,
"BUY_LEVEL": 0.1,
"GAIN": 0.6,
"HIGH_BB": 60,
"LOW_BB": 40,
"PANIC_SELL": false
}
Change to this configuration once you got rid of your bags
"strategies": {
"bb": {
"PERIOD": 15,
"BUY_LEVEL": 0.1,
"GAIN": 0.6,
"HIGH_BB": 40,
"LOW_BB": 40,
"PANIC_SELL": false
}
Disclaimer: you need capital to average down. Rather you are able to deposit more bitcoin at your exchange account or you need some immediate liquidity from existing bags. How much capital or how much liquidity you need to start using this strategy? Same amount in BTC (or primary coin) of one of your bags: say you have a list of 10 bags > deposit BTC (or primary coin) amount equal to ONE OF YOUR BAGS HOLDING VALUE IN BTC (i.e. if one of your bags is ETH and its value in BTC is 0.02BTC: deposit 0.02BTC), or sell one of your bags (any of your choice) at market price so to give your account an immediate liquidity, if you are unable to deposit more BTC (or primary coin). You dont need to deposit a lot of BTC (or primary coin) to average down your bags: it is enough to cover just one bag only and your GUNBOT will start a chain of bags-recovering, getting liquidity as it sells your bags. Keep this in mind by now on when you use GUNBOT: dont use all your capital, GUNBOT will need a reserve in case averaging down is needed because market conditions.
How to start GUNBOT
Windows: compile the config.js file and double click on gunthy.exe
Linux/MacOs: compile config.js file and run ./gunthy
I'm pretty sure a lot of questions will come out and i'm looking forward to all of you bugging me 24/7 on forums and Telegram...but this is why we love GUNBOT!
Please report any bag immediately!!!
Thanks!
~Gun
49
General Discussion / Gunbot 3.3.2 - Poloniex/Bittrex Patch
« on: June 04, 2017, 10:18:31 PM »
Gunbot 3.3.2 - Poloniex/Bittrex Patch
@GuntharDeNiro GuntharDeNiro released this 3 minutes ago
Changelogs:
-Bump Bittrex to v3.3.x
-fix multiple buy on bittrex
-fix "waiting to sell" at zero balance if obsolete sell orders were deleted
Instructions:
- Just replace executables.
Config changes:
-Bittrex has now 3 levels on STEPGAIN
-Beware: api/secret input has changed in v3.3, they are now in the "market settings" section. Beware what you write there!
Tips:
-Bittrex is not checking nonce for now....you can try to speed up your bot even with a lot of pairs
Please report any bug immediately
Thanks!
~Gun
@GuntharDeNiro GuntharDeNiro released this 3 minutes ago
Changelogs:
-Bump Bittrex to v3.3.x
-fix multiple buy on bittrex
-fix "waiting to sell" at zero balance if obsolete sell orders were deleted
Instructions:
- Just replace executables.
Config changes:
-Bittrex has now 3 levels on STEPGAIN
-Beware: api/secret input has changed in v3.3, they are now in the "market settings" section. Beware what you write there!
Tips:
-Bittrex is not checking nonce for now....you can try to speed up your bot even with a lot of pairs
Please report any bug immediately
Thanks!
~Gun
50
General Discussion / GUNBOT v3.3.1 - Poloniex patch
« on: June 04, 2017, 01:04:12 AM »
GUNBOT v3.3.1 - Poloniex patch
@GuntharDeNiro GuntharDeNiro released this 16 minutes ago
Please use this on poloniex only.
Changelogs:
- fix nodemailer: you can get an email alert with no funds on wallet (settings in pair's config file or ALLPAIRS params.js)
- if we don't have assets, we don't need the security margin set to the last bought price: make it fluctuate with the market price
- fix multiple buy
- tuning price to sell with BB strategy
- mitigating errors 422 and 429.
- sending lib.mark for EMA1 and EMA2 on console.logs
- bump color and debug consoles to the latest v3.3
- introducing "Night Vision" GUI
- cleanup debug console every 30 minutes so we don't get stuck with huge logs buffer
- add some anchor to GUI panels
- attempt to use askmike's solution to add some padding to nonce
Please report any bug immediately
Thanks!
~Gun
@GuntharDeNiro GuntharDeNiro released this 16 minutes ago
Please use this on poloniex only.
Changelogs:
- fix nodemailer: you can get an email alert with no funds on wallet (settings in pair's config file or ALLPAIRS params.js)
- if we don't have assets, we don't need the security margin set to the last bought price: make it fluctuate with the market price
- fix multiple buy
- tuning price to sell with BB strategy
- mitigating errors 422 and 429.
- sending lib.mark for EMA1 and EMA2 on console.logs
- bump color and debug consoles to the latest v3.3
- introducing "Night Vision" GUI
- cleanup debug console every 30 minutes so we don't get stuck with huge logs buffer
- add some anchor to GUI panels
- attempt to use askmike's solution to add some padding to nonce
Please report any bug immediately
Thanks!
~Gun
51
Technical Support & Development / Bugs/Issues tracker v3.3.2
« on: May 30, 2017, 09:49:08 PM »
Here as usual all yrou reports of bugs/issues features requests for the v3.3.2
Thanks!
~Gun
Thanks!
~Gun
52
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
53
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
54
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!
55
Technical Support & Development / Bugs/Issues tracker v3.2
« on: May 11, 2017, 11:01:31 PM »
This post is for your reports about bugs/issues to be fixed in the actual 3.2 version for all strategies. Please report any bug here, possibly with console screenshots or detailed description of the bug/issue. I will not answer here but i will answer with improved/fixed code: i'll use this post as a list of "to-do" things and reminder and i will tag [SOLVED] any fixed report of yours once i found the solution. I'll delete posts that are reporting "not reproducible" bugs, such as user's errors/misconfigurations and such: if you see your post deleted, please post it again in Beginners and Help, you will receive answers there.
Thanks!
~Gun
EDIT: please notice that this post is highly moderated to keep it cleaned up from off topics. This is a bug tracker, post your help/support requests on other boards or in PM.
Thanks!
~Gun
EDIT: please notice that this post is highly moderated to keep it cleaned up from off topics. This is a bug tracker, post your help/support requests on other boards or in PM.
56
General Discussion / Gunbot 3.2 - Core edition: Windows(no GUI)/Linux/MacOs/armv6/armv7 - Release nam
« on: May 11, 2017, 10:49:48 PM »Gunbot 3.2 - Core edition: Windows(no GUI)/Linux/MacOs/armv6/armv7 - Release name "Portugal"
This is the core edition of the v3.2- all os/cpu are supported headless without GUI. This release is a great improvement on algo and strategies: all reported bugs of v3.1 has been fixed/improved. Thanks to all contributors of https://gunthy.org
Changelogs:
-Increasing the power of BB strategy with the following algo: StepGain, Gain, PingPong. You can now mix the 4 strategies as you wish on the 3 supported markets: Bittrex, Kraken, Poloniex.
Here are the possible algo you can use:
Pure BB: the BB formula has been improved, it now shows good values and it is not
consuming the amount of CPU it used in v3.1. I suggest to start with 30 lowBB and
30 highBB values and then tune them on the fly for each coin. You can restart the
bot whenever you want: it will remember the BB. To use this strategy set
BUY_STRATEGY: 'BB' and SELL_STRATEGY: 'BB' in your config files.
Pure STEPGAIN: BUY_STRATEGY: 'STEPGAIN' and SELL_STRATEGY: 'STEPGAIN' in your config files, will give you the power to explore up and down until the bot finds the best price to buy and the highest price to sell (supergun trend watchdog applies with improved algo). All of this on all 3 markets: Bittrex, Kraken, Poloniex. We have now 2 levels of BUY and 2 levels of SELL only in config files, since the third has not been really useful. Set BUYLVL and SELLLVL to the right level you want to use. Example: if you have BUYLVL1 to 3 and BUYLVL2 to 5, set BUYLVL to 2 if you want to explore from to 5%to infinite, or set BUYLVL to 1 if you want to explore from 3% to infinite.
Pure GAIN: BUY_STRATEGY: 'GAIN' and SELL_STRATEGY: 'GAIN' in yoru config files will give you the power to explore from BUY_LEVEL % to infinite and from GAIN % to infinite. For example: if you set BUY_LEVEL to 3 and GAIN to 5, it will buy at 3% or more (supergun trend watchdog applies) and it will sell at 5% or more (again supergun trend watchdog applies). All of this in all markets: Bittrex, Kraken, Poloniex.
Pure PINGPONG: set a price to buy and a price to sell in PINGPONG_BUY and PINGPONG_SELL config values and your bot will continuosly buy at PINGPONG_BUY price or lower and sell at PINGPONG_SELL or higher. Supergun trend watchdog applies and this strategy is available in all markets: Bittrex, Kraken, Poloniex
Any MIX of above strategies: you can set BUY_STRATEGY and SELL_STRATEGY values to any mix you want. For example you can buy with BB and sell with PINGPONG, or you can buy with PINGPONG and sell with GAIN, or BUY with STEPGAIN and sell with GAIN, and so on. Any mix you use, supergun trend watchdog will always help you to get a lower price to buy and an higher price to sell of what you put in configs: all of this on all markets, Bittrex, Poloniex, Kraken.
Bugs fixed and improvements:
All reported bugs at https://gunthy.org and in the Telgram group, have been refactored and fixed, especially the following:
-CPU and RAM leak on BB
-Fixed BB formula and reverted back to 2 as multiplier
-Fixed supergun trend watchdog not switching: we have now a separated MAX_LATEST_PRICES (which is used for BB) and MAX_LATEST_PRICES_TREND (which is used for supergun. I suggest to use 300 prices for BB and 30 prices for supergun trend.
-There is now a config file which can be used to change values for ALL PAIRS: for example, you want to change the BOT_ON_FAIL_DELAY for all pairs but you dont want to open all config files > open ALLPAIRS-params.js and set it like this:
Code: [Select]
var config = {
BOT_ON_FAIL_DELAY:(1000)*5
}; module.exports = config;
then save the file and all your pairs will change that value on the fly. You can put in the ALLPAIRS-params.js any value that is included in the traditional config file, so you are allowed to change any value you want at once.
-Fixed DASH and GNO pairs on Kraken
-Fixed deleting old BUY orders from order book
-Fixed BUY of tiny amounts
-Fixed email alerts: it now works again
-Code cleanup and refactoring of outputs: the save.json file outputs all variables every X seconds you put in bot delay time. With this feature you can build your own plugin, GUI, app based on yoru gunbot.
-Introducing dynamic reading
How to migrate from 3.1 to 3.2
1.- Move all your save.json files from the 3.1 folder to the new 3.2 folder
2.- Start your bot
How to start 3.2
This version is packaged: you dont need to install anything, it is all there. No node.js, no .NET, anything: the bot knows what to do.
Windows: your GUI will come in the next days, i know a lot of you are already using it with no GUI so here to you
Code: [Select]
gunthy.exe BTC_ETH poloniex
gunthy.exe BTC_ETH kraken
gunthy.exe BTC_ETH bittrex
Linux: chmod +x this file > gunthy-linux and then run it like this
Code: [Select]
./gunthy-linux BTC_ETH poloniex
./gunthy-linux BTC_ETH kraken
./gunthy-linux BTC_ETH bittrexMacOs and Arm: i have built on those CPU the gunthy-mac and gunthy-arm files to start like Linux
CONFIG FILES
We have now a separated config file for each market and a params file you can use to change any value you want in all pairs, as described above. Here are the config files names:
Code: [Select]
poloniex-BTC_ETH-config.js
kraken-BTC_ETH-config.js
bittrex-BTC_ETH-config.js
ALLPAIRS-params.jsIn ALLPAIRS file you can move any value you want directly from config.js files. Simply copy/paste those values from config.js file to ALLPAIRS and save ALLPAIRS. All your bots will reload values yu cahnged/added to ALLPAIRS.
Here are the values in config and a brief explanation:
Code: [Select]
var config = {
// DEBUG
DEBUG_LOG:true,
I_REALLY_WANT_IT:false,
BUY_SMALL_PORTION:1,
INSUFFICIENT_FUNDS_ON_SELL_FIX: 0.0005,
INSUFFICIENT_FUNDS_ON_BUY_FIX: 0.0005,
//-----------------------------------------------
// STARTUP OPTIONS
//-----------------------------------------------
SELL_ON_START:false,
CANCEL_SELL_ORDERS_ON_START:false,
CANCEL_BUY_ORDERS_ON_START:false,
CANCEL_OPEN_ORDERS_ON_START:false,
MAX_LATEST_PRICES: 200,// limit of latest prices to analyze to determine if price is growing or falling
MAX_LATEST_DIRECTIONS:30,// limit of latest price directions ,used in supergun detection
MAX_LAST_ORDERS:5, // keeping last orders bought
PERIOD: 15, // candlestick period
SAVEFILE_SUFFIX: '-save.json',
//-----------------------------------------------
// PRIMARY SETTINGS
//-----------------------------------------------
DEFAULT_MARKET_NAME:"poloniex",
DEFAULT_CURRENCY_PAIR:"BTC_ETH", // single pair format for all markets !
BUYLVL1: 3, //buy when the price drops by this percentual or lower if BUYLVL is 1
BUYLVL2: 12, //buy when the price drops by this percentual or lower if BUYLVL is 2
SELLLVL1: 2, //sell when the price drops by this percentual or higher is SELLLVL is 1
SELLLVL2: 70, //sell when the price drops by this percentual or higher is SELLLVL is 2
BUYLVL: 2, //possible values 1 and 2 (if you want to buy at level 1 or level 2)
SELLLVL: 2, //possible values 1 and 2 (if you want to sell at level 1 or level 2)
BUY_STRATEGY: "BB", // accepted values BB or STEPGAIN or GAIN or PINGPONG
SELL_STRATEGY: "GAIN", // accepted values BB or STEPGAIN or GAIN or PINGPONG
LOW_BB: 5, //buy when the price is higher than low BB by this percentual
HIGH_BB: 5, //sell when the price is lower than high BB by this percentual
PINGPONG_BUY: 0.001, //price to buy (or lower) in the ping pong strategy
PINGPONG_SELL: 0.002, //price to sell (or higher) in the ping pong strategy
BUY_LEVEL: 0.1, // If GAIN buy strategy is used, buy at this percentual below lower ema value
GAIN: 0.1, // If GAIN sell strategy is used, sell at this percentual above bought price
BTC_TRADING_LIMIT: 0.01,// max amount of BTC balance to use for each pair
SECURITY_MARGIN: 60, // sell all balance if currency decreases x% after you bought it
MIN_VOLUME_TO_BUY: 0.0005, // bitrex min volume
//---BITTREX
BITTREX_KEY:'',
BITTREX_SECRET:'',
BITTREX_PRICE_METHOD:'ohlc',// ohlc OR vwa "price to buy" definition method
BITTREX_VWA_1_INTERVAL: 10,// weighted average interval in minutes
BITTREX_VWA_2_INTERVAL: 120,// weighted average interval in minutes
//---KRAKEN
KRAKEN_ASSET_PAIR:'XETHXXBT',
KRAKEN_KEY: '',
KRAKEN_SECRET: '',
KRAKEN_PRICE_METHOD:'vwa',// ohlc OR vwa "price to buy" definition method
KRAKEN_VWA_1_INTERVAL: 1,// weighted average interval in minutes
KRAKEN_VWA_2_INTERVAL: 15,// weighted average interval in minutes
//---POLONIEX
POLONIEX_KEY: '',
POLONIEX_SECRET: '',
POLONIEX_PRICE_METHOD:'vwa',// ohlc OR vwa "price to buy" definition method
POLONIEX_VWA_1_INTERVAL: 0.02,// weighted average interval in hours
POLONIEX_VWA_2_INTERVAL: 0.04,// weighted average interval in hours
//-----------------------------------------------
// BOT TIMINGS
//-----------------------------------------------
API_CALLS_DELAY:777,
BOT_SLEEP_DELAY:(1000)*10,// bot cycle delay (koef*sec)
BOT_MAX_LIFETIME:999999999,// overall bot lifetime(koef*min),
BOT_ON_FAIL_DELAY:(1000)*5, // bot repeat cycle delay if previous cycle failed (koef*sec)
//-----------------------------------------------
// EMAIL
//-----------------------------------------------
ALERT_ON_NO_FUNDS:false, // email on insufficcient funds
SMTP_EMAIL: '%40@gmail.com',
ALERT_EMAIL:'********',
SMTP_PASSWORD: '**********',
SMTP: true,
SMTP_PROTOCOL: 'SMTPS',
SMTP_HOST: 'smtp.gmail.com',
//-----------------------------------------------
// OUTPUT
//-----------------------------------------------
MAX_LATEST_PRICES_SHOWN: 0, // limit of latest prices to show in console.log
SHOW_LASTEST_DIRECTIONS:false, // show chart in console
MAX_LATEST_DIRECTIONS_SHOWN:0, // chart height
LASTEST_DIRECTIONS_LIST_WIDTH:0, // chart width
//-----------------------------------------------
// OTHER (might be deprecated/not in use)
//-----------------------------------------------
BTC_BALANCE: 2// btc balance for test purposes,
};
module.exports = config;
This is all folks (for now). Keep reporting everything you notice and/or improvements because, as you can see, you are listened.Thanks!
~Gun
57
General Discussion / Set Kraken and Bittrex SELL level at least 2%
« on: May 04, 2017, 09:53:57 PM »
It seems like kraken and bittrex are using something called "average" last price when we ask for last price on their API: in this condition, if you set sell level too low (say at 1%) and we are not fast enough to get the "last price" it can easily and fastly drop at 0.25% for example, because it is not a real last price but an "average".
So, until i will not get an answer from the ticket support i open on their desks, please set kraken and bittrex GAIN at least 2% (or higher if your trading style is fine with it).
Thanks!
So, until i will not get an answer from the ticket support i open on their desks, please set kraken and bittrex GAIN at least 2% (or higher if your trading style is fine with it).
Thanks!
58
General Discussion / MOVED: feature request: reload config on SIGHUP / CONFIG_FS_WATCH:false
« on: May 03, 2017, 01:50:45 AM »
This topic has been moved to Technical support & Development.
https://gunthy.org/index.php?topic=218.0
https://gunthy.org/index.php?topic=218.0
59
General Discussion / Release v3.1 - x3 GUI Edition - Windows/Linux/Mac/ARM - All CPUs
« on: April 25, 2017, 05:13:29 PM »Release v3.1 - x3 GUI Edition - Windows/Linux/Mac/ARM - All CPUs
(the x3 profit multiplier)
This is a major release. If you want to start old pairs from 2.x with the new Bollinger Band do the following (otherwise you can run the STEP_GAIN strategy by just copy/pasting old save.json files into the new x3 folder):
1- Copy all your "BTC_XXX-save.json" file to the new GUNBOT folder
2- Rename all your "BTC_XXX-save.json" file to "poloniex-BTC_XXX-save.json"
Windows users just start GUNBOT.EXE.
Linux/MAC/ARM (Pi2/Pi3 only) start from command line with following commands:
"node BB BTC_ETH poloniex" for poloniex market on Bollinger Band strategy
"node BB BTC_ETH kraken" for kraken market on Bollinger Band strategy
"node BB BTC_ETH bittrex" for bittrex market on Bollinger Band strategy
"node stepgain BTC_ETH" for poloniex market on STEP_GAIN strategy
"node 1000trades" for poloniex market on 1000trades strategy
"node supergun" for poloniex market on Russian Roulette strategy
Here are the config files for each strategy (Linux/Mac/ARM only):
BB-BTC_XXX-config.js for Bollinger Band strategy pairs
BTC_XXX-config.js for STEP_GAIN strategy pairs
config.js and params.js for 1000trades and supergun strategies pairs.
By this edition there is an initial commit for API development: the BTC_XXX-save.json file, dumps all variables from the bot every X seconds (bot delay) and you can use them all for your own data plugin.
Pre-requisites and environment:
You need node installed (you should already have it installed from 2.0.4b. If this is not the case, install the latest node (actually 7.9). The package already includes all node_modules. You can run "npm install" if you wish to update to the latest modules in the future. After installation, if you get some errors for missed npm modules, run again the command for the missed module only. For example: "npm install request" (if you got an error for missed "request" module. Or: "npm install mathjs" if you received an error about missed mathjs module.
Changelogs:
Embedding all profitable strategies in Windows GUI and Linux/Mac/ARM package
Fix "Bought price not set!!!!" bug.
Better CPU profiling to make AWS users happier
Code cleanup and refactor.
Known issues:
Some Kraken pairs are actually giving an error (DASH and fiat) and accordingly to their public API call, some of them are retrieving errors directly from their API code > https://api.kraken.com/0/public/Assets
I am working on it.
Please report any bug immediately !!!!
Thanks!
~Gun
60
General Discussion / GUNBOT v3.1 - Release name: "x3"
« on: April 19, 2017, 10:42:09 PM »GUNBOT v3.1 - Release name: "x3"
(the x3 profit multiplier)
I'm proud to announce a great target the entire GUNBOT community reached: the GUNBOT x3 edition. This edition is the result of the hard work and efforts of over 300 people that continuously cooperated in the past 4 months to improve, suggest code, test and finance, the first automatic trader with a unique feature: its stable profit income. All users reports, ideas, enthusiasm have been melted in a single product which is now able to multiply the invested amount of BTC in multiple exchanges platforms: Bittrex, which is rich of unexplored and impressive altcoins, Kraken with the highest "volume/number of pairs" rate, and Poloniex, the largest lab for all cryptocurrencies lovers.
How does the x3 Edition work?
It's highly customizable settings, allow you to decide how to move on the markets: the concept is basic but the algorithm behind it, is one of the most backtested and profitable, buy low and sell high. How? The Bollinger Band indicator has been implemented: short-ema, long-ema, and volume weighted price are now confirming what we need to know. The price is low enough > we need to buy OR The price is high enough > we must sell!
What settings am I allowed to change?
If you used the Poloniex GUNBOT you know what was missed: a real indicator of a low price to buy at. This user has described this procedure better than me:
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 :-)
So how does it work exactly?
You have 2 options: use pure Bollinger Band or a mix of %GAIN and Bollinger Band:
- You can set a percentual value from the lowest Bollinger Band, which will be your buy area: I want to buy only when there is a dump that reaches 20% of the bottom Bollinger Band area. The % value is customizable.
- You can set a percentual value from the highest Bollinger Band, which will be your sell area: I want to sell only when there is a pump that reaches 20% of the top Bollinger Band area. In this way you will always buy at the lowest values of BB and sell at the highest, generating so very high profits per trade
- You can decide to buy using Bollinger Band and sell at a defined % from the bought price: I buy soon as the dump is over in the 20%
lowest Bollinger Band and I sell soon as I reach %GAIN I set in configs
Are all other features we had in the Poloniex GUNBOT implemented?
Yes, they are. The final tuning for the "manual trades" tho, is not complete yet, that's the only feature I am not satisfied with (yet), so the final job will be in the 3.2 release.
Ok you got me: how do i buy it?
The GUNBOT x3 edition comes with different packages:
- The Family pack: if you bought the Poloniex GUNBOT before 20 April 2017, you are considered a "contributor". You can have 50% off discount on the Kraken license and the Bittrex license: 0.1BTC for both licenses
- The Estimator pack: if you didn't buy the Poloniex GUNBOT because you were waiting for Kraken or Bittrex exchange, you are considered an "estimator". You can have 50% off discount on the second and third exchange license: 0.1BTC for the first exchange, 0.05BTC for the second, 0.05BTC for the third
- New Gun pack: the new Guns can purchase each license at 0.1BTC each one. You can buy either Poloniex or Bittrex or Kraken license (and you can upgrade later to one of the other packages).
Currently selling Linux version only
The process of license distribution is split in the next days: actually, only Linux users will receive their copy. In the next 2 days, Windows users will receive their copy too. This is because licensing all the API keys will take time: please be patient and allow me to secure your GUNBOT copy and to protect it from leakers and lurkers: your GUNBOT has a value and we must take care of it.
Please PM me in this forum with your desired exchange and your public API key. Wait for a unique BTC address to deposit the license cost and notify me by PM with the transaction id. In this initial state, i will send copies every 3 hours.
Thank you for your patience, contribution and help: we are making the perfect money machine, together.
~Gun