Trading, Launch & Whale Intelligence

This page defines behavioral intelligence derived from Solana trading and token lifecycle activity.

It targets monitoring, dashboards, and alert pipelines.

Signals are descriptive and non-opinionated. They are not trading recommendations.

---

Coverage (what this page includes)

• Swap & trade analytics

  • Pair activity, flow imbalance, and short-horizon intensity.

• Token launch monitoring

  • First-liquidity and early post-launch behavior.

• Whale intelligence

  • Large-actor transfers, liquidity moves, and impact-sized swaps.

Common windows: 1m, 5m, 15m, 1h, 4h, 24h.

---

Swap & trade analytics

Normalized trade fields (canonical shape)

Trade events are treated as economic events. They are normalized before aggregation.

Core aggregates (interval analytics)

Aggregates are computed over explicit windows.

Key fields:

• Asset identity

  • base_mint, quote_mint, decimals for both

• Amounts

  • native amounts + decimal-adjusted UI amounts

• Pricing

  • price (quote per base), fee fields when observable

• Attribution

  • protocol, pool_address, program_id, tx_signature, slot, block_time

Routed swaps may produce multiple legs. Prefer a de-duplicated “economic trade” view when available.

• OHLCV

  • Open/high/low/close, base/quote volume, trade count.

• Flow

  • Base-in vs base-out as an imbalance proxy.

• Concentration

  • Top pool share for a pair, top route share when observable.

• Stress proxies

  • Swap size vs liquidity, and volume-to-liquidity divergence.

Example: interval aggregate (conceptual)

{
  "window": "5m",
  "start_time": "2025-12-17T10:00:00Z",
  "end_time": "2025-12-17T10:05:00Z",
  "base_mint": "So11111111111111111111111111111111111111112",
  "quote_mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
  "protocol": "amm",
  "pool_address": "ExamplePoolAddress",
  "ohlcv": {
    "open": 201.42,
    "high": 203.1,
    "low": 200.98,
    "close": 202.77,
    "trade_count": 129
  },
  "flow": { "imbalance_ratio": 0.043 },
  "concentration": { "pair_volume_share_top_pool": 0.71 }
}

Token launch monitoring

Launch monitoring tracks a token’s transition from “new mint” to “tradable market”.

Launch lifecycle model (event-driven)

Token metadata can lag mint creation. Early launch signals may precede complete metadata.

Example: launch signal (conceptual)

{
  "signal_type": "token_launch",
  "mint": "ExampleMintAddress",
  "detected_at": "2025-12-17T10:02:14Z",
  "milestones": {
    "first_liquidity_at": "2025-12-17T10:01:02Z",
    "first_trade_at": "2025-12-17T10:01:19Z"
  },
  "early_window": "15m",
  "trading": { "volume_usd": 92114.72, "trade_count": 211, "unique_traders": 87 },
  "concentration": { "top_trader_volume_share": 0.23, "top_pool_volume_share": 0.78 },
  "severity": "medium",
  "confidence": 0.84
}

---

Whale activity detection

Whale intelligence detects large-actor behavior that can shift liquidity or price dynamics.

Whale definition (context-based)

Whale sizing is evaluated relative to context:

• absolute notional size

• size vs circulating supply (when known)

• size vs pool liquidity / TVL (impact-aware)

Whale categories

• large_transfer

• liquidity_move

• high_impact_swap

• repeated_large_actor_interaction

Noise control (Solana realities)

Solana has program-owned accounts and vault flows. Raw transfers are not always “human intent”.

• exclude obvious program vault patterns when determinable

• de-duplicate multi-instruction transfers inside one transaction

• apply cooldown windows via a stable dedupe_key

Example: whale signal (conceptual)

{
  "signal_type": "whale_activity",
  "detected_at": "2025-12-17T10:04:31Z",
  "actor": "ExampleWalletAddress",
  "mint": "ExampleMintAddress",
  "category": "liquidity_move",
  "context": { "protocol": "amm", "pool_address": "ExamplePoolAddress", "slot": 312345678 },
  "size": { "notional_usd": 154203.55, "pool_tvl_share": 0.19 },
  "reason_codes": ["LARGE_LP_WITHDRAWAL", "POOL_DEPTH_DROP"],
  "severity": "high",
  "confidence": 0.91,
  "dedupe_key": "whale_activity:ExampleWalletAddress:ExamplePoolAddress:liquidity_move:5m"
}

---

Consumer guidance

Recommended integration defaults:

• Trigger alerts on completed windows.

• De-duplicate using dedupe_key.

• Prefer “size vs liquidity” over absolute thresholds for swaps.

• Treat finality explicitly (confirmed vs finalized) when strict correctness matters.