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

Pages: [1]

Beginners & Help / Configuration Update: Version III - Colloquially known as “The Machine Gun”

« on: February 14, 2021, 12:33:32 AM »

Buy Method: gain
Buy Level: -10
Sell Method: gain
Gain: 0.25
Trading Limit: 100
Min Volume To Buy: 11
Min Volume To Sell: 11
Funds Reserve: 1
Period: 1
Medium EMA: 60
Fast EMA: 30
Double Up Enabled: on
DU Cap: 0.1
DU Cap Count: 12
DU Method: 0.5
DU Buydown: 0.5
TrailMe Buy: on
TrailMe Buy Range: 0.05
TrailMe Sell: on
TrailMe Sell Range: 0.05
TrailMe DU: on
Market Buy: on
Market Sell: on
Market DU: on
Trades Timeout: 0
Exchange Delay: 0

Version 3 AutoConfig:

Code: [Select]

 {
    "CheckIfBull": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "BullCheck1": {
                "type": "exact",
                "ducount": 0
            }
        },
        "overrides": {
            "TRAIL_ME_SELL_RANGE": 0.1
        },
        "clearOverrides": false,
        "schedule": "*/3 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "CheckIfNormal": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "BullCheck2": {
                "type": "biggerThan",
                "ducount": 0
            }
        },
        "overrides": {
            "TRAIL_ME_SELL_RANGE": 0.05
        },
        "clearOverrides": false,
        "schedule": "*/3 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Fast": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount1": {
                "type": "smallerThan",
                "ducount": 2
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 1,
            "TRAIL_ME_BUY_RANGE": 0.05,
            "DU_METHOD": 0.25,
            "DU_BUYDOWN": 0.25
        },
        "clearOverrides": false,
        "schedule": "*/3 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Normal": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount2": {
                "type": "biggerThan",
                "ducount": 1
            },
            "ducount3": {
                "type": "smallerThan",
                "ducount": 7
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 0.1,
            "TRAIL_ME_BUY_RANGE": 0.05,
            "DU_METHOD": 0.5,
            "DU_BUYDOWN": 0.5
        },
        "clearOverrides": false,
        "schedule": "*/3 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Slow": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount4": {
                "type": "biggerThan",
                "ducount": 6
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 0.1,
            "TRAIL_ME_BUY_RANGE": 0.1,
            "DU_METHOD": 1,
            "DU_BUYDOWN": 1
        },
        "clearOverrides": false,
        "schedule": "*/3 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    }
}

Tightening the Entry Phase:
As you can see in the new settings, I’ve brought the entry purchases back to a happy medium between the first two versions. I started looking at my graphs throughout the week and noticed that more often than not I’d only have up to two rounds of DCA before the pair profited and reset. It was close but if you counted the times between one buy one sells and then single or double rounds of DCA it was greater then the total that went all the way to round three. To me this meant I was leaving money on the table with the smaller entry purchases, something I debated in the last post.

Now it buys in with $100 but only has two rounds of 1:1 DCAs. This gets us back to the same amount of $400 before the AutoConfig kicks in and just like last time starts making much smaller 1:0.1 purchases as the market travels downwards. I’m seeing better profits this way but you do lose a considerable amount of position when the markets continue to travel downwards and it doesn’t make that third 1:1 anymore. I’d say this is up to you personally depending on how conservative you are. Greedy to the max? Run with what I’ve done here in the new version. Want to be safer? Run with how it was done in the previous version.

Cutting DCAs by 33% To Open More Pairs:
Crypto markets are insane, -10% one day can be +10% the next. Often, I’ve wondered how far down I should chase a market before it’s just going to end up in holdings anyway. Sure, getting the best possible position for reentry is favorable but I’m also not made of endless funds. I have a limited amount I can trade on and there has to be a balance between keeping funds working in other markets vs. securing the best position on falling markets. What I decided to test in this version was eliminating the “Lost In Space” section of the AutoConfig completely. That means instead of making 18 total rounds of DCAs it now does 12. Two very sharp 1:1 rounds in the fast category of the AutoConfig, then five in both the normal and slow sections.

This means we now end with pairs holding roughly $1000 at max DCA depth instead of $1700. We’re going to take that extra money and put it into opening more markets. The idea behind this is that while some are failing, hopefully we have a better chance of others continuing to ride the wave. It also increases our ability to hit bull runs as we’ve got more ground covered. Now I’ve made over a grand in profits since my last post so I now have 6k on the bot to work with instead of 5k. Working on the grounds that I can generally “do the dance” discussed in the first post and have twice the markets open then I can actually afford this means I can run twelve now. Once again, if things go to hell and we see complete market downfall / crashes I’m going to be super fucked.

I want to point out that in the last ten rounds of DCA we’re still getting an entire 1:1.5 ratio in purchasing. Just because we cut out the last five rounds doesn’t mean it’s not averaging down a considerable amount. We’re going from $400 exiting the fast section of the AutoConfig to $1000 by the end of the process. That’s 150% of bettering our position for reentry. Mean while the rounds we cut out, from $1000 to $1700 is only 70%. This is why I feel the funds are better served continuing to make trades elsewhere. As you’ll see in the results for this configs test cycle, it worked out.

Increasing TrailMe Sell Range for One Buy One Sell Situations:
As you can see in my last post there has been great debate over the TrailMe Sell setting of 0.1 vs 0.05. This has continued on and nobody seems to have a clear answer given the situation is so variable. Just watching the graphs over the last week I’m still favoring my original position with 0.05 being the best for min/maxing profits while machine gunning sub percentage trades. Though when the market is just shooting upwards and it’s only making one buy one sells over and over the 0.05 is triggering sell offs too early.

This is causing it to have to buy back in and we’re losing profits because it has to stop and start, which leaves a middle ground between the two purchases that is lost gains as well pay another cycle of trade fees. This sucks. The easiest most straight forward solution I could come up with for this is to introduce a new section to the AutoConfig where it simply checks if we’ve made any DCA purchases. If not, change the TrailMe Sell Range to 0.1, meaning it can go through one buy one sell cycles over and over with the better setting. Though when we start making DCA purchases it changes it back to 0.05 as there has now been a fall in the market and we’re probably going back into sub percent machine guns again.

This isn’t complicated and it does a great job. You can even use this same system to swap between say 0.25 on bulls and 0.1 on normal markets if you absolutely hate the 0.05 setting. Simple edit the AutoConfig and you’re off to the races.

Changing Trade Timeouts Back to Zero:
You can see in the last post discussion over Trade Timeouts. Not wanting to accidently create duplicate purchase orders thanks to lag along the way both to and from your exchange. A mindboggling long wait time of 10 seconds was introduced in order to make sure no matter what this would never happen. Though over a week of reviewing this later I’m not having it. I tried a number of AutoConfig scripts to fix this for each situation in which it mattered.

Example, I was experimenting with “ourBaginBase” checks to see if we’re holding then changing the Trade Timeout based off that. Sadly, like some of my attempts at changing DU Cap Counts live the changes would not take effect until the bot was fully stopped and started again. I could see the script getting ran in the console, pairs were being filtered, but when you checked the logs it wouldn’t ever actually make the changes live. I honestly don’t know if that’s just a bug in the current version of the software or if my basic scripts weren’t cutting the mustard.

Regardless, after review and thinking about how the bot processes pairs, I’ve returned it to a setting of 0 for now. This setting is most important in real world practice when we’re in a bull run scenario making one buy one sells all the way up the charts or when there are massive sudden dips out of no where and you want to buy all the way down even if they’re fractions of a second from each other. You need to maintain that lightning ability in both of these cases and it just can’t get done with an absurdly long wait time like the previous setting of ten seconds.

I’ve had maybe a couple misfired orders thanks to latency over the span of the last week. There have been thousands of trades happening so in the grand scheme of things this has been deemed acceptable. I’d rather maintain the speed and deal with the extremely rare accidentally double purchase then slow things down so much. Though I’m on fiber and have a sub 25ms run to my exchange. Depending on your connection reliability & speed you may consider keeping the long delay from the previous version. Just watch your bot each day whenever you can and look for the double / triple purchases. If you see them on your charts then go into your dashboard & logs to see if it was just different rates your exchange was issuing you on market orders or if you were actually submitting multiple orders.

Increasing Precision with Multiple Instances:
So this goes hand in hand with the above topic but the bot processes your trading pairs in a rolling cycle. The more pairs you have, the longer it takes to get back to the first one. This is further controlled by the delay in your exchange settings. Though even at the fastest setting of 0 it’s still going to take time to get through each pair. Example, let’s say you had twelve pairs trading and it was taking an average of one second to process each pair. That would mean it would take twelve seconds total to make a full rotation. In reference to the above topic, this is why even with a Trade Timeout of 0, you’re still not getting instantaneous results. There’s a defacto gap as it polls other pairs.

In order to make the bot as fast as possible and increase order precision we need to request as many pairs per second as we can. This is done by opening up more then one instance of the bot with your pairs equally divided. This will be naturally limited by one of two things, your hardware resources and/or your exchanges API limits. In my case, I’m still stuck on Coinbase Pro (yeah another week, still haven’t cleared binance verification) which when you look at their documentation has a limit for Private Endpoints of “5 requests per second, up to 10 requests per second in bursts.” So we take the twelve pairs we’re running for this test, divide them equally by 3, we end up with four clients we need. Given they request slightly faster then one per second with a delay setting of 0 that means we’ll be just at or under the limit of five requests per second the exchange has.

This is covered on the Gunbot Wiki under the “running multiple instances” section. Though it’s very simple. Basically, we just copy our Gunbot folder. Then change the config files to only have the pairs we want running in each new instance. You then need to change the port for both the GUI and WS section in the config plus the clientport in the WS section as well. This is to keep them from interacting with each other and allow you access to the different instances. If you want to do some house cleaning and get rid of your old pair logs that will no longer be running in any given copy you can do that too. Now I have four copies of Gunbot running, requesting over four pairs a second from my exchange. My delay via pair cycling has been effectively reduced by 75% which greatly helps increase order precision when hunting those epic dips or catching just the right time to sell off.

This has jacked my trade servers resource usage up considerably though. Where previously it was almost idle occasionally hopping to 5% during busy times, I’m now seeing a constant processor use with peaks to 20%. Disk time is up as it’s writing four times the logs, memory is up, etc. While I’ve got plenty of headroom on the server, this might be something to watch for if you’re running Gunbot on limited hardware. Another side effect of speeding things up so much is I had to change the AutoConfig to update every three seconds to stand a chance at catching the changes it needs to make before additional orders are placed. @_@

24 Hour Test Run Results: (once again please note: this is too short of a test to be of any real value)
Same as last time I shut down everything, sold off all my coins, downloaded the newest nightly version of the bot (v21.3.4), setup the config then let it rip for a day. This trial run of the new config was pretty damn good, easily qualifying as one of my best days. Ultimately it came down to having those extra pairs running as only a few markets made all the cheddar while the other ones sat around almost idle. A couple people requested actual screenshots from my console rotation which I’m more than happy to provide. NOTE: You can click the image for the full-sized screenshot to make for easier reading.

Total: +$274.74560414 – AVG: $1.126006574344262 – Trades: 1014 – Closes: 244

Wowsa, look at ALGO and GRT, just killing it. Meanwhile yet another trial period where BTC did absolutely nothing, it didn’t even close a single trade in 24 hours. LOL. Volatility is our friend! Good machine gunning over this run too, 1014 trades with 244 closes! Now that’s what I’m talking about. Funny between our last versions trial run and this one, our average only increased by four cents! The downsides include really slow days on most the other pairs including losing -$2.33 on AAVE. Which is counter productive to say the least. I’m not sure why this happen and I think it’s from Coinbase’s +/- 10% price guarantee on market orders. It could’ve slipped into the negatives on really tight extremely low sub percent sales or maybe it was a calculation error on Gunbots part. I’m really not sure what to make of that and will have to dig in deeper to find out what happen there. Overall a very successful day considering I’m still trading on top of 0.2% fees!

When You Start Your Bot Makes a Difference:
I wanted to take a moment and talk about when you first start your bot up. I’ve spoke to people with a range of results from being told it’s amazing to wow look at all those DCA rounds pop off. This is natural to the markets and requires a tad bit of forethought. If you just got your accounts setup and scripts in place, then turn it on right at the end of a huge bull run then it’s going to start trying to acquire bags and position itself on a massive downhill slide. This is going to be rough as the first entry purchase is set to happen pretty quickly. The configuration is meant to stay active all the time, almost always holding.

There is nothing that mine or most other configurations can do if the markets drop 15% in a day after you’re bought in. The only way to tackle bags is to set a stop loss where you’re going to take a loss to reset your position or dollar cost average on the way down so you have a better position on the way up. There’s always reversal trading as well but it’s not something this configuration is setup to do at all. This is partially what I hear makes the Grid config so popular is it’s using more complex calculations to determine when is the right time to place an order. As marketed, it’s “always in position” so to speak.

This is one of the great headaches of day trading, what to do once you’re holding and the market goes south. Everybody has as theory or method to their madness, how much loss they can handle, etc. I’ll personally manually reset a pair if it’s been dead for many days into a week. Mainly if I read some sort of news about a coin that I think will keep it out of position for an extended period of time. Though overall I don’t like doing this as it’s just throwing away money. I’ll generally keep calm and wait a bag out. Holding sucks but this is crypto, what’s down one moment will be booming the next.

There’s also no way myself or anyone out there can predict how your specific pairs are going to behave. Maybe you’re trading a coin I’ve never even heard of and it’s only available on some remote exchange. +50% in a day, -50% in a day, these are all possibilities. The machine gun here is setup to run heavily trafficked popular coins that it can play the sub percent market on constantly. There is a lot of other configurations if that’s not what you’re looking for. Just give it some thought, I want the best for everybody, I want the most profits for everybody, but this is specifically setup for a use case that I’m trying my best to detail out in these posts.

People Keep Asking for Tip / Donation Addresses:
Well, I keep receiving the same question over and over. Where do I accept tips / donations for the help? I’ve been telling people it’s not needed and happy trading. The whole point of starting this thread was to encourage open communication in the community and help build something better for all of us. Though some people insist and it’s making me feel weird. It’s not that hard to open a couple wallets up though so if anyone seriously wants too, feel free to use the addresses below. It is by no means expected nor encouraged but it will be deeply appreciated. I’ll use whatever comes in to grab the back testing addon or upgrade my account. Once again, it’s heart touching, but focus on your trading and your family first.

BTC: 3Lasb2qnbKcG4Ppbdgp7CDmEzwWaHEzYQJ
ETH: 0xADd0453F442cC4BA9a5F9bC0fB9dE5313759a331
UNI: 0x96d5bc9BD7F7632B6C59710B4dD3c6ff641D52A9
USDC: 0x32C875516D61d061816d2Ae910c1abA590115422

Future Improvements I’d Like to Make:
There is a long list of things I’d like to build into the AutoConfig for this strategy. I’m constantly busy so mainly it’s just a time issue that I’ve not had a chance to sit down and figure them out yet. You’re more then welcome to tackle any of these and post your results in this thread! I’d be delighted if some clever solutions showed up here.

Here’s an example of one, being still stuck on Coinbase Pro my exchange has a min. order size of 0.001 BTC, 0.01 BCH, 0.01 ETH, or 0.1 LTC. As BTC keeps booming depending on what version of this config you’re running, you might bump into that minimum order size and catch a trade error. Specifically, if you’re running version 2 with the really small $50 entry purchases. I’d be cool to have a script that just checks the current prices and adjusts the trading limit accordingly. That way it can fluctuate with the market without breaking.

Another idea is an automatic dead market culler. This is a risky one, basically once a market has been out of position for trades for a set period of time, say over a week it’ll trigger a stop loss on it. Then either replace the market with a better one or allow the current one to restart so it can get back in position. I assume this would be a simple modification of one of the pair selection scripts on the market place though I’ve not had time to really look into it. It might not even need to be such a lengthy amount of time as a week, maybe even a couple days. It makes me uncomfortable to think about automatic stop losses being placed but it would help keep things in position, although probably not cheaply.

Another one is a bull run detector for one buy one sell trading limit increases. This one is also risky because when the bull run ends, you’re going to end up with too big of an initial entry purchase at some point. Though the idea is simple enough, it notices there’s a bull run happening, notices it’s only making one buy one sells consistently, so ups the trading limit to make greater profit while this is occurring since no DCAs are being placed. Once things slow down and return to normal, it returns the trading limit to your normal amount. I have no idea where to start on this one it’s just on the list.

Feel free to jump in here and make the configuration more versatile for all of us. Your ideas are always welcome!

The Pim Effect:
As I was discussing in the Gunthy Elite Telegram group, there is a wide difference between masterfully scripted and tested configurations and what I’m presenting to you. The only reason I’m not running Grid right now is that in my limited testing of it, I just earn more with my settings. Though there is no comparing the two as far as technical brilliance and ability. This morning I saw a screenshot from Pim (@boekenbox) that had results looking exactly like what I’m doing here and it was hashtagged #machinegun.

The intro graphic for this post was created days ago and the nickname has been going all week in chat, not to mention referenced since the beginning of this thread. I gotta say that makes me feel like my time contributing and constructing here is probably coming to an end. This isn’t about accolades this is about all of us making more money. If Pim (@boekenbox) sets his sights on this manner / method of trading we’re going to have an amazing configuration soon. Here’s hoping #machinegun isn’t just a nod it’s a future.

Conclusion:
Alright you made it through a third wall of text post! Respect. Hopefully you’re making good returns every day and watching hundreds of trades fly by in true machine gun fashion. I apologize it’s taken me so long to get another one of these posts out, as you can tell they’re quite lengthy. When you add that into testing ideas and my limited free time, you can see why it’s taken me a moment. That +$274 trial run though, loving it. If I could get on Binance and start paying 0.075% fees vs the 0.2% I’m paying now that would’ve been an even better day.

I’m also looking forward to trying the local exchange, the Gunthy Mex Spot and hopefully get into some futures trading as well. I was experiencing some technical difficulties with swapping over to it but I’ll be sure to keep everybody up to date on how that goes. It was also brought to my attention by staff member @mrpapaya34 (aka: spicy meme lord) that I could be getting paid for trades instead of paying for them. Kinda blew my mind, he sent me a link to a service called ByBit. Though sadly I’m a U.S. citizen so they won’t do business with me, even jumping through VPNs doesn’t help in this case. Given I’ve spent north of $2,000 in trade fees this month alone over at Coinbase Pro, I’d love to get in on this.

If anyone knows a place like ByBit that will work with US residents PLEASE post here, send me a PM, talk to me on Telegram, just reach out in any way possible. Anything I can find and figure out I’ll be more than happy to share with the community so we can all profit! Anyways that’ll do it for today.

Cheers everybody, thanks for reading!

‘Goblin

(@TheWhiteGoblin on Telegram)

Beginners & Help / Configuration Update: Version II Now Powered By Community Interaction!

« on: February 06, 2021, 12:19:39 AM »

02/18/21 Update: It’s become important to note that I am not staff. Also, I do not have my own group or channel; I’m merely a user who hangs out in the official ones. I cannot grant you access to the official telegram groups; you’re going to need to request this from your reseller. You can find a list of the official groups here. Beware of anyone trying to sell you something, request account information, or even interact with you directly. The staff will not contact you first. I will not contact you first. I’m posting here to create a blog styled educational experience for new comers, that’s the end of it. Just be safe, use your head, and happy trading!

Introduction:
Hey everybody here we are a couple days later and the response has been amazing. Not really here on the forums that much, though in the official Telegram groups as I’ve been in constant communication since posting. People from all experience levels came out to talk to me and it’s been a perfect opportunity for education all around. People asked me questions that I had to do research on before answering meanwhile hardened Gunbot experts dropped endless amounts of wise words and advice.

It’s been an odd experience for me personally as people took my settings with their life savings in hand and let it fly. For me, I’m okay risking my own money. Seeing adoption of my trading methods makes me smile but it also causes me a bit of fear and feelings of responsibility for other’s futures when I hear it. I want everybody to be successful and profitable. Though I’m also not a guru, not a financial adviser, nor have I tested this in every scenario. Some people came out and ran it on large scale futures / margin trading setups and I was just like, hey I’ve never done that. On the other side people who didn’t know how to read a chart where letting it run as their first strategy they’ve ever tried. Needless to say, you’ve all given me a lot to think about.

I talked to Pim (@boekenbox) for a while and he even let me see some of his commented files so I could better understand his magic. This led to some very thought-provoking moments where I changed how my configuration works. I’d like to go over the recent changes here and discuss why I made them. There’s also some open debate on things I might just be wrong about, I’ll make sure to note them as well.

The New Entry Theory:
Alright so I was looking at Pim’s settings and noticed he entered into the market with the lowest hand possible then had large 1:1 or higher DCAs. This helps a lot because the first purchase is generally just a place holder incase things continue to fly upwards, at least you’ve got some skin in the game. Though the real important purchases are normally the next 2-3 rounds of DCA afterwards which I discussed in my previous post. That’s why they have the sharpest settings in my AutoConfig file that separates DCA orders into different categories. Most the time (in my experience) the market will determine what direction it’s going after a bit of a volatility phase which is where these first few orders get placed. It’s your bag building time.

With my old settings we’d have a $200 opener, then three quick rounds of 20% averaging. Leaving us with roughly a $345 bag to profit off of if the markets went up or to start slowing working against if they went down. This has made me good money so I was reluctant to change it. Though by adopting Pim’s style what happens is we make our first pretty pointless entry order, nothing really at risk. Then by doing larger 1:1 DCAs for the next three rounds we spend about the same amount of money but end up in a much better position every time. By the end of the third round we’ll now be holding a $400 bag, so $55 more than before but we’ll have secured ourselves a much better position towards gains at each step.

This has resulted in instantaneous profit a bunch of times for me during this first testing trial. By the time the third-round kicks in the markets will have given off at least one solid dip that it grabbed. Making the breakeven line drop below the current rebound of the market. Gunbot makes a sell immediately as its profitable and the whole machine gun concept just got sped up dramatically. I really like what he’s done here but it comes with a few downsides.

The Bull Run Trade Off:
This much better entry system to markets really sucks on bull market runs upward. You’re basically throwing down $50 to make sure you catch the market if it keeps soaring but the gains off $50 are really small. Previously my bot was doing $200 buys for the first purchase and that was decent enough for running uphill all day. Actually, made some of my better returns compared to the standard sub percent machine guns as it would move multiple percentages up with each run before selling off. That’s four times the profit then I’m seeing now.

But straight runs upwards are a rarity so you’re basically sacrificing profits when this happens for better results the rest of the time. I’m sure a scripting wizard out there could add a system to the AutoConfig file that would notice we’re flying directly upwards and change it to start throwing down large entry purchases instead but it’s currently just an idea that I’ve not build into the configuration for now. It’ll be something I’ll work on later for sure though. This discussion actually leads into another issue I’ve been facing in the new version.

The Problem with Trade Timeouts:
In the previous version I ran a setting of 0 for Trade Timeout. The bot would buy and sell instantly after having placed an order. Sometimes the bot would not get information back from the exchange intime given it was running on an exchange delay of 0 and this would result in multiple orders being placed. I really didn’t mind as an accidental 20% DCA round wasn’t that big of a deal compared to the speed it had. It would catch volatility dips like a psychic being that fast.

The problem is in the new version we’re doing some monster 1:1 purchases of DCA for the first three rounds. There needs to be time for the markets to actually move between these purchases and there needs to be time for the bot to run the AutoConfig file and adjust it’s purchasing behavior to the new category once it’s maxed out it’s time in the fast lane. Example: let say it’s completed round 3 of DCAs and you’re now holding a $400 bag. With zero delays it might not get the information back from the exchange right away so it throws down another 1:1 order. You’re now holding a $800 bag and you’ve not travelled anywhere fruitful in your market depth.

So I had to implement a rather long wait time of 10 seconds via the Trades Timeout setting. Any shorter and it would sometimes (albeit rarely) still throw off a second purchase. This is like waiting a year in machine gun trade time, it’s painfully slow. Which also causes a loss of profit on the run up because the bot will sell off at the slightest movement downwards. Which means it’ll need to put in another order right on top of itself if the market keeps going up. Previously in the first version it was so fast that there would generally be no gap between the two. It would empty heavy bags then start fresh again right away. Now though it’s got to wait 10 painful seconds before it can do this. That’s an incredible amount of market travel if things are being a bull on rockets upwards. I’ve watched 1-2% gains just get lost thanks to the new Trades Timeout setting cock blocking it.

I’m honestly not sure how to combat this. I attempted to put different levels of DU Cap Counts per category into my AutoConfig script so it would be forbidden to make a 1:1 purchase while going from the fast behavior section to the normal section but the bot wouldn’t actually change the Cap Count until it was stopped and started again. It would just hold its previous now full Cap Count and stop additional DCAs until restarted. You could try dialing down the Trades Timeout setting to the lowest number possible but I wanted to include some room for lag on both your side and the exchanges side. Accidently ending up with an $800 bag or worse another round on top of that leading to a $1600 bag is a major problem.

There is probably a better way of fixing this that I’ve not even thought about yet and I look forward to hearing from you guys on possible solutions. I want the bot to return to it’s godlike 0 trade timeout speed but without the accidental purchases. This whole issue actually leads into another discussion that came up.

Is the 0.05 TrailMe Sell Range Leaving Money on The Table:
To me I always believed the 0.05 vs 0.1 argument on sell settings was that 0.1 was losing money compared to 0.05. Specifically, on very tight trading days where you’re trying to make a buck with no movement. AKA the lower end of the sub percentage trade market. But it’s been brought to my attention that for every other trading situation that can arise, people think 0.1 is better as 0.05 is accidently triggered too early. When the Trades Timeout was 0 and the bot was ultra-fast this wasn’t as big of an issue because it would purchase again literally right on top of itself if things kept going upwards. But now that there’s a large delay afterwards it would be nice if it didn’t accidentally trigger if things were still generally travelling upwards.

The profits lost from waiting the ten seconds to buy back in again are staggering. I’ve been watching it happen time after time in the last day of trying the new settings out. The argument that 0.05 is too lean is really ringing through my head right now. It’s going to make the low-end sub percent market much harder to play and much less profitable but how often does that matter compared to the time the bot spends in all other situations. I like to take money when it’s on the table, 0.05 does this every time. But I also hate watching it throw money into the wind by selling off too early. If we could find a solution to the bot’s rather large new Trades Timeout problem then I’d feel better about keeping it lean.

This would be a great time for others opinions to be presented. I’d enjoy hearing more of what you all have to think about this. The only way I know to see what is better overtime is to just run long testing cycles on it. With the natural chaotic fluctuation of the markets from day-to-day small testing samples of 24 hour runs just aren’t going to cut it. I don’t have the Ultimate Edition of Gunbot so I don’t have access to the Backtesting Addon. I think this would be a wonderful tool for getting some good hard numbers on the situation inside the same market periods. If anyone out there does have this and wouldn’t mind giving us some insight, I’d deeply appreciate it.

Extending DCA Rounds By 50%:
A big part of the changes in this version is the new market entry strategy discussed above. Though there’s no way I can continue to support large 1:1 DCA rounds past the first three that leave us with a $400 bag. That’s thanks to my personal financial situation so you may be able to continue down that path longer. The important part is not throwing out my previous ideas that worked well. So what happens in this version is when the first three rounds are over, the fast section of the AutoConfig script changes to the normal section. Here things return to the much smaller purchases. Though now we’re doing 10% DCA rounds instead of the 20% from before but we’re able to do more of them.

Previously this wasn’t possible because a 10% DCA order on $200 was too small for markets like BTC on my exchange. It would kick back an order error which you might remember I was talking about in the previous post. Now though since our bag is much bigger this isn’t a problem and we can actually extend its DCA abilities out to 18 smaller rounds. 3 fast lanes, then 5 normal, slow, & lost in space rounds. The idea being that with smaller 10% rounds we can make the bot more granular which helps keep things on target as well up its bag size more often so that when the market does switch directions it’s better prepared all around. Given you’re paying a percentage trade fee and not a set amount you’re not paying any more just securing a better position by doing this.

I kept the settings pretty much the same outside of changing the DCA amount. Minus the Lost in Space rounds which now simply double from 1.0% DU Method and DU Buydown to 2.0% instead of going all the way to 2.5%. The reason behind this is I wanted to make sure we were at least covering 10% of market fall in these last rounds when the big purchases were happening. Since we’ve got an extra round now, we can actually purchase slightly more often while covering the same distance.

This also changes the total bag size you’ll ever hold from $1800 max with the old settings to $1700 max in the new. Starting with $50, then three 1:1 fast rounds to $400 followed by fifteen 1:0.1 rounds ending at $1,670.90. This number will never be exact thanks to the way purchases happen but you’ll be around there. For this test period I’m running six pairs, which would require $10,025.40 to fully cover if everything crashed and went to round 18. I started with $5,000 in total funds as I’m being EXTREMELY GREEDY and hoping that only one or two markets will need to go deep into the extended DCA rounds at any given time. I’d be super fucked in a crash at this level of greed. If I wanted to be safe, I could only run THREE pairs and completely secure them all the way to round 18 of DCAs. Though that’s going to cost a lot of profit as the more hands you’re playing the better chance you’ll have at riding a good market for a while. Once again with the dance described in the first post.

Though I can see the profits rolling in from having a much finer grain already in my trial run. This is considerably better than my old settings I first posted. You could probably even cut them in half again and extend this out to more rounds if you liked. It’s on the list for future ideas I’d like to test. It’s already like a wave of purchasing as it stands currently and you do need to provide room for the market to actually move so this may be the happy medium. More than before but not too much, time will tell. This would be another great time to have the Backtesting Addon from Gunbot Ultimate.

New Config: (bold settings are new to version 2)

Buy Method: gain
Buy Level: -10
Sell Method: gain
Gain: 0.25
Trading Limit: 50
Min Volume To Buy: 11
Min Volume To Sell: 11
Funds Reserve: 1
Period: 1
Medium EMA: 60
Fast EMA: 30
Double Up Enabled: on
DU Cap: 0.1
DU Cap Count: 18
DU Method: 0.5
DU Buydown: 0.5
TrailMe Buy: on
TrailMe Buy Range: 0.05
TrailMe Sell: on
TrailMe Sell Range: 0.05
TrailMe DU: on
Market Buy: on
Market Sell: on
Market DU: on
Trades Timeout: 10
Exchange Delay: 0

New AutoConfig:

Code: [Select]

 {
    "DURange-Fast": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount1": {
                "type": "smallerThan",
                "ducount": 3
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 1,
            "TRAIL_ME_BUY_RANGE": 0.05,
            "DU_METHOD": 0.25,
            "DU_BUYDOWN": 0.25
        },
        "clearOverrides": false,
        "schedule": "*/6 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Normal": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount2": {
                "type": "biggerThan",
                "ducount": 2
            },
            "ducount3": {
                "type": "smallerThan",
                "ducount": 8
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 0.1,
            "TRAIL_ME_BUY_RANGE": 0.05,
            "DU_METHOD": 0.5,
            "DU_BUYDOWN": 0.5
        },
        "clearOverrides": false,
        "schedule": "*/6 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Slow": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount4": {
                "type": "biggerThan",
                "ducount": 7
            },
            "ducount5": {
                "type": "smallerThan",
                "ducount": 13
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 0.1,
            "TRAIL_ME_BUY_RANGE": 0.1,
            "DU_METHOD": 1,
            "DU_BUYDOWN": 1
        },
        "clearOverrides": false,
        "schedule": "*/6 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-LostInSpace": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount6": {
                "type": "biggerThan",
                "ducount": 12
            }
        },
        "overrides": {
            "DOUBLE_UP_CAP": 0.1,
            "TRAIL_ME_BUY_RANGE": 0.25,
            "DU_METHOD": 2,
            "DU_BUYDOWN": 2
        },
        "clearOverrides": false,
        "schedule": "*/6 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    }
}

Small Note:
You’ll notice I also had to increase the speed at which AutoConfig polls to every six seconds instead of ten so that it would safely detect and make config changes while the new Trade Timeout was active. I’m sure this isn’t great for conserving CPU cycles and it does tend to generate large log files rather quickly. Though it does a fine job of keeping things correct between trades. As always, community optimizations are welcome.

How to Safely Test This Configuration:
A lot of people contacted me looking to give my configuration a trial run but weren’t sure how to do it without interrupting their other already running pairs. This is actually rather simple. First create a new trading strategy following the above settings and apply it to the pair(s) you want to test it on. Then go into the AutoConfig file and you’ll see two lines in each of the four sections. You’re looking for the "exclude" & "include" parts. Here you can list pairs you want this to run on and pairs you don’t. Directly out of the Gunbot Wiki a couple examples for using this would be:

EXAMPLE #1:

"exclude": "DOGE",
"include": "BTC-",

This would automatically apply the script to all “BTC-x” pairs but not to “BTC-DOGE”, which would be excluded.

EXAMPLE #2:

“exclude": "BNB,XVG",

This would not run the script on pairs containing “BNB” or “XVG” in their name.

EXAMPLE #3:

"exclude": "DOGE,ETH",
"include": "USDT,BNB",

This would run the script on all active trading pairs that include "USDT" or "BNB" but do not include "DOGE" or "ETH" in their pair name.

Make sure you add your test pair(s) to include and your other currently running pairs to exclude. You’re also going to need to edit the exchange settings (there’s four, one per section) to wherever you’re running the bot as well. After that you should be good for a live trial run to compare my configuration to others without disrupting your current trades.

24 Hour Test Run Results: (please note: this is to short of a test to be of any real value)
Alright so I started with a fresh install of Gunbot v21.2.5 yesterday, put the new configuration into place and let it rip. This trial run had 5k in starting funds available, ran six pairs, and paid 0.2% in fees per trade. The bot hasn’t even ended the first 24-hour cycle in the console yet but this is when I have time to write the post. So roughly a day later here is where it stands:

BTC: +5.40578027 – AVG: 0.90096338 – Hero: 2.307439450069353 – Closes: 6
ETH: +14.25858332 – AVG: 1.01847024 – Hero: 2.8612470483936363 – Closes: 14
UNI: +15.22203978 – AVG: 0.72485904 – Hero: 1.7714818585867533 – Closes: 21
UMA: +47.97587734 – AVG: 1.54760895 – Hero: 9.84181911799999 – Closes: 31
AAVE: +33.72025167 – AVG: 1.08775005 – Hero: 7.971438273999922 – Closes: 31
LINK: +17.74478474 – AVG: 0.84498975 – Hero: 2.156571064199966 – Closes: 21
Total: +134.32731712 – AVG: 1.08328482 – Trades: 360 – Closes: 124

The first thing I notice is that my average is way down. That has to be thanks to the much smaller entry buys of $50 vs $200 as we’re just not making as much money when it’s one buy, one sell. Or even within the first two DCA rounds as we’re still not backup to what we use to hold right away by then. You can also see how BTC was a real slow-moving pair over the last day while UMA and AAVE had lots of volatility resulting in the most trades and the most profits. I honestly expected to see more out of this second version of the configuration but it has only been a single day of testing.

I checked in on it throughout the run and at times I saw it effectively using up to 85% of the total funds available through DCA rounds. It never got locked up by not having enough funds to continue but it was pretty close. Once again, I’m being really greedy here as 5k is only enough to fully support three pairs all the way down to DCA round 18. Luck was with me over the last day. If you read the first post about how I’m stuck on Coinbase Pro for now, I can’t wait to run on Binance. The lower trade fees will not only bring in more money per trade but increase the bot’s agility allowing it to get out of markets easier. This could’ve been a much more profitable day purely based on switching exchanges.

Conclusion:
Hey, Congratulations! You’ve made it through another wall of text post. Your understanding of this configuration should have leveled up at least twice if not three times over this process. As you can see from the extremely short test I’ve ran, it turned out to be a pretty good day. Compared to the previous settings I posted it qualifies as alright. It wasn’t a bad day, it wasn’t a monster day, but with only 5k to work with I’ll certainly take it. Overall, I’ve identified some areas that need improvement. As well some places I’m losing profits compared to before. I’ve also fixed a handful of problems that arose from the new changes. Plus, I’ve created an extremely long winded and detailed post to try and help the community.

You better believe I’m looking forward to talking about this with all of you in the coming days. Hopefully bright ideas on how to fix the problems I’ve detailed within this version of the configuration will come to light. There’s always a better way to trade out there, it’s often just about getting knee deep in and observing how the bot reacts to each step you take. Keep in mind the staff keep making it better with each version so you need to stay up to date as well. You can get nightly / beta builds from the official Telegram group “Gunthy Announcements” so don’t forget to request access to this from your reseller. While you’re at it make sure you come on by and say hello to us in the Elite channel. Feel free to post here on the forums as well!

That’ll do it for now though. Thanks again to everybody who hit me up, special shots out to Pim (@boekenbox) for all the time and help as well. Cheers everybody, thanks for reading!

‘Goblin

(@TheWhiteGoblin on Telegram)

THIRD VERSION POSTED! Keep scrolling down or click this link: https://forum.gunthy.org/index.php?topic=4362.msg16687#msg16687

Beginners & Help / Introduction to a basic gain with trailing & dollar cost averaging configuration

« on: February 03, 2021, 10:54:00 PM »

Introduction:
Hello! I’m Goblin an amateur crypto nerd for the last four+ years. I’m the same Goblin from the ArsTechnica Openforums as well the Monero community. I’ve been a miner, node operator, staker, day trader, & blogger across my crypto history. I started using Gunbot back around version 8 or 9 and still find it to be the most worthwhile investment for making profits in the industry. That’s to say, putting the same amount of money into Gunbot will yield you more profits and safeties then putting it into mining, yield farming, or staking.

It’s because of this that I’m a believer in Gunbot, I want to see its continued success and development. We have a small but tight community, everybody is very helpful, and you should not fear joining us in the official Telegram groups. It’s where you’re going to find the most interaction, discussion, and meaningful conversation. Not to mention direct interaction with the staff, resellers, and market place contributors.

02/18/21 Update: It’s become important to note that I am not staff. Also, I do not have my own group or channel; I’m merely a user who hangs out in the official ones. I cannot grant you access to the official telegram groups; you’re going to need to request this from your reseller. You can find a list of the official groups here. Beware of anyone trying to sell you something, request account information, or even interact with you directly. The staff will not contact you first. I will not contact you first. I’m posting here to create a blog styled educational experience for new comers, that’s the end of it. Just be safe, use your head, and happy trading!

Disclaimer:
Hey I’m not a financial adviser. I don’t work for any large firms. I don’t have a background education in this. I’m a retarded autistic monkey on the same level as the guys over at r/wallstreetbets. In the last four years I’ve at times lost over twenty thousand dollars in my enthusiastic love of crypto. I have literally gone homeless and lived in a car over making bad decisions when it comes to life as a full time cryptonaut. (twice)

If you’re going to get into this for a career or even as a major part of your financial capabilities then take caution, do not play with more then you can risk. Markets crash, the losses always come faster then the gains, a dollar earned will be a hard painful journey but a fortune lost will come in the blink of an eye. If you want to keep waking up comfortably in your bed then never play with your rent / mortgage / survival money.

Intention:
The reason for this post today is to share how to setup the bot in the same manner that I run it. It’s also to encourage community interaction to create a better more profitable setup that we can all benefit from. I know there is more to be gained then how I’m currently trading though as I’m not a markets / scripting wizard. This comes purely from years of literally trying every possible way you can configure the bot and seeing what works and what doesn’t.

That said this morning I was reading the official Telegram group chat and noticed people discussing the profitability of the very popular Grid strategy for spot trading. I have been thinking about moving over to it a lot lately and comparing earnings. It’s even gained a place in the newest versions of the bot by default so it must be pretty damn good. I read one person saying they were doing $100 in profit a day with $20k to work with. Another person said they were earning about $25 a day with $5k. I’ve personally got about $5k I’m working with at the moment and I’m doing $100+ per 24 hours on good days and $25+ on slow dreadful days.

I brought this up in the chat and was asked to post up my settings here and in the market place. I even had a nice little conversion with Pim (@boekenbox) the creator of Grid. The thing is, Pim and others are much more experienced traders then I am. My settings have been working out lately but have major flaws that do not work in all situations. I’m honestly not sure how lucky I’ve been lately compared too actual long-term sustainability. Grid looks to be good all around and is probably the better option. Though in the name of profits for everybody I’m here posting today. With any luck, we’ll all make more money through open discussion & collaboration.

Config Settings: (only changed settings listed)

Buy Method: gain
Buy Level: -10 (discussion below)
Sell Method: gain
Gain: 0.25 (discussion below)
Trading Limit: 200 (depends on how much you have to work with)
Min Volume To Buy: 11 (gdax specific setting)
Min Volume To Sell: 11 (gdax specific setting)
Funds Reserve: 1
Period: 1
Medium EMA: 60 (almost doesn’t matter anymore)
Fast EMA: 30 (almost doesn’t matter anymore)
Double Up Enabled: on
DU Cap: 0.2
DU Cap Count: 12 (depends on how much you have to work with)
DU Method: 0.5 (will change with autoconfig)
DU Buydown: 0.5 (will change with autoconfig)
TrailMe Buy: on
TrailMe Buy Range: 0.05 (will change with autoconfig)
TrailMe Sell: on
TrailMe Sell Range: 0.05 (discussion below)
TrailMe DU: on
Market Buy: on
Market Sell: on
Market DU: on
Delay: 0 (in your exchange settings)

Settings Discussion:
These settings are made in an attempt to ride every single wave of the market as it ebb and flows. I mainly try to hit the sub percent trades but wanted it to move with the market as much as possible. This is why I use trailing instead of a set gain amount. Now you might ask, why are you still using gain over just setting up TSSL. That’s because I’ve experienced issues over numerous versions when using TSSL with other trailing settings turned on. This is probably thanks to my lack of understanding of how one setting works with another and not the program itself. That said, everything works as I expect when I just use gain as a base then enable additional settings on top of it.

I think the reason I’m seeing such good returns compared to grid is simply because of the trailing activity. My average trade return is $1.7 though goes from $0.25 all the way to hero trades of $10+. It has a pretty extreme range as it’ll get out of a market as soon as the tides start traveling in the opposite direction but still benefits from large spikes when they occur. Let’s talk about a couple settings in particular. Buy Level, this is set at -10 so that it basically disables EMA protection. A couple versions back you use to be able to set this at 0 to disable it, as still noted in the Gunbot Wiki TSSL example description as a “pure tssl”. Though somewhere down the line this changed and a setting of 0 just became zero percent below EMA instead of turning it off.

This has caused me a lot of trouble for a while now but when looking into Grid I noticed he was able to use -10 to effectively do the same thing. Now for people wondering why this is important. This allows for you to profit on the way up instead of waiting for the markets to cross back down below your EMA. This makes A HUGE DIFFERENCE to your earnings. Normally you’d be sitting through bull runs as there just wasn’t a good deal to be had as the price will always be above your EMA lines. This allows you to keep purchasing and profiting no matter what the market is doing. I mean there’s only two options right? It’s either going to continue going up after a purchase which means you’re going to make money or it’s going to go down which will allow you to buy more at a lower price. Why would you want to stop making money on the way up? When I look at people’s screenshots from Grid, this is half the key to success IMHO.

This is why I wrote ”almost doesn’t matter anymore” as a note in my above settings as we’re effectively disabling it. Though I still like the settings as they are so I can watch trends live in the client. Now let’s talk about the Gain setting. This is set to 0.25 though I’ve often ran it at 0.1. The reason for the increase is we’re using a trailing on sells of 0.05 which will run downwards past your sell at line as long as it doesn’t also cross your breakeven line. This means in actuality at worse you’re going to sell for 0.2 percent profit. That’s actually some considerable head room as you can run at half that (a setting of 0.15 or 0.1) and be able to duck out of markets sooner. SIDE NOTE: If you’re wondering why you’d want to do this it’s because dumping your heavy bags and resetting your position at a small profit is often better than watching the markets tumble into the darkness while you’re still holding. If you empty out then your funds are free & the drop is nothing but a great opportunity to start the buy cycle again.

So back on track, the problem I run into is I’m doing market trades on Coinbase Pro currently and they have expensive trade fees. (currently paying 0.2% taker fees!) Plus their market order price guarantee is +/- 10%! Which when put into practice means while running at a really lean setting of say 0.1 I’ll occasionally spit out trades that I lose money on. They’ll show up anywhere from -$0.005 to like -$0.25. @_@ As you can imagine, I’m not here to lose money I only want to make it. By upping it just a bit to 0.25 it accounts for this slippage and I’ll never see a negative trade. I might only make a couple cents sometimes, but it’s at least always profitable while remaining extremely agile. Thanks to trailing you’re rarely ever going to be trading off at this small amount it’s just important to preserve as much ability as you can in getting in and out of markets.

Now let’s talk about those tight buying and selling percentages. I’ve done a lot of testing and find the bots default 0.5% to be waaay to loose for this application. I’ve even spent a lot of time trying 0.25 & 0.1. The objective of having a flowing sub percent machine gun trader is hitting each up and down as soon as the market even looks the opposite direction. Having settings of 0.05 will trigger on the same exact market moves as 0.1, you’re just getting more profit as you bought & sold earlier in the direction change. Remember I’m trying to fire off hundreds of trades a day so if I’m only making say 0.2% profit on a trade then the difference between buying/selling at a trailing of 0.1 vs 0.05 is huge. That actually doubles your profit as you’re walking away with 0.2 instead of 0.1. It’s all about min maxing to the best of the bot’s ability.

This also helps with your reentry into a market after selling off. Ideally it would go down so you can say you’ve sold at the peak and are looking for the next dip to buy. Though if it continues to go up, you’re going to have to purchase again and buying as close as to where you last sold off is the best option. The gap between your exit and entry points on the charts is just lost profits in this case. These settings will dump your heavy bags at profit then reset your position almost instantly if that where to happen. Yes, sometimes you sold out just to see it buy again as the markets continue to fly upwards. You didn’t know if the market was going to go further up or down, it made an emotionless decision to make you money while there was money on the table and that’s why you bought this program.

Another beneficial side effect of having the bot setup this sharply is it’s a dip hunter. Anytime you see swings in the market where there is a high level of volatility it’ll grab at the very bottom of dips even if they only existed for a mere second of opportunity. I’ve got a whole collection of screenshots in a folder called “epic dips” just because they make me smile and serve as a reminder that I’m on the right track with setting up the bot. Now let’s talk about Trading Limit, DU Cap, & DU Cap Count. This is modelled after Gunthar’s post from waaay back in version 11 called ”The Way I Run It” in which he shows how buying smaller amounts on the way down works better then direct 1:1 double ups.

Yes 1:1 will average the distance between your last and new purchase exactly half way between the two but it gets to be insanely expensive really quickly. I don’t have unlimited funds so when the markets keep dropping I need a way of slowly lowering the bar for reentry. 20% buys don’t spend a lot of money at first. The first few rounds are basically there to increase your bag size while the market quickly decides which direction it’s going again. If it shoots back up then great you made a little bit more then you would’ve as you cheaply picked up additional coins while the opportunity was there.

If it starts going down then not to worry you didn’t spend too much yet. Though as the market continues to drop over an extended period of time you keep buying with increasingly bigger orders to where you’re slowly overriding your initial purchases. I generally shoot for a DU Cap of 12 and that’s just the sweet spot I’ve personally identified with my own level of investment. I start with $200 buys so that while playing the sub percent market I can atleast make a dollar of profit with the middle ground 0.5% gain. This means if I don’t do any DU purchases there’s still enough in hand to make a little bit of profit. $100 buys were too little, $300 buys became too big through the DU process. Not to mention on the lower end with some coins like BTC I couldn’t actually submit a DCA order of 20% as the amount was smaller than my exchange would let me place resulting in an order error. (thanks to my reseller @Leeview for catching that)

The other big factor in picking these numbers is I need to run a handful of markets so that when some of them are having a slow or painful day the others can remain fruitful. In actuality if I’m running even just five markets, I cannot afford to pay for all of them if 12 DCA orders are placed. I’m being greedy and utilizing the idea that generally only one or two is having a really bad day so I can use funds from the other markets that aren’t hurting to better secure their positions for reentry. This is one of the downfalls of my particular financial situation as I’m dancing the line here. If we go through a crash of a cycle with all markets down eventually one or two of them will get caught up not being able to complete 12 full rounds of dollar cost averaging. Now as some markets come back, these other troubled markets will finish their DCA rounds though it’s a burden on your newly freed bags for sure. Given this rarely happens, I make more doing this dance then not but it’s far from ideal.

I further manipulate the situation with an AutoConfig file that is as simple as one could write a script. It’s not advanced wizardry like you see from other packages on the marketplace. We’ll cover that in the next section.

AutoConfig File:

Code: [Select]

{
    "DURange-Fast": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount1": {
                "type": "smallerThan",
                "ducount": 3
            }
        },
        "overrides": {
            "TRAIL_ME_BUY_RANGE": 0.05,
            "DU_METHOD": 0.25,
            "DU_BUYDOWN": 0.25
        },
        "clearOverrides": false,
        "schedule": "*/10 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Normal": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount2": {
                "type": "biggerThan",
                "ducount": 2
            },
            "ducount3": {
                "type": "smallerThan",
                "ducount": 6
            }
        },
        "overrides": {
            "TRAIL_ME_BUY_RANGE": 0.05,
            "DU_METHOD": 0.5,
            "DU_BUYDOWN": 0.5
        },
        "clearOverrides": false,
        "schedule": "*/10 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-Slow": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount4": {
                "type": "biggerThan",
                "ducount": 5
            },
            "ducount5": {
                "type": "smallerThan",
                "ducount": 9
            }
        },
        "overrides": {
            "TRAIL_ME_BUY_RANGE": 0.1,
            "DU_METHOD": 1,
            "DU_BUYDOWN": 1
        },
        "clearOverrides": false,
        "schedule": "*/10 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    },
    "DURange-LostInSpace": {
        "pairs": {
            "exclude": "",
            "include": "-",
            "exchange": "gdax"
        },
        "filters": {
            "ducount6": {
                "type": "biggerThan",
                "ducount": 8
            }
        },
        "overrides": {
            "TRAIL_ME_BUY_RANGE": 0.25,
            "DU_METHOD": 2.5,
            "DU_BUYDOWN": 2.5
        },
        "clearOverrides": false,
        "schedule": "*/10 * * * * *",
        "type": "manageOverrides",
        "debug": false,
        "enabled": true
    }
}

AutoConfig Discussion:
What this file does is simply check your markets DU Cap Count every ten seconds. It then changes the Trail Me Buy Range, DU Method, and DU Buydown depending one what range out of four it falls into. The first is fast, this says you just exited a market and are looking to get back in, ready to snap some coin up and get rid of it like a machine gun. It contains three rounds of dollar cost averaging at very sharp purchase levels. This is great when markets aren’t fluctuating a great deal as it lets you buy the tiny dips then get rid of them at profit over and over.

The next range is called Normal, it keeps the same Trail Me Buy Range but extends the Method and Buydown by double. This stops the bot from rocketing through your DU Caps and money when things are just starting to go downhill. By doubling the distance while still maintaining such a sharp range you’re saving yourself twice the buy ins. This occurs for another three rounds.

After that if things continue to go down, we’re now in the Slow range. This really slows down how often you’re purchasing those dollar cost average rounds by upping the Trail Me Buy Range to double what it was before, now at 0.1. It also doubles the Method and Buydown again to 1.0. It’s important to notice how we’ve dulled the edge a bit so the market has to start coming back a little bit more before it’ll trigger a purchase, it also has to travel at least a full percent (twice the distance) before it can happen. This also occurs for another three rounds of dollar cost averaging.

Then finishing it up, if all hope is lost on a market it’ll be put in the Lost In Space range. This is for the last possible rounds of dollar cost averaging I can afford, the real big purchases. I want the largest range of possible distance down before making these buys to help lower my reentry point. There for the Trail Me Buy Range is changed to a huge 0.25 while the Method and Buydowns are increased to over double at 2.5. Normally I see considerably more traffic down then 2.5% as the 0.25% trail range doesn’t accidently trigger until the markets are actually coming back. It’s a very dull setting and wouldn’t work for the normal machine gun sub percent trades I’m trying to make all day but once you’re this far out from profitability and down deep into the DCA dungeon you’re playing a very different position.

It’s not the Dynamic DCA script you find on the market place but it remains dynamic using the built-in trailing system from the bot. We’re basically just changing the behavior of how we want that trailing system to work into four different categories. Like I said before, it’s drop dead simple. It works well, though I’m sure this is one of the areas more experienced traders / scripters could increase profitability.

Dollar Cost Average Excel Calculator:
I created a very simple excel file to help me determine what the proper levels for initial purchases & dollar cost averages should be. You can simply enter your initial buy in, how much you want to double up per round, & how much your trade fees are then it’ll do the rest. It’ll conveniently plot out twenty rounds for you to look at. It has three separate calculators on the same page so you can easily play with the settings and compare them without having to take screenshots or write the results down.

Now I generally find I rarely need rounds 9-12, which is why they’re the lost in space rounds. So however much you can start out with and still get to round 12 while maintaining the total amount of markets you wish to run is the correct number. Example as per what I’m running at time of posting. $200 buy ins @ 20% DCAs means by round 12 I’m holding a staggering $1800 bag. This would be if it bought the perfect amount each time which rarely happens, most the time it’s slightly less but plan ahead.

Given I’m working with about $5k in funds right now this means I cannot even afford three markets to be round 12 fucked. As per the dance we talked about above. Given this rarely happens I can afford to send one or two markets to round 12 so that it can prep for a much better reentry point.

I’ve uploaded a copy of this simple excel calculator to google for you to download: here

Simple Things to Earn More Money:
If you’re planning on going down the route I have here and running a sub percent machine gun bot then it’s all about paying as little in transaction fees as possible. This not only allows you to take home more money but it allows your bot to get in and out of markets faster, making it more agile. You want the lowest bar possible to reentry and Coinbase, even their Pro side, isn’t the place for this.

I’ve done north of 500k in volume this last cycle already. They change your trading fees based on levels depending on how much volume you’re pushing. Though even on a good month I’m probably not going to push a million+ on this little amount of money I’m working with. Which means I’m stuck at 0.1% maker fees and 0.2% taker fees. This is too high and costing me an arm and leg while machine gunning sub percent trades. I’ve paid over TWO GRAND in fees so far this cycle alone.

A quick look around an exchange listing shows Binance offering an entry level 0.075% fee for both making and taking. That would more then cut my fees IN HALF. I’d have made $1000+ more by just taking my business over there. Which at the time of posting I have actually gone through all the account creation processes to do so and have been waiting for the last level of account verification forever.

It goes to show that where you do business is just as important as how you’ve setup the bot. Find a quality exchange that is going to appreciate your Gunbot. Don’t forget to lockdown your account access, API, and whitelist your bot’s IP. Do every additional security enhancement possible. We live in a time where Gunbot accounts are a generally a good target so protect yourself.

Conclusion:
End of the day this configuration has provided pretty good returns since it's last iteration. I’ve been seeing $25 on terrible days, averaging $100 plus on normal days, and I’ve seen as high as $200 on monster days. That’s with $5k total to work with. Though in all honesty I could just be getting extremely lucky as the markets have been very kind lately. It’s not hard to make money when everything is bull popping off booming and zooming.

The real test of a bot setup is how it handles bad days, back-to-back bad days, into bad weeks. How much you profit over a month, a couple months, into a year. I don’t have that data right now as I’ve been dicking around with the settings a lot lately to arrive where I am currently. I’ve been using this bot for years trying to develop the perfect settings to play every possible hand throughout the day. I want it to be super human and often I’ll challenge it by sitting for twelve hours with my markets open doing it by hand.

It can beat me most the time but I’m also not a great trader, I think and process situations differently than it does. My human brain goes for larger more profitable trades while it’s over there consistently winning over and over at the tight game. It’s emotionless and that’s the beauty. Even if I’ve not got it perfectly dialed in, it works while you sleep, while you’re out with your kids or on a date, it’s making you money while you’re not thinking about markets. That’s well worth the cost of the license.

As for what you should run. I’m not sure. I still think Pim’s (@boekenbox) Grid package for spot trading is worth trying. I read today that he’s implemented dynamic gain adjustment and that’s probably going to really be the winning feature that will bring in more profits than what I read earlier this morning. This entire wall of text post was created on the grounds I was seeing better returns machine gunning trades out in this fashion then grid users were making. To explore how that was happening and hopefully offer some education to the community that we could then in return collaborate on for a better all-around configuration across the board.

Remember, I am an amateur, Pim is not. My settings DO NOT handle massive market drops well at all. The only things you can do while running my config is set a stop loss to get your bot back on track once you’ve maxed out your funds via dollar cost averaging or… sit around and wait for them to come back someday. Holding. If you’ve got considerably more resources then me then you could always expand the range at which you can run DCA purchases. There’s probably a range around 20 that you’d never really lose sight of the markets and stay trading all the time. I’m not able to test that and have decided playing more markets is the solution to sustained profits.

Ultimately thanks to the times we find ourselves in (see: covid), I have bills and have to live my life on top of what the bot is bringing in. I literally eat at times thanks to the bot. So while I’m slowly trying to build my wealth back up and be able to expand what the bot can do other people can probably come right in and test a lot of variables I can’t afford to yet. I assume users providing settings packages like Pim are in a much better position then I am to advise you on how to trade. Though hopefully the time I’ve spent today creating this post will give some of you out there a lesson in using the bot and succeeding. This is worth your time, do not give up if you’re having trouble finding the profits. Come talk to us in the official Telegram groups or post here on the forums!

Cheers everybody, thanks for reading.

‘Goblin

(@TheWhiteGoblin on Telegram)

NEW VERSION POSTED! Keep scrolling down to the second post or click this link: https://forum.gunthy.org/index.php?topic=4362.msg16653#msg16653

THIRD VERSION POSTED! Keep scrolling down for a while or click this link: https://forum.gunthy.org/index.php?topic=4362.msg16687#msg16687

Beginners & Help / DU Method & Buydown only consider original buy even after additional purchases?

« on: November 19, 2020, 11:57:25 PM »

Hello everybody! Not sure if really a bug or if my understanding of DCA is off. I've been using Gunbot for a couple years now and been a pretty big fan of the DCA system. I've been away from the bot for about six months though and coming back I'm a bit thrown off on how it's now working in the newest v20 of the program. I'm almost positive that in previous versions it would apply the range you set in DU Method & Buydown to the latest purchase you've made instead of always referring to the original purchase. Example: if you set 0.5 to both, it wouldn't perform a third purchase until it was 0.5 down from the second DCA buy.

Currently I'm using DCA with Method & Buydown both set to 0.5 then TrailMe DU turned on with a setting of 0.25. It'll trigger multiple DCA purchases back to back when it sees the proper trailing being matched even if they're right next to each other at the same price. So it's only using DU Method & Buydown to look that it's below the set amount in comparison to the original purchase. I'm pretty sure it use to take additional purchases into consideration so that it wouldn't buy at the same price again and again burning through your DCA Cap Count.

Anyone else experiencing this? Am I off in my understanding? I know I want it to consider the latest purchase instead of always referring to the original so that it can keep working it's way down and better utilizing each Cap Count as it can get pretty expensive quickly. Like I said before, I'm pretty sure that's always the way it's worked so I wanted to post a bug report on this, but not entirely sure it's a bug verse the program changing in the new version.

Thanks for your time, /cheers

Beginners & Help / Re: Using different trailing ranges per DCA cap count?

« on: November 19, 2020, 11:32:15 PM »

I'll have to try the autoconfig sometime and see what it has in comparison. The previous post a year back that had done this was obviously running a pre-autoconfig version of the bot though exploring every options screen I can find it doesn't appear to be a thing. I was thinking this would require some more in-depth modifications to be made instead of using the standard settings menus. Given this hasn't received many views I'll probably have to go back to searching the forums in hope I can find that old post again to see how it's done.

Any help / advice from more experienced users would be great though. Thanks for your time everybody! /cheers.

Technical Support & Development / Timeline buttons don't match properly (bug report)

« on: November 19, 2020, 11:25:22 PM »

Hello! Just wanted to pop in with another quick bug report. Same as my last one I'm running the newest version 20 of the bot inside Windows. While trading on GDAX the bottom left timeline buttons (right before the "Go To..." button) don't actually work properly. For example if I click 5y it gives me 1 week. Here's what it pulls up for each button:

5y = 1 week
1y = 1 week
6m = 2 hours
3m = 1 hour
1m = 30 minutes
5d = 5 minutes
1d = 1 minute

Just wanted to make a post letting everybody know though I'm sure you've figured this one out on your own if you've clicked them. /cheers

Technical Support & Development / Trades continue on disabled pairs (bug report)

« on: November 19, 2020, 11:12:53 PM »

Just wanted to pop in with a quick bug report. Currently while using the newest version 20 of the program inside Windows pairs will continue to operate even after being turned off. I've tried this with both manually turning off pairs (which strikes them out with a line) and using the count sell function to automatically turn them off. The GUI will not show them anymore though they are still trading in the background. The only way I've been able to stop a pair from trading is to delete it from the pairs list completely. I've experimented with this a couple times to make sure it's happening before posting, just wanted to let everybody know in the case it's not just me.

/cheers

Beginners & Help / Using different trailing ranges per DCA cap count?

« on: November 12, 2020, 05:14:32 PM »

Hello everybody! Been a while since I've been around but it's great to see things still progressing here. A year or two back I remember seeing a thread where a guy had created the ability for the bot to place trailing DCA orders at different percentages depending on what number of it's cap count it was on. I've searched the forums and can't seem to find it again. I'd like to try this out in the newest v20 of the bot and am not sure where to start. Example: DCA #1 is purchased on a trailing of 0.25%, DCA #2 is purchased on a trailing of 0.5%, and DCA #3 is purchased on a trailing of 1%. I never fully explored the previous persons post about this so I'm not sure how he achieved this I just remember seeing it. Any help would be greatly appreciated.

Thanks in advance, /cheers!

Technical Support & Development / Re: [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: May 11, 2019, 01:22:26 PM »

There's a thread on the Github Issues page about this problem as well. See: https://github.com/GuntharDeNiro/BTCT/issues/710. The newest download on GitHub is v12.9.2 which I'm running. (from: https://github.com/GuntharDeNiro/BTCT/releases) The only other version you can download is 12.8.9 as found here: https://github.com/GuntharDeNiro/Gunthy/releases. The only other branches I can find are Gunbot Lite & the Beta edition which was last updated two years ago.

Could you please link where we can download v12.9.9 to fix this? I'm sure the guys on the GitHub would like the link as well.

Technical Support & Development / Re: [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: May 11, 2019, 02:41:06 AM »

Looks like you guys changed something again, got more expensive? Gunbot has been working fine since the last time I posted here. (still never got my grand fathered ultimate license back) Though here at 7pm it just stopped working again. Haven't touched anything since the last time.

Technical Support & Development / Re: [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 28, 2019, 08:50:20 PM »

Exchanged one PM with Gunthar & it works again. Didn't even get one back it'd just been a while so I decided to try it. Turned it on, V12 Pro license pops right up. Didn't have to change anything or do any swapping or any of that bullshit. Wasn't a problem on my side, didn't do anything wrong. I'd like to have my Grandfathered Ultimate back but I'm just happy to see the software working again. Thank you Gunthar I really appreciate the help & support.

Technical Support & Development / Re: [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 28, 2019, 12:53:29 AM »

Just got the response:

I don't mean to call in the big dog here but I'm pretty sure Leeview is absolutely useless. Now he's questioning if I had a grand fathered ultimate license? What are you guys taking back that now? I wrote both Gunthar and Leeview a thank you letter upon receiving it. Which I assumed was because of all the problems we've been having. Neither of them replied to the thank you letter but it's one of those things you don't really expect a response to so it didn't seem out of place. Let's see, that was at the time of my purchasing a 0.1 BTC difference in price. So today a BTC is $4,014.27, making 0.1 worth $401.43. Pretty much what it was at when I bought this software, I did the upgrade path so one purchase was $400+ and one was just under $350. I was very impressed with you guys for gifting the upgrade, it showed a legitimate concern for your user base and that you felt bad such bullshit had occurred.

Now you're questioning it? Where do you think I got the screenshot? Why do you think you got a thank you very much I really appreciate that letter for a license I didn't even know existed until that morning? It was sent on Mon, Mar 18, @ 11:35 AM. That's 9 days ago & I've had a grandfathered ultimate license every minute of every day since then until now. Also, I don't think I'm doing anything wrong here. Was it making hella trades this morning on both exchanges? Yuuuuuuuuuup. Was it making trades without issue the day before? Sure was. Oh shit at 3:30pm today something on your side changed and all a sudden my license is invalid, the software doesn't work, and it's my fault, I'm not doing something correctly. I wish I would've purchased this software through ANY other reseller then Leeview aka: thecryptobot.com.

This is bad business practice fine sir; you're not helpful, you don't read emails, and you blame the customer.

Technical Support & Development / Re: [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 28, 2019, 12:20:36 AM »

Got a response from LeeView:

Which even though this seems like complete nonsense to have to go through given everything on my end worked fine when I woke up this morning and continued to be fine until 3:30pm, I did it anyways. Thank goodness I made backups of my entire GunBot directory because you know what happens when you remove either exchange? This:

This includes going from a completely blank brand new install. If you run the backup I made (that was working perfectly 24/7 with no changes till this) then you get this:

You know what it said at 3:30pm? When it stopped working all a sudden & before I contacted my reseller?

Which still leaves me with one completely broken copy of Gunbot. You know what I had this morning? I had a working copy of this:

Now I've got a useless copy of this:

All without touching a single thing or doing anything.

Technical Support & Development / Re: [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 27, 2019, 10:30:20 PM »

Alright everybody I wrote LeeView back asking him what exactly he was going to do over live support he couldn't do over email and he wrote me back this:

So I've done as such and I'm currently waiting for a reply. I'll let you know what happens.

Technical Support & Development / Re: [RESOLVED] Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 27, 2019, 10:01:37 PM »

Well I thought these issues were over but at 3:30pm MST today I'm guessing you guys made the jump over to the token system. I got the email yesterday about how soon this would be the new way it's done and to make sure you're prepared. Given everything we previously went through I was pretty sure I was golden. Nope, I've got a balance of zero which has officially shut down the software & it's tits useless now. I took a screenshot of the VM including date and time for reference & emailed LeeView my reseller again, this is the eighteenth email in the chain. I explained to him in the previous email how the link to the Telegram Live Support group is getting caught in my network's pi-hole dns server so I've returned via email for the time being. To which the reply I got was: "If you are unable to get Gunbot to work, please contact me over Telegram, my nickname is @leeview and I will assist you live." Well thanks for reading my email @leeview.

So I wrote back "Are you saying there's nothing you can do currently and that you have no idea why I didn't get my tokens this time?" and within a couple minutes got the return: "Yes, sadly we do not manage tokens or airdrops. The only way to get real-live news about that is over Telegram Gunbot groups."

Oh i just wanna pull my hair out, I was sure we had fixed all this with the "Grandfathered Ultimate License" last time but I guess we still got some kinks to work out. How would you guys like me to proceed? After posting this I've got to finish work then I'll rotate over to the pi-hole and try to whitelist my way to your technical support. I'm honestly not sure which blocklist could be triggering you guys as that seems pretty innocent & its only setup to block established ad/malware. I'd really prefer if we could just do this via email but that doesn't appear to be a thing in this operation.

'Goblin

Technical Support & Development / Re: Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 09, 2019, 06:34:07 PM »

Thanks for the help everybody!

I woke up today with a fresh PM from Gunthar & an inbox full of responses from my reseller Leeview. After a couple replies we where able to get to the bottom of it & my issues with the second exchange have been resolved. He was able to take my info, update his side of things, and ta'da it just turned on perfectly again. I'd like to take a moment to say these problems appear to have been created partially on my behalf as I registered an exchange gunthy address as my wallet inside the software. Which upon reexamination this morning is specifically what the documentation says not to do. As things changed in the background this eventually hit the wall so to speak and generated some of the issues I came to post about here.

I'd like to apologize for any of the problems I've created while using the new license system. I got that email about having a couple hours till the tokens went live on IDAX and rushed to get everything setup in time to cash in before I headed out to work. Clearly I screwed the pooch on my own and there's nobody else to blame but myself for that. I'd also like to say sorry if I came off like a dick, I've been very frustrated over all this. I understand you guys are building something new and there's gonna be some bumps in the road. Specifically when users don't follow instructions. (lol/sigh)

As a friendly note to any other end users out there that happen to be reading this thread, there's a new Wiki location! I just learned this today. Make sure you update your bookmarks, here's the new one: https://wiki.gunthy.org

'Gobby

Technical Support & Development / [NOT RESOLVED]Couple issues, Invalid License amongst them - Reseller Not Helpful

« on: March 08, 2019, 08:32:06 PM »

Hey everybody! First off thanks for your time today. I don't know what's been going on in the background lately but I've had a number of problems in the last few weeks. I'm a novice user and I keep that in mind at all times. I'm positive pretty much 99% of my problems are because I didn't properly understand something, not because the software is broken or anything like that. Though occasionally things seem out of my repair & I've been left trying to figure out what to do. I PM'd Gunthar about one of them but I imagine he's just to busy to be bothered with personal responses to end users.

I run Gunbot inside a Hyper-V copy of Windows 10 Pro Workstation; it's completely isolated, has way more horsepower then it needs, and is wrapped in security given we're talking about money here. It's not used for any other purpose and the machine that hosts it is a stable server that doesn't go up or down including a large battery it sits on to make sure of it. I mention this in order to say, once setup and turned on nothing interferes with the GunBot software. There's no users in the environment, there's no changes every getting made, all updates have been suspended until it's scheduled service day, it exists completely inside it's own world.

Now I paid $750 for this software and it's been a good investment so far, it works far better then I do sitting there staring at the markets all day given I don't want to be staring at the markets all day. Though when things go mysteriously wrong there's very little avenue for self correction, you basically just gotta fire an email off to your reseller and hope they get back to you. I bought through "thecryptobot.com" & have exchanged emails with "Leeview" from there though they've not really been very helpful. My first issue I had was just complete license rejection one day out of the blue. GunBot would refuse to boot and tell me to contact my reseller as my license keys weren't valid. Within a couple hours I got an email back saying they were working on things on their side and that it should be normal now. Okay, great, double check, software turns on again and works. License servers go down, we've all had this happen before, no big deal.

Then I get that email about Gunthy coins going live soon and here's the steps to complete to make sure you get yours. So I go through the email and make an account over at IDAX, get everything setup and on launch.. no coins. Okay well probably something I missed or screwed up, no big deal, we'll just fire a PM off to Gunthar about it. Didn't think posting publicly could really yield any helpful solutions given the launch was already over and it's all stuff on the back end anyways. Then days go by and I get no response, no coins, no communication. Whatever kind of a bummer but i'm trying to stay positive here it's probably not a big deal. Overall I'm still happy with the software just would've liked to have got some money back on it given how much it cost.

Then the portfolio value graph just up and stopped working. Would just load zero balance. Instead of bothering Leeview about this since it's not a reseller issue or contacting Gunthar since it didn't matter last time, I do everything in the bag I can think of. Reinstalling, rebooting, reimaging, actually wiping my accounts back to my base currency regardless of where it was in the trade then reinstalling the software, I mean I tried it all. I checked my firewall logs and my connections to api.gunthy are waaay down so I figured there's just something going on in the background that they're fixing / updating. It's not the biggest problem in the world it's just a major inconvenience and not one I'd expect for such an expensive package. I continue waiting a couple more days and wham it just comes back alive with no changes on my part. I could've not done any of the diag work or hours dicking with things and came to the same solution. Another not on my side problem. Fantastic.

Now for the last few days it's been telling me my second exchange I'm on has an invalid license and to contact my reseller. Nothing has changed, I haven't touched anything, and now I can't trade at all on the exchange. Funds just sitting in the middle of trades and double ups, nope, license invalid. I reinstall, I try readding the API keys, nothing I do works. So I write Leeview from thecryptobot.com again as he's my reseller. Get an email back saying "Hello there, You probably have 2 Licenses . In this case, for each license try a different wallet when you setup the API Key." What? I haven't changed anything, it just stopped working. So I write back "Could you possibly explain that any further? How did it break in the first place? I mean nothing changed on my side at all it just stopped working and it says it's an invalid license." at which I get back "Hello again, You did not break anything. But, you have 2 different licenses (speculating). With the new Gunbot wallets licenses, you will need to create 2 installs, each with its own API Key and wallet."

WTF IS GOING ON HERE. This software generally is great, I love it, but it breaks alot and it's never something I've done. This is a financial sector application, it's uptime and stability should be of the upmost importance. Does my reseller just suck or is something going on? Isn't the whole point of this to be able to add multiple exchanges inside the same instance? There's so many settings directly related to this that I must be misunderstanding Leeview here. I have one Pro edition license to this software, not two, not three, just one. I'm currently connected to two exchanges out of my three allowed on my license. (or well, trying to be) I don't screw with them or the software outside of logging in to check the portfolio balances. Could somebody please explain to me what has happen this time and how to properly get my second exchange backup and running.

Thank for your time in advance, I really appreciate any and all help.

'Gobby

Edit: Updated thread title to reflect resolved status. Thanks again!

Edit 2: Updated thread title to reflect new unresolved status.

Pages: [1]