# Whale tracking is too noisy and late
> Source report: https://gapforapp.com/reports/whale-tracking-is-too-noisy-and-late

## 1. What we're building
Build a Polymarket whale intelligence terminal that turns raw wallet activity into actionable signals. The product should include zero-delay real-time whale alerts, Telegram and Discord notifications, wallet watchlists, historical wallet performance, labeled wallets, and filtering that removes sports bets, low-impact events, and fragmented fills so users can focus on meaningful conviction. It should also flag suspicious patterns such as fresh wallets, oversized trades relative to market size, clustered bets before resolution, and possible multi-account behavior.

The must-have workflow is not just monitoring, but deciding: a backtesting tool for whale-following strategies, a filtered whale list based on historical accuracy and stability, and paper trading / sandbox mode so users can test copy-trading without taking execution risk. To address the strongest asks, the product should also offer a cross-platform Polymarket and Kalshi scanner, live on-chain signal feeds, exit alerts when large wallets unwind positions, and clearer market-definition / resolution context. In short: a low-latency fraud-radar-plus-copy-trading tool that helps users separate real smart money from noise before the market moves.

**Working name:** WhaleRadar Polymarket
**Tagline:** Real-time, filtered whale trade intelligence with explainable 0–100 alerts for prediction markets.
**Main goal:** Deliver near-real-time whale trade alerts that are filtered and ranked by an explainable 0–100 score, so users can act before the noise becomes unusable.
**Target users:** Active Polymarket/Kalshi traders who want actionable “smart money” signals without manual wallet monitoring.

**Main user result:** A trader receives only high-conviction (e.g., 70+) whale trade alerts with clear reasons and market/odds impact context.
**5-minute outcome:** They create a watchlist, set a 70+ score threshold, and see the live radar feed start delivering filtered alerts.
**What we solve first:** Zero/near-zero real-time monitoring of prediction-market whale trades with default noise filters and explainable 0–100 scoring.
**Out of scope for MVP:**
- Backtesting studio and strategy sandbox execution
- Cross-venue alpha inference (Polymarket vs Kalshi) beyond basic normalization
- Advanced multi-account/decoy graphing and deep entity labeling

## 2. Why this is worth building
- Verdict: **LOW** (59/100)
- The problem appears consistently across nearly every chunk: whale-following is described as too slow, too noisy, and too easy to misread. Users repeatedly ask for better real-time alerts, filtering, wallet history, and suspicious-activity detection, which indicates a clear unmet need rather than a one-off complaint. The concern is not only about missing trades, but about lacking enough context to distinguish skill from manipulation or hedging. That combination makes this a strong product opportunity.

**Current pain:** Whale tracking is described as noisy and too time-consuming, and on-chain explorers arrive after prices already moved. Even when whales are visible, retail often can’t interpret what matters fast enough.
**Current workaround:** Users manually track/scan (e.g., Dune/on-chain) and rely on leaderboard visibility, then decide reactively after they’ve already seen the move.
**Why existing tools fail:** Existing tools surface wallet activity but lack a Polymarket/Kalshi-specific fraud/risk scoring with explainable reasons, strong default noise filtering (e.g., non-sports/min impact), and resolution-aware stats. As a result, users still face confusion/divergences and late signal delivery.

## 3. Must-have capabilities
### 3.1 Fraud-radar scoring for prediction market whale trades
**Why:** Users explicitly want a “fraud radar” that ranks/flags suspicious or high-conviction whale behavior with reasons.
**Evidence:** post #9164 — *"more like a "fraud radar" for prediction markets."*

### 3.2 Wallet watchlists with configurable alerts (Discord/Telegram/email)
**Why:** Users asked for a way to set up alerts on wallets instead of manual checking, and for Discord/Telegram notifications.

### 3.3 Noise filtering: default to non-sports + minimum impact thresholds
**Why:** Key pain is “too noisy,” and users specifically want filters to remove sports bets and low-impact events.
**Evidence:** post #9144 — *"every non-sports trade over $10k"*

### 3.4 Zero/near-zero real-time monitoring of whale wallet movements & trades
**Why:** The core ask is live monitoring; users also cite the need for real-time whale-trade monitoring.

### 3.5 Suspicious-pattern detection (fresh wallets, clusters, oversized trades, perfect timing)
**Why:** Users demanded explicit flags for fresh wallets, oversized trades, clusters pre-resolution, and perfect-timing behavior.
**Evidence:** post #9164 — *"Fresh wallets with no history."*

### 3.6 Open-trades inspection for tracked whales (and resolution-aware stats)
**Why:** Users want a way to check open trades of whales and avoid misleading win-rate for unresolved positions.

### 3.7 Filtered whale leaderboard/list by historical accuracy & stability (risk-adjusted, not raw PnL)
**Why:** Users want a better way to track whales plus a filtered list based on hit rate/quality—not raw profit and not zombie/unresolved noise.
**Evidence:** post #9161 — *"only if multiple whales align"*

### 3.8 Backtesting tool for whale-following strategies + consensus-based entry logic
**Why:** Backtesting is a must-have workflow, and users want copy only if multiple whales align.

### 3.9 Paper trading / sandbox mode for whale copy-trading (no execution risk)
**Why:** Users explicitly requested paper trading so they can test copy-trading safely.

### 3.10 Exit/unwind alerts when large wallets reduce exposure
**Why:** Users asked for alerts when huge wallets unwind positions.
**Evidence:** post #9153 — *"Have to figure out an alert when huge wallets escape also"*

### 3.11 Cross-platform scanning: Polymarket + Kalshi + signal normalization
**Why:** Users want scanning across Polymarket and Kalshi and cross-venue interpretation to avoid venue-spread false alpha.

### 3.12 Backtest/alerts framework must include explainable “trade-level” scoring (0-100) and thresholding (e.g., 70+)
**Why:** Users demanded trade scoring and to only flag high-score trades (70+), to reduce noise.
**Evidence:** post #9140 — *"We rank every trade 0-100"*

## 4. Use cases & user stories
Build a web SaaS “whale intelligence terminal” MVP that monitors Polymarket whale wallet activity in near real time, decodes trades, assigns an explainable 0–100 fraud/radar score, filters out sports/low-impact activity by default, and sends immediate Discord/Telegram alerts. Provide watchlists and an alert inbox with trade-level context plus open-trade inspection (resolution-aware where possible)

### Use cases
**4.1 Retail follows a high-conviction whale entry in real time**
A retail trader maintains a watchlist of 10 wallets inside the terminal. When a watched wallet opens a large non-sports position, the fraud-radar scores the trade 0–100 and only surfaces it if it clears the user’s default threshold (e.g., 70+). The trader sees what pattern triggered the alert (fresh wallet + oversized trade + cluster) and how large the odds impact is, then decides whether to mirror the exposure in paper-sandbox before considering live copy.

**4.2 Validate a whale-following strategy with realistic resolution-aware backtests**
A systematic user wants to know whether copying the top historical wallets works once you exclude unresolved positions and zombie/lucky variance. They run a backtest that filters to high-stability wallets (minimum trade count, quality-adjusted scoring) and enforces a consensus entry rule (copy only if multiple aligned whales hit the same side within a short window). The results show strategy performance under noise filtering (non-sports, minimum impact), improving decision quality before allocating capital.

### User stories
- **As a Active trader**, I want real-time alerts for tracked wallet trades, filtered to high-impact non-sports activity with a 0–100 trade score, *so that* I can react before prices move and avoid noise like sports bets or tiny fills.
- **As a Strategy builder**, I want a backtesting tool that supports whale-following strategies and resolution-aware accuracy (excluding unresolved/open positions), *so that* I can measure whether copy-trading works on real outcomes, not misleading leaderboards.

## 5. Pages & form factor
**Form factor:** Real-time Web SaaS (with push alerts via Discord/Telegram/email) for whale intelligence
**Why:** Users want zero/near-zero monitoring, configurable noise filtering, and explainable “fraud radar” scoring with leaderboard/backtesting. A Web SaaS centralizes wallet/market watchlists, alert routing, and backtest tools while supporting low-latency alert delivery through external channels.

### Pages
**5.1 Dashboard**
Primary landing page for the current scan state plus a live, filtered “radar” feed of whale trade signals.
Key elements:
- Live Whale Radar feed (ranked by fraud radar score)
- Filters summary chips (non-sports default, min impact/size)
- Scan status + ingestion latency indicator
- Quick links to top markets/venues involved
- Signal detail preview (score + top reasons)

**5.2 Alert Inbox**
Inbox for delivered alerts with full context and post-resolution-aware stats when available.
Key elements:
- Chronological alert list with read/unread
- Alert status timeline (triggered → resolved/updated)
- Per-alert explanation panel (insider/fraud score reasons)
- Actions: open-trades inspection, copy event link
- Export/share (CSV / permalink)

**5.3 Whale Leaderboard**
Ranked list of tracked wallets using historical accuracy and stability (risk-adjusted), not raw PnL.
Key elements:
- Wallet list sortable by risk-adjusted accuracy/stability
- Hit-rate / sample size / rolling window controls
- Consensus alignment stats (when multiple whales align)
- Category filters (market type, sports vs non-sports)
- Wallet profile drill-in entry point

**5.4 Wallet Watchlists**
Manage specific wallets and notification preferences; configure score thresholds and alert routing.
Key elements:
- Watchlist builder (follow/unfollow wallets)
- Threshold controls (e.g., fraud score 70+ default)
- Delivery settings (Discord/Telegram/email)
- Event types toggles (buys/sells/exit/unwind/cluster)
- Cross-venue tracking toggle (Polymarket vs Kalshi)

**5.5 Market Radar**
Cross-market/venue view showing which markets whales are piling into and the trade impact on odds.
Key elements:
- Market list ranked by sudden-accumulation + odds impact
- Odds delta chart/summary per market
- Signal feed scoped to venue(s)
- Explainable “why now” indicators (timing/cluster/fresh wallet inputs)
- Drill-down to related whale alerts

**5.6 Backtesting Studio**
Backtest whale-following strategies with consensus-based entry logic and risk-adjusted evaluation.
Key elements:
- Strategy builder (wallet set, thresholds, time windows)
- Consensus entry logic configuration
- Results: equity curve, hit rate, drawdown, sample size gates
- Filter presets: non-sports, min size, minimum trades (e.g., 200+)
- Exportable report

**5.7 Open Trades Inspector**
Inspect what tracked whales currently have open and how that maps to resolution-aware stats.
Key elements:
- Tracked-wallet open positions table
- Market status and resolution-aware flags
- Position size vs market/impact context
- Unwind/exit signal indicators
- Per-trade “fraud radar” score link

**5.8 API & Integrations**
Self-serve API key portal, webhook endpoints, and integration documentation (stable under volatility).
Key elements:
- API key generation + rotation
- Webhook/test endpoint for alert delivery
- Rate limits + reliability/volatility guarantees
- Docs entry point and examples
- Integration status (health/readiness)

### Key functions
- **Rank trade with fraud radar score** *[on: Dashboard]*
  - Trigger: Whale trade event ingested and matched to market/filters
  - Assigns a trade-level 0-100 fraud/risk intelligence score and stores explainable contributing factors for UI tooltips.
- **Apply default noise filters to alerts** *[on: Dashboard]*
  - Trigger: User opens app or receives a new alert payload
  - Filters out low-signal and sports activity by default and enforces minimum size/impact thresholds before surfacing the alert.
- **Deliver Discord whale trade alerts** *[on: Wallet Watchlists]*
  - Trigger: A new high-confidence alert passes threshold for any followed wallet
  - Posts an immediate Discord notification for live whale trades with score + key reasons.
- **Add wallet to watchlist and set alert rules** *[on: Wallet Watchlists]*
  - Trigger: User submits a wallet address or selects from saved wallets
  - Creates/updates a watchlist entry with per-wallet alert preferences (score threshold, event types, venues).
- **Detect fresh-wallet and clustered timing fraud patterns** *[on: Dashboard]*
  - Trigger: Trade sequence arrives (timing, wallet age, and co-movement analysis window)
  - Flags suspicious behavior such as fresh wallets (no history) and clusters of new wallets betting the same direction before resolution.
- **Detect oversized trades relative to market size** *[on: Dashboard]*
  - Trigger: A trade event is evaluated against market liquidity/size context
  - Identifies and scores trades that are disproportionately large versus the market to help users avoid noisy signals.
- **Show open-trades inspection for tracked whales** *[on: Open Trades Inspector]*
  - Trigger: User opens an alert or clicks a wallet from leaderboard/watchlist
  - Displays current open positions for tracked wallets with resolution-aware context and links back to triggering fraud/radar scores.
- **Trigger exit/unwind alerts for tracked wallets** *[on: Alert Inbox]*
  - Trigger: Tracked wallet reduces exposure sharply or closes positions unexpectedly
  - Sends an alert when large wallets unwind/exit so users can react rather than relying only on entry signals.
- **Compute cross-venue alpha signals (Polymarket vs Kalshi)** *[on: Market Radar]*
  - Trigger: A matched whale move appears on one or more venues
  - Compares odds movements across venues to infer whether the move likely reflects true alpha or venue-specific spread effects.
- **Backtest consensus-based whale-follow entry rules** *[on: Backtesting Studio]*
  - Trigger: User runs a backtest configuration
  - Simulates copying only when multiple independently selected whales align within a configured time window.
- **Rank wallets by risk-adjusted historical accuracy and stability** *[on: Whale Leaderboard]*
  - Trigger: Leaderboard refresh after enough new trades or parameter changes
  - Shows a filtered leaderboard based on historical accuracy/stability with minimum trade gates and excludes unresolved distortions.

### UX details
- **Trade alert list:** Default filter shows only high-confidence alerts (e.g., fraud score threshold such as 70+).
- **Noise filtering (market-type):** Use non-sports-first presets and require minimum trade size (e.g., > $10k) before showing alerts by default.
- **Scoring transparency:** Expose trade-level score factors in tooltips so users can understand why something was flagged (not just a number).
- **Leaderboard evaluation:** Use minimum-trades gates and risk-adjusted scoring (not raw profit), and handle unresolved positions explicitly.
- **Alert explanation panel:** Include “why now” contributing signals such as fresh-wallet behavior, oversized trades, and perfect timing on niche events.
- **Integration UX:** Provide self-serve API key access rather than requiring community/Discord discovery, with explicit docs entry points.

## 6. Monetization
**Model:** subscription

### Suggested pricing tiers
**Starter** — $24/month — *Solo trader, just getting started*
- Watch 10 wallets (alerts + trade feed)
- Trade scoring + non-sports/size filtering presets
- Email alerts + daily summary
- Paper-sandbox mode for one strategy

**Pro** — $49/month — *Active trader, multiple positions*
- Unlimited wallets and advanced thresholds (e.g., 70+)
- Real-time Discord + Telegram alerts
- Backtesting + consensus-based entry rules
- Cross-venue Polymarket/Kalshi whale scanner

**Team+API** — $199/month — *Multi-trader team / fund operator*
- Team seats + shared watchlists
- API access for wallet trade events and scored signals
- Exit/unwind alerts for tracked wallets
- Priority support and model explainability exports

## 7. Competitors to beat
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| swarmintellect.com | It surfaces whale positions and live updates, but users still note confusion, divergences, and the need for interpretation and better signal handling. | - | - |
| Backtest top whales by historical performance | Backtests need careful filtering because raw profit and win rate can be distorted by zombie orders and lucky streaks. | Not specified | - |
| Follow public Polymarket whale accounts/behavior | Execution lag can erase the edge, and commenters warn whale bets may be hedges or specialized in only certain categories. | Free public data; no explicit price mentioned | - |
| tracking whales / right wallets | Users say whale tracking is not enough to catch insiders, and the best wallets may hide with multiple accounts or decoys. | not mentioned | - |
| Use on-chain/Polygonscan monitoring to watch whale flow | By the time activity is visible and acted upon, prices may already have moved several cents. | Not specified | - |
| @sightwhale_bot | It promises zero-delay whale alerts, but the post itself argues retail is already late if they rely on leaderboard visibility; Pro/Elite priority delivery also suggests uneven access. | free basic alerts; Pro and Elite priority delivery | - |
| alerts on wallets | Manual tracking is described as brutal and too time-consuming; users want a better way. | not mentioned | - |
| Arbitix (arbitix.io) | Built to compare Kalshi and Polymarket, but the author explicitly says it is still early and seeks feedback; another commenter suggests a competitor already exists and questions the 10-15% gap claim. | free to use | - |

## 8. Distribution
- reddit
- x_twitter
- discord
- seo
- Top subreddits to launch in: r/CryptoCurrency, r/polymarket, r/CryptoMarkets, r/predictionmarkets, r/gachagaming, r/polyman, r/heartopia, r/ai_trading, r/Uma_xyz, r/TNOmod

## 9. Users & roles
**Primary persona:** Prediction-market active trader

**Roles:**
- **Subscriber user** — Create watchlists, set score/impact filters, receive alerts via dashboard/Discord/Telegram, and view trade/open-trade context.

## 10. Data model & integrations
- (no data model extracted)

## 11. States
**Empty state:** User sees an empty radar feed and prompts to add wallets and set a 70+ score threshold.
**Error state:** If trade decoding or scoring fails, the user sees a banner with the affected venue and continues monitoring other events.

## 12. Analytics & metrics
- (not synthesized for this report)

## 13. Risks & open questions
- (no risks/questions extracted)

## 14. Post-launch
- See https://gapforapp.com/reports/whale-tracking-is-too-noisy-and-late for DM-able hot leads (workarounds × buying intent).
- See https://gapforapp.com/reports/whale-tracking-is-too-noisy-and-late for verified key quotes you can use as landing copy.

## 15. Suggested build order (3-week MVP cut)
- Week 1: §3 must-haves + §5 page 1.
- Week 2: §5 remaining pages + auth/persistence if needed.
- Week 3: §6 monetization wiring + analytics + launch checklist.

## 16. Setup hints (your stack overrides these)
- `pnpm create next-app . --typescript --tailwind --app`
- `npx shadcn@latest init`
- The agent SHOULD ask the user before committing to a stack.

## 17. How to use this file
You're an AI coding agent reading this in AGENTS.md. Your job:
1. Confirm the stack with the user (their preferences override this file).
2. Scaffold an MVP covering §3 + §5 page-1 first.
3. Defer §6 (monetization) and §14 (post-launch) until §3 ships and works.
4. Re-fetch the live PRD anytime via:
   curl https://painfinder-api.fly.dev/api/public/reports/whale-tracking-is-too-noisy-and-late/export.json?size=compact

## 18. Verbatim key quotes (top 10)
> "It's not a bet. It's a HYSA"  
> — Uncategorized, post #9169

> "It’s the sports betting biz they call this picking up pennies in front of a steam roller"  
> — Uncategorized, post #9169

> "Everyone on Polymarket says “follow the whales”, but no one actually tells you how to do it without quitting your job to stare at order books 12 hours a day."  
> — Latency, post #9140

> "By the time a whale bet hits the Polymarket leaderboard, it’s already too late to get a good entry."  
> — Latency, post #9140

> "The real problem with whale-following is latency."  
> — Latency, post #9140

> "Not all whales are winners."  
> — Whale quality, post #9140

> "We rank every trade 0-100, and only flag trades from wallets with a score of 70+"  
> — Uncategorized, post #9140

> "Polymarket’s data is all public, it just isn’t easy to visualize or filter out all the sports bets and low-impact events."  
> — Uncategorized, post #9144

> "a website that tracks large whale trades and potentially suspicious activity across Polymarket in real time."  
> — Manipulation, post #9144

> "A calculated “insider score” (might suggest someone knows something)"  
> — Uncategorized, post #9144

## 19. Manual workarounds users cobble together (top 15)
- (none extracted yet — see live report)

## 20. "I would pay for…" quotes (top 10)
- (none extracted yet — see live report)

## 21. Hot leads summary
- (none extracted yet — see live report)

## 22. Full competitor list (top 10)
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| swarmintellect.com | It surfaces whale positions and live updates, but users still note confusion, divergences, and the need for interpretation and better signal handling. | - | - |
| Backtest top whales by historical performance | Backtests need careful filtering because raw profit and win rate can be distorted by zombie orders and lucky streaks. | Not specified | - |
| Follow public Polymarket whale accounts/behavior | Execution lag can erase the edge, and commenters warn whale bets may be hedges or specialized in only certain categories. | Free public data; no explicit price mentioned | - |
| tracking whales / right wallets | Users say whale tracking is not enough to catch insiders, and the best wallets may hide with multiple accounts or decoys. | not mentioned | - |
| Use on-chain/Polygonscan monitoring to watch whale flow | By the time activity is visible and acted upon, prices may already have moved several cents. | Not specified | - |
| @sightwhale_bot | It promises zero-delay whale alerts, but the post itself argues retail is already late if they rely on leaderboard visibility; Pro/Elite priority delivery also suggests uneven access. | free basic alerts; Pro and Elite priority delivery | - |
| alerts on wallets | Manual tracking is described as brutal and too time-consuming; users want a better way. | not mentioned | - |
| Arbitix (arbitix.io) | Built to compare Kalshi and Polymarket, but the author explicitly says it is still early and seeks feedback; another commenter suggests a competitor already exists and questions the 10-15% gap claim. | free to use | - |
| Arkham Intel | Suggested as a starting point for wallet tracking, but again framed as requiring manual wallet-level work. | - | - |
| Beansapp.com | Promoted as low-friction DeFi yield access, but only one comment endorses it and no tradeoffs are discussed. | 14% APY right now | - |

## 23. Where this conversation lives (top subreddits)
- r/CryptoCurrency (17 posts)
- r/polymarket (15 posts)
- r/CryptoMarkets (15 posts)
- r/predictionmarkets (11 posts)
- r/gachagaming (2 posts)
- r/polyman (1 posts)
- r/heartopia (1 posts)
- r/ai_trading (1 posts)
- r/Uma_xyz (1 posts)
- r/TNOmod (1 posts)