This glossary defines trading bot and product terms you encounter while monitoring automated crypto trading. Each term explains the definition, why it matters, a common mistake, the related product feature, and the related learning page so readers can move from vocabulary to practical operating detail.
Automation And Access Terms
| Term | Definition | Why it matters | Common mistake | Related feature | Related learn page |
|---|---|---|---|---|---|
| Gunbot Live | A crypto trading bot product with a web interface for monitoring, managing, and reviewing automated trading operations. | It shows portfolio, risk, charts, history, strategy, automation, and control detail in one workspace. | Treating it as a guaranteed profit system instead of trading automation software that still requires configuration, monitoring, and risk control. | Live dashboard & portfolio | Trading bot dashboard |
| Gunbot | The trading automation software that runs strategy logic and interacts with exchanges. | The workspace shows Gunbot-related details, while the bot and exchange still define execution reality. | Confusing the public documentation site with the logged-in trading engine. | Bot control | Crypto trading bots |
| Exchange API access | API credentials and permissions used by software to read data or place orders on an exchange. | Bad permissions, expired keys, wrong passphrases, or blocked IPs can break data and execution. | Sharing raw API keys in support messages or using broader permissions than needed. | Security and privacy | Crypto trading automation |
| Connected instance | A local, remote, cloud, or private Gunbot environment selected inside the dashboard. | Every edit, chart, balance, and risk view depends on which instance is currently selected. | Changing the wrong instance because several setups look similar. | Multi-instance monitoring | Trading bot dashboard |
| Demo mode | A restricted mode intended for viewing or demonstration without allowing normal frontend changes. | It protects you and shared environments from unintended edits. | Assuming demo visibility means editing should be allowed. | Bot control | Trading bot risk management |
Trading State Terms
| Term | Definition | Why it matters | Common mistake | Related feature | Related learn page |
|---|---|---|---|---|---|
| Pair | The market being traded, such as USDT-BTC in Gunbot notation or BTC/USDT in exchange notation. | Pair notation affects history fetching, charts, order placement, and risk review. | Sending a Gunbot pair name directly to an exchange API that expects a different symbol. | Trading history | Crypto trading bots |
| BTC/USDT | Common exchange notation for the Bitcoin and Tether market, where BTC is the base asset and USDT is the quote asset. | It is often used as a major-pair example for liquidity, spreads, fills, history, and risk review. | Assuming BTC/USDT, USDT-BTC, futures symbols, and exchange-specific symbols are interchangeable without mapping. | Live dashboard & portfolio | BTC and ETH trading bot risk checklist |
| ETH/USDT | Common exchange notation for the Ethereum and Tether market, where ETH is the base asset and USDT is the quote asset. | It is a common major-pair example for monitoring spread, partial fills, volatility, and exchange-side history. | Treating ETH/USDT behavior as identical across spot, futures, and every exchange. | Low-lag charts | BTC and ETH trading bot risk checklist |
| Base asset | The asset being bought or sold in a pair, such as BTC in BTC/USDT or ETH in ETH/USDT. | It affects order amount, position size, inventory, exposure, and how fills should be read. | Confusing base amount with quote value and sizing orders incorrectly. | Trading history | Crypto trading bots |
| Quote asset | The asset used to price the base asset, such as USDT in BTC/USDT or ETH/USDT. | It affects balances, trading limits, order value, fees, and portfolio comparison. | Thinking the quote balance is the same thing as base inventory or position size. | Live dashboard & portfolio | Trading bot dashboard |
| Major pair | A high-volume pair such as BTC/USDT or ETH/USDT that often has deeper liquidity than smaller markets. | Major pairs can reduce some spread and liquidity problems, but they still need monitoring during volatility. | Assuming a liquid major pair is automatically safe for any strategy or order size. | Risk management | BTC and ETH trading bot risk checklist |
| Altcoin pair | A market involving a smaller or less dominant asset, often with thinner liquidity or wider spreads than major pairs. | Altcoin pairs may need stricter spread, sizing, slippage, and history checks. | Using the same assumptions from BTC/USDT on a thin altcoin market. | Risk management | Trading bot risk management |
| Open order | An order submitted to an exchange that has not fully filled, canceled, or closed. | Open orders can still execute later and change exposure unexpectedly. | Stopping a bot and assuming exchange-side orders disappeared automatically. | Live dashboard & portfolio | Trading bot dashboard |
| Fill | The executed part of an order, including timestamp, price, amount, side, and sometimes fee. | Fills are the factual basis for trading history, PnL, recovery, and JSON exports. | Relying on summary cards without checking fill-level evidence. | Trading history | Trading bot dashboard |
| Portfolio value | The reported value of the selected account, setup, or assets when your setup provides the data. | It gives a broader view than one closed trade or one pair result. | Treating realized PnL as complete performance while ignoring open exposure. | Live dashboard & portfolio | Trading bot dashboard |
| Realized PnL | Profit or loss from closed trades or completed sell/exit events when calculable. | It shows closed-trade outcome but not necessarily current account risk. | Thinking realized gains mean the account has no underwater exposure. | Deep strategy statistics | Backtesting vs live trading |
| Unrealized PnL | Estimated profit or loss on open exposure that has not been closed. | It can reveal risk hidden behind attractive closed-trade results. | Ignoring it because it is not final yet. | Risk management | Trading bot risk management |
| DP1K | A normalized performance metric used in product fits to express result per 1,000 units over a daily reference when present. | It helps compare activity across different capital sizes, but only when the underlying assumptions and data source are understood. | Treating DP1K as a guaranteed future daily return instead of a historical or contextual metric. | Deep strategy statistics | Backtesting vs live trading |
| ROI | Return on investment, usually expressed as a percentage relative to the capital or position basis being measured. | It gives a compact performance view, but it needs drawdown, exposure, fees, and time in market to be useful. | Comparing ROI values without checking capital deployed, open exposure, drawdown, or fee drag. | Deep strategy statistics | Backtesting vs live trading |
Risk And Review Terms
| Term | Definition | Why it matters | Common mistake | Related feature | Related learn page |
|---|---|---|---|---|---|
| Exposure | Capital currently at risk through open positions, inventory, or orders. | High exposure can turn a small market move into a large account problem. | Looking only at available balance and ignoring positions or pending orders. | Risk management | Trading bot risk management |
| Drawdown | Decline from a previous wallet, equity, or performance peak. | It shows downside stress and how painful a strategy path can become. | Comparing strategies only by profit and not by drawdown path. | Risk management | Backtesting vs live trading |
| Fee drag | The portion of strategy results consumed by fees, spread, and trading costs. | Scalping and high-frequency strategies can look active while fees eat the edge. | Optimizing entries while ignoring exchange fee tier and spread. | Deep strategy statistics | Backtesting vs live trading |
| Backtest | A historical simulation of strategy logic under assumptions. | It helps review ideas before live capital but cannot reproduce future execution perfectly. | Treating a good backtest as a guarantee. | Spot & futures backtesting | Backtesting vs live trading |
| Paper trading | A rehearsal mode without live capital when supported. | It can help test workflow but may still differ from live liquidity and emotion. | Assuming paper fills prove live fills. | Spot & futures backtesting | Backtesting vs live trading |
| Live trading | Execution against current markets with real account impact. | It exposes capital to real fees, latency, outages, spread, liquidity, and your decisions. | Scaling immediately after one good historical test. | Live dashboard & portfolio | Backtesting vs live trading |
Strategy And Tooling Terms
| Term | Definition | Why it matters | Common mistake | Related feature | Related learn page |
|---|---|---|---|---|---|
| Strategy | A set of trading rules and parameters used by the bot. | It determines entries, exits, sizing, filters, and behavior under market conditions. | Selecting a strategy by name without understanding its assumptions. | Strategy library | Crypto trading bots |
| Built-in strategy | A native strategy shipped with the platform. | Built-ins provide documented starting points, but settings still need review. | Assuming native means safe for every pair or timeframe. | Strategy library | Crypto trading bots |
| Community strategy | A strategy from a community or external developer ecosystem. | It can expand choices but requires license, support, and risk review. | Equating popularity with suitability. | Strategy library | Copy trading automation |
| Custom JavaScript strategy | Custom JavaScript strategy logic and related metadata when supported. | It gives more flexibility and more responsibility. | Hardcoding one custom strategy workflow instead of loading custom metadata. | Custom JavaScript strategies | Crypto trading automation |
| Autoconfig | Rule-based automation that changes selected settings as market conditions change. | It can improve responsiveness but can also alter live behavior quickly. | Letting volatile signals change too many settings at once. | Autoconfig | Trading bot risk management |
| Code editor | A frontend editor for supported config, autoconfig, state, and strategy files. | It helps with direct file work but must protect demo mode and secrets. | Editing live config without backups or validation. | Code editor | Crypto trading automation |
Marketplace, Recovery, And Deployment Terms
| Term | Definition | Why it matters | Common mistake | Related feature | Related learn page |
|---|---|---|---|---|---|
| Copy trading | Using another provider, strategy, signal, or copied workflow as part of your own operation. | It can import both useful ideas and unsuitable risk. | Thinking a purchased or copied strategy guarantees future results. | Copy trading | Copy trading automation |
| Provider | The person, source, service, or strategy owner that supplies a marketplace strategy, settings, or signal workflow when copy trading is configured. | Provider detail helps you understand what you would be following before connecting capital to a copied workflow. | Assuming provider history will match the follower account after fees, timing, exchange differences, and sizing. | Copy trading | Copy trading automation |
| Signal provider | A provider that emits trade or management signals for another account or workflow to review or follow. | Signal quality, timing, frequency, and market assumptions can materially affect follower results. | Treating every signal as executable at the same price, size, or liquidity on every account. | Copy trading | Copy trading automation |
| Signal history | A record of prior strategy or provider signals when present. | It helps review behavior before subscribing or copying. | Reading signal history without checking market, exchange, fees, and drawdown. | Copy trading | Copy trading automation |
| Subscription state | The current access state for a paid or managed copy trading workflow, such as pending, active, expired, or canceled when the module exposes it. | It tells you whether access or copying should be available, but it does not validate strategy quality. | Confusing an active plan with a safe or profitable strategy. | Copy trading | Copy trading automation |
| Copy count | A count of active or historical copies/subscribers shown for a strategy when present. | It can provide adoption signal, but it is not a performance or safety guarantee. | Using popularity as the main reason to copy a strategy. | Copy trading | Copy trading automation |
| Marketplace strategy | A strategy listed in the copy trading or marketplace area when the required database, billing, and deployment configuration are active. | It gives you a structured way to inspect strategy descriptions, provider details, pricing, and review data. | Assuming listing in a marketplace means endorsement, guaranteed profitability, or suitability for every account. | Copy trading | Copy trading automation |
| Exchange-native bot | A trading bot or automation workflow provided inside an exchange interface, such as exchange-side grid or DCA tools where available. | It can be convenient, but it may not expose the same independent bot state, custom strategy logic, deployment control, or cross-exchange review. | Assuming exchange-native automation and an independent trading bot dashboard answer the same operational questions. | Strategy library | Binance trading bot dashboard |
| Disaster recovery | Rebuilding useful records after missing history, damaged files, or failed imports. | Clean recovery supports support, audit, risk review, and tax workflows. | Fetching all pairs when only one selected pair is needed. | Disaster recovery | Trading bot dashboard |
| Tax download | A structured export of trading history for accounting or audit review. | It preserves evidence but does not decide tax treatment. | Sharing a full export when only one pair is relevant. | Tax downloads | Trading bot dashboard |
| BitRage spot/futures | A workflow comparing spot and futures market differences. | Fees, funding, latency, partial fills, and margin can erase the apparent edge. | Calling BitRage risk-free. | BitRage spot/futures | Crypto trading automation |
| Private deployment | Running the stack on infrastructure you control, a VPN, a proxy, a firewall, or a private network. | It lets you avoid exposing the Gunbot instance publicly when you prefer private infrastructure. | Assuming private deployment removes the need for credential hygiene. | Cloud or private deployment | Trading bot risk management |
FAQ
Why are glossary terms longer than one line?
Trading bot terms affect real decisions. A short definition is rarely enough without risk and product concepts.
Where should I go after the glossary?
Read core concepts, risk management, and the feature page related to the term you are researching.
Last updated: