Skip to main content

Current Limitations

Signals fire regardless of wallet status, but trade execution will fail without a funded Polygon wallet and valid CLOB API keys configured. Signals are still delivered and can be acted on manually on Polymarket.com.
Win/loss attribution in whale profiles requires market resolution data from the Gamma API. This is not always available at signal time — win rate in whale analysis only populates when the API returns profit fields for the wallet.
Whale category classification uses fixed keyword matching, not semantic understanding. Edge cases exist for ambiguously worded market questions that don’t contain recognisable keywords.
All data is stored in a local SQLite file. This is not suitable for multi-user horizontal scaling without migration to PostgreSQL.

Roadmap

📈 Signal Backtesting

Replay historical market data to compute per-pattern win rates. Know your edge before going live.

🔗 Market Correlation Engine

Surface related markets when a signal fires — trade the same event across multiple correlated questions.

✅ Resolution Tracking

Automatically update signal_history.resolved when markets close, enabling accurate per-pattern win rate calculations.

🔀 Multi-Leg Strategies

Combine two correlated markets in a single hedged trade to reduce directional risk.

🔔 Push Notification Webhooks

Outbound HTTP hooks for integrating signals with external systems, dashboards, or custom notification pipelines.

🐘 PostgreSQL Migration

Multi-user horizontal scaling support via PostgreSQL backend as an alternative to SQLite.

ApeIndex · v2.0 · March 2026