Username: Password:

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.


Messages - ruphus

Pages: 1 [2] 3
21
General Discussion / Re: XT stopped working
« on: December 11, 2017, 03:38:19 AM »
You tried reboot ?

Had the same error during the week-end.

First reboot
then update && upgrade
then update gb

nothing helps. still there just nothing happening at all.

any idea what might be the reason? I mean it stopped working from the one minute to the other after gb has been running for weeks i think.

22
General Discussion / Re: XT stopped working
« on: December 11, 2017, 02:13:31 AM »
6.0.2 worked!  I just dropped in the old config in the folder and off it goes!  Pretty sure the old log is gone now, but better than nothing.

I updated - a new done with all new files.
I configured the new config with my old data (and some changes).
Again: nothing whatsoever after executing.....

23
General Discussion / Re: XT stopped working
« on: December 10, 2017, 04:29:50 PM »
updated to 602... still the bot is not doing anything.

i am on a linux VPS. after starting "gunthy-linx64" nothing happens. no error message, no "loading config..." no nothing.

great

24
General Discussion / Re: XT stopped working
« on: December 10, 2017, 12:58:15 PM »
same things happened to me. i will try out 602 now.

anyway: if a new versions lets the old one stop working, why the heck is that not being promoted in the forum or via mail or whatsoever?!

25
General Discussion / Re: XT version sending/receiving a TON of data
« on: December 04, 2017, 09:59:16 AM »
Interesting question

26
Technical Support & Development / Xtreme GUI - https not working on VPS
« on: November 16, 2017, 09:47:41 AM »
Hey guys,

for some curiosity I can only reach the Xt GUI through http and port 5000 (with VPS ip). Even though my config says port 5001 and hostname my external IP. With this config I reach the GUI only with my IP(http):5000 (not 5001).

Anyone know what is wrong here?

Greetings


27
General Discussion / Re: gb 6 memory usage ,,,,
« on: November 13, 2017, 01:52:17 AM »
Upgraded today, running 25 Pairs - currently running without big memory usage on VPS

28
General Discussion / Re: Gunbot XT Edition + Gunthy GUI
« on: November 09, 2017, 03:43:38 PM »
Is this an upgrade or is this a wholly separate product?

Same question here. Is this an upgrade included within the prior purchased versions?

29
In the end I downgraded to 4.05, which is running now. Additionally I manually got rid of most bags and sold most pairs by hand to get something like a clean start.

Now it is trading again. Thank you for any help. I will not update to any 5.x version for now...

30
Hey Guys/Botters,

since 5.055 is not running properly (empty response - other threat) I started 5.04 again. I did some little changes in my config, but I can not get, why it is not trading at all now for days...

The Console even says things like
"There are some trading opportunities for XXX_XXX at poloniex. Scanning history...""
and
"Tips&Tricks: XXX_XXX can be sold!!!"
Only warning I can find is: "WARNING: We coulnt get a BOUGH_PRICE for XXX_XXX. Please manually override it using config.js"
Does this error mean, that I need to manually put a BOUGHT_PRICE for every pair I use?!

I would be glad if someone finds any crucial errors in my bb-config. (most pairs run bb, some stepgain, some bbstepgain, some bbgain)

this config is for vers. 5.04
Code: [Select]

"bot": {
"debug": false,

"period_storage_ticker": 2000,
"interval_ticker_update": 25000,

"timeout_buy": 60000,
"timeout_sell": 60000,

"WATCH_MODE": false,
"VERBOSE": false,
"TV_GAIN": 0.6,
"TV_TRADING_LIMIT": 0.001,
"BOT_DELAY": 13
},
"strategies": {
                    "bb": {
"BTC_TRADING_LIMIT": 0.005,
"PERIOD": 15,
"EMA1": 2,
"EMA2": 4,
"GAIN": 1.0,
"HIGH_BB": 42.5,
"LOW_BB": 42.5,
"STDV": 2,
"SMAPERIOD": 30,
"PANIC_SELL": false,
"DOUBLE_UP": false,
"STOP_LIMIT": 97.5,
"BUY_ENABLED": true,
"MIN_VOLUME_TO_BUY": 0.0001,
"MIN_VOLUME_TO_SELL": 0.0001
},

Greetings

31
I'm getting a lot of "Empty response from exchange...retrying again..."
... Same here on Poloniex. No trades in the past and frequently seeing that mentioned message.
Code: [Select]
"bot": {
"debug": false,
"BOT_DELAY": 13,
"interval_ticker_update": 25000,
"period_storage_ticker": 2000,
"timeout_buy": 60000,
"timeout_sell": 60000,
"TV_GAIN": 0.6,
"TV_TRADING_LIMIT_BUY": 0.001,
"TV_PYRAMID": false,
"TV_TRADING_LIMIT_SELL": 0.001,
"TV_PROTECTION": true,
"RETRY_TV_ORDER": false,
"VERBOSE": false,
"WATCH_MODE": false
}

"bb": {
"TRADING_LIMIT": 0.001,
"PERIOD": 15,
"BUY_LEVEL": 0.1,
"GAIN": 0.6,
"EMA1": 2,
"EMA2": 4,
"HIGH_BB": 43,
"LOW_BB": 43,
"STDV": 2,
"SMAPERIOD": 20,
"BUYLVL1": 0.9,
"BUYLVL2": 2.5,
"BUYLVL3": 10,
"SELLLVL1": 0.6,
"SELLLVL2": 2,
"SELLLVL3": 4,
"BUYLVL": 3,
"SELLLVL": 3,
"LASTPOINTS": 6,
"AVGPOINTS": 75,
"AVGMINIMUM": 0.00000001,
"GUNTHY_API": false,
"PP_BUY": 0.00000001,
"PP_SELL": 0.12345678,
"PANIC_SELL": false,
"DOUBLE_UP": false,
"STOP_LIMIT": 60,
"BUY_ENABLED": true,
"MIN_VOLUME_TO_BUY": 0.0001,
"MIN_VOLUME_TO_SELL": 0.0001
}

32
thank you from me as well!! :)))

33
On Win 10 I have encountered the same errors on 3.x.x versions. In the end I am using a Linux VPS with 4.0.5 now and it runs just fine.

34
General Discussion / Re: My first results with Gunbot 4.0.1 patch #4013
« on: August 20, 2017, 05:01:16 PM »
How can your 4.0x actually buy/sell without all those "error undefined is not a function" errors ?! ... BB and BBSTEPGAIN let my v4.04 pop up with those errors every now and then. and further on it buys more than the BTC limit was set to.

35
Why the use of 45 for BB ? Seems pretty agressive and ends up paying much higher isn't it? Or I misunderstand the 45?

Thank you

I am mainly still trying out some different configs. This one would buy more aggressive, yes. But I am often watching nothing to happen eventhough the market looks very good for some trades. This way I want to force the bot to do more buys and then sell em with stepgain.

36
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 20, 2017, 02:16:48 AM »
GB v4.04 buys way too much and ignores the max BTC limit:

ETC/BTC   Buy   Exchange   0.00324000   3.06911745   0.00767279 ETC (0.25%)   0.00994394   19.08.17 23:54
BTS/BTC   Buy   Exchange   0.00003005   24.74418605   0.06186047 BTS (0.25%)   0.00074356   19.08.17 23:53
BTS/BTC   Buy   Exchange   0.00003019   313.36560084   0.78341400 BTS (0.25%)   0.0094605   19.08.17 23:53
ETC/BTC   Buy   Exchange   0.00324951   3.07680947   0.00769202 ETC (0.25%)   0.00999812   19.08.17 23:45
BTS/BTC   Buy   Exchange   0.00003011   169.26647654   0.42316619 BTS (0.25%)   0.00509661   19.08.17 23:11
FCT/BTC   Buy   Exchange   0.00510135   1.94951169   0.00487378 FCT (0.25%)   0.00994514   19.08.17 23:05
FCT/BTC   Buy   Exchange   0.00514091   0.42307147   0.00105768 FCT (0.25%)   0.00217497   19.08.17 23:05
FCT/BTC   Buy   Exchange   0.00516965   1.18777630   0.00296944 FCT (0.25%)   0.00614038   19.08.17 22:47


adds up to

FCT   0.01826049
BTS   0.01530067
ETC   0,01994206

even though the limit should be 0.01 BTC    :-(
I better stop using v4.04 now. who know what GB will buy in future :D

Pair:
Code: [Select]
"BTC_BTS": {
"strategy": "bb",
"override": {"BTC_TRADING_LIMIT": 0.005, "BOUGHT_PRICE": 0.00005899}
},
"BTC_ETC": {
"strategy": "bb",
"override": {}
},
"BTC_FCT": {
"strategy": "bb",
"override": {"BOUGHT_PRICE": 0.00841000}
},

strategy:
Code: [Select]
"bb": {
"BTC_TRADING_LIMIT": 0.01,
"PERIOD": 15,
"GAIN": 1.6,
"HIGH_BB": 45,
"LOW_BB": 40,
"PANIC_SELL": false,
"DOUBLE_UP": true,
"STOP_LIMIT": 60,
"BUY_ENABLED": true,
"MIN_VOLUME_TO_BUY": 0.001,
"MIN_VOLUME_TO_SELL": 0.001
},

37
Technical Support & Development / Re: Trailing stop loss feature request
« on: August 19, 2017, 09:02:10 PM »

EDIT: I heard a better idea from another user. In fact, I think it's better to "trail" the stop-loss a user configurable percentage of price behind. So, for example, if we set "TRAILING_PERCENT_SELL" to like 1% for example. Now if we bought at 100 and are going to sell at 105, the stop is set at 105 - (105 * 0.01) = 103.95, and as the price rises, the size of the trailing stop increases in absolute terms, so if price rises to 200, now the stop is at 200 - (200 * 0.01) = 198, so now we are risking 2 units of profit vs 1.05 units earlier, but it's still 1%. This makes sense, because as we get a bigger and bigger gain on the trade, we may wish to be more agressive about risking a bit more of that gain to make even more - we already locked in a big profit, so why not "let it ride" a bit more.


I'd suggest slightly different approach (allowing for higher shortterm variation of coin price) with the following configuration parameters:
1. Gain after which trailing stop is triggered --> e.g. if we set to 5%, and we bought at 100, trailing stop would activate at 105
2. Max loss of profit allowed from the best observed price --> e.g. if we set it to 20%, the following will happen:
 - trailing stop activated at 105, while the best price observed was 105. Current profit is 5, with 20% of it considered OK to lose. Bot would sell if price drops below 104.
 - price keeps rising, the best observed is 110. Difference between best observed and bought is 10, with 20% of it considered OK to lose. Bot would sell if price drops below 108.
 - price keeps rising, the best observed is 200. Difference between best observed and bought is 100, with 20% of it considered OK to lose. Bot would sell if price drops below 180.
 - price drops a little to 190. The best observed is still 200. Difference between best observed and bought is 100, with 20% of it considered OK to lose. Bot would sell if price drops below 180.
 - etc.

What do you think?

And possibly, there is 1 more potential improvement that could be considered.
In above example, if bot should sell if price drops below 104 --> this means bot could create a stop-limit order to sell.
Once "best observed" rises, bot could cancel previous stop-limit order and create a new one, at higher values.

This approach has 2 advantages:
1. We pay smaller fees (on polo it's 0.10% difference)
2. We are safe from possible bot / network crashes

+1 for any of those functions! those functionality would make gunbot even more golden!

38
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 19, 2017, 07:06:14 PM »
After a while GB 4.04 seems to run VERY high on CPU usage - as high as up to 99 - 100% and stays here...



EDIT
It went  down again to normal amounts of CPU usage, but nevertheless there seems to be something wrong. maybe it has to do with those undefined function errors @bbstepgain

EDIT2
and up again to 100% ...

39
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 19, 2017, 06:39:21 PM »
Also have this errors

Error on strategy BB_STEPGAIN for BTC-LTC on bittrex while getting ema2 -\ Error: undefined is not a function

Error on strategy BB for BTC-LTC on bittrex while getting ema2 -\ Error: undefined is not a function
...

I am experiencing the same errors with BBSTEPGAIN @poloniex pairs.
Nevertheless it is not happening all the time. After some time passed the exact same pair brings up no error of an undefined function. Maybe it has something to to, if the bot wants to sell and there are no altcoins to sell?! I assume something like this.

There is definetly something wrong with the bbstepgain strategy. I assume it is mainly happening when the bot trys to buy/sell. Right now I watched the bot, while trying to make some trade/buys (ETH_ETC), with enough ETH in stock, and throwing out the Error on strategy BB_STEPGAIN for ETH_ETC on poloniex while getting ema2 -\ Error: undefined is not a function

EDIT
Have experienced the exact same error also with the BB strategy.

40
EDIT
Ok, i figured out, that my config was wrong as I have had written several poloniex pairs, each within an own poloniex function (or how ever one call it). Now I changed it to only one poloniex {...} with several pairs within the {...}

I am watching what happens now :D


Original Post
Hey guys,

I finally got v4.04 configured, up and running. But while watching it I get confused since it over and over repeats scanning/calling/kicking the last pair out of my config (which is ETH_ETC right now). Every couple of seconds it repeats the cycle. VERY fast....

I am a little bit worried about that and scared to get my API banned ... what is happening here? since I don't even see any other pair is being worked on?!

Code: [Select]
│ ɢƱҊƁØŦ v4.0.4  │ LowBB                    │ HighBB │ Buy at │ Last │ ETH │ ETC │ Pair    │
├───────────────┼──────────────────────────┼────────┼────────┼──────┼─────┼─────┼─────────┤
│ Buy cycle     │                          │        │        │      │     │     │ ETH_ETC │
├───────────────┼──────────────────────────┼────────┴────────┴──────┴─────┴─────┴─────────┤
│ Callbacks     │ Waiting to cash some BTC │                                              │
└───────────────┴──────────────────────────┴──────────────────────────────────────────────┘
------------------------------------------------------------------------------------------------
 ɢՍÑƁØŁ v4.0.4  Scanning poloniex for trading opportunities 2017/08/19 18:56:56
------------------------------------------------------------------------------------------------
2017/08/19 18:57:03: Trend for ETH_ETC:    UP!!!   
2017/08/19 18:57:03: There are some trading opportunities for ETH_ETC at poloniex. Scanning Trade History
2017/08/19 18:57:03: Last Bid price ETH_ETC: 0.04573 | Last Ask: 0.04647083
2017/08/19 18:57:03: Balance ETH: 0.00000000
2017/08/19 18:57:03: Balance ETC: 0.00000000
2017/08/19 18:57:03: On Orders ETC: 0.00000000
2017/08/19 18:57:03: Trend for ETH_ETC:    UP!!!   
Processing strategy BB_STEPGAIN for ETH_ETC on poloniex
┌───────────────┬──────────────────────────┬────────┬────────┬──────┬─────┬─────┬─────────┐
│ ɢՍҊɮםŁ v4.0.4 │ LowBB                    │ HighBB │ Buy at │ Last │ ETH │ ETC │ Pair    │
├───────────────┼──────────────────────────┼────────┼────────┼──────┼─────┼─────┼─────────┤
│ Buy cycle     │                          │        │        │      │     │     │ ETH_ETC │
├───────────────┼──────────────────────────┼────────┴────────┴──────┴─────┴─────┴─────────┤
│ Callbacks     │ Waiting to cash some BTC │                                              │
└───────────────┴──────────────────────────┴──────────────────────────────────────────────┘
------------------------------------------------------------------------------------------------
 ɢƱŋɃ๏Ł v4.0.4  Scanning poloniex for trading opportunities 2017/08/19 18:57:03
------------------------------------------------------------------------------------------------



Greetings

Pages: 1 [2] 3