MagicTradeBot v3.1 — Introducing the Hyperliquid Whale Copy Trading Feature

Posted: 17 October, 2025

MagicTradeBot’s new Hyperliquid Whale Tracker lets you follow wallet-level trading activity on Hyperliquid and other decentralized, wallet-based exchanges. You can now track any wallet address, receive real-time notifications, and even automatically mirror (copy) whale trades with full safety, filtering, and control options.

🚀 Overview

The Hyperliquid Whale Tracker is a new module in MagicTradeBot v3.1 designed for traders who want to leverage on-chain transparency. It continuously monitors selected whale wallets and reacts when those wallets open or close positions. You can use it in two main modes:

  • Signal-only mode — receive real-time whale trade alerts via Telegram, Discord, WhatsApp, or Webhooks.
  • Mirror mode — automatically execute mirrored trades on your connected exchange account, with intelligent safeguards.

Configuration is entirely managed through your tradesettings.yaml file and can be enabled per bot instance. By default, it’s turned off for safety.

⚙️ Configuration Example

To activate the tracker, add the following section in your tradesettings.yaml file:

HyperLiquidWhaleTracker:
  is_enabled: true
  tracking_addresses:
    - "0x2aB3...Ff12"
    - "0x1cD4...Aa77"
  place_order: true
  order_amount: 150.0
  leverage: 3
  broadcast_signals: true
  max_open_per_whale: 2
  slippage_tolerance_percent: 0.5
  follow_partial_fills: true
  close_on_whale_close: true
  include_liquidations: false
  only_follow_buy: false
  only_follow_sell: false
  min_whale_order_value: 100.0
  cooldown_seconds: 60

This configuration tracks two whale wallets, mirrors their trades at 3x leverage with $150 per trade, and automatically closes mirrored positions when whales close theirs.

🧠 How It Works

  1. Event Source — The bot subscribes to Hyperliquid’s on-chain wallet events for specified addresses.
  2. Event Detection — When a whale opens or closes a position, the bot validates the trade based on filters (size, cooldown, direction).
  3. Decision — If place_order = true, a mirrored trade is created using your connected exchange API; otherwise, a signal is broadcast.
  4. Execution — Orders are placed respecting slippage limits, leverage, and available margin. Partial fills can be mirrored proportionally.
  5. Lifecycle — The bot monitors mirrored positions and closes them automatically if close_on_whale_close is enabled.
  6. Logging & Alerts — All events are logged and optionally sent to your notification or monitoring channels.

🔒 Security & Risk Controls

  • Never hardcode API keys or private keys — use environment variables or encrypted secrets.
  • Limit permissions to trading only; never enable withdrawals.
  • Use DemoMode for initial testing before going live.
  • Set max_open_per_whale and slippage_tolerance_percent conservatively.
  • Enable error monitoring (e.g., Sentry, PagerDuty) for production deployments.

📣 Notifications & Broadcasts

When broadcast_signals: true, MagicTradeBot sends formatted alerts for each whale trade event.

Example (Telegram / Discord):

[Hyperliquid Whale] NEW ORDER
Whale: 0x2aB3...Ff12
Action: BUY (Long)
Symbol: BTCUSDT
Size: 0.5 BTC (~25,000 USDT)
Leverage: 3x
Mirrored: yes (Order ID: M-123456)

Example (Webhook JSON):

{
  "type": "hyperliquid.whale.event",
  "whale_address": "0x2aB3...Ff12",
  "action": "open",
  "side": "buy",
  "symbol": "BTCUSDT",
  "size": 0.5,
  "notional": 25000,
  "leverage": 3,
  "mirrored": true,
  "timestamp": "2025-10-16T12:34:56Z"
}

🧩 Testing & Demo Mode

  • Set place_order: false and DemoMode: true for safe testing.
  • Verify signal messages before enabling mirrored trading.
  • Start with small order_amount and confirm accurate event detection.
  • Monitor completedorders.yaml for mirrored trade logs.

⚡ Operational Best Practices

  • Use cooldown_seconds to prevent over-trading from whales splitting orders.
  • Keep signal-only mode during volatile markets.
  • Combine with money-management modules for dynamic sizing and risk mitigation.
  • Use Prometheus and Loki for observability metrics and event auditing.

⚠️ Limitations & Risks

  • Whale tracking ≠ guaranteed profit — whales can also lose or manipulate.
  • Execution latency and slippage may cause deviations in mirrored trade outcomes.
  • Tracking many wallets increases API load — adjust rate limits accordingly.

💬 FAQ

Q: Can I track any wallet?

Yes. Add any public wallet address under tracking_addresses — the bot will detect related trade activity automatically.

Q: Does it match the whale’s exact position size?

No. It uses your configured order_amount or proportional size if follow_partial_fills is enabled.

Q: What if a whale sends multiple micro-orders?

Use cooldown_seconds and follow_partial_fills to prevent duplicate trades and control overexposure.

While following public wallet activity is on-chain transparent, ensure compliance with exchange terms and local regulations. MagicTradeBot provides the tools — you are responsible for legal and ethical usage.

🛠️ Support & Troubleshooting

  • Check completedorders.yaml and logs for errors.
  • Verify API permissions and environment variable configurations.
  • Contact official MagicTradeBot Support via your dashboard for technical assistance.

Tags

Categories