Practical overview
When it fits
Use it when you want a self-hosted, recurring or one-off scan of Polymarket activity and a rule-based alerting workflow rather than manual review alone.
Who it is for
- Polymarket users who want automated alerts about unusual trade and wallet patterns.
- Developers comfortable installing and configuring a Python command-line project.
Documented uses
- Monitor active Polymarket markets and recent trades for patterns such as fresh wallets, unusually large bets, concentrated activity and low-liquidity-market trades.
- Review scored suspicious activity through terminal alerts or optional Slack notifications.
- Run a one-time scan or inspect historical alert statistics and recent activity.
Requirements & limits
The repository is public and identifies the project as MIT-licensed. The README requires Python 3.10 or later.
- SQLite stores wallet behavior over time, so its local database is part of the monitoring design.
- Slack delivery is optional and requires a separately configured incoming webhook; console alerts are also described.
- The README describes asynchronous processing with aiohttp, SQLite, connection pooling, caching and retry handling.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and configure the monitoring bot
Prepare the Python CLI and configure its environment before starting a scan.
Before you start
- Python 3.10 or later
- The repository and its requirements.txt dependencies
Steps
Clone the repository and enter its project directory.
Create and activate a Python virtual environment.
Install dependencies with pip install -r requirements.txt.
Copy .env.example to .env and adjust settings such as the suspicious-score threshold and polling interval.
Expected outcome
The project dependencies are installed and a local environment file is configured for use.
Guide limitations
- The documented setup does not describe a successful run or guarantee compatibility.
- Slack notifications require separate Slack Incoming Webhooks setup and a webhook URL in the environment file.
Run a scan or inspect alert statistics
Use the documented CLI modes to request a single scan or display stored activity statistics.
Before you start
- A prepared Python environment with project dependencies installed
- The project environment configured as needed
Steps
Run python run.py --mode scan for a one-time scan.
Run python run.py --mode stats to display historical alert statistics and recent activity.
Expected outcome
The CLI is instructed to perform one scan or show its statistics, depending on the selected mode.
Guide limitations
- The README does not specify the Polymarket data-access configuration or detail the statistics output beyond historical alerts and recent activity.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- NickNaskida/polymarket-insider-bot · Official homepage title · retained in its source language