Frequently asked questions

MagicTradeBot is a self-hosted crypto trading automation platform built in Rust for speed, deterministic performance, and full infrastructure control. It runs entirely on your own server — your API keys, trading data, and positions never leave your machine. It supports automated strategies (DCA, Market Watch, Funding Farming), TradingView signal execution, Hyperliquid whale copy trading, and signal broadcasting to Telegram and Discord.

Unlike cloud bots, MagicTradeBot runs on infrastructure you own and control. Your API keys are stored locally — we have no access to them. There is no shared multi-tenant environment, no third-party holding your exchange credentials, and no cloud outage that affects your live positions. You get full privacy, lower latency to your preferred exchange, and complete control over uptime and scaling.

MagicTradeBot runs on Windows, macOS, Linux (Ubuntu, Debian, CentOS), and Docker. The binary is self-contained — no runtime dependencies, no database installation required. Deploy on a local machine, VPS, or cloud instance with equal ease.

No. MagicTradeBot uses an embedded SQLite database that requires no installation or management. It stores all trade history, configuration, and state in a single local file. For Redis-based fleet deployments (multiple instances sharing market data), RedisMarketBridge is available as a companion service — but this is optional and only needed for advanced multi-instance scaling.

An Active Bot Instance is a single running MagicTradeBot process. Each instance can be configured to target a specific exchange, run a particular strategy, and scan hundreds or thousands of symbols in real time — executing trades only when your predefined conditions are met. You can run multiple instances across the same or different servers to scale coverage, isolate risk by strategy, or target multiple exchanges simultaneously.

Yes. The Free plan includes unlimited paper / demo trading — no license required and no time limit. You can simulate any strategy using live market data and virtual funds. Paper trading gives you full access to all bot features including DCA, Market Watch, TradingView signals, and risk management settings before committing real capital.

Yes. Paper trading uses live market data streamed directly from your connected exchange. Simulated order fills are calculated against real bid/ask prices at the time of execution, giving you an accurate picture of how the same strategy would perform in live conditions — including slippage behaviour.

Toggle the demo_mode setting in your config.yaml:

• demo_mode: true — paper trading (no real orders)
• demo_mode: false — live trading with real funds

Save the file and restart the bot. No other configuration changes are required.

We recommend a minimum of 7–14 days of paper trading in current market conditions before deploying with real capital. Markets change — a strategy that looked strong in a bull trend may behave very differently in a ranging or bearish market. When you do go live, start with the smallest viable position sizes and scale up only after confirming the strategy behaves as expected.

The DCA engine automatically places additional buy orders as the price moves against your position, lowering your average entry price. It includes a Volatility Gate that pauses DCA during abnormally fast price drops to prevent catching falling knives, and automatic position size calculation to prevent DCA from scaling beyond your configured risk budget. You control the number of DCA levels, the price step between each level, and the order size multiplier.

Configure the wallet addresses of Hyperliquid traders you want to mirror. MagicTradeBot continuously monitors their on-chain positions and automatically opens and closes matching trades on your connected exchange when they act. You control position size scaling, maximum orders per whale, which symbols to allow, and risk limits — the bot follows their signals but applies your risk parameters.

Funding Farming automates a delta-neutral yield strategy that earns from positive funding rates on perpetual futures. The bot selects the top N symbols by current funding rate, opens matching spot (long) and perpetual short positions to create a market-neutral pair, and collects the funding payment at each settlement interval. It automatically exits when funding turns negative or when your exit conditions are met. This strategy requires significant capital and is not risk-free — see the Knowledgebase for full risk details.

MagicTradeBot exposes a webhook endpoint on your server. Add this URL as the alert action in your TradingView Pine Script strategy. When your alert fires, TradingView sends a JSON payload to your bot, which executes the trade on your connected exchange. You define the payload format, position size, and risk parameters. The webhook also applies your configured stop-loss, DCA, and take-profit rules to each signal-triggered trade.

The Intelligent Decision Engine manages exits after entry. Smart stop-loss dynamically tightens as the position moves in your favour — locking in profits while still allowing room for continuation. Trailing take-profit moves the exit target upward as price rises, closing only when momentum fades by a configurable percentage. You can configure multiple partial take-profit rules (e.g., close 25% at +2%, another 25% at +4%) alongside a trailing stop for the remainder.

MagicTradeBot supports real-time trade and alert notifications via Telegram, Discord webhook, and WhatsApp. Notifications include trade entries, exits, DCA events, stop-loss triggers, emergency closes, and system health alerts. Multiple channels can be active simultaneously.

MagicTradeBot currently supports Binance, Bybit, OKX, Bitget, MEXC, and Hyperliquid (for Whale Copy Trading). New exchange integrations are added regularly. See the Documentation for the current full list and any platform-specific limitations (e.g., Bybit supports One-Way Mode only).

Grant read (account balance, position data) and trade (place and cancel orders) permissions only. If using futures or perpetuals, enable futures permission as well.

Never enable withdrawal permissions on any API key used with MagicTradeBot — the bot has no feature that requires it and it poses significant security risk.

No. Your exchange API keys are stored in your local config.yaml or environment variables on your own server. MagicTradeBot's servers never receive, process, or store your exchange credentials. All API calls to exchanges are made directly from your server to the exchange — MagicTradeBot infrastructure is not in that data path.

In One-Way Mode, you can only hold one direction (long or short) per symbol at a time — opening a short automatically closes any existing long. In Hedge Mode, you can hold simultaneous long and short positions on the same symbol independently. MagicTradeBot supports both modes. Note that Bybit only supports One-Way Mode in MagicTradeBot — configure your exchange position mode accordingly before running the bot.

Minimum: 2 vCPUs, 4 GB RAM, 50 GB SSD.
Recommended for high-frequency or multi-instance: 4+ vCPUs, 8 GB RAM, 100 GB NVMe SSD.

OS: Ubuntu 22.04 LTS or Debian 12 recommended for VPS deployments. Docker is also fully supported. The binary is extremely lightweight — most standard VPS plans well below these specs run MagicTradeBot without issue for typical single-instance setups.

Yes. Each instance runs as an independent process with its own configuration file and port. For fleet deployments where multiple instances share real-time market data, use RedisMarketBridge — it caches exchange market data centrally and serves it to all bot instances, dramatically reducing the total number of API calls to the exchange and avoiding rate limit issues at scale.

Open positions remain on the exchange as live orders — they are not affected by bot downtime. However, while the bot is offline:

• New trade entries will not be placed
• Bot-managed stop-losses and take-profits will not fire
• DCA orders will not be placed on price dips

For critical positions, consider placing exchange-native stop-loss orders as a backup. Use systemd, Docker restart policies, or a process manager to automatically restart the bot after crashes.

Back up two files regularly:

• config.yaml — your full configuration
• The SQLite database file — contains trade history and state

Copy these to an off-server location (object storage, remote server) daily. Restoring from backup on a new server requires only copying these files and running the bot binary — no complex database migration needed.

MagicTradeBot uses a day-based license extension model — you purchase a fixed number of days (7 days to 60 months) with no recurring charges and no auto-renewals. Your account simply reverts to the Free tier when a license expires. Renewing adds days to your current expiry — your configuration and trade history are preserved throughout.

MagicTradeBot accepts cryptocurrency only via NowPayments. Accepted currencies include Bitcoin, Ethereum, USDT (ERC20 and TRC20), USDC, Litecoin, and 100+ other cryptocurrencies. Credit cards, bank transfers, and fiat payment methods are not currently accepted.

Yes. Volume discounts apply automatically:

• 3 months — 5% discount
• 1 year — 12% discount + 30 bonus days
• 2 years — 25% discount + 90 bonus days
• 3 years — 35% discount + 180 bonus days

See the Pricing page for current rates.

Cryptocurrency payments are irreversible by nature, so refunds are generally not issued. Exceptions are considered only for verified platform failures, duplicate purchases, or unauthorised transactions. We strongly recommend testing thoroughly with the free unlimited paper trading before purchasing. See our full Refund & Cancellation Policy.

Yes. MagicTradeBot offers an affiliate program for individuals, influencers, educators, and community admins. Affiliates can earn up to 30% commission on each referred user's license purchases. Features include a personal dashboard, custom referral links, marketing creatives, and instant approval. Contact sales@magictradebot.com to apply.

Store API keys in environment variables rather than directly in config.yaml — this prevents accidental exposure if the config file is shared. Additionally:

• Enable IP whitelisting on each API key — restrict to your server's IP
• Never enable withdrawal permissions
• Never commit config.yaml to version control
• Rotate keys immediately if you suspect exposure

Never. MagicTradeBot staff will never request your exchange API keys, webhook URLs, or license keys in any support communication — by email, ticket, or any other channel. If you receive such a request, it is a phishing attempt. Report it immediately to sales@magictradebot.com with subject PHISHING REPORT.

We collect only what is necessary to operate your account: name, email, password hash, and payment transaction references for license activation. We never collect or access your exchange API keys, trading data, positions, or strategy configurations — all of that lives on your server. See our Privacy Policy for full details.