1
Beginners & Help / Configuration Update: Version III - Colloquially known as “The Machine Gun”
« on: February 14, 2021, 12:33:32 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:
Hello everybody! Back again with some minor updates to the configuration as well some answers to popular questions I’ve been receiving on Telegram. I’d like to give shot outs as well say thanks to everybody who’s been contacting me! It’s been brilliant getting to talk to people from all around the world. You’ve given me lots of new ideas, different tweaks you’ve tried on your own, and all around made my life more cheerful with your kind words.
I’ve been using this software for years and still learn stuff all the time. It had slightly fallen off my radar how much it can be to first timers. Though after speaking with so many of you I’ve started to remember that this can be a very daunting task to setup and understand for newcomers. The best advice I can give is to start small and learn comfortably knowing your life isn’t on the line. Don’t go dropping all your funds in the first week you’re playing with the bot. I know it’s exciting and you want to start making profits but the key is to make money, not to lose it from a basic misunderstanding.
People have really enjoyed my down to earth explanation of the experience. Though I want to stress that this is just the way I’m trading with my goals in mind. Depending on what type of time frames you’re working with it might be better to make bigger trades less often over my rapid-fire small ones. The objective of this configuration is to hit every wave throughout the day, to make money whenever it can. The zoomed out bigger picture isn’t applied. It’s not looking for trends, it’s not monitoring what’s hot on social media, it’s not running a marathon. This thing is sprinting to each profit it can, yelling cha’ching, and taking back off again.
Version 3 Config: (bold settings are new to version 3)
- 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
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)