Frequently Asked Questions & Wiki

machineGun is a complex sub-percentage strategy focused on riding micro-oscillations, utilizing long chain algorithms to create profits where traditional technical analysis traders struggle. Using a plethora of the world's top Nobel Prize winning Mathematicians works' we preemptively make moves in markets and capitalize on each swing, creating outstanding profits in every day normal market conditions while pushing the boundaries of what's possible. We've been in development since 2020! Meaning we're bringing years of comprehensive whiteboarding and dedicated day trading to you in a simple to use, single setting required, strategy that's available to everybody. As long standing members of the Gunbot Community, it's always been our mission to simplify high end trading and bring it to the end user without asking them to have an in-depth prerequisite knowledge across many topics. Here in v5, we have roughly three hundred settings, intricate logic chains for both sides of the market, and a really nice user interface that properly explains what is happening at every moment of operation. There are also preset profiles included for many of the different ways people commonly like to run machineGun, just click a button and you're off to the races with all the underlying systems changed automatically. If you're one who likes to tinker, don't worry everything is completely open to modify! Including full descriptions for every setting, mouse over tool tips, and our entire 100+ page technical manual if you want to get deep. To begin trading all you need to do is pick a market on your exchange and then enter how much you'd like to trade with. That's it, the famous "one and done" setup! We release full feature length films on YouTube detailing out all the settings, proper operation, and time-lapsed market runs so you can watch it work live. These all come with voice overs, where I personally walk you through what's going on. A great resource for new comers who are just getting their feet wet. Over the years we've also built an awesome Telegram community with hundreds of active users, you're always welcome and encouraged to drop on by and say hello to us! If you're just starting out we highly recommended using the simulator feature found inside Gunbot to experiment and begin trading with. This way you can try out different settings, profiles, and overall get a better understanding of how the algorithm works before putting real trades on the books. Once you're comfortable with normal operation, reading the charts, understanding our interface as well as the dashboard, just generally knowing overall what your money is doing, then it's time to go live! Team machineGun is and always has been built on the love from our community, it's the fuel to our never ending relentless search for perfection. So thank you for joining us and welcome aboard!

1.) Enable AutoConfig: Navigate to "AutoConfig" in the Gunbot user interface via clicking the three vertically aligned dots in the middle of the top navigation bar and then selecting it in the new drop-down menu: https://static.wixstatic.com/media/f8796d_b7939a539b0a4ee29f88e16a5d87a7af~mv2.png Once there, make sure you have enabled the use of AutoConfigs: https://static.wixstatic.com/media/f8796d_f6ce48b9029743dc80bff6a3b66c4d99~mv2.png 2.) Add Trading Pairs: Navigate to "Trading Settings" in Gunbot's top navigation bar and select the exchange and the trading pair you wish to trade. https://static.wixstatic.com/media/f8796d_5ea7050937374dfeaa5eca9b9083b0d8~mv2.png 3.) Configure Strategies: Click on the strategy button, inside the new window that pops up select "Community" and then select “machineGun”. (you can also verify your license as shown below) https://static.wixstatic.com/media/f8796d_5725b0b8ff3246f399770f2314b73381~mv2.png 4.) The “One & Done” Automated Configuration: Now inside the options menu for your new pair, expand “Automatic Management”. All you need to do is set “Investment Level” to the total amount in Base currency you want machineGun to work with for this pair. https://static.wixstatic.com/media/f8796d_f8a7d9bd1dd14c12aace2fb979416376~mv2.png Afterwards, click on the "Add Pair" button. Don’t forget to save your changes. https://static.wixstatic.com/media/f8796d_09e8f9036745479c99f54d640e4e1a29~mv2.png 5.) Start Trading: Once you’ve reached this point, everything is setup! Simply press the "Start Trading" or "Start Simulator" button in Gunbot's top navigation bar and you’re off to the markets. 😎 Friendly tip, inside the charts screen make sure you expand the right-side pull-out menu to access our custom user interface. It's in the bottom right hand corner and looks like a little tab you click.

Inside the charts screen if you look on the bottom right hand corner, there's a little tab you click to expand the right-side pull-out menu, which accesses our custom user interface. Here you can find everything there is to know about what is currently happening inside machineGun and with your investment. This is broken down into six parts, starting at the top: • Pair, Position, & Financial Stats • machineGun Overview • Core Overrides (logic conclusions) • Buy Conditions (accumulation chain) • Sell Conditions (exit chain) • Indicators (technical data) Here's an example of what our user interface look likes when properly running: Also, while not included inside Gunbot as part of the normal user interface, we also offer the same chart's screen layout as found inside our release videos! If anyone would like to come along for the ride with all the extended technical analysis unfolding live on your screen, all you need to do is extract the new_gui.sqlite file from this .zip archive (https://f8796d93-6f0c-46b1-b80b-7ce095bcc389.usrfiles.com/archives/f8796d_e26122bcb6024d6d83f7075faf279480.zip)and place it inside your root Gunbot installation directory. Afterward, your chart's screen will display these additional seven types of technical analysis: https://static.wixstatic.com/media/f8796d_0e6d84c27c2343cf94d39888fa96f892~mv2.png NOTE: Please for security purposes never get this file from anywhere else. You're always welcomed and encouraged to open this up in your favorite database editor and give it an inspection. Inside you should find nothing more than each of the major technical analysis forms we can pull from inside Trading View and then formatting options like various line colors, heights, and widths. Also please note this will alter your Gunbot installation completely. Meaning these new indicators will now show up for every pair you're running, regardless if they're running machineGun or not. These layouts can be saved, loaded, and changed at will via the drop down in the upper right hand corner of your chart's screen. Meaning you can save ours, make new ones, or even revert back to the stock appearance for other pairs. 👍

To get to the pair settings menu, first click "Trading Settings" found at the top of the screen, inside the Gunbot navigation dashboard. https://static.wixstatic.com/media/f8796d_8bf1ae1169954fd780260c447c919cb2~mv2.png Inside the page that loads will be all your current pairs and the ability to add / remove pairs. Next, you'll click the "edit" button found on the right hand side of the screen. https://static.wixstatic.com/media/f8796d_e911bd9e1c0249fbab18b02bc9abc15c~mv2.png This will bring you to the settings menu for your pair! Here you will find all three hundred settings of machineGun categorized into 28 easy to use sections based on which features they control. It's important not to get overwhelmed! Most users only ever need to do the famous "One and Done" setup by entering an "Investment Level" inside the first section, "Automatic Management". General operation where the user changes pairs overtime and tries different preset profiles out only requires users interact with the first 3 sections. The other 25 sections are for finetuning and customization that most users will never be interested in or find themselves needing to do. https://static.wixstatic.com/media/f8796d_38fbbf470c6c4418b77358c7e5ac3c27~mv2.png One section in specific I'd like to draw attention to before closing out this chapter, • is the last, Automated Internals. The majority of these settings are changed every five seconds by the algorithm, overriding any changes made by the user. The other settings are mission critical and / or settings from the underlying stepGridHybrid strategy that are not utilized by machineGun. • Users should not change these settings. Manipulating these settings requires a deep under the hood knowledge of machineGun's workings and should only be done by people inside the simulator feature of Gunbot. • Highly recommended not to make any changes to these settings in live markets.

This is an extremely important section so please take your time to read through this multiple times. It is critical to understanding how machineGun utilizes your Investment Level. Let's start with Capital Stages. • If you are between 0-10% invested, you are in the first Capital Stage, 1. • If you are between 90-100% invested, you are in the last Capital Stage, 10. This number is created by dividing your Investment Level into two different 10% sectioned stages, a "Base Stage" and a "Quote Stage", these are not displayed and simply underlying mathematics being explained. These measure your investment by looking at how much Base you currently have versus how much Quote you currently hold for the pair you're trading. These two systems protect each other by comparing what should be versus what actually is. Example: if your Investment Level is $5000 but you only have $1950 in the account, your Base Stage will be at 7 because you only have 39% of the expected base in your account. Example 2: if you had $1100 of Base invested into Quote, then your Quote Stage would be 3 because you're holding 22% of your Investment Level as a bag. Capital Stages display the remaining assets that should be in existence. Validating them by checking each the Base Stage and the Quote Stage, then working off which is currently in the highest position, as a failsafe. Meaning: • if Base Stage = 4 and Quote Stage = 7, then your Capital Stages have 40 - 30% remaining. • if Base Stage = 9 and Quote Stage = 8, then your Capital Stages have 20 - 10% remaining. This allows for the system to adapt live to withdrawals and deposits. If you need to take Base funds out of the trading account temporarily you can do this, machineGun will adapt by assigning you a new Capital Stage as soon as the funds leave the account. Get things straightened out? When you deposit the funds back into the account, it will once again adjust accordingly by changing your Capital Stage. This makes machineGun dynamic and able to cope with the stresses of living in the digital age. This works the same way with Quote Stage outside of the fact that the bot will see and react accordingly to manual sells if you were to make them. Meaning the only thing we're really discussing here is if you were to withdrawal quote by transferring it out while the bot is operating live. The same thing will happen with your Quote Stage automatically changing, machineGun can handle this. Though the underlying PNL & Orderbook systems inside Gunbot will become very confused. You absolutely do not want to mess up your orderbooks inside Gunbot. So overall this practice should be avoided at all costs. So let's review real quick: • moving Base around while live trading is not a problem, things keep working. • moving Quote around while live trading is a problem, things stop working. Now let's move onto understanding Trading Phases because they're just as important as and work directly with the Capital Stage. A Trading Phase is first created by dividing your Investment Level by your Max Buy Count (max steps) which gives you the first Trading Phase, 1. Example: Your Investment Level is 2500 and your Minimum Volume to Sell is 1.25, so your Max Buy Count = 2000. So, Investment Level (2500) / Max Buy Count (2000) = Phase 1 (1.25) Much like Capital Stages, there are also 10 Trading Phases. Now that we have Trading Phase 1 determined, we can generate the other Phases on the grounds that: • Trading Phase 10 Max Buy Count = Trading Phase 1 Max Buy Count / 10 Meaning, Trading Phase 1 represents the theoretical maximum possible number of steps you could ever make. While, Trading Phase 10 represents the theoretical fewest possible number of steps you could ever make before additional order manipulation. After the first Trading Phase, each continual Trading Phase represents an additional 10% reduction in maximum steps when compared to the first. This translates into an additional 10% increase to your Risk : Reward ratio. This concept can be confusing as it's 10% of the starting number of steps, not the current number of steps. An easy way to think about this, is that Trading Phase 10 orders will always be worth 10x that of Trading Phase 1 orders. Example 1: (Investment Level: 2500, Minimum Volume to Sell: 1.25, 10% Phase Weight) • Trading Phase 1 = 2000 Steps = $1.2500 (MVTS) • Trading Phase 2 = 1800 Steps = $1.3888 • Trading Phase 3 = 1600 Steps = $1.5625 • Trading Phase 4 = 1400 Steps = $1.7857 • Trading Phase 5 = 1200 Steps = $2.0833 • Trading Phase 6 = 1000 Steps = $2.5000 • Trading Phase 7 = 800 Steps = $3.1250 • Trading Phase 8 = 600 Steps = $4.1666 • Trading Phase 9 = 400 Steps = $6.2500 • Trading Phase 10 = 200 Steps = $12.500 Example 2: (Investment Level: 7500, Minimum Volume to Sell: 3.75, 10% Phase Weight) • Trading Phase 1 = 2000 Steps = $3.7500 (MVTS) • Trading Phase 2 = 1800 Steps = $4.1666 • Trading Phase 3 = 1600 Steps = $4.6875 • Trading Phase 4 = 1400 Steps = $5.3571 • Trading Phase 5 = 1200 Steps = $6.2500 • Trading Phase 6 = 1000 Steps = $7.5000 • Trading Phase 7 = 800 Steps = $9.3750 • Trading Phase 8 = 600 Steps = $12.500 • Trading Phase 9 = 400 Steps = $18.750 • Trading Phase 10 = 200 Steps = $37.500 Example 3: (Investment Level: 12500, Minimum Volume to Sell: 6.25, 10% Phase Weight) • Trading Phase 1 = 2000 Steps = $6.2500 (MVTS) • Trading Phase 2 = 1800 Steps = $6.9444 • Trading Phase 3 = 1600 Steps = $7.8125 • Trading Phase 4 = 1400 Steps = $8.9285 • Trading Phase 5 = 1200 Steps = $10.416 • Trading Phase 6 = 1000 Steps = $12.500 • Trading Phase 7 = 800 Steps = $15.625 • Trading Phase 8 = 600 Steps = $20.833 • Trading Phase 9 = 400 Steps = $31.250 • Trading Phase 10 = 200 Steps = $62.500 You can see these all have a Max Buy Count or Max Steps of 2000, even though they're different investment levels trading different pairs with different minimum volumes. Meaning since their risk reward ratios are all the same, the bot will act the same with each pair in terms of aggression and risk acceptance / tolerance. This is something we'll discuss a lot more in the section below this one. Okay so now you understand how we derive Capital Stages & Trading Phases, here's where things get neat! We assign each Trading Phase to a Capital Stage. This allows us to start with and return to high-risk high reward behavior when the markets are great, we're not bagged, we can afford to ride unit cost just printing money. Though as our bags start to fill, buying dips, riding downward trends, we slowly decrease how risky we're willing to be by the same 10% steps from before. Meaning: • Capital Stage 1 = Trading Phase 10 • Capital Stage 2 = Trading Phase 9 • Capital Stage 3 = Trading Phase 8 • Capital Stage 4 = Trading Phase 7 • Capital Stage 5 = Trading Phase 6 • Capital Stage 6 = Trading Phase 5 • Capital Stage 7 = Trading Phase 4 • Capital Stage 8 = Trading Phase 3 • Capital Stage 9 = Trading Phase 2 • Capital Stage 10 = Trading Phase 1 Meaning if you're 35% bagged, you're in Capital Stage 4, meaning you're also in Trading Phase 7. Your access to those very expensive top Trading Phases has been revoked because as per your risk reward ratio, you don't have an appropriate amount of Investment Level remaining to be that risky. Here's a more complete example: (Investment Level: 12500, Minimum Volume to Sell: 6.25, 10% Phase Weight) • Capital Stage 1 = Trading Phase 10 = 200 Steps = $62.500 = 0-10% Invested • Capital Stage 2 = Trading Phase 9 = 400 Steps = $31.250 = 10-20% Invested • Capital Stage 3 = Trading Phase 8 = 600 Steps = $20.833 = 20-30% Invested • Capital Stage 4 = Trading Phase 7 = 800 Steps = $15.625 = 30-40% Invested • Capital Stage 5 = Trading Phase 6 = 1000 Steps = $12.500 = 40-50% Invested • Capital Stage 6 = Trading Phase 5 = 1200 Steps = $10.416 = 50-60% Invested • Capital Stage 7 = Trading Phase 4 = 1400 Steps = $8.9285 = 60-70% Invested • Capital Stage 8 = Trading Phase 3 = 1600 Steps = $7.8125 = 70-80% Invested • Capital Stage 9 = Trading Phase 2 = 1800 Steps = $6.9444 = 80-90% Invested • Capital Stage 10 = Trading Phase 1 = 2000 Steps = $6.2500 = 90-100% Invested In this manner, even though we're machineGun and constantly accumulating, we slow burn through your Investment Level by constantly lowering our risk tolerances. This means that when the markets are hot, you're utilizing your investment level to the max, making great returns, though the very moment things start to slow down, so do we. Look at the radical jump in Trading Limit from Capital Stage 1 / Trading Phase 10 = $62.50 to Capital Stage 2 / Trading Phase 9 = $31.25. That's cutting things in half just because we're 10% bagged. This gives us a really good grasp on reality in the subpercentage markets and allows us to protect your Investment Level as we transition the strategy through different modes of operation. Now, that's a lot to take in. But wait, there's more! So, what we do next is technical analysis via the Chande Momentum Oscillator. This allows us to make all 10 Trading Phases selectable any given moment. It's no longer a downward stepping staircase of risk. Meaning with every update of data from the exchange, we now select a Trading Phase to push forward in the logic as appropriate for the current markets conditions. • This means you could be inside Capital Stage 1 but at Trading Phase 3. Meaning we didn't value the current markets at Trading Phase 10 or anything else above Trading Phase 3. If we were going to purchase at this moment, it's only worth $7.8125 to us, not $62.50, as it would have previously been before CMO analysis. This means that every couple of seconds, as the market changes, our analysis changes with it, and your Trading Limits will be constantly moving around. This is normal operation! It is extremely difficult to trigger a Trading Phase 10 order, because if you're going to be spending 10x the money, it better be for a really good reason. Most the time, you will generally accumulate around the middle of the Trading Phases that you still have unlocked via Capital Stage. The technical analysis done through CMO actually spreads out risk evenly as you lock out Trading Phases via growing Capitals Stages. Meaning if you have six Trading Phases left, it will treat Trading Phase 6 as if it was Trading Phase 10, the previous points of distinction from before have all be evenly distributed amongst the remaining Trading Phases. Meaning no matter how many Trading Phases you have left, we're still spending the proper amount at any given time, making sure we capitalize on opportunities as they show up. This means that it's impossible to determine how many actual buys / steps you'll make across your Investment Level, because it's always generated dynamically depending on the live markets. Though this is a good thing because now you're spending less when it's not a great deal and you're spending more when it is. This helps lower unit cost SIGNIFICANTLY. Meaning we can pull your overarching trade sequence's unit cost down much faster than ever before. I cannot express how big of a deal this part of our strategy alone is in increasing profits. Layering is massive! Now, that's a lot to take in. But wait, there's even more! Next, we do another round of technical analysis, this time via the SMI Ergodic Indicator. What we're looking to determine here is when there's a recovery after a dip or bear in the market. Then we assign the highest three Trading Phases you still have access to via Capital Stage, to only be enabled if the markets are actively recovering. What does this do? This means at any time, your top Trading Phases, worth the most amount of your money, are locked out, until a new bottom has been found and things are starting to travel upwards again. This means you cannot spend large sums of money on the way down or middle of a drop. How does this work with the previous CMO analyst? When Trading Phases are locked, CMO now selects from the remaining ones just the same as if they were locked out via Capital Stage. When the markets recover, these Trading Phases unlock, and CMO addresses having the additional three Trading Phases to work with again. Light accumulation into and through a dip? You're always spending the most money at the very bottom and into the swing as the markets start to come back. This is another feature that allows us to drag unit cost down like never before! It's in this manner that machineGun handles your Investment Level, just remember: Capital Stage + (Trading Phase + Chande Momentum Oscillator + SMI Ergodic Indicator) = Current Expenditure Assessment. Updated every 5 seconds. Now before I end this section, I want to point out, there is even more going on past this that will determine your final Trading Limit at any given time. Though this is how we interact with it up to this point in the logic chain. Take a moment to breath, give this a second read, and move on to the next chapters when you're ready. 😎

machineGun comes with five preset scenarios that let you know roughly, in our opinion, where your investment currently stands on the risk reward ratio scale. • This is measured via Max Buy Count (steps) available at the Minimum Volume To Sell (MVTS) for your particular unique combination of: Exchange, Pair, & Investment Level. The resulting number is then measured across a generalized scale for the expected likelihood to enter into a temporary bagged state while trading. This means, in a prolonged market depression, you may run out of funds and no longer be able to manipulate the outcome of the situation. These classifications include: • 0 > 1500 Steps = Highest Risk • 1500 - 3000 Steps = Higher Risk • 3000 - 5000 Steps = Normal Risk • 5000 - 7500 Steps = Lower Risk • 7500 < Steps = Lowest Risk You can always check to see what you're currently running by placing your cursor over the "Bag Risk" section of the right-side pull-out menu interface. https://static.wixstatic.com/media/f8796d_c9d1a46d47504482863b51835e4d7f01~mv2.png The tool tip that pops up will contain all of the relevant information as to how this is being calculated for your specific pair. We recommend people generally start with step counts of around 3000. Some users love to trade around 250 steps, some users prefer 10,000. This is a different strokes for different folks topic and there is not a correct answer, this is up to how you feel about trading in your particular markets. We always recommend people start with as many steps as they can afford, as the more steps you have the longer your runtimes will be and the greater your ability to handle prolonged market depressions. This is exactly how the built in Automatic Risk system handles your investment, by putting you at the lowest possible risk by default and then letting you turn it up if you wish and as you become more familiar with the algorithm. What's all this mean? Let's take a second to discuss some of the finer aspects to step counts. In the practical sense this number represents your ability to "ride the wave", following the currently accepted value of an asset throughout its travels while still continuing to trade it on each oscillation. Utilizing the concept of continual accumulation our number one goal is always to lower your overarching trade sequences unit cost. This is the green line on your chart's screen and represents the break even point of your entire investment. Below it you're in the red, above it you're in the green. With low step counts you're going to spend your investment level much faster and more aggressively, the lower the number the higher the risk, the higher the rewards. The higher the number the lower the risk, which lowers the rewards, but extends your runtime throughout continued market depressions. General rule of thumb, lower is not always better. Meaning, high(er) risk != higher profits. The misconception here is that people often love running very small step counts because profits in the short term are generally outstanding. Which makes sense because you're swinging much larger trades. Though what you're giving up here is your ability to weather the storm. Think about it like your ability to catch longer term market dips. If the market slowly winds down over the span of a week, you want to be able to buy every bit of that dip, because it'll constantly be lowering your overarching unit cost. Meaning when the markets have a positive rally on the next oscillation, you'll have heavy bags ready for big profits, and be much closer to breaking through unit cost than you were at the beginning of your accumulation cycle. To maximize this effect over longer periods of time you need larger step counts. This is the key to better sustained long-term profits as you'll be able to capitalize on longer term market opportunities and trends. How do I interact with this? Inside your pair setting's menu there is a section called "Risk Management" and there you will find all the settings related to controlling your step counts. https://static.wixstatic.com/media/f8796d_aaaa3b14a6764101a78aecb1dba64745~mv2.png The first setting "Automatic Risk" is enabled by default and is standard operation. This setting is a percentage slider starting at 100 and ending at 1000. 100% represents the default aggression level utilizing Minimum Volume To Sell (MVTS) as it's the basis of its calculations. You cannot lower the setting below 100% as you would no longer be able to place orders at your exchange. Though you're welcome to increase this number and it will automatically recalculate your steps accordingly. 200% being twice the risk, meaning you would see your total step count get cut in half compared to 100%. Example: if you normally had 2000 steps at 100%, then at 200% you would have 1000 steps. You can change this number at any time, including in mid operation, and it will recalculate and continue on properly. The second setting is "Manual Risk" and this is where you can set a completely custom step count if you already know exactly how many steps you'd like your Investment Level to be spread out across. This is considered for advanced users who are familiar with the algorithm and how it works. The default setting of 0 means the "Automatic Risk" system will used instead. NOTE: You can only have one of the above two settings active at any given time. If you have a "Manual Risk" set it will disable the "Automatic Risk" system. There is another very important setting called "Accept High Risk" and what this feature does is act like a safety mechanism for the end user. Until this setting is enabled, trading is disabled for users who happen to find themselves calculated inside the "Highest" risk level for holding a bag as per their unique combination of: exchange, pair, and investment level. This means any step count below 1500 requires "Accept High Risk" be enabled, regardless if the number of steps was obtained through the Automatic or Manual system. The reasoning behind this design choice, we found sometimes new users would unintentionally be trading at much higher risks than they were aware. So we wanted to put a safety check in place to put the pause button on things until a user specifically stated they were aware of the situation and wanted to proceed. This does not mean there is any problem with trading in or at the highest risks, tons of users in our community do this and love it. This is exactly why everything in machineGun is an open book, we want our users to be in control and hope everybody can appreciate why this additional step exists. Just looking after folks, specifically those very eager to begin and who might have overlooked their step counts or how the risk systems work. 😇 As you've probably noticed, there are even more settings in "Risk Management" but we'll cover those down below in a chapter dedicated to more in-depth explanations for each setting.

machineGun comes with three different Operational Modes and one Mode Override, that change the overall behavior of the algorithm. These include: • Moon Mode • DCA Mode • Flipper Mode • Close Override Each fully configurable with its own settings, including the ability to turn entire modes on and off. These are also automatically configured by using the profiles system found in the "Automatic Management" section of your pair settings menu. By default, the bot changes Operational Mode depending on which Capital Stage it's currently in. • Capital Stages 1 - 4 = Moon Mode • Capital Stages 5 - 8 = DCA Mode • Capital Stages 9 - 10 = Flipper Mode The only difference is the Override, Close Mode. This occurs whenever we're not in Moon Mode & within X distance of Unit Cost. You can find which Operational Mode you're currently inside by checking our user interface inside the charts screen's right side pull out menu. Each Operational Mode serves a different purpose and function. It's important to understand why they exist and what they do before altering their settings. Let's start with Moon Mode: Moon is the default Operational Mode of machineGun, it's where you'll start trading and it's where you always want to be trading. In this mode we're riding every oscillation of the markets with your overarching trade sequence's unit cost constantly being dragged down with each market depression. We invest heavy, we invest quick, we use much tighter trailings on orders, and you have full access to the highest Trading Phases meaning you can burn through Capital Stages very quickly. This is the idea state of machineGun and when profits are the most extreme. This mode makes partials exits until it's almost depleted its hand, then it will close up the entire order books and make a complete exit. This allows it to ride waves upwards and be extremely selective about which assets it can sell and which ones it'll keep to further work down on the market's next oscillation through an accumulation cycle. Normal behavior is the constant riding above and below of Unit Cost, which is the green line on your chart's screen. If the Skimmer system is currently enabled this means exits can be made BELOW unit cost as well, this is activated when the markets are inside extremely tight conditions. This allows machineGun to ride micro-oscillations where the markets would not have made it over the traditional boundaries of unit cost, given it's based on the entire trade sequence's position. In these situations as long as the profits are correct, this expands the exit logic to work under unit cost. Ideally we would never leave Moon Mode, but markets are markets, and depressions have a tendency to prolong themselves for many reasons outside of the algorithmic day trader's ability to control or even know about. Let's move on to DCA Mode: Once you've entered into DCA, or Dollar Cost Average Mode you're no longer looking to partial out bags at each peak. You're not looking to make small exits or maximize profits across your entire position. This looks at the situation and says it's time to start bringing it all home and closing out existing trades that are out of position and overvalued. • This is a risk reduction mode, it's only focus is a profitable return of your entire hand. In this mode we are much more selective about when we accumulate, we turn on all the long term technical analysis systems, we increase the trailing requirements, and overall slow down the rapid fire nature of machineGun. Here you will not see partial exits ever be made, nor any exits below unit cost. The only thing you will see on your chart's screen is endless accumulation cycles until it's managed to lower your entire trade sequence's overarching unit cost enough that on the next positive oscillation it's able to properly close all of your trades out, at profit. Now there are even settings about how you can record the following interaction on your books and inside the dashboard screen. The default setting is to show you a true Unit Cost split of your entire position. This means, you will see losses, reported as "fck up trades" inside the dashboard screen, for every part of your position you had that was over valued, over priced, and closed above the green unit cost line, at a loss. This also means you'll see a whole stack of green profitable trades reported at the same exact timestamp. These are all the parts of your position that were sold under unit cost, or in the money. These will always equal more than the losses, which is why DCA Mode can make the trade and close your entire sequence out at profit. Though if you did not want losses reported and only wanted to see the profits from the entire sequence, then we have a setting you can turn on that will change the exit target from "Unit Cost" to "Break Even". This simplifies all the math down to just the profits you earned and doesn't report the rest of the trades at all, just the final lump sum. This was mainly included for yearly financial reporting purposes (see: taxes) and it might be something to look into depending on where you live and what your government asks of / wants from you. Though let me go back a bit and restate something, as I find users often contact me over this. • Close Mode is not concerned with hunting perfect exits, it's a risk reduction mechanism. So what happens here is people will be deeply invested, in their later Capital Stages, the markets will pop up, they'll pull everything home, get their entire hand back, and make some really good money while it happens. Great day in the markets right? That's not the reason folks reach out, it's if a sizable rally happens in following hour(s) and they're upset that such a large amount of their investment level was used to close out at what they perceive was too early a time or too small of a profit. Which generally means there is a foundational misunderstanding as to the purpose and function DCA Mode. Having the ability to close all of the parts of your trade sequence that were wildly out of position is worth all the money in the world. Also, as much as we do advanced mathematics to preemptively identify market trends, this is algorithmic day trading. When the logic chains are completely validated, trading happens. It's emotionless, it's completely automated, it lives purely in the world of the numbers it's requested to operate within. It is not a magic ball that can see the future nor does it care, it's seeking parameters and executing orders based on them. If you're ever looking at the charts and find something you'd rather have been handled differently, instead of getting upset, the proper response is, now how do I change that? All three hundred settings that control machineGun are completely open to the end user and fully customizable. If you would like to fine tune required gains or any functionality of the algorithm, it's in the pair settings menu and something you're encouraged to do. After five years of development, our presets have been back tested to exhaustion across hundreds of markets, but they might not apply to your market or your particular trading style. Many users in our Telegram community have heavily modified and tuned their machineGuns, so if you're the creative type, come show us what you've made! Back on track, I wanted to explain why the Capital Stages are positioned in this manner, splitting your Investment Level up 40/40/20. This is so that when you transition out of Moon Mode, you still have enough funds left to make an exact 1:1 DCA pull downwards (as measured in base investment) from the preexisting unit cost that you acquired inside Moon Mode. Now thanks to dynamic accumulation there is not a simple calculation one can run as to how much any given trade will lower your overarching unit cost. Though we go through tremendous effort and many design tricks to dramatically lower that number throughout this process. A great example of that is order layering, where we only allow access to the highest Trading Phases when the markets inside a depression have bottomed out and started to recover. Furthermore, if you change your preset profile to disable Flipper Mode (see: only running Moon and DCA Mode) then the Capital Stages would be reconfigured to a 50/50 split of your Investment Level instead. This still maintains the 1:1 drawdown relationship between Moon and DCA mode. For customization, the more you favor DCA, the safer your trading will be as it'll start trying to return your hand earlier. Counter, the more you favor Moon, the longer you'll continue hunting statistical peaks and partialling off bags at the perfect exit points. Alright, moving on to Flipper Mode: So it's extremely important to understand that this mode can and will change the future of your trade sequence, often in ways that newcomers misunderstand or don't even notice at first. Here in Flipper Mode, our goal is to return to making profits, even though we're currently going through an extended market depression that has taken us to the verge of our bags. Which can be difficult to do because you have an extensive trade sequence hanging over your head as the markets continue to faulter. You can think of Flipper Mode much like you think of Moon Mode, but instead of oscillating above and below unit cost, it's now going to perform the same partial exit mathematics on positions it's opening at the end of the Capital Stage system instead of the beginning. Meaning it's going to begin rapid accumulation cycles but with much smaller plays, wait for the markets to mature, then partial out exits at statistical peaks, rinse and repeat. The only difference, and where the plot is often lost, is you're operating below unit cost. • This means every order you place will impact your overarching trade sequence. A great way of explaining this to people is how you get out of Flipper Mode, at which there are two methods. 1.) the markets return enough for you to sell out the bottom of your position, returning enough funds to raise your Capital Stages therefore returning you to DCA Mode. Or, 2.) the markets return enough for you to enter Close Override then exit your entire hand, returning you to Moon Mode. In case of the first situation, what you've done is managed to profit throughout the extended downtime of the markets, but with each position flipped below unit cost you've removed the most valuable (weighted per base) orders when it comes to getting you out of the entire trade sequence and back inside Moon Mode which is where you want to be at all times. This is a trade off, if the markets didn't return for a lengthy amount of time, well, you profited every day. Though when the markets do run up, you're ultimately making it harder on yourself by raising the bar to closure as you exit out the bottom of your position. This is why it's very common for users to use the preset profile that disables Flipper Mode completely. This means they get the entire draw down of every single order placed below Unit Cost, meaning the barrier to re-entry into Moon Mode is lower and easier to obtain. Though in exchange, lose the ability to continue profiting until they have completely exited their trade sequence. As many other topics in trading, this is once again a different strokes for different folks situation where the correct answer just depends on how you feel about it. Finally, let's talk about Close Override: This is the only Mode Override found inside machineGun, and this has the ability to turn on when you leave Moon Mode and enter into DCA or Flipper Mode. What this does is look for when you're close to your overarching trade sequence's unit cost and change settings in preparation for the closing out of your entire position. If the markets go back down, you'll re-enter the previous Operational Mode you came from, if the markets continue to run you'll properly exit out and return to Moon Mode. You can think about it like the final handshake to exiting all of the risk you've acquired throughout this trade sequence. Completely resetting your trade books and allowing you to start a new sequence of positions at the current accepted value of the asset instead of having a ranging spread on both sides of the markets. Risk reduction is so important when it comes to living to trade another day and maximizing profits across never ending runtimes. If your bot has been live and trading for over a year straight, you want to make sure it's books are pristine, it's ledgers are flawless, and everything is fully functional as even the smallest issue will cause problems over months into years. Every single time you Close Override back to Moon Mode, everything is wiped clean and ready to start fresh again. This means there's no complicated CPU intensive partial calculations going on, there are no orders still open on the exchange, trades have all been finalized, are on the books, and even your Tax software will now properly report them. This is critical to running machineGun on lower end hardware as found in most common home installations, like laptops or old desktops. It's pretty much good all around and a feature you should keep enabled at all times. Looking to tinker? Everything related to the Operational Modes can be found inside the Mode Management sections of your pair settings menu. 😎 https://static.wixstatic.com/media/f8796d_09717ea559b74686a25fbe46611daa3a~mv2.png

So let's talk about logic chains and how machineGun determines when it's a good time to enter or exit a market. https://static.wixstatic.com/media/f8796d_b099e49c50db470385b64feffcbaf4db~mv2.png Here in the screenshot you can see the "Buy Conditions" section of our custom user interface. NOTE: This can be found by pulling out the right side menu inside your chart's screen. This shows you the current status of 15 different forms of technical analysis we do before validating the accumulation logic chain and allowing purchases to begin. The first 7 are calculations derived from other mathematicians while the remaining 8 are forms of analysis we've created in house. All of these can change between various states: validated (green for go), invalidated (red for stop), currently not enabled (off), or temporarily disabled by another form of technical analysis (blue). It's also important to note that the actual analysis being done within each section can and often does change depending on market conditions and which Operational Mode machineGun is in. These differences, like if MACD is currently being followed or if MACD's Signal is being followed, can be found by mousing over each section with your curser. Popup tooltips exist for every part of the chain and can be found in this manner, letting you know exactly what it's requirements are and what it's using to validate them. https://static.wixstatic.com/media/f8796d_b6c432baf3324b9c99f99d57bbc6cce9~mv2.png Here you can see the same thing as above, but for the exit logic chain. There are 12 different conditions that need to be met, the same core 7 forms of technical analysis from above, then an additional 5 we've created along the way. Though there is actually a 13th hidden condition for an exit to be made, one that is not from machineGun so therefore is not seen inside the UI. The last step before an order can be placed once the exit side logic chain is fully greenlighted, is it needs to meet the criteria of stepGridHybrid's v2 Trend Module. While we've spent years building on top of stepGridHybrid, its underlying mechanics are still fantastic. Here we return back to the underlying strategy and let it make the final pull of the trigger now that everything we're concerned with has been validated. Both of these sections, all of the 27 different Buy and Sell Conditions, work exactly the same inside the user interface. Meaning you can quickly glance at them and know exactly what is going on. Once you've become familiar with this process and what the different forms of technical analysis are for, you'll be able to derive pretty deep market insight through these alone. Though one thing I'd like to note is, reading both of these sections is often unneeded. For casual users who aren't concerned which out of 27 different things is holding up the logic flow in one direction or another, then the section above these "Core Overrides" is basically all you'll need to look at. https://static.wixstatic.com/media/f8796d_7d7a603a4cf8436e8dea351a9e54861c~mv2.png Here you can see the ultimate conclusion of the logic chains here, with a much simpler three conditions. Are buys currently enabled? Are sells currently enabled? Is Forever Bags currently enabled? Yes or No. These are binary options and there's no other colors or symbols. Super easy. These will change with the Conditions from each section above as they validate. Also since up to this point we've not discussed Forever Bags, this is showing you if you're currently holding bags in order to partial them out at statistical peaks. This is how both Moon and Flipper Mode operate. If this is not validated it means you're currently attempting to exit your entire trade sequence, returning your hand inside DCA Mode or Close Override. At the most basic level, this is all the information one needs in order to see exactly what their markets are doing. Are we buying? Are we selling? If so, is it partialling my bag out at peaks, or is it looking to bring it all home? In this manner you don't need to complicate your life with reading each of the 27 different conditions below this, you already know the outcome. Between these three sections of our user interface, you can learn everything you need to know about the logic chains of machineGun. 😎

A user asked the other day in the official machineGun Telegram group if there was any advantage or disadvantage to running 20-30 pairs within a single instance of Gunbot. This is actually a great question and I thought it deserved a place in the manual. So let's talk about REST pair cycling! Let's say it takes 8 seconds to get data you requested from an exchange. (that's what I'm generally getting right now on Coinbase) Then you also add your Exchange Delay value, which for a lot of users is around 2 seconds. (depends on exchange, and note: this is a core Gunbot setting) This means you have 10 seconds of time invested in a single pair cycle. Afterwards Gunbot will cycle to the next pair and so on until it's finished all of your pairs, at which it'll start back at the beginning. • Meaning you're making it through 6 pairs per minute. If you had 20 pairs running, this would mean there's a 3+ minute cycle time before you get back to your first pair. This is really anti-machineGun behavior and will cost you greatly in terms of performance, profits, and success. I cannot stress enough how terrible this will be for your end results. To help get around this, you should split your pairs up across multiple instances of Gunbot. Keep increasing the amount until you get temp banned for requesting too much data from, therefore hammering, your exchange. This will tell you how many pairs you can cycle at the same time simultaneously. Dial it back down by a client once you've found the limit and after that add additional pairs to each of those clients. Spread them out evenly, making sure each gets two pairs before any gets three pairs, etc. This is the fastest you can possible run Gunbot / machineGun on your exchange with multiple pairs, keeping each pair up to date with the latest market information as often as possible if you're using the REST protocol. (which is the default found inside machineGun & Gunbot) But wait, let's talk about Websockets! Now here's a really cool feature that the core Gunbot team ported over from their arbitrage tool. What this does is establish a direct connection with the exchange and stream the live data into Gunbot, no longer requiring any cycling. This is called websockets and you can enable it in your core Gunbot Settings, it is not a machineGun setting. This means you can establish connections for all of your pairs inside a single Gunbot client and no longer require running additional clients to spread all your pairs out across. This is much more efficient and requires significantly less hardware wise to trade large numbers of pairs. Now here's the downside, if you experience instability in your connection or setup, then you might drop a stream and not be able to reconnect. The robot nature of the REST system is not found here and it's a more fragile ecosystem. You'll want to keep a healthy eye on your pairs and make sure they're currently properly socketed from time to time. Also, • machineGun was designed on the REST system. While most users report back compatibility without issue, we didn't design machinGun using websockets. So if you're interested in using it, by all means, give a whirl! If you find success where you trade, then let the community know in the Telegram channel, I'm sure others would appreciate the information.

Every exchange returns a different amount of candles when you request data from them. Some will give you access to weeks of history, some days, some only hours. This means that when we perform any technical analysis, we have to work within the time frames returned by the exchange. Almost every mainstream exchange offers at least the last 100 candles of data to their customers. So the time we have to study the markets becomes 100 candles. This way the strategy works the same for everybody no matter where they happen to be trading. Now the underlying stepGridHybrid system we build on top of does it's own technical analysis by looking at these candles across the: 15 minute, 1 hour, and 4 hour periods. machineGun itself does all it's own technical analysis utilizing the 5 minute period. Though extrapolates multiple protections across various time frames ranging from 5 minutes all the way to 8 hours. This is because: • 100 candles x 5 minutes = 500 minutes of historical data = 8.33 hours of hindsight. This means, while unsupported and outside of the design spec, you could change the PERIOD setting from 5 to 15 and now review the last 25 hours. This would give you trading behaviors based on much more long term data. In this manner, you could also change it from 5 to 1 and now you'd only be reviewing the last 1.66 hours, making your bot incredibly reactive to short term trends but lacking any long term knowledge. Throughout design we continually tested other periods and were always validated that the 5 minute period is the best blend of both worlds. It's the goldilocks' zone. Here we're still very agile to short term trends, but we still have the last eight hours of the trade day to look back on and consider. • We do not recommend changing the period away from the default of 5. There are times, commonly on decentralized exchanges (DEXs), where the trading periods found on mainstream exchanges are not available. A great example of this currently at the time of writing is Hyper Liquid. While their website lets you see the markets in all the common periods, this is just an import of Trading View. Their actual exchange only lets you trade in the 1 or 15, not the 5. Here you're going to be required to go off spec and change machineGun away from how it was designed if you want to trade there. Which while it sounds as simple as changing the period setting, we cannot stress enough, wildly invalidates some forms of our technical analysis, specifically many market protection mechanisms. Because we do not design outside of the 5 minute period, it's 100% worth your time to visit the machineGun Telegram community and ask other traders which modifications they've made, if they're trading on one of these more remote exchanges. Also, be prepared, because this is another different strokes for different folks topic and you're probably going to get a handful of different opinions presented to you. Take what feels right and what you agree with, how you trade is your business and it's important you know what you're doing.

This is a complex topic so I hope this section helps more people understand why some pairs are expensive to trade while others are literally just above the exchanges minimums. Let's use KuCoin & SOL as an example, this would have a MVTS of: • A.) 0.1 USDT • B.) 0.01 SOL If you were trying to trade SOL and it's price was 145 USDT (for 1 SOL), the MVTS in USDT is $1.45 because of B. If you wanted to invest $1000 into this pair, it would give you a Max Buy Count of $1000 / $1.45 = 689. This places you in what we consider an aggressive, high bag risk scenario. • But there is another problem. The size of an order is given in Quote, not Base. So while Gunbot uses Base as the way to define the Trading Limit, the orders have to contain the Trading Limit in Quote. Now each exchange allows a different number of digits to send in an order for each coin. For USDT-SOL, KuCoin allows 2 digits. That means the lowest possible order size is 0.01 SOL. Since Gunbot works with Base, the Trading Limit needs to be converted from USDT to SOL. Because of rounding issues by divisions and dynamic prices, we could end up at a SOL order size lower than the allowed 0.01 SOL. Example: • Trading Limit is set to $1.45 and the price of SOL is currently $147. • Your order size would be 1.45 / 147 = $0.0098. • GB truncates the order size to 2 digits = $0.00 • That order would be rejected. To address this issue we have to increase the Trading Limit (in Base). The entire Minimum Trading Limit Calculation is done in price ranges, we do this as to not constantly change the Trading Limit and the rest of the underlying depending values every 5 seconds as the script runs. machineGun finds a Trading Limit which will always result in an allowed order size for any given 50% price range. If the value of the asset goes beyond this, it will be recalculated. This situation hits hard if a Quote has only a few (1 to 2) allowed digits on your exchange. Example: • An order of 0.01 SOL will cost you $1.45 USDT. • The next possible order size is 0.02 SOL, that will cost you $2.9 USDT. • That means your minimum order size has doubled. This also hits hard if the value of your asset is extremely high. • If your MVTS = $8.66 • Then for every 1000 Steps (Max Buy Count) you'd require $8,660 in Investment Level. If you wanted to run right in the middle at the "Normal Bag Risk", then you'd need: • $8.66 x 3000 = $25,980 Investment Level This means that some users might accidently run machineGun at extremely high risk scenarios without realizing it, simply because the pair they're trying to trade has a high MVTS on their exchange. Meanwhile plenty of other pairs on the same exchange might have a much lower and more manageable barrier to entry. A great representation of this is the rule of thumb that most pairs at the popular Binance exchange have a $5 MVTS. Though this is not true, they offer a number of pairs at $1 minimums. MVTS is extremely important to understand and to how machineGun works as we base so much of our logic around it. Make sure you've given this chapter a couple of reads before moving on.

https://static.wixstatic.com/media/f8796d_f84910944c994983b225278bc1a56b0a~mv2.png • "Investment Level" Enter the total amount of Base currency you want to invest into the trading of this pair. Example: with the pair "USDC-BTC". USDC is your Base. BTC is your Quote. This number does not represent the amount you will spend on any given trade, yet the total amount of funds you want to make available for machineGun to use at its discretion. NOTE: If the amount entered triggers machineGun's High Bag Risk warning protection, then you'll also need to enable the "Accept High Risk" setting found inside the "Risk Management" section of your pair settings menu. Normal operation will resume afterwards. • "Settings Profile" Popular preset configurations allowing changes to overall behavior at the click of a button! NOTE: This only updates your settings once you have saved your changes, applied the changes, and then cycled machineGun. Upon activation for the first time, machineGun sees the request to change your settings and then does it. It does not change them in your settings menu live as you select profiles. Standard Settings: 40/40/20 split of Capital Stages between Moon, DCA, & Flipper Mode. These are the defaults and standard operation for machineGun. All Modes. Partial & complete exits. Only DCA/Close Mode: 100% DCA/Close Mode. No Moon or Flipper Modes. No partial exits, only complete. Moon Mode Disabled: 50/50 split of Capital Stages between DCA & Flipper Mode. Complete exits preferred, then partials. DCA/Close Mode Disabled: 50/50 split of Capital Stages between Moon & Flipper Mode. Partial exits preferred, then complete. Flipper Mode Disabled: 50/50 split of Capital Stages between Moon & DCA/Close Mode. Partial & complete exits. Goblin's favorite. Have some amazing presets? Let us know! We can add you right to the list! • "Update Version" Update all non-mission critical settings to the default values found in this version. This will overwrite your current settings with the newest ones. This flag will deactivate once the values have been updated upon the first cycle of machineGun. It does not stay enabled once the update is completed.

https://static.wixstatic.com/media/f8796d_d3b91d66c57e494b9ea3abba3cec0812~mv2.png • "Stop Trading After Next Exit" When enabled, machineGun will stop trading this pair after completely exiting your current trade position at profit. Use this to properly exit a market you no longer wish to trade. • "Ignore Trades Before Timestamp" Force machineGun to not consider any trades before the set timestamp. Useful when returning to markets with previous trade history that you do not wish machineGun to consider moving forward. You can use www.currentmillis.com to convert human readable time into unix timestamps, make sure to use the timestamp in milliseconds. • "Always Keep X Amount of Quote" Force machineGun to respect the set amount of Quote, which will be held back in reserve & never sold. Example: if you set this to '2' while trading USD-ETH, machineGun would always keep 2 ETH on hand & only allow exits on Quote beyond that amount. • "Disable Notification Spam" Turns off the Gunbot popup notification system, preventing the constant spam of logic updates in the bottom right hand corner of the UI. Enabled by default, a highly recommended quality of life improvement. • "Fix Order Bubble Spam" Removes logic spam from inside the chart screen's notification bubbles. Now only showing successfully executed orders. Enabled by default, a highly recommended quality of life improvement. • "Update Instance Name" This automatically updates your client's instance name so it's easier to find in your tabs and browser history. Enabled by default, a highly recommended quality of life improvement. • "Minimum Partial Quote Balance" Minimum amount of Quote required before Partial Exits are possible. As measured by 'MVTS x Minimum Partial Quote Balance'. Designed to help avoid ghost quote generated by stepGridHybrid & improve the partial exit system. • "Exchange Rebate" Percentage of Exchange Fees rebated. Doesn't apply to everybody, only for select exchanges and users if you qualify for a rebate via a VIP or subscription program. Default of 0 disables feature.

https://static.wixstatic.com/media/f8796d_6edf0671ec9f44c98b4c539d5276b7f0~mv2.png • "Automatic Risk" Automatic management for your Investment Level without needing to understand more complex concepts. Measured as a percentage, 100% being normal operation, trading at the minimum order size accepted by your exchange for your pair. This setting can only be increased above 100 & not brought below 100. Example: A setting of 250 would result in your lowest Trading Phase being "MVTS x 2.5". Meaning if the minimum order size for your pair was $1.06, machineGun will now use $2.65 instead. If you set a Manual Risk, it will disable this system. The risk of holding a bag is calculated by total available step count: Highest Risk: 0000 - 1500 Steps Higher Risk: 1500 - 3000 Steps Normal Risk: 3000 - 5000 Steps Lower Risk: 5000 - 7500 Steps Lowest Risk: 7500+ Steps • "Manual Risk" This allows you to manually define your risk reward tolerance via setting a maximum step count across your Investment Level. By default machineGun will always add more steps as you increase Investment Level, meaning it continually lowers your risk. By manually setting a maximum step count, when you increase Investment Level you would now increase the size of each individual purchase instead of increasing steps. This would mean MVTS (Trading Phase 1) would now be determined by Investment Level / Manual Risk. Setting a Manual Risk overrides the Automatic Risk system. The default of '0' uses the Automatic Risk system. Thoughts on various step counts: 200 steps would be considered very high risk, thanks to its extremely limited runtime. 3000 steps would be considered average where statistically through back-testing most hands are returned before the user reaches the end of their funds. 5000 steps would be considered low risk & has been found to be a community favorite! Allowing for longer operation through greater depressions in markets, returning exceptionally good draw down of Unit Cost for your patience. 10,000+ steps is where testing starts to show decline in bag utilization over prolonged trading sequences. Considered the whale standard, being able to successfully continue trading through all levels of market fickleness at a machineGun pace can get expensive. If your minimum order size was $5.50 then a setting of 10000 requires a minimum Investment Level of $55000. • "Trading Phase Weight" Determines at which percentage overall steps are reduced per Trading Phase. 10% being the highest risk to reward ratio, with 5% being the lowest. This gives the user greater control over how much they invest per individual order. The default of 5% places users at the lowest risk via greatly limiting how much capital the higher Trading Phases have access to. Example: 2000 Steps with a $1 Minimum Order Size @ 10% vs 5% Trading Phase 1: 2000 ($1.00) vs. 2000 ($1.00) Trading Phase 2: 1800 ($1.110) vs. 1900 ($1.052) Trading Phase 3: 1600 ($1.250) vs. 1800 ($1.110) Trading Phase 4: 1400 ($1.428) vs. 1700 ($1.176) Trading Phase 5: 1200 ($1.666) vs. 1600 ($1.250) Trading Phase 6: 1000 ($2.000) vs. 1500 ($1.332) Trading Phase 7: 800 ($2.500) vs. 1400 ($1.428) Trading Phase 8: 600 ($3.332) vs. 1300 ($1.538) Trading Phase 9: 400 ($5.000) vs. 1200 ($1.666) Trading Phase 10: 200 ($10.00) vs. 1100 ($1.818) Meaning: • with a 10% weight: your Trading Limits can range from $1 - $10. • with a 5% weight: your Trading Limits can range from $1 - $1.818. These values represent Trading Limits before further modification by other features like Risk Tuning. • "Weight Focus" Determines where to focus the weight of the Trading Phase system. The default setting of "Depression / Dip" invests more throughout market depressions with the highest value orders occurring inside the dip. This is standard operation. While the "Recovery / Swing" setting invests more once the drop has finished and markets have started to recover, with the highest value orders occurring during bull runs and upward trending markets. Being seen as safer investing by some traders, this methodology celebrates upward trending markets and looks to capitalize larger with heavier investments in less risky situations. Trading profit for security • "Accept High Risk" Enabling this setting clears the alert from both the console and the UI warning the user their current unique combination of exchange, pair, & investment level has a projected high risk of holding a bag at times. Enabling this allows the user to trade inside the higher bag risks, clearing the protection halt, and returning normal operation. Generally users trading with smaller investment levels will need to turn this on as they cannot afford enough steps to be considered at anything but high risk, even when trading at the minimum accepted order size on their exchange for their pair. Example: If you have an Investment Level of $500 on Binance & your minimum order size is $5.25, then you can only afford to make 95 steps at the MVTS. This situation would be considered at a high risk of temporarily obtaining a bagged status because drawing down Unit Cost becomes very difficult to do with such limited resources. Meaning you'll occasionally enter into a holding pattern until market recovery occurs.

https://static.wixstatic.com/media/f8796d_6adef6a5b3bd43b2accb4ef1c86be43b~mv2.png • "Moon Mode: Required Gain" While inside Moon Mode, defines the minimum profit percentage above the unit cost of an asset that must be achieved before a partial exit can be made. Example: A setting of 1% ensures that exits can only occur when gains are 1% or higher. This mode is designed to make partial exits of your position at technical moons in the market while oscillating above and below unit cost. It's aggression and behavior is heavily altered depending if Skimmer is enabled. Normal: Exit Logic Unit Cost & Partial Gain Protection Respected. Accumulation based on long term technical analysis. Exits based on short term technical analysis. Skimmer: Exit Logic Unit Cost & Partial Gain Protection NOT Respected. Accumulation & exits are both based on short term technical analysis. Will naturally close your position through partials or accumulate into DCA Mode. • "Moon Mode: Order Trailing Range" While inside Moon Mode, defines the specific percentage used for the order trailing range. Example: A setting of 0.25 means the trailing range will be 0.25% of the current price. • "Moon Mode: Trend Trailing Exit Multiplier" Applies a multiplier to Moon Modes Order Trailing Range when exit conditions are favorable via stepGridHybrid's v2 Trend Module. Used to increase the trailing range of exits during positive market trends in order to find more favorable positioning. Example: A setting of 2 would double the Moon Mode Order Trailing Range default of 0.01 to a value of 0.02.

https://static.wixstatic.com/media/f8796d_cf5451e7db4647fb88acfac58a304e9d~mv2.png • "DCA Mode: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling DCA Mode. Meaning machineGun is transitioning out of Moon Mode. Example: If you select a value of 4, DCA Mode will be disabled in Capital Stages 1, 2, & 3. This mode is designed to lower your overarching position's unit cost. No exits are enabled in this Mode. Its accumulation aggression is heavily altered depending if Skimmer is enabled. Normal: Accumulation based on long term technical analysis. Skimmer: Accumulation based on short term technical analysis. Can Close Mode back to Moon Mode or accumulate into Flipper Mode. • "DCA Mode: Required Gain" While inside DCA Mode, defines the minimum profit percentage above the unit cost of an asset that must be achieved before a partial or full exit can be made. Example: A setting of 1% ensures that exits can only occur when gains are 1% or higher. • "DCA Mode: Order Trailing Range" While inside DCA Mode, defines the specific percentage used for the order trailing range. Example: A setting of 0.25 means the trailing range will be 0.25% of the current price. • "DCA Mode: Trend Trailing Exit Multiplier" Applies a multiplier to DCA Mode's Order Trailing Range when exit conditions are favorable via stepGridHybrid's v2 Trend Module. Used to increase the trailing range of exits during positive market trends in order to find more favorable positioning. Example: A setting of 2 would double the DCA Mode Order Trailing Range default of 0.1 to a value of 0.2.

https://static.wixstatic.com/media/f8796d_35621adba726432386a3fe550394c772~mv2.png • "Flipper Mode: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Flipper Mode. Meaning machineGun is transitioning out of DCA Mode. Example: If you select a value of 8, Flipper Mode would only be enabled in Capital Stages 8, 9, & 10. This mode is designed to make partial exits at technical moons in the market while underneath your position's overarching unit cost. Can naturally transition back to DCA Mode or Close Mode back to Moon Mode. Exits based on short term technical analysis. It's accumulation aggression is heavily altered depending if Skimmer is enabled. Normal: Accumulation based on long term technical analysis. Skimmer: Accumulation based on short term technical analysis. • "Flipper Mode: Required Gain" While inside Flipper Mode, defines the minimum profit percentage above the unit cost of an asset that must be achieved before a partial exit can be made. Example: A setting of 1% ensures that exits can only occur when gains are 1% or higher. • "Flipper Mode: Order Trailing Range" While inside Flipper Mode, defines the specific percentage used for the order trailing range. Example: A setting of 0.25 means the trailing range will be 0.25% of the current price. • "Flipper Mode: Trend Trailing Exit Multiplier" Applies a multiplier to Flipper Mode's Order Trailing Range when exit conditions are favorable via stepGridHybrid's v2 Trend Module. Used to increase the trailing range of exits during positive market trends in order to find more favorable positioning. Example: A setting of 2 would double the Flipper Mode Order Trailing Range default of 0.01 to a value of 0.02.

https://static.wixstatic.com/media/f8796d_134eb59162a440af92ae20fc1c5026df~mv2.png • "Close Mode: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Close Mode. Once enabled, machineGun will close it's entire trade sequence out in a single exit instead of through multiple partial exits. Example: If you select a value of 3, Close Mode would be enabled in every Capital Stage but 2 & 1. Keep in mind, both "Close Mode Minimum Capital Stage" & "Close Mode Minimum Distance" must be satisfied before Close Mode will activate. This mode is only concerned with closing out your entire trade sequence in a single exit. This allows you to clear all of your out of position orders above the current accepted market value. This allows machineGun to reset (at profit) back to Moon Mode with all Capital Stages and Trading Phases available. Exits based on long term technical analysis. • "Close Mode: Minimum Distance" Sets the minimum distance required from Unit Cost before Close Mode can activate. Example: If you set this at -1, Close Mode will activate when the markets are within 1% of your positions Unit Cost. • "Close Mode: Bagged Exit" Modifies the Close Mode logic chain to only concern itself with returning your entire hand at its first opportunity instead of waiting for technical analysis to validate an exit at a better position. When enabled, all forms of exit related technical analysis are disabled except Unit Cost & Gain. Works as a percentage of remaining Investment Level and is activated upon crossing the threshold. Meaning if you set a value of 5% and have 4% of your Investment Level remaining, this feature would be activated. If you had 6% remaining, this would be deactivated. • "Close Mode: SMIEI Sell Detection System" While Close Mode is active, sets the line used for detection of SMIEI Sell Protection: SIGNAL, INDICATOR, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower than the INDICATOR line. Considered long(er) term technical analysis depending on methodology selected. SMIEI uses the preemptive T-2 mathematics developed by William Blau to detect early market trends as they're developing & react beforehand. • "Close Mode: MACD Sell Detection System" While Close Mode is active, sets the line used for detection of MACD Sell Protection: SIGNAL, MACD, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower then the MACD line. Considered long(er) term technical analysis depending on methodology selected. MACD uses mathematics developed by Gerald Appel to identify price trends, measure trend momentum, & identify entry points. • "Close Mode: KVO Sell Detection System" While Close Mode is active, sets the line used for detection of KVO Sell Protection: SIGNAL, PLOT, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower then the PLOT line. Considered long(er) term technical analysis depending on methodology selected. KVO uses mathematics developed by Stephen Klinger to predict long-term trends in money flow while also detecting short-term fluctuations. • "Close Mode: AO Sell Detection System" While Close Mode is active, sets the line used for detection of AO Sell Protection: AO or OFF. This feature uses mathematics developed by Bill Williams to measure how fast prices are changing in a particular direction by comparing the recent price movements with longer-term averages. • "Close Mode: Required Gain" While inside Close Mode, defines the minimum profit percentage above the unit cost of an asset that must be achieved before a full exit can be made. Example: A setting of 1% ensures that exits can only occur when gains are 1% or higher. • "Close Mode: Order Trailing Range" While inside Close Mode, defines the specific percentage used for the order trailing range. Example: A setting of 0.25 means the trailing range will be 0.25% of the current price. • "Close Mode: Trend Trailing Exit Multiplier" Applies a multiplier to Close Modes Order Trailing Range when exit conditions are favorable via stepGridHybrid's v2 Trend Module. Used to increase the trailing range of exits during positive market trends in order to find more favorable positioning. Example: A setting of 2 would double the Close Mode Order Trailing Range default of 0.25 to a value of 0.5. • "Close Mode: Exit Logic Based on Unit Cost" Switches Close Mode exit logic which determines how the break-even price is calculated. When enabled: break-even reflects the average cost per unit of the remaining balance. When disabled: break-even reflects the price at which all remaining units can be sold without loss. On: exits based on Unit Cost Target. Off: exits based on Break Even Target.

https://static.wixstatic.com/media/f8796d_6401aba801964204b38a78b09bd974b5~mv2.png This features limits the rate at which you can place orders on both sides of the market. This is important for controlling expenditures and as well allowing markets to mature as you ride the tops and bottoms of any given oscillation. This feature is specifically important if you're intending to experiment with websockets! • "Buy Cooldown: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Buy Cooldown. Useful for controlling accumulation aggression. Example: If you select a value of 3, Buy Cooldown will be disabled in Capital Stages 1 & 2. • "Buy Cooldown: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Buy Cooldown. Example: If you select a value of 8, Buy Cooldown will be disabled in Capital Stages 9 & 10. • "Buy Cooldown" Sets the amount of time (in seconds) to disable accumulation after completing a purchase. Example: A setting of 30 will disable orders for the next half of a minute while a setting of 60 will disable orders for the next minute. The default setting of Auto gives users different timeouts depending on their current risk of holding a bag: Highest Risk: 15 Seconds Higher Risk: 10 Seconds Normal Risk: 5 Seconds Lower Risk: 5 Seconds Lowest Risk: 5 Seconds • "Sell Cooldown: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Sell Cooldown. Useful for controlling partial exit aggression. Example: If you select a value of 3, Sell Cooldown will be disabled in Capital Stages 1 & 2. • "Sell Cooldown: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Sell Cooldown. Example: If you select a value of 8, Sell Cooldown will be disabled in Capital Stages 9 & 10. • "Sell Cooldown" Sets the amount of time (in seconds) to disable exits after completing a sell. Example: A setting of 30 will disable orders for the next half of a minute while a setting of 60 will disable orders for the next minute. The default setting of Auto gives users different timeouts depending on their current risk of holding a bag: Highest Risk: 15 Seconds Higher Risk: 10 Seconds Normal Risk: 5 Seconds Lower Risk: 5 Seconds Lowest Risk: 5 Seconds

https://static.wixstatic.com/media/f8796d_aeaa86e57a0c4dcdba65453943683a1b~mv2.png Considered short term, fast paced, technical analysis. This feature uses previous order history as well the preemptive T-2 mathematics developed by William Blau to dynamically channel orders on both sides of the market depending on developing trends. Uses the Stochastic Momentum Index Ergodic Oscillator (SMIEO/SMIIO) for determining when to switch between "Drop Sensitivity" & "Recovery Sensitivity". • "Channel Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Channel Buy Protection. Example: If you select a value of 3, Channel Buy Protection will be disabled in Capital Stages 1 & 2. • "Channel Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Channel Buy Protection. Example: If you select a value of 8, Channel Buy Protection will be disabled in Capital Stages 9 & 10. • "Channel Buy Protection: Antilag Average Offset" Sets how many candles to go back in history before the "Antilag Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "Channel Buy Protection: Antilag Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "Channel Buy Protection: Reset on Exit" Resets the accumulation channel after an exit is made allowing for a new accumulation cycle to begin outside of the last channel. Example: If you selected False, the currently known and respected order channel would stay in effect until either: 1.) it was timed out via the Antilag system, or 2.) the entire trade sequence was exited, meaning you're no longer holding a position. • "Channel Buy Protection: Hindsight Distance" Sets the historical candle used for comparison with the current price for the measurement of "Run Sensitivity" which triggers Channel Buy Protection. Example: If you select a value of 3, Channel Buy Protection will compare the current market value with what it was worth 15 minutes ago. • "Channel Buy Protection: Drop Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Channel Buy Protection during downward market movements. Example: If you select a value of 1, the difference in measurement must meet or exceed -1% before activation can occur. • "Channel Buy Protection: Recovery Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Channel Buy Protection when declining markets have started to stabilize or recover. Example: If you select a value of 1, the difference in measurement must meet or exceed -1% before activation can occur. • "Channel Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Channel Sell Protection. Example: If you select a value of 3, Channel Sell Protection will be disabled in Capital Stages 1 & 2. • "Channel Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Channel Sell Protection. Example: If you select a value of 8, Channel Sell Protection will be disabled in Capital Stages 9 & 10. • "Channel Sell Protection: Antilag Average Offset" Sets how many candles to go back in history before the "Antilag Average Period" beings. Example: If you set this at 6, the last 30 minutes of market data would be ignored. • "Channel Sell Protection: Antilag Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "Channel Sell Protection: Reset on Exit" Resets the exit channel after accumulation is made allowing for a new exit cycle to begin outside of the last channel. Example: If you selected False, the currently known and respected order channel would stay in effect until either: 1.) it was timed out via the Antilag system, or 2.) the entire trade sequence was exited, meaning you're no longer holding a position. \ • "Channel Sell Protection: Hindsight Distance" Sets the historical candle used for comparison with the current price for the measurement of "Run Sensitivity" which triggers Channel Sell Protection. Example: If you select a value of 3, Channel Sell Protection will compare the current market value with what it was worth 15 minutes ago. • "Channel Sell Protection: Run Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Channel Sell Protection during upward trending market movement. Example: If you select a value of 2, the difference in measurement must meet or exceed 2% before activation can occur. • "Channel Sell Protection: Decline Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Channel Sell Protection when upward market movement has started to decline. Example: If you select a value of 2, the difference in measurement must meet or exceed 2% before activation can occur.

https://static.wixstatic.com/media/f8796d_00d4c8b766ae4f33a470bf4853528674~mv2.png This feature reviews the historical average value of an asset then manipulates the current trading limit by multipliers depending on if the current market price is above or below the average. You can think about this like a "Good Deal / Bad Deal" indicator. We spend less when an asset is overpriced as the investment is risky, and on the other side, we spend more when an asset is undervalued as it's a good deal. This is an additional modification of the "Trading Limit" on top of the Capital Stage & Trading Phase systems and takes place after them in the logic chain. • "Risk Tuning: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Risk Tuning. Example: If you select a value of 3, Risk Tuning will be disabled in Capital Stages 1 & 2. • "Risk Tuning: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Risk Tuning. Example: If you select a value of 8, Risk Tuning will be disabled in Capital Stages 9 & 10. • "Moon Mode: Price Above Average Multiplier" While inside Moon Mode, defines the risk tuning order size multiplier when the current price is above the historical average. Example: If you set a value of 0.5, your currently active Trading Phase would be reduced by half whenever the Quote is considered overpriced. • "DCA Mode: Price Above Average Multiplier" While inside DCA Mode, defines the risk tuning order size multiplier when the current price is above the historical average. Example: If you set a value of 0.5, your currently active Trading Phase would be reduced by half whenever the Quote is considered overpriced. • "Flipper Mode: Price Above Average Multiplier" While inside Flipper Mode, defines the risk tuning order size multiplier when the current price is above the historical average. Example: If you set a value of 0.5, you're currently active Trading Phase would be reduced by half whenever the Quote is considered overpriced. • "Moon Mode: Price Below Average Multiplier" While inside Moon Mode, defines the risk tuning order size multiplier when the current price is below the historical average. Example: If you set a value of 2, your currently active Trading Phase would be doubled whenever the Quote is considered undervalued. • "DCA Mode: Price Below Average Multiplier" While inside DCA Mode, defines the risk tuning order size multiplier when the current price is below the historical average. Example: If you set a value of 2, you're currently active Trading Phase would be doubled whenever the Quote is considered undervalued • "Flipper Mode: Price Below Average Multiplier" While inside Flipper Mode, defines the risk tuning order size multiplier when the current price is below the historical average. Example: If you set a value of 2, your currently active Trading Phase would be doubled whenever the Quote is considered undervalued. • "Risk Tuning: Average Offset" Sets how many candles to go back in history before the "Average Period" beings. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Average Period" plus "Average Offset" should never exceed a value greater than 99. Example: the maximum "Average Period" of 96 plus an "Average Offset" of 3 equals 99. Though an "Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Risk Tuning: Average Period" Sets how many candles are used in the averaging calculation after the "Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours.

https://static.wixstatic.com/media/f8796d_d0bae44a242a42059ed4f18fea8c2f26~mv2.png This feature detects volatile price movement & enables exits via temporarily disabling extended technical analysis throughout the exit logic chain. Extremely useful in wild altcoin markets. • "Wick Sniper: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Wick Sniper. Example: If you select a value of 3, Wick Sniper will be disabled in Capital Stages 1 & 2. • "Wick Sniper: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Wick Sniper. Example: If you select a value of 8, Wick Sniper will be disabled in Capital Stages 9 & 10. • "Wick Sniper: Hindsight Distance" Sets the historical candle used for comparison with the current price for the measurement of "Run Sensitivity" which triggers Wick Sniper. Example: If you select a value of 3, Wick Sniper will compare the current market value with what it was worth 15 minutes ago. • "Wick Sniper: Run Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Wick Sniper. Example: If you select a value of 2, the difference in measurement must meet or exceed -2% before activation can occur.

https://static.wixstatic.com/media/f8796d_8bc84a2a52b7415093058a78367e6c51~mv2.png This feature detects upward trending price movement & temporarily disables exits until the run has started to stabilize or decline. Useful for obtaining better exit positioning. Overridden by Wick Sniper. Uses the Stochastic Momentum Index Ergodic Oscillator (SMIEO/SMIIO) for determining when to switch between "Run Sensitivity" & "Decline Sensitivity". • "Flood Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Flood Protection. Example: If you select a value of 3, Flood Protection will be disabled in Capital Stages 1 & 2. • "Flood Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Flood Protection. Example: If you select a value of 8, Flood Protection will be disabled in Capital Stages 9 & 10. • "Flood Protection: Hindsight Distance" Sets the historical candle used for comparison with the current price for the measurement of "Run Sensitivity" & "Decline Sensitivity" which both trigger Flood Protection. Example: If you select a value of 3, Flood Protection will compare the current market value with what it was worth 15 minutes ago. • "Flood Protection: Run Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Flood Protection during upward trending market movement. Example: If you select a value of 2, the difference in measurement must meet or exceed 2% before activation can occur. • "Flood Protection: Decline Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Flood Protection when upward market movement has started to decline. Example: If you select a value of 2, the difference in measurement must meet or exceed 2% before activation can occur.

https://static.wixstatic.com/media/f8796d_7c5a4ceab0d64e2281d7847ba6a6aa38~mv2.png This feature detects downward price movement & temporarily disables accumulation until the drop has started to stabilize or recover. Useful for obtaining better entrance positioning & lowering of overarching unit cost. Uses the Stochastic Momentum Index Ergodic Oscillator (SMIEO/SMIIO) for determining when to switch between "Drop Sensitivity" & "Recovery Sensitivity". • "Waterfall Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Waterfall Protection. Example: If you select a value of 3, Waterfall Protection will be disabled in Capital Stages 1 & 2. • "Waterfall Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Waterfall Protection. Example: If you select a value of 8, Waterfall Protection will be disabled in Capital Stages 9 & 10. • "Waterfall Protection: Hindsight Distance" Sets the historical candle used for comparison with the current price for the measurement of "Drop Sensitivity" & "Recovery Sensitivity" which both trigger Waterfall Protection. Example: If you select a value of 3, Channel Sell Protection will compare the current market value with what it was worth 15 minutes ago. • "Waterfall Protection: Drop Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Waterfall Protection during downward market movements. Example: If you select a value of 1, the difference in measurement must meet or exceed -1% before activation can occur. • "Waterfall Protection: Recovery Sensitivity" Sets the percentage difference in price required as measured from "Hindsight Distance" for activation of Waterfall Protection when declining markets have started to stabilize or recover. Example: If you select a value of 1, the difference in measurement must meet or exceed -1% before activation can occur.

https://static.wixstatic.com/media/f8796d_d8901b8845834c2ab3af4efd3b4e87eb~mv2.png This feature detects down trending markets & disables accumulation until the price has started to stabilize. Useful for waiting out slower depressions in markets where other forms of technical analysis would have accumulated. • "River Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling River Protection. Example: If you select a value of 3, River Protection will be disabled in Capital Stages 1 & 2. • "River Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling River Protection. Example: If you select a value of 8, River Protection will be disabled in Capital Stages 9 & 10. • "River Protection: Average Offset" Sets how many candles to go back in history before the "Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Average Period" plus "Average Offset" should never exceed a value greater than 99. Example: the maximum "Average Period" of 96 plus an "Average Offset" of 3 equals 99. Though an "Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "River Protection: Average Period" Sets how many candles are used in the averaging calculation after the "Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "River Protection: Moon Mode Sensitivity" While inside Moon Mode, defines the percentage difference in price required as measured from "Average Period" for activation of River Protection. Example: If you select a value of -1, the difference in measurement must meet or exceed -1% before activation can occur. • "River Protection: DCA Mode Sensitivity" While inside DCA Mode, defines the percentage difference in price required as measured from "Average Period" for activation of River Protection. Example: If you select a value of -1, the difference in measurement must meet or exceed -1% before activation can occur. • "River Protection: Flipper Mode Sensitivity" While inside Flipper Mode, defines the percentage difference in price required as measured from "Average Period" for activation of River Protection. Example: If you select a value of -1, the difference in measurement must meet or exceed -1% before activation can occur.

https://static.wixstatic.com/media/f8796d_8dbab232dfcb4a3387f53377fbc26f93~mv2.png This feature detects upward trending market movement & increases gain requirements per Operational Mode while active. Useful for obtaining better exit positioning & increasing returns. • "Climb Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Climb Protection. Example: If you select a value of 3, Climb Protection will be disabled in Capital Stages 1 & 2. • "Climb Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Climb Protection. Example: If you select a value of 8, Climb Protection will be disabled in Capital Stages 9 & 10. • "Climb Protection: Average Offset" Sets how many candles to go back in history before the "Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Average Period" plus "Average Offset" should never exceed a value greater than 99. Example: the maximum "Average Period" of 96 plus an "Average Offset" of 3 equals 99. Though an "Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Climb Protection: Average Period" Sets how many candles are used in the averaging calculation after the "Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "Climb Protection: Sensitivity" Defines the percentage difference in price required as measured from "Average Period" for activation of Climb Protection. Example: If you select a value of 1, the difference in measurement must meet or exceed 1% before activation can occur. • "Climb Protection: Moon Mode Gain" While inside Moon Mode, defines the additional amount of gain applied when Climb Protection is active. Example: If the gain for your mode was 0.5 & you selected a value of 1, then when activated the mode's new gain requirements would be 1.5. • "Climb Protection: DCA Mode Gain" While inside DCA Mode, defines the additional amount of gain applied when Climb Protection is active. Example: If the gain for your mode was 0.5 & you selected a value of 1, then when activated the mode's new gain requirements would be 1.5. • "Climb Protection: Flipper Mode Gain" While inside Flipper Mode, defines the additional amount of gain applied when Climb Protection is active. Example: If the gain for your mode was 0.5 & you selected a value of 1, then when activated the mode's new gain requirements would be 1.5. • "Climb Protection: Close Mode Gain" While inside Close Mode, defines the additional amount of gain applied when Climb Protection is active. Example: If the gain for your mode was 0.5 & you selected a value of 1, then when activated the mode's new gain requirements would be 1.5.

https://static.wixstatic.com/media/f8796d_b03795b5bc2643b98a64a312ca2529a3~mv2.png This feature detects market crashes & disables accumulation until the price has started to stabilize. Extremely useful in wild altcoin markets. • "Freefall Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Freefall Protection. Example: If you select a value of 3, Freefall Protection will be disabled in Capital Stages 1 & 2. • "Freefall Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Freefall Protection. Example: If you select a value of 8, Freefall Protection will be disabled in Capital Stages 9 & 10. • "Freefall Protection: Average Offset" Sets how many candles to go back in history before the "Average Period" beings. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Average Period" plus "Average Offset" should never exceed a value greater than 99. Example: the maximum "Average Period" of 96 plus an "Average Offset" of 3 equals 99. Though an "Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Freefall Protection: Average Period" Sets how many candles are used in the averaging calculation after the "Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "Freefall Protection: Minimum Time Requirement" Sets how many candles inside the "Average Period" are required to be below a mode's "Sensitivity" before Freefall Protection can be activated. Example: If you select a value of 3, then at least 15 minutes of the "Average Period" would need to be spent beyond "Sensitivity" before accumulation would be disabled. This feature works both ways, meaning deactivation cannot occur until at least 15 minutes haven't been spent beyond "Sensitivity". Meaning accumulation would continue to be halted across the entirely of the "Average Period" until it's cleared the offending time. This is used to better judge when the market crash has actually ended & not just temporarily stopped. • "Freefall Protection: Moon Mode Sensitivity" While inside Moon Mode, defines the percentage difference in price required as measured from "Average Period" for validation inside "Minimum Time Requirement". Example: If you select a value of -3, the difference in measurement must meet or exceed -3% before activation can occur. • "Freefall Protection: DCA Mode Sensitivity" While inside DCA Mode, defines the percentage difference in price required as measured from "Average Period" for validation inside "Minimum Time Requirement". Example: If you select a value of -1, the difference in measurement must meet or exceed -1% before activation can occur. • "Freefall Protection: Flipper Mode Sensitivity" While inside Flipper Mode, defines the percentage difference in price required as measured from "Average Period" for validation inside "Minimum Time Requirement". Example: If you select a value of -5, the difference in measurement must meet or exceed -5% before activation can occur.

https://static.wixstatic.com/media/f8796d_5092299b58864ba6bf82f0f05d4a884f~mv2.png This feature detects tight market conditions then changes the SMIEO, MACD, KVO, & AO technical analysis to respond quicker during market fluctuations. This allows machineGun to profit in extremely tight market conditions. On the buy side, this feature changes long term technical analysis to respond quicker & be more agile. On the sell side, this feature allows partial exits of your position to be made when it has met the mode specific gain requirements, even if the entire trade sequence has not. This helps increase accumulation aggression during prolonged periods of market stabilization. It also alters aggression when starting new pairs or when you're currently only holding a small amount of Quote to work with. • "Skimmer Buy: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling accumulation related Skimmer features. Example: If you select a value of 3, Skimmer will be disabled in Capital Stages 1 & 2. • "Skimmer Buy: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling accumulation related Skimmer features. Example: If you select a value of 8, Skimmer will be disabled in Capital Stages 9 & 10. • "Skimmer Buy: Automatic Activation" Automatically turns on accumulation related Skimmer features when current bag in base is less than set percentage of Investment Level. Example: If you select 10, machineGun will have Skimmer enabled throughout all of Capital Stage 1. • "Skimmer Buy: SMIEI Detection System" While Skimmer is active, sets the line used for detection of SMIEI Buy Protection: SIGNAL, INDICATOR, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower than the INDICATOR line. • "Skimmer Buy: SMIEI Antilag Period" While Skimmer is active, sets how many candles are used in the averaging calculation after the "Antilag Average Offset" for SMIEI Antilag. Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Skimmer Buy: MACD Detection System" While Skimmer is active, sets the indicator used for detection of MACD Buy Protection: SIGNAL, MACD, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower than the MACD line. • "Skimmer Buy: MACD Antilag Period" While Skimmer is active, sets how many candles are used in the averaging calculation after the "Antilag Average Offset" for MACD Antilag. Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Skimmer Buy: KVO Detection System" While Skimmer is active, sets the line used for detection of KVO Buy Protection: SIGNAL, PLOT, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower then the PLOT line. • "Skimmer Buy: KVO Antilag Period" While Skimmer is active, sets how many candles are used in the averaging calculation after the "Antilag Average Offset" for KVO Antilag. Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Skimmer Buy: AO Detection System" While Skimmer is active, sets the line used for detection of AO Buy Protection: AO or OFF. • "Skimmer Buy: AO Antilag Period" While Skimmer is active, sets how many candles are used in the averaging calculation after the "Antilag Average Offset" for AO Antilag. Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Skimmer Sell: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling exit related Skimmer features. Example: If you select a value of 3, Skimmer will be disabled in Capital Stages 1 & 2. • "Skimmer Sell: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before enabling exit related Skimmer features. Example: If you select a value of 8, Skimmer will be disabled in Capital Stages 9 & 10. • "Skimmer Sell: Unit Cost Sensitivity" While Skimmer is active, defines the minimum distance in price from Unit Cost (as a percentage) required for activation of Unit Cost Exit Protection. Example: If you select a value of 1, Unit Cost Exit Protection will not be enabled until the current price is 1% above your entire trade sequence's Unit Cost. Unit Cost Protection prevents exits below Unit Cost. Forcing the entire trade sequence to be in profit before considering exits, partial or full. • "Skimmer Sell: Partial Gain Sensitivity" While Skimmer is active, defines the minimum distance in price from Unit Cost (as a percentage) required for activation of Partial Gain Protection. Example: If you select a value of 1, Partial Gain Protection will not be enabled until the current price is 1% above your entire trade sequence's Unit Cost. Partial Gain Protection requires the current price's distance above Unit Cost to match or exceed the operational mode's gain value before exits are allowed. • "Skimmer Sell: SMIEI Detection System" While Skimmer is active, sets the line used for detection of SMIEI Sell Protection: SIGNAL, INDICATOR, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower then the INDICATOR line. • "Skimmer Sell: MACD Detection System" While Skimmer is active, sets the indicator used for detection of MACD Sell Protection: SIGNAL, MACD, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower then the MACD line. • "Skimmer Sell: KVO Detection System" While Skimmer is active, sets the line used for detection of KVO Sell Protection: SIGNAL, PLOT, or OFF. Example: During this form of technical analysis the SIGNAL line is considered slower then the PLOT line. • "Skimmer Sell: AO Detection System" While Skimmer is active, sets the line used for detection of AO Sell Protection: AO or OFF. • "Skimmer: Sensitivity" Sets the maximum top to bottom price difference (as a percentage) allowed across "Average Period" before disabling Skimmer. Example: If you select a value of 5 & there was a 6% difference in asset value across "Average Period" then Skimmer would be disabled. Meanwhile, if there was a 4% difference in price, then Skimmer would be enabled. On the buy side, this feature changes long term technical analysis to respond quicker & be more agile. On the sell side, this feature allows partial exits of your position to be made when it has met the mode specific gain requirements, even if the entire trade sequence has not. This creates a chasing Unit Cost upwards effect since after exiting you'll only have the remaining out of position orders left inside your trade sequence. • "Skimmer: Average Offset" Sets how many candles to go back in history before the "Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Average Period" plus "Average Offset" should never exceed a value greater than 99. Example: the maximum "Average Period" of 96 plus an "Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. • "Skimmer: Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours.

https://static.wixstatic.com/media/f8796d_eefb3f373b7a4cad881d76e62c490bec~mv2.png This feature prevents accumulation above and exits below Unit Cost. Which controls inflation of a trade sequence's Unit Cost, helping prevent chasing it upwards into unobtainable trading zones that can rarely be satisfied. • "Unit Cost Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Unit Cost Buy Protection. Example: If you select a value of 3, Unit Cost Buy Protection will be disabled in Capital Stages 1 & 2. • "Unit Cost Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Unit Cost Buy Protection. Example: If you select a value of 8, Unit Cost Buy Protection will be disabled in Capital Stages 9 & 10. • "Unit Cost Buy Protection: Sensitivity" Defines the distance in price from Unit Cost (as a percentage) required for deactivation of the protection. Example: If you select a value of -1, accumulation will not be enabled until the current price is -1% below your entire trade sequence's Unit Cost. • "Unit Cost Buy Protection: Antilag Average Offset" Sets how many candles to go back in history before the "Antilag Average Period" beings. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. This feature disables technical analysis when it's results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "Unit Cost Buy Protection: Antilag Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "Unit Cost Buy Protection: Minimum Percentage Requirement" Sets a percentage requirement for how many candles inside the "Antilag Average Period" are required to be above your entire trade sequence's Unit Cost before Antilag can be activated. Example: If you select a value of 50, then at least 50% of the "Antilag Average Period" would need to be spent above Unit Cost before Antilag would disable Unit Cost Buy Protection. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "Unit Cost Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Unit Cost Sell Protection. Example: If you select a value of 8, Unit Cost Sell Protection will be disabled in Capital Stages 9 & 10. • "Unit Cost Sell Protection: Sensitivity" Defines the distance in price from Unit Cost (as a percentage) required for deactivation of the protection. Example: If you select a value of 1, exits will not be enabled until the current price is 1% above your entire trade sequence's Unit Cost. • "Partial Gain Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling Partial Gain Protection. Example: If you select a value of 3, Partial Gain Protection will be disabled in Capital Stages 1 & 2. This feature requires the current price's distance above Unit Cost to match or exceed the operational mode's gain value before exits are allowed. This helps aid the stepGridHybrid partial exit system & stops it from immediately selling out the bottom of your trade sequence when it's met the Gain requirements though the entire position has not. • "Partial Gain Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling Partial Gain Protection. Example: If you select a value of 8, Partial Gain Protection will be disabled in Capital Stages 9 & 10. • "Partial Gain Protection: Custom Requirement" Changes the required distance above unit cost for Partial Gain Protection to a unique singular value instead of using each operational mode's individual gain. Example: A setting of 1 would require the price be at least 1% above Unit Cost before exits would be enabled. The default of zero uses the normal automatic system.

https://static.wixstatic.com/media/f8796d_0f279d8eb5f447f4968349a663c0f98f~mv2.png Considered short term fast paced technical analysis. This feature uses the preemptive T-2 mathematics developed by William Blau to detect early market trends as they're developing & react beforehand. • "SMIEO Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling SMIEO Buy Protection. Example: If you select a value of 3, SMIEO Buy Protection will be disabled in Capital Stages 1 & 2. • "SMIEO Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling SMIEO Buy Protection. Example: If you select a value of 8, SMIEO Buy Protection will be disabled in Capital Stages 9 & 10. • "SMIEO Buy Protection: Sensitivity" Sets the oscillator requirement which must be matched or exceeded for activation of SMIEO Buy Protection. Example: If you select a value of -0.10, then accumulation would be disabled until the moment the oscillator dropped to & then surpassed -0.10. It would continue to be valid while below -0.10 & invalidated once above -0.10. • "SMIEO Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other short term technical analysis features. Example: If SMIEO is currently returning no across the logic chain, but AC & CMO are both returning yes, then SMIEO would be overruled and the short term technical analysis logic chain would validate without it. This increases market agility and moves overall behavior towards quicker responses. Allowing one to enter or exit markets when 2/3rds of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "SMIEO Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling SMIEO Sell Protection. Example: If you select a value of 3, SMIEO Sell Protection will be disabled in Capital Stages 1 & 2. • "SMIEO Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling SMIEO Sell Protection. Example: If you select a value of 8, SMIEO Sell Protection will be disabled in Capital Stages 9 & 10. • "SMIEO Sell Protection: Sensitivity" Sets the oscillator requirement which must be matched or exceeded for activation of SMIEO Sell Protection. Example: If you select a value of 0.20, then exits would be disabled until the moment the oscillator rose to & then surpassed 0.20. It would continue to be valid while above 0.20 & invalidated once below 0.20. • "SMIEO Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other short term technical analysis features. Example: If SMIEO is currently returning no across the logic chain, but AC & CMO are both returning yes, then SMIEO would be overruled and the short term technical analysis logic chain would validate without it. • "Trading Phase: Drop Lockout" When enabled, locks out the top three remaining Trading Phases that are still available until inside a market recovery. Example: If you have Trading Phases 1-7 currently available then Trading Phases 5, 6, & 7 would be temporarily disabled until the current market drop has started to stabilize or recover. This significantly helps lower unit cost via saving the largest available purchases & highest risk Trading Phases until the perceived bottom of a market depression. • "Trading Phase: Lockout Hindsight Distance" Sets the historical candle via the oscillator histogram used for comparison with the current for determination of "Drop Lockout" status. Example: If you select a value of 3, Drop Lockout will compare the current oscillator with the value from 15 minutes ago. • "SMIEO: Fast Length" The number of periods used inside the SMI Ergodic Indicator & Oscillator (SMIEO/SMIIO) calculation for a moving average that reacts quickly to recent price changes, commonly used for short-term trend analysis. Highly recommended to not alter this value. • "SMIEO: Slow Length" The number of periods used inside the SMI Ergodic Indicator & Oscillator (SMIEO/SMIIO) calculation for a moving average that responds more slowly to price fluctuations, useful for identifying longer-term trends. Highly recommended to not alter this value. • "SMIEO: Signal Length" The number of periods used inside the SMI Ergodic Indicator & Oscillator (SMIEO/SMIIO) calculation for an EMA of the SMI which is subtracted from the SMI to create the SMI Ergodic Oscillator. The oscillator is then displayed as a histogram, with positive & negative values reflecting the direction of the momentum. Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_a24b34744bc64030b6600fb7323fe16e~mv2.png Considered short term fast paced technical analysis. This feature uses mathematics developed by Tushar Chande to identify overbought/oversold conditions, trend strengths, & potential reversal points. • "CMO Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling CMO Buy Protection. Example: If you select a value of 3, CMO Buy Protection will be disabled in Capital Stages 1 & 2. • "CMO Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling CMO Buy Protection. Example: If you select a value of 8, CMO Buy Protection will be disabled in Capital Stages 9 & 10. • "CMO Buy Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of CMO Buy Protection. Example: If you select a value of -40, then accumulation would be disabled until the moment the oscillator dropped to & then surpassed -40. It would continue to be valid while below -40 & invalidated once above -40. • "CMO Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other short term technical analysis features. Example: If CMO is currently returning no across the logic chain, but AC & SMIEO are both returning yes, then CMO would be overruled and the short term technical analysis logic chain would validate without it. This increases market agility and moves overall behavior towards quicker responses. Allowing one to enter or exit markets when 2/3rds of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "CMO Buy Protection: Trading Phase Unlock" Disables CMO Protection inside the BUY_ENABLED logic chain during upward trending market recoveries. Restoring full access to all currently available Trading Phases. This feature uses mathematics developed by Tushar Chande & William Blau. • "CMO Buy Protection: Phase Unlock Hindsight Distance" Sets the historical candle via the SMIEO histogram used for comparison with the current for determination of "Trading Phase Unlock" status. Example: If you select a value of 3, Phase Unlock will compare the current oscillator with the value from 15 minutes ago. • "CMO Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling CMO Sell Protection. Example: If you select a value of 3, CMO Sell Protection will be disabled in Capital Stages 1 & 2. • "CMO Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling CMO Sell Protection. Example: If you select a value of 8, CMO Sell Protection will be disabled in Capital Stages 9 & 10. • "CMO Sell Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of CMO Sell Protection. Example: If you select a value of 40, then exits would be disabled until the moment the oscillator rose to & then surpassed 40. It would continue to be valid while above 40 & invalidated once below 40. • "CMO Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other short term technical analysis features. Example: If CMO is currently returning no across the logic chain, but AC & SMIEO are both returning yes, then CMO would be overruled and the short term technical analysis logic chain would validate without it. • "CMO: Length" The number of periods used inside the Chande Momentum Oscillator (CMO) to find the difference between the sum of recent gains & the sum of recent losses & then divides the result by the sum of all price movements over the same period. Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_f7b6d0e78b6b46a6b9adf9390ad0105e~mv2.png Considered short term fast paced technical analysis. This feature uses mathematics developed by Bill Williams to measure the acceleration or deceleration of market momentum and forecast potential price changes. • "AC Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling AC Buy Protection. Example: If you select a value of 3, AC Buy Protection will be disabled in Capital Stages 1 & 2. • "AC Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling AC Buy Protection. Example: If you select a value of 8, AC Buy Protection will be disabled in Capital Stages 9 & 10. • "AC Buy Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of AC Buy Protection. Example: If you select a value of -40, then accumulation would be disabled until the moment the oscillator dropped to & then surpassed -40. It would continue to be valid while below -40 & invalidated once above -40. • "AC Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If AC is currently returning no across the logic chain, but SMIIO & CMO are both returning yes, then AC would be overruled and the long term technical analysis logic chain would validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 2/3rds of the analysis is in agreement instead of waiting for unification across all forms of technical analysis • "AC Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling AC Sell Protection. Example: If you select a value of 3, AC Sell Protection will be disabled in Capital Stages 1 & 2. • "AC Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling AC Sell Protection. Example: If you select a value of 8, AC Sell Protection will be disabled in Capital Stages 9 & 10. • "AC Sell Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of AC Sell Protection. Example: If you select a value of 40, then exits would be disabled until the moment the oscillator rose to & then surpassed 40. It would continue to be valid while above 40 & invalidated once below 40. • "AC Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If AC is currently returning no across the logic chain, but SMIIO & CMO are both returning yes, then AC would be overruled and the long term technical analysis logic chain would validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 2/3rds of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "AC: Fast Length" The number of fast periods used inside the Accelerator Oscillator (AC) to measure the acceleration or deceleration of market momentum and forecast potential price changes. Highly recommended to not alter this value. • "AC: Slow Length" The number of slow periods used inside the Accelerator Oscillator (AC) to measure the acceleration or deceleration of market momentum and forecast potential price changes. Highly recommended to not alter this value. • "AC: Smoothing Length" The number of periods that are smoothed inside the Accelerator Oscillator (AC) to measure the acceleration or deceleration of market momentum and forecast potential price changes. Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_8337469e5ea24cc190f618cf373b99ef~mv2.png Considered long(er) term technical analysis depending on methodology selected. This feature uses mathematics developed by Gerald Appel to identify price trends, measure trend momentum, & identify entry points. • "MACD Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling MACD Buy Protection. Example: If you select a value of 3, MACD Buy Protection will be disabled in Capital Stages 1 & 2. • "MACD Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling MACD Buy Protection. Example: If you select a value of 8, MACD Buy Protection will be disabled in Capital Stages 9 & 10. • "MACD Buy Protection: Detection System" Sets the indicator used for detection of MACD Buy Protection: SIGNAL or MACD. Example: During this form of technical analysis the SIGNAL line is considered slower than the MACD line. • "MACD Buy Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of MACD Buy Protection. Example: If you select a value of -50, then accumulation would be disabled until the moment the indicator dropped to & then surpassed -50. It would continue to be valid while below -50 & invalidated once above -50. • "MACD Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If MACD is currently returning no across the logic chain, but SMIEI, KVO, & AO are all returning yes, then MACD would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "MACD Buy Protection: Antilag Average Offset" Sets how many candles to go back in history before the "Antilag Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "MACD Buy Protection: Antilag Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "MACD Buy Protection: Antilag Minimum Percentage" Sets a percentage requirement for how many candles inside the "Antilag Average Period" are required to be above "Sensitivity" before MACD Buy Protection Antilag can be activated. Example: If you select a value of 50, then at least 50% of the "Antilag Average Period" would need to be spent above "Sensitivity" before Antilag would disable MACD Buy Protection. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "MACD Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling MACD Sell Protection. Example: If you select a value of 3, MACD Sell Protection will be disabled in Capital Stages 1 & 2. • "MACD Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling MACD Sell Protection. Example: If you select a value of 8, MACD Sell Protection will be disabled in Capital Stages 9 & 10. • "MACD Sell Protection: Detection System" Sets the indicator used for detection of MACD Sell Protection: SIGNAL or MACD. Example: During this form of technical analysis the SIGNAL line is considered slower then the MACD line. • "MACD Sell Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of MACD Sell Protection. Example: If you select a value of 50, then exits would be disabled until the moment the indicator rose to & then surpassed 50. It would continue to be valid while above 50 & invalidated once below 50. • "MACD Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If MACD is currently returning no across the logic chain, but SMIEI, KVO, & AO are all returning yes, then MACD would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "MACD: Fast Length" The number of periods used inside the Moving Average Convergence Divergence (MACD) calculation for short-term exponential moving averages (EMA). Highly recommended to not alter this value. • "MACD: Slow Length" The number of periods used inside the Moving Average Convergence Divergence (MACD) calculation for long-term exponential moving averages (EMA). Highly recommended to not alter this value. • "MACD: Signal Length" The number of periods used inside the Moving Average Convergence Divergence (MACD) calculation for moving averages (MA). Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_f1514725e8294893ae43f4a61765c224~mv2.png Considered long(er) term technical analysis depending on methodology selected. This feature uses the preemptive T-2 mathematics developed by William Blau to detect early market trends as they're developing & react beforehand. • "SMIEI Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling SMIEI Buy Protection. Example: If you select a value of 3, SMIEI Buy Protection will be disabled in Capital Stages 1 & 2. • "SMIEI Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling SMIEI Buy Protection. Example: If you select a value of 8, SMIEI Buy Protection will be disabled in Capital Stages 9 & 10. • "SMIEI Buy Protection: Detection System" Sets the line used for detection of SMIEI Buy Protection: SIGNAL or INDICATOR. Example: During this form of technical analysis the SIGNAL line is considered slower than the INDICATOR line. • SMIEI Buy Protection: Sensitivity Sets the requirement for which must be matched or exceeded for activation of SMIEI Buy Protection. Example: If you select a value of -0.10, then accumulation would be disabled until the moment the indicator dropped to & then surpassed -0.10. It would continue to be valid while below -0.10 & invalidated once above -0.10. • "SMIEI Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If SMIEI is currently returning no across the logic chain, but MACD, KVO, & AO are all returning yes, then SMIEI would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "SMIEI Buy Protection: Antilag Average Offset" Sets how many candles to go back in history before the "Antilag Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "SMIEI Buy Protection: Antilag Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "SMIEI Buy Protection: Antilag Minimum Percentage" Sets a percentage requirement for how many candles inside the "Antilag Average Period" are required to be above "Sensitivity" before SMIEI Buy Protection Antilag can be activated. Example: If you select a value of 50, then at least 50% of the "Antilag Average Period" would need to be spent above "Sensitivity" before Antilag would disable SMIEI Buy Protection. This feature disables technical analysis when it's results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "SMIEI Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling SMIEI Sell Protection. Example: If you select a value of 3, SMIEI Sell Protection will be disabled in Capital Stages 1 & 2. • "SMIEI Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling SMIEI Sell Protection. Example: If you select a value of 8, SMIEI Sell Protection will be disabled in Capital Stages 9 & 10. • "SMIEI Sell Protection: Detection System" Sets the line used for detection of SMIEI Sell Protection: SIGNAL or INDICATOR. Example: During this form of technical analysis the SIGNAL line is considered slower than the INDICATOR line. • "SMIEI Sell Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of SMIEI Sell Protection. Example: If you select a value of 0.20, then exits would be disabled until the moment the indicator rose to & then surpassed 0.20. It would continue to be valid while above 0.20 & invalidated once below 0.20. • "SMIEI Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If SMIEI is currently returning no across the logic chain, but MACD, KVO, & AO are all returning yes, then SMIEI would be overruled and the long term technical analysis logic chain would validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "SMIEI: Fast Length" The number of periods used inside the SMI Ergodic Indicator & Oscillator (SMIEO/SMIIO) calculation for a moving average that reacts quickly to recent price changes, commonly used for short-term trend analysis. Highly recommended to not alter this value. • "SMIEI: Slow Length" The number of periods used inside the SMI Ergodic Indicator & Oscillator (SMIEO/SMIIO) calculation for a moving average that responds more slowly to price fluctuations, useful for identifying longer-term trends. Highly recommended to not alter this value. • "SMIEI: Signal Length" The number of periods used inside the SMI Ergodic Indicator & Oscillator (SMIEO/SMIIO) calculation for an EMA of the SMI which is subtracted from the SMI to create the SMI Ergodic Oscillator. The oscillator is then displayed as a histogram, with positive & negative values reflecting the direction of the momentum. Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_0bc40845d5964ff8898139ae060dab4f~mv2.png Considered long(er) term technical analysis depending on methodology selected. This feature uses mathematics developed by Stephen Klinger to predict long-term trends in money flow while also detecting short-term fluctuations. • "KVO Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling KVO Buy Protection. Example: If you select a value of 3, KVO Buy Protection will be disabled in Capital Stages 1 & 2. • "KVO Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling KVO Buy Protection. Example: If you select a value of 8, KVO Buy Protection will be disabled in Capital Stages 9 & 10. • "KVO Buy Protection: Detection System" Sets the line used for detection of KVO Buy Protection: SIGNAL or PLOT. Example: During this form of technical analysis the SIGNAL line is considered slower than the PLOT line. • "KVO Buy Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of KVO Buy Protection. Example: If you select a value of -100, then accumulation would be disabled until the moment the oscillator dropped to & then surpassed -100. It would continue to be valid while below -100 & invalidated once above -100. • "KVO Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If KVO is currently returning no across the logic chain, but SMIEI, MACD, & AO are all returning yes, then KVO would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "KVO Buy Protection: Antilag Average Offset" Sets how many candles to go back in history before the "Antilag Average Period" begins. Example: If you set this at 6, the last 30 minutes of market data would be ignored. When assigning custom settings please keep in mind "Antilag Average Period" plus "Antilag Average Offset" should never exceed a value greater than 99. Example: the maximum "Antilag Average Period" of 96 plus an "Antilag Average Offset" of 3 equals 99. Though an "Antilag Average Offset" of 4 would make 100 & would not be advised. This allows us to work within the generally limited data returned by most exchanges of 99-100 candles. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "KVO Buy Protection: Antilag Average Period" Sets how many candles are used in the averaging calculation after the "Antilag Average Offset". Example: If you select 96 machineGun will review the last eight hours of market data. 24 would review the last two hours. • "KVO Buy Protection: Antilag Minimum Percentage" Sets a percentage requirement for how many candles inside the "Antilag Average Period" are required to be above "Sensitivity" before KVO Buy Protection Antilag can be activated. Example: If you select a value of 50, then at least 50% of the "Antilag Average Period" would need to be spent above "Sensitivity" before Antilag would disable KVO Buy Protection. This feature disables technical analysis when its results are considered invalid. This helps keep machineGun active instead of getting delayed on any given single indicator or form of technical analysis. • "KVO Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling KVO Sell Protection. Example: If you select a value of 3, KVO Sell Protection will be disabled in Capital Stages 1 & 2. • "KVO Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling KVO Sell Protection. Example: If you select a value of 8, KVO Sell Protection will be disabled in Capital Stages 9 & 10. • "KVO Sell Protection: Detection System" Sets the line used for detection of KVO Sell Protection: SIGNAL or PLOT. Example: During this form of technical analysis the SIGNAL line is considered slower than the PLOT line. • "KVO Sell Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of KVO Sell Protection. Example: If you select a value of 200, then exits would be disabled until the moment the oscillator rose to & then surpassed 200. It would continue to be valid while above 200 & invalidated once below 200. • "KVO Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If KVO is currently returning no across the logic chain, but SMIEI, MACD, & AO are all returning yes, then KVO would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "KVO: Fast Length" The number of periods used inside the Klinger Volume Oscillator (KVO) for the calculation of the shorter-term exponential moving average (EMA) of the volume force. Highly recommended to not alter this value. • "KVO: Slow Length" The number of periods used inside the Klinger Volume Oscillator (KVO) for the calculation of the longer-term exponential moving average (EMA) of the volume force. Highly recommended to not alter this value. • "KVO: Signal Length" The number of periods used inside the Klinger Volume Oscillator (KVO) for the calculation of moving averages. (MA) Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_79d44c503ceb40b58d3cfa1838517788~mv2.png Considered long(er) term technical analysis. This feature uses mathematics developed by Bill Williams to measure how fast prices are changing in a particular direction by comparing the recent price movements with longer-term averages. • "AO Buy Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling AO Buy Protection. Example: If you select a value of 3, AO Buy Protection will be disabled in Capital Stages 1 & 2. • "AO Buy Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling AO Buy Protection. Example: If you select a value of 8, AO Buy Protection will be disabled in Capital Stages 9 & 10. • "AO Buy Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of AO Buy Protection. Example: If you select a value of -40, then accumulation would be disabled until the moment the oscillator dropped to & then surpassed -40. It would continue to be valid while below -40 & invalidated once above -40. • "AO Buy Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If AO is currently returning no across the logic chain, but SMIEI, MACD, & KVO are all returning yes, then AO would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "AO Sell Protection: Minimum Capital Stage" Sets the Minimum Capital Stage required before enabling AO Sell Protection. Example: If you select a value of 3, AO Sell Protection will be disabled in Capital Stages 1 & 2. • "AO Sell Protection: Maximum Capital Stage" Sets the Maximum Capital Stage accepted before disabling AO Sell Protection. Example: If you select a value of 8, AO Sell Protection will be disabled in Capital Stages 9 & 10. • "AO Sell Protection: Sensitivity" Sets the requirement for which must be matched or exceeded for activation of AO Sell Protection. Example: If you select a value of 40, then exits would be disabled until the moment the oscillator rose to & then surpassed 40. It would continue to be valid while above 40 & invalidated once below 40. • "AO Sell Protection: Majority Rule" Overrules the current technical analysis if its results are counter to the majority of the other long term technical analysis features. Example: If AO is currently returning no across the logic chain, but SMIEI, MACD, & KVO are all returning yes, then AO would be overruled and the long term technical analysis logic chain would be validated without it. This increases market agility and moves overall behavior towards shorter term trends. Allowing one to enter or exit markets when 3/4ths of the analysis is in agreement instead of waiting for unification across all forms of technical analysis. • "AO: Fast Length" The number of fast periods used inside the Awesome Oscillator (AO) to measure how fast prices are changing in a particular direction by comparing the recent price movements with longer-term averages. Highly recommended to not alter this value. • "AO: Slow Length" The number of slow periods used inside the Awesome Oscillator (AO) to measure how fast prices are changing in a particular direction by comparing the recent price movements with longer-term averages. Highly recommended to not alter this value.

https://static.wixstatic.com/media/f8796d_ea8c96eee08b434792ac877486ce989f~mv2.png • "Manual MVTS" In case: • machineGun is not trading at the order sizes expected for your exchange & pair. • your console and / or the bag risk tooltip says you need to set a "Manual MVTS". • your console says machineGun cannot find a MVTS for your pair. • you would like to set a custom minimum volume to sell value. This value will override the default "SGH: Min Vol To Sell" value. To disable "Manual MVTS", returning to the automatically calculated MVTS, set this field to 0.

https://static.wixstatic.com/media/f8796d_ef2c716760204a14ab99e7dabd77346c~mv2.png These are used to calculate the financial statistics. They are set automatically for you. Do not change them. • "Pair Start Time" The timestamp for when you first started the machineGun strategy. • "Last Time No Position" The timestamp for the last time machineGun cleared its entire bag resetting its hand.

https://static.wixstatic.com/media/f8796d_49da219649b642d6a07a66d1aeb56eac~mv2.png These are original stepGridHybrid strategy settings, these do not require manual configuration. Most of these settings automatically change every five seconds as the AutoConfig file cycles, meaning any user inputs will be rendered useless on the next cycle. The remaining are for settings unused by machineGun but present in the original strategy. • Do not change these settings outside of a simulation environment. • Do not change these settings in a live market nor while trading. • "SGH: Forever Bags" Enables a strategy of holding onto trades indefinitely, ignoring the break-even price & focusing on potential long-term gains from significant market upswings. • "SGH: Buy Enabled" Allows the placement of buy orders within the strategy, facilitating continuous trading activity & potentially increasing profitability. • "SGH: Sell Enabled" Enables the placement of sell orders, ensuring the strategy can take profits & manage positions effectively. • "SGH: Trend Basic" Enables dynamic trading actions based on market conditions, such as increased sell steps & trailing ranges during favorable markets, immediate buy orders during strong uptrends, & higher partial sell ratios following such buys. • "SGH: Trend Plus" Further enhances dynamic trading by enabling immediate buy orders during perceived short-term opportunities & increasing partial sell ratios following these buys, aiming to capitalize on market momentum. • "SGH: Use PSR" Automatically adjusts the partial sell ratio based on price. When prices are low, a higher ratio is used, leading to selling nearly the entire amount of the previous buy order. Conversely, a lower ratio is used when prices are high, resulting in smaller partial sell orders aimed at capturing better sell prices. • "SGH: Auto Step Size" Allows the strategy to automatically determine a grid step size that matches the current volatility of the trading pair. • "SGH: Auto Trend Orders" Limits the execution of trend-initiated orders to periods during a 4h uptrend, refining the strategy's market engagement to potentially more profitable times. • "SGH: Custom Trading Range Mode" Enables the definition of a specific price range within which the strategy operates. New trades are only opened within a price band of 8000 to 10000 USDT. DCA trades can occur at any price, but if the price falls below 7000 USDT, all holdings are sold. • "SGH: Dynamic Exit Logic" Modifies the exit strategy based on market conditions. In an uptrend, the exit target is the unit cost; in other situations, it is the overall break-even price. This setting is dependent on the 'unit cost' setting being disabled. • "SGH: Dynamic Stop Loss" Provides a dynamic stop loss target when used with volatility or TA mode, offering a safety mechanism that is not visible until it triggers, which can lead to potential losses. • "SGH: Enforce Step Size" Ensures that the specified step size is strictly adhered to, which can prevent orders from executing if the price does not align precisely with the grid steps, aiding in more precise capital management. • "SGH: Partial Sell Cap" Limits the maximum quantity of a partial sell order to prevent selling more than intended. • "SGH: Percent Sell Trailing Range" Allows you to set a custom percentage for the sell trailing range, which overrides the default automatic setting based on current market conditions. • "SGH: Percent Step Size" When enabled, the step size is treated as a percentage of the current price, modifying how the grid steps are calculated. • "SGH: Percent Trailing Range" Enables setting a custom percentage to define the buy trailing range, which overrides the default automatic setting based on support & resistance distances. • "SGH: Pullback Mode" Restricts new trades to times when a price pullback occurs, as primarily observed on 4h charts. This setting aims to optimize entry points but can significantly limit trading opportunities. • "SGH: TA Mode" Restricts trading to bullish pairs that meet specific technical analysis fractals, aiming to optimize trade entries based on technical signals. • "SGH: Trend Orders" Controls whether orders initiated by "SGH: Trend Basic" & "SGH: Trend Plus" settings are allowed, providing a method to toggle these dynamic features on & off without disabling the settings entirely. • "SGH: Trend Sync" Restricts the initiation of new trades to periods when the 4h & 1h trends are aligned, enhancing consistency but potentially reducing trade frequency. This setting does not affect dollar-cost averaging (DCA) trades. • "SGH: Trend Trailing" Automatically adjusts buy trailing ranges in bearish market conditions to avoid premature or unprofitable buying, enhancing strategy efficiency during downtrends. • "SGH: Unit Cost" Determines how the break-even price is calculated. When enabled, the break-even price reflects the average cost per unit of the remaining balance. When disabled, it reflects the price at which all remaining units can be sold without loss. • "SGH: Use TRL" Enables dynamic adjustment of the buy amount based on price. The buy amount varies between 0.25 to 1 times the trading limit, depending on whether the price is high or low. • "SGH: Volatility Mode" Limits trading to bullish pairs within a controlled volatility range. It aims to start trades at lower prices & stop at peaks, with a built-in stop mechanism to potentially minimize losses on the final sell order. • "SGH: Partial Sell Ratio" Defines the percentage of previously bought volume that can be sold at each sell step. For example, if 200 units were bought at lower prices, a partial sell ratio of 0.4 would allow selling 80 units at the current price. • "SGH: Trend Trailing Bearish Multiplier" Applies a larger multiplier to buy trailing ranges when both the 4h & 15m trends are bearish, significantly widening the buy range to capture better entry points during pronounced downtrends. • "SGH: Trend Trailing Multiplier" Applies a smaller multiplier to buy trailing ranges when the 4h trend is bullish but the 15m trend is bearish, allowing for adjusted buy points that reflect short-term market dips within a generally positive trend. • "SGH: Trailing Multiplier" Applies a multiplier to the trailing range when conditions detected by "SGH: Trend Basic" or "SGH: Trend Plus" warrant a larger trailing range, such as in specific bullish conditions. This setting also affects custom pct trailing ranges. • "SGH: Sell Step Multiplier" Increases the size of sell steps by a factor of 1.2 in certain market conditions identified by the trend modules, enhancing profit potential during specific trends. • "SGH: Step Size" Manually sets the grid step size for buy & sell orders when auto step size is not used. This setting can represent an absolute value in fiat (e.g., 500 USDT in USDT-BTC) or a percentage when pct step size is enabled. • "SGH: Minimum Step Percent" Sets a minimum percentage for the grid step size to ensure it does not fall below a certain threshold, which can override the auto step size if it is set lower than this minimum percentage. • "SGH: Custom Trailing Range" Defines the specific percentage used for the buy trailing range when "SGH: Percent Trailing Range" is enabled. A setting of 0.5% means the trailing range will be 0.5% of the current price. • "SGH: Custom Sell Trailing Range" Specifies the percentage used for the sell trailing range when "SGH: Percent Trailing Range" is enabled. A setting of 0.5% sets the trailing range to 0.5% of the current price, affecting how sell orders are trailed. • "SGH: Min Vol To Buy" Sets the minimum notional order value for buy orders. It is critical to align this value with your exchange's minimum trade requirements to avoid order rejections. For example, if your exchange has a minimum trade value of $10, set this parameter accordingly to ensure valid orders. Uses the same denomination as for "SGH: Trading Limit". • "SGH: Min Vol To Sell" Sets the minimum notional order value for sell orders. Like the buy setting, this should be aligned with the exchange's minimum trade requirements to ensure orders are valid & executable. If the exchange minimum is $10, this should be set to at least $10. Uses the same denomination as for "SGH: Trading Limit". • "SGH: Period" Selects the candle period used for auto-calculating step size & trailing range. A lower period value increases trading frequency & associated risks. This strategy also considers longer periods like 1h & 4h for trend analysis. • "SGH: Gain" Defines the minimum profit percentage above the current break-even or unit cost that must be achieved before a full sell order is executed. For instance, a setting of 1% ensures that full sells only occur at prices 1% higher than the break-even or unit cost. • "SGH: Gain Partial" Sets the minimum profit target for partial sells. A setting of 0.5% means partial sell orders are placed only when the buy price is at least 0.5% lower than the current price, after accounting for trading fees. • "SGH: Trading Limit" The base amount you invest for each individual buy order. Due to the Capital Stage, Trading Phase, & a plethora of other features found inside machineGun the actual investment per order will heavily range as per your configuration & live market conditions. • "SGH: SMA Period" Defines the number of candles used to calculate support & resistance levels for trailing range calculations. The default setting of 96 is typically adequate without adjustments. • "SGH: ATR Period" Specifies the number of candles used to determine the Average True Range, which helps calculate the auto step size for the strategy. The default setting of 1 generally does not require modification. • "SGH: Max Buy Count" Limits the total position size to a maximum of X times the trading limit. When this maximum is reached, the strategy will only place sell orders. • "SGH: Max Investment" Limits the total investment in base currency, which in the case of USDT-BTC would be the USDT amount. For example, setting this to 1000 limits the maximum investment to 1000 USDT. • "MG: Last AC Execution" Timestamp when machineGun has last been executed.