⚡ MagicTradeBot Standard Trading Signals

In MagicTradeBot v6.0, signal handling has been completely redesigned. There are no static signal tables or hardcoded mappings inside the core system. All signals are now managed through the /settings/signal_registry.yaml configuration file.

This provides full flexibility to define how each signal behaves — whether it should trigger auto trade execution or be used only for broadcast notifications. It is strongly recommended to use the Bot Configurator UI instead of manual editing.

⚙️ Signal System Overview

MagicTradeBot v6.0 supports a unified signal processing pipeline with two primary categories:

Auto Trade Execution Signals → Execute real trades based on strategy and risk engine
Broadcast / Notification Signals → Send alerts to Telegram, Discord, UI dashboards, etc.

All signals pass through the same validation engine before routing to execution or notification layers.

🧠 Signal Registration System (v6.0 Core)

Signals are registered inside /settings/signal_registry.yaml. This file defines exactly how each signal behaves in the system.


# ------------------------------------------------
# Order Execution Signals (REAL TRADING)
# ------------------------------------------------
register_trading_signals:
  - "LONG_PUMP_SIGNAL"
  - "SHORT_CRASH_SIGNAL"
  - "SHORT_CRASH_ACCELERATION_SIGNAL"
  - "SHORT_MOMENTUM_FORMING_CANDLE_SIGNAL"
  - "LONG_MOMENTUM_ACCELERATION_SIGNAL"
  - "LONG_MOMENTUM_FORMING_CANDLE_SIGNAL"
  - "TV_EMA_CROSS_LONG_EXTERNAL_SIGNAL"
  - "TOP_GAINER_LONG_SIGNAL"
  - "TOP_GAINER_SHORT_SIGNAL"
  - "TOP_LOSER_SHORT_SIGNAL"
  - "TOP_LOSER_LONG_SIGNAL"

# ------------------------------------------------
# Broadcast / Notification Signals (NO TRADING)
# ------------------------------------------------
register_broadcast_signals:
  - "LONG_PUMP_SIGNAL"
  - "SHORT_CRASH_SIGNAL"
  - "SHORT_CRASH_ACCELERATION_SIGNAL"
  - "SHORT_MOMENTUM_FORMING_CANDLE_SIGNAL"
  - "LONG_MOMENTUM_ACCELERATION_SIGNAL"
  - "LONG_MOMENTUM_FORMING_CANDLE_SIGNAL"
  - "TV_EMA_CROSS_LONG_EXTERNAL_SIGNAL"
  - "TOP_GAINER_LONG_SIGNAL"
  - "TOP_GAINER_SHORT_SIGNAL"
  - "TOP_LOSER_SHORT_SIGNAL"
  - "TOP_LOSER_LONG_SIGNAL"

📡 Signal Types Explained

1. Auto Trade Execution Signals

These signals trigger real trade execution through the bot’s risk engine, money management system, and strategy logic.

Validated by decision engine before execution
Fully integrated with SL/TP, DCA, and trailing logic
Respect exchange constraints and position rules

2. Broadcast Signals (Monitoring Only)

These signals do NOT execute trades. They are used for:

Telegram / Discord alerts
Dashboard visualization
Manual trading decision support

📊 TradingView Signal Format

TradingView signals are standardized using the following format:


TV_{STRATEGY}_{DIRECTION}_EXTERNAL_SIGNAL

Example:


TV_EMA_CROSS_LONG_EXTERNAL_SIGNAL

These signals are injected into the system via the TradingView Signal Bridge.

🌉 TradingView Signal Bridge (Required)

In v6.0, TradingView signals are not processed directly by the bot. Instead, they must pass through the TV Signal Bridge.

Receives webhook alerts from TradingView
Validates and normalizes signal format
Streams signals to the bot execution engine
Ensures reliable and structured signal delivery

Without proper configuration of the TV Signal Bridge, TradingView signals will not be executed.

⚠️ Key v6.0 Changes

No legacy signal tables inside core bot logic
All signals must be explicitly registered in signal_registry.yaml
Bot Configurator UI is the recommended management method
Signal behavior is fully decoupled from strategy logic

🚀 Summary

MagicTradeBot v6.0 introduces a fully modular signal architecture where every signal is explicitly defined and routed through configurable execution or broadcast pipelines.

This ensures maximum flexibility, transparency, and control over how trading decisions are triggered and monitored.