Strategy review means checking the method, parameters, pair, exchange, market type, and risk assumptions behind a bot setup. The workspace shows strategy configuration workflows, descriptions, defaults, individual settings descriptions, and related detail.
What This Feature Does
Strategy review should keep the method, the market, and the settings together. When the setup provides them, you can compare built-in, custom, community, scalping, trend-following, and preset strategy areas without losing the selected pair and exchange context.
Common Mistakes
A preset is only a starting point. Before using one with capital, understand its parameters, the market type it was designed for, and the assumptions it makes about fees, spread, liquidity, and timeframe.
Trading Reality
It gives Gunbot a browser workspace for monitoring, strategy work, backtesting, risk review, history, and exchange-connected operations. These pages explain what the product does. Your account data stays on your local trading bot, behind login.
Operational Limits
The dashboard depends on the connected Gunbot instance, the exchange API, and the network between them. It can make problems easier to notice, but it does not remove market risk or take responsibility away from you: exchange permissions, strategy settings, open orders, and capital allocation still need your review.
Plain Definition
Strategy review is the practice of understanding a trading method before using capital. You should know what the strategy tries to exploit, when it should not trade, how it sizes orders, how it exits, what timeframe it expects, and what market conditions can break it.
Strategy Review Questions
A strategy should be understandable before it gets capital. Know whether it is designed for spot, futures, or both, what kind of market behavior it assumes, what liquidity and spread it needs, how it handles exits and cooldowns, which settings are dangerous to change, and whether the idea can be checked through backtests or ledger history.
From Description To Parameters
A good strategy page should connect the plain-language idea to actual parameters. For example, if the description says "scalping", you should inspect spread limits, target size, stop behavior, cooldown, session filters, fees, and minimum order values. If it says "trend following", you should inspect timeframe, moving average lengths, breakout rules, trailing exits, and drawdown tolerance.
FAQ
Are custom strategies documented publicly?
Custom strategy behavior depends on you - the trigger behavior is defined in your own code. Public documentation can explain the workflow, but not every custom algorithm.
Can a strategy work on every exchange?
No. Pair naming, market type, liquidity, fees, and exchange API behavior can change the outcome - for example some exchanges might not allow limit orders while others do.
Why should pretty names and descriptions matter?
They help you avoid treating raw method keys as magic words. A strategy library should explain the idea, not only expose configuration fields.
Can a preset be used without review?
It can be selected, but it should not be trusted blindly. A preset is a starting point, not a guarantee of suitability.
Last updated: