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 - allanster

Pages: 1 2 3 [4] 5
61
Beginners & Help / Re: Starting Amount
« on: July 06, 2017, 10:55:18 AM »
Prepare for information overload and a lot of digging. Definitely join the Telegram group. Run a free proxy (works great) https://gunthy.org/index.php?topic=570.0 or pay for proxy (some extra cool features) https://gunthy.org/index.php?topic=491.0

I just bought Sjakil's GUI last night and it is phenomenal to use. I can't get over how sleek and functional it is... https://gunthy.org/index.php?topic=336.0

66
Beginners & Help / Re: GUNBOT V3 FOR MAC OS X
« on: July 03, 2017, 05:15:47 PM »
Awesome info. Thanks so much! I'm brand new to all of this and you've helped piece some of this together for me.

Does your random timing affect profitability?

Random timing is to aid with 422 errors on Poloniex, it is to stagger the delays between pairs so that they don't clash their API calls...

For Bittrex however, where 422 problems don't occur, I use 3 second delays, and they are not randomly generated. I also run 5 minute candles and the appropriate parameter changes. I am yet to test if this works better than the previous settings due to the recent bearish reversal trends, for which I am compensating for with increased SG buy levels, however I will keep people updated with my results.

When you say appropriate parameter changes, could you be more specific like what sma/ema1/ema2 is appropriate for 5 min candles?

67
Technical Support & Development / Re: Bugs/Issues tracker v3.3.2
« on: July 03, 2017, 01:14:24 PM »
I'm being told by someone way smarter than me that this issue is a Polo being overwhelmed issue and not a Gunbot issue. I'm hoping that's the case, I'm seriously excited about Gunbot's potential.

It should come with a hazard warning though, I've only slept about 12 hours total in the last 4 days! Something like...

Caution: Sleep deprivation may be caused by using Gunbot!

68
Technical Support & Development / Re: Bugs/Issues tracker v3.3.2
« on: July 03, 2017, 08:00:05 AM »
Okay,

I'm a new customer and was emailed link for 3.3.2 to use. After reading 5 pages in here this build is scaring the crap out of me.

Started:     6/29/17 @ 1PM

Poloniex:    Dedicated child account funded with .05 BTC (not a big amount for me)

Config:       Gunthar's "How I Run" default settings using BB/BB on 10 pairs

Max Trade: .005 BTC on BB/BB default 10 pairs

First Buy:    6/29/17 @ 8:41PM!

Results:      Ran 60 hours, 14 buys (2 of which were double buys), 6 trades (+2% profit), 8 bags, 1 Max trade slot left 0.00590980

So now I'm stuck learning bag strategies with no capital to continue trading in this test account.

QUESTION - WTF is everyone doing about this? Can we downgrade, is there a more stable previous version? In hindsight I should have tested with smaller fund and that's my fault, I foolishly thought that trading software like this would be more thoroughly tested prior to release. I don't want to piss anyone off in here, I'm just being honest. I think this bot is absolutely amazing and can't wait to get my hands on the next version, but until then, just need advice on how to proceed.

Thanks!

69
@bney

Thanks for answer. I'm running on Windows 10 now and it seems really buggy. Looks like all the cool kids are doing nix. Do you know if there's a preferred or more popular flavor being used by the big guns in here?

I'm comfortable with whichever, prefer security over user friendly though.

70
What they're trying to do is the same thing I'm doing in Windows, we're trying to limit the number of connections from Gunbot to Poloniex. I just spent hours the other night testing different angles of attacking this same problem. Registry hacks, 3rd party apps, etc...

I can't speak to what their purpose is but I suppose it's the same as mine, to reduce 422 timeout errors.

I also want to prevent exceeding the 6 api calls per second rule. Problem is, I don't know how many calls are made per connection or session. So even if I limit it to one connection, I may still get 429 error.

May I ask why I see everyone limiting to 3 connections instead of 6? Has someone already figured this out?

71
Technical Support & Development / Re: Preventing 422 Errors
« on: July 03, 2017, 12:44:18 AM »
I'm curious if Gunbot is using returnTradeHistory or not? If not, why not?

If default BB is 60/120 w/300 then we must wait 5-10 hours after pair start before we can even begin trading. According to Poloniex using the call below we could have 2/3rd of that data to start with OR possibly all of it based off pulling date range.

I'm guessing from their example the date range query is using epoch time, so the question there is if it's available up to real time point or at least up to 200 trades back, Gunbot could (query the 200) + (query the 201-300 by date range) = 300 trades, and then pair could start with BB mode near instantly. See... https://poloniex.com/support/api/

returnTradeHistory
Returns the past 200 trades for a given market, or up to 50,000 trades between a range specified in UNIX timestamps by the "start" and "end" GET parameters. Sample output:

[{"date":"2014-02-10 04:23:23","type":"buy","rate":"0.00007600","amount":"140","total":"0.01064"},{"date":"2014-02-10 01:19:37","type":"buy","rate":"0.00007600","amount":"655","total":"0.04978"}, ... ]

Call: https://poloniex.com/public?command=returnTradeHistory&currencyPair=BTC_NXT&start=1410158341&end=1410499372

72
Technical Support & Development / Re: How much pairs per API?
« on: July 02, 2017, 03:20:16 AM »
In addition to timing question I'd like to know which OS. Linux?

73
Technical Support & Development / Re: double,x3 even x5 buys. why?
« on: July 02, 2017, 03:02:59 AM »
Double buy was an issue only with previous version....
I am yet to see double buy on new 3.3.2 version

I'm using 3.3.2 Poloniex 10 pair running on Win 10 64bit VM allocated with dual Xeon 8Gb ram. CPU is snoring. Only been running for 2 days.

74
I haven't noticed any lag on Coinigy but I wasn't suggesting Gunbot support trades there. My point is they have found a way to reduce 422 errors by employing multiple sub keys and multiple IP addresses. Poloniex restricts users to maximum of 6 API calls per IP. Said another way... 6 calls per API per IP. So what they've done is made it where each call is done from a different IP and a different key.

The member hawking the 0.1 BTC service on here says they are using a proxy to get 3s/3s timing in Gunbot without being banned. I'd wager their using Squid to do this. There's nothing special about just using a normal proxy, but Squid can be configured to roll each query through a different IP, thus flying under the radar.

I don't know how Gunthar feels about this, he's seemed to have a pretty firm stance on not violating the exchange restrictions. Technically this doesn't violate rule. This morning I came up with ways to limit connections to 6 for Poloniex IP's in Windows 10. This way I can test more aggressive polling without violating rules.

But I'd like to know how many "calls" each pair makes per loop. I'm snipping sessions that may not need to be limited because I don't know this answer. I may have to packet capture but I'd rather not have to take the time if someone in here knows the answer.

75
Technical Support & Development / Re: How much pairs per API?
« on: July 01, 2017, 10:41:17 AM »
@magictrade - can you please share with me your timing settings?

Thanks!

76
Beginners & Help / Re: Starting Amount
« on: July 01, 2017, 09:05:51 AM »
I'm brand new as well but I have spent days pouring over and devouring everything I can get my hands on, so I think I can answer that but others may give better answer. From what I'm seeing "average" ranges from 3-5% per trade.

Your initial investment doesn't impact how many pairs you trade with. I'm 2 days in trying something similar to what your doing. I gave Gunbot only .05 for testing/tweaking. I set max trade at 1/10 or .005 so ten trades could potentially be open at any given time.

I'm trading 10 pairs and in 36 hours with Gunthar's default "How I Run" settings Gunbot has only bought 10 times and sold 4 times so I have 6 "slots" or "max trades" available.

Once I get my feet wet and build more trust with Gunbot then I will allocate more. So far I'm thoroughly impressed with operation but there is a learning curve to be sure.

To save time for Gunthar and yourself, set up a 2nd Poloniex account now, generate API keys for both accounts, give Gunthar BOTH API keys. I did it after purchasing and had to pester Gunthar a second time to add 2nd API key, better to do it now.

You will use this 2nd account exclusively for Gunbot and you can continue using your primary as normal. This way you and Gunbot don't step on each other's toes trading and it makes accounting much easier. You just fund your 2nd wallet from your 1st (I recommend LTC for fastest/cheapest transfer).

You can optionally link it to your 1st (it only took me a couple of minutes to do, must use separate email or alias). When you go to link the 2 accounts do it from your current (original) account and your current (original) account will become the primary. The 2nd (new Gunbot) account will become a child account of your primary. 2nd account will inherit your Tier level instantly so you don't have to reverify. The only caveat to linking is your withdrawal limit is imposed on pair of accounts (you don't get to withdraw double amount).

I had very few trades first 12 hours because of 422 timeouts until I stopped, implemented ELECTRIC_WIZARD's timing tip, and restarted. I would do this before your first launch...

In your Gunbot folder you will also find a file called ALLPAIRS-params.js and yes, these settings will affect all your pairs.

I recommend you include the following lines between the curly-braces (that is these: {   }):

BOT_SLEEP_DELAY: ((1001)*90*(Math.random()*0.3+0.7)),
BOT_MAX_LIFETIME:999999999,// overall bot lifetime(koef*min),
BOT_ON_FAIL_DELAY:((1001)*120*(Math.random()*0.3+0.7)),

This randomizes your pairs so to minimize them all calling Polo at once, which will reduce your '422' and '429' error codes at times of peak server traffic. If you are suffering from these, you will want to increase the numbers between the asterisks, so perhaps 90 becomes 120 and 120 becomes 180, or you can experiment like the newly-weds you are until you find what works best for you.

77
The community could really use something like "best currencies" from earlier versions.
here's a pretty good one I used earlier for another bot before. http://boho.insomnia247.nl/td/ 
He is using some sort of point system for volatility and volume. It shows a score in the left column, then you have hourly, daily and weekly volatilty and at last volume.
 You want to choose coins with highest scores and you also wanna check that the hourly volatilty is high and weekly volatilty is low.Unfortunately this site is not running anymore.
If we then could add one more indicator which somehow could identify proper zig zag patterns in the volatility and I think we would have a pretty kick-ass tool for GUNBOT.
As you might have guessed, I have no damn clue how to whip this one together, but I am sure there are members in this community who can make this happen, for free ;)

edit: Found something that could be helpful for a dev. http://www.onlinetradingconcepts.com/TechnicalAnalysis/ZigZag.html

@bolenath - Thanks for posting this info. Very useful stuff in here.

PS... [BUMP] The site you mention IS STILL RUNNING!... http://boho.insomnia247.nl/td/

78
Technical Support & Development / Re: double,x3 even x5 buys. why?
« on: July 01, 2017, 01:49:07 AM »
Not fixed, I have a double Poloniex buy in latest build.

79
This is a tough one, not sure how you would police, but it would sure be nice for both parties if we could add/remove subkeys without having to go through Gunthar. Less work for him and less pain/wait for us.

You are policing this now by some method, I am assuming that method could be automated.

80
Technical Support & Development / Re: Getting double buys on bittrex
« on: July 01, 2017, 01:41:59 AM »
Annoying or not, IMO this violates directive for max PER trade. I guess one could argue technically that this is two trades but it still goes against implied behavior.

Pages: 1 2 3 [4] 5