How Darkmen works: where every alert comes from
Updated
Darkmen is a Telegram bot and web feed that sends alerts about large Polymarket positions, whale-wallet transfers, exchange and on-chain anomalies. This page explains where every one of those alerts comes from, what it is built on, and what it does not claim.
Everything we read is public
Darkmen has no private data, no insider sources and no trading desk. Each feed reads a public API or a public data stream — the same data anyone can query — and checks it against a fixed rule. The table names the venues we watch; the data services we read them through are described rather than named, because the provider behind a feed can change. What we add is the watching: reading all of it, all the time, and sending one message when a rule is met.
| Feeds | What is read | Public source |
|---|---|---|
| Polymarket whales, sweeps, new markets, accumulation, resolution watch, rising and ranked wallets | Trades, markets and their event tags, holder lists, profit leaderboards | Polymarket Data API and Gamma API |
| Whale exchange flows, whale DeFi swaps, dormant wallets waking up | Transfers of a hand-picked list of wallets, priced in dollars | Public blockchain data (how Ethereum transactions work), Coinbase prices |
| New token pools and the scam check | New pools on Ethereum and Base; contract checks | Public DEX pool data, a public token-security API |
| BTC composite signal | Funding rate, open interest, momentum, hash rate, mempool fees, sentiment | Bybit, public Bitcoin network and market data, the Fear & Greed Index |
| DeFi hack alerts and market-moving news | Headlines | RSS feeds of Cointelegraph, Bitcoinist, Decrypt and CoinDesk |
| Macro countdown | The US economic-events calendar | Nasdaq |
| Stablecoin depeg | Spot prices | Coinbase |
| Stablecoin mint and burn | Issuance and redemption transfers | Public blockchain data |
| ETH gas spikes | The base fee of each block | Public Ethereum RPC nodes |
| Cross-exchange arbitrage | Order books | Bybit, KuCoin and OKX, through the open-source CCXT library |
| Volume spikes, open interest, funding divergence, trading halts | Candles, open interest, funding rates, contract statuses | Bybit, OKX, KuCoin, Binance |
| Big DEX swaps | Trades in the highest-volume pools | Public DEX pool data |
| Liquidation cascades | Forced orders | Binance's futures liquidation stream |
| Token unlocks | A schedule we maintain by hand from each project's published vesting | The projects' own documentation |
How a reading becomes an alert
- A rule. Every feed has one, and its numbers live in the code that applies it: a $20K floor on a Polymarket whale trade, $3M inside 60 seconds for a liquidation cascade, and so on. The thresholds printed on our module pages are read from those same constants when the page is built, so the page cannot quote a number the feed does not use.
- One message per event. When a reading meets the rule, the feed writes one event. A cooldown stops one cascade from becoming twenty messages.
- Your plan decides delivery, not the event. The web feed shows every alert from the modules your plan includes. In Telegram the Free and Basic plans have a daily allowance, spread through the day; Pro has none. What each plan includes is on the pricing page.
What an alert does not say
- It is not advice. An alert reports something that happened in public data. Nothing in it says what to buy, sell or hold.
- A whale is a size, not a person. Our whale feeds select on the size of one trade. They do not know who is behind a wallet, and do not claim anyone knew anything others did not.
- A leaderboard place is Polymarket's, not ours. When an alert shows a wallet's rank, it is the wallet's place on Polymarket's public profit board for that period. It is a record of past profit, not a forecast and not a win rate.
- We do not publish a win rate for any feed. Where we do show outcomes, we show all of them: the Corvus journal lists every alert that channel posted and how each market resolved, including the ones that went the other way.
The numbers on our pages
Every number we publish is one of two things. Either it is derived from our own records — computed from the rows the feeds wrote, over a window we state, with what it does not count stated next to it — or it is cited from named research, with the author or publisher, the date and a link. Figures in our articles are dated snapshots of our records: one liquidation cascade, minute by minute and what the Polymarket sports feed recorded over 55 days are two examples. Our own figures are what our pipelines recorded, not what any reader received.
When we get something wrong
We fix it, and where a published figure was wrong we say so on the page that carried it. One example: until 29 October 2026 the liquidation module priced coin-margined contracts as if each contract were a coin, which overstated the totals of many cascade alerts. The parser was corrected that day, and the liquidation article explains the error next to the figures it affected.
Contact
Questions about a feed, a figure or a source: support@darkmen.app.