Monitor Whales

Real-time monitoring system for tracking large cryptocurrency transactions (whales) across multiple blockchains. Detects significant wallet movements, analyzes market impact, and provides automated alerts through multiple channels (Slack, Discord, Telegram, email).

Supports: Ethereum, Bitcoin, Binance Smart Chain, Polygon, Arbitrum, Optimism, Avalanche, Solana

When to Use This Command

Use /monitor-whales when you need to:

• Track large transactions that could impact market prices (typically >$1M USD)
• Monitor whale wallet accumulation/distribution patterns
• Receive real-time alerts for significant on-chain movements
• Analyze exchange inflows/outflows for market sentiment
• Identify potential market manipulation or coordinated movements
• Track smart money movements for trading signals
• Monitor specific whale addresses of interest
• Detect unusual transaction patterns before price movements

DON'T use this command for:

• Small retail transactions (<$100K USD) - Creates noise
• Historical analysis - Use /analyze-chain instead
• Portfolio tracking - Use /track-wallet instead
• Price predictions - Use /generate-signal instead
• Tax calculations - Use /calculate-tax instead

Design Decisions

Why Multiple Blockchain Support? Whales operate across multiple chains. Cross-chain tracking provides complete picture of institutional movements and arbitrage activities.

Why Real-Time vs Batch Processing?

• Real-time chosen: Market impact occurs within seconds of large transactions
• Batch rejected: 15-minute delays make alerts useless for trading

Why Threshold-Based Filtering?

• Threshold chosen: Configurable minimums ($100K-$10M) reduce noise
• All transactions rejected: Would generate 100,000+ alerts/day

Why Multi-Channel Alerting?

• Multi-channel chosen: Different traders prefer different platforms
• Email-only rejected: Not suitable for time-sensitive trading alerts

Why Market Impact Scoring?

• Scoring chosen: Quantifies potential price movement (0-100 scale)
• Binary alerts rejected: Traders need severity assessment

Prerequisites

Before running this command, ensure you have:

1. Blockchain Node Access (choose one per chain):

• Infura API key (Ethereum, Polygon, Optimism, Arbitrage)
• Alchemy API key (Ethereum, Polygon, Arbitrum, Solana)
• QuickNode endpoint (all chains)
• Self-hosted nodes (advanced)

1. Price Data API:

• CoinGecko API key (free tier: 50 calls/min)
• CoinMarketCap API key (recommended for real-time)
• DEX price aggregator (1inch, 0x)

1. Alert Delivery Services (at least one):

• Slack webhook URL
• Discord webhook URL
• Telegram bot token + chat ID
• SendGrid API key (email alerts)
• Twilio credentials (SMS alerts, optional)

1. Database (for historical tracking):

• PostgreSQL 13+ (recommended)
• MongoDB 5+ (alternative)
• TimescaleDB (for time-series optimization)

1. Infrastructure:

• Linux server (Ubuntu 20.04+) or Docker
• 4GB RAM minimum (8GB for multi-chain)
• 100GB storage (30 days history)
• Webhook endpoint for alerts (optional)

Implementation Process

Step 1: Configure Blockchain Connections

Create config/chains.json:

{
  "ethereum": {
    "rpc_url": "https://eth-mainnet.g.alchemy.com/v2/YOUR_KEY",
    "websocket_url": "wss://eth-mainnet.g.alchemy.com/v2/YOUR_KEY",
    "whale_threshold_usd": 1000000,
    "native_symbol": "ETH",
    "block_time": 12
  },
  "bsc": {
    "rpc_url": "https://bsc-dataseed.binance.org/",
    "websocket_url": "wss://bsc-ws-node.nariox.org:443",
    "whale_threshold_usd": 500000,
    "native_symbol": "BNB",
    "block_time": 3
  },
  "solana": {
    "rpc_url": "https://solana-mainnet.g.alchemy.com/v2/YOUR_KEY",
    "websocket_url": "wss://solana-mainnet.g.alchemy.com/v2/YOUR_KEY",
…

Step 2: Set Up Alert Channels

Create config/alerts.json:

{
  "channels": {
    "slack": {
      "enabled": true,
      "webhook_url": "https://hooks.slack.com/services/YOUR/WEBHOOK/URL",
      "channel": "#whale-alerts",
      "min_severity": 50
    },
    "discord": {
      "enabled": true,
      "webhook_url": "https://discord.com/api/webhooks/YOUR_ID/YOUR_TOKEN",
      "min_severity": 60
    },
    "telegram": {
      "enabled": true,
      "bot_token": "YOUR_BOT_TOKEN",
      "chat_id": "YOUR_CHAT_ID",
      "min_severity": 70
…

Step 3: Initialize Database Schema

-- PostgreSQL schema for whale tracking
CREATE TABLE whale_transactions (
    id SERIAL PRIMARY KEY,
    tx_hash VARCHAR(66) UNIQUE NOT NULL,
    chain VARCHAR(20) NOT NULL,
    block_number BIGINT NOT NULL,
    timestamp TIMESTAMP NOT NULL,
    from_address VARCHAR(42) NOT NULL,
    to_address VARCHAR(42) NOT NULL,
    value_native NUMERIC(36, 18) NOT NULL,
    value_usd NUMERIC(18, 2) NOT NULL,
    token_symbol VARCHAR(20),
    token_address VARCHAR(42),
    transaction_type VARCHAR(20),
    severity_score INTEGER,
    market_impact_score INTEGER,
    is_exchange_related BOOLEAN DEFAULT FALSE,
    exchange_name VARCHAR(50),
…