What is TradingMode?
TradingMode is a configuration setting in MagicTradeBot that defines the bot’s operational role.
It determines what functionality is active and what features are locked within a specific bot instance.
In simple terms:
One bot instance = One dedicated purpose.
This design prevents conflicts, reduces complexity, and ensures predictable behavior.
Why TradingMode Exists
MagicTradeBot supports multiple advanced features, such as:
- Standard signal-based trading
- Funding rate farming
- HyperLiquid whale copy trading
Each of these features requires different internal logic, workflows, and data handling.
If all were allowed simultaneously in one instance, it would:
- Create logical conflicts
- Increase configuration complexity
- Make troubleshooting harder
- Introduce execution risk
Therefore, TradingMode locks the bot into one focused operational mode.
Available TradingMode Options
1️⃣ funding-farming
Purpose: Hedged funding rate capture.
When enabled:
- The bot focuses only on funding rate opportunities
- It executes hedged positions to collect funding payments
- Signal-based trading is disabled
- Copy trading is disabled
This mode is optimized specifically for funding arbitrage strategies.
2️⃣ signal-processing
Purpose: Standard signal-driven trade execution.
When enabled:
- The bot processes configured trading signals
- Executes long and short positions
- Applies DCA, SL, TP, and risk management
- Runs your configured strategies
Funding farming and whale copy trading are disabled in this mode.
This is the standard trading mode most users operate.
3️⃣ hyperliquid-whale-copytrading
Purpose: Copy trades from designated HyperLiquid whale accounts.
When enabled:
- The bot monitors registered whale accounts
- Mirrors trades according to configuration
- Normal signal trading is disabled
- Funding farming is disabled
The bot becomes fully dedicated to copy trading behavior.
How TradingMode Affects Bot Behavior
When you select a TradingMode:
- Other major trading features are locked
- Strategy engines not related to that mode are disabled
- The bot instance becomes purpose-specific
- Resource allocation becomes optimized
This ensures:
- Clean execution logic
- Reduced risk of unintended trade overlap
- Easier performance monitoring
- Better debugging and stability
Running Multiple Modes? Use Multiple Instances
If you want to run multiple functionalities simultaneously, the correct approach is:
Run Separate Bot Instances
Example setup:
BotName: Bybit_Trading_Bot
Mode: signal-processing
Purpose: Standard strategy trading
BotName: Bybit_Farm_Funding
Mode: funding-farming
Purpose: Funding rate capture only
BotName: Bybit_HyperLiquid_CopyTrading
Mode: hyperliquid-whale-copytrading
Purpose: Whale copy trading only
Each instance runs independently, avoiding conflicts.
This is the recommended professional deployment structure.
Important Notes
-
Changing TradingMode may require:
- Bot restart
- Symbol re-sync
- Exchange re-initialization
- Always stop the bot before switching modes.
- Ensure configuration aligns with the selected mode.
Why This Design Is Important
This strict separation:
- Prevents confusion
- Avoids accidental mixed strategies
- Reduces execution risk
- Improves stability
- Keeps operational logic clean
It enforces a professional, modular trading structure.
Summary
TradingMode:
- Defines the operational purpose of a bot instance
- Locks unrelated features
- Prevents multi-purpose conflicts
- Improves stability and clarity
Available modes:
- funding-farming
- signal-processing
- hyperliquid-whale-copytrading
For multiple strategies, run multiple bot instances — one mode per instance.
This architecture ensures safer, cleaner, and more controlled automation.