polymarket-whales: what it does, how to run it, where it stops

What it does

Every CHECK_INTERVAL seconds (default 30) it fetches recent trades and compares each against MIN_TRADE_SIZE (default $500). A hit prints the market name, side, amount and price, coloured green for YES and red for NO. A deduplication step stops repeat alerts for the same trade.

• Exports to CSV or JSON
• Runs in the background under nohup; the README claims under 10MB of RAM
• Optional Telegram push via TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID, or a DISCORD_WEBHOOK_URL
• POLYMARKET_API_URL and HTTPS_PROXY settings for regions where the API is blocked

Setup

Clone the repository, pip install the requirements, edit .env or config.yaml, run python main.py. That is the whole install.

Venues and data

Polymarket only, via the public CLOB API. It is a polling loop, so the floor on latency is the interval you set, and it sees fills rather than order-book changes.

Where it falls short

The repository has a single day of commit history: created 2026-03-20, last push 2026-03-20. Nothing is wrong with the code today, but if Polymarket changes an endpoint nobody is on call.

It filters on trade size only. There is no wallet scoring, no watchlist and no consensus logic, so a $500 trade from a losing wallet and one from a top wallet look the same.

Polling at 30 seconds is slower than websocket-based feeds, and running it means a machine of yours stays on.

Who should use it

Traders who want a raw large-trade feed they control and can edit, or a starting point for their own alert bot. People who want scored wallets should look at the hosted trackers on this site.