Milestone alerts
A milestone alert posts when a coin’s live multiple over its first call crosses one of 11 fixed thresholds.
Thresholds
Thresholds are multiples of the first call’s market cap. There are 11, fixed in code — no per-bot or per-coin configuration exists.
Milestone thresholds
| # | Threshold |
|---|---|
| 1 | 2x |
| 2 | 3x |
| 3 | 4x |
| 4 | 5x |
| 5 | 10x |
| 6 | 20x |
| 7 | 40x |
| 8 | 100x |
| 9 | 200x |
| 10 | 500x |
| 11 | 1000x |
The constant
CALLS_MULTIPLIERS = (2, 3, 4, 5, 10, 20, 40, 100, 200, 500, 1000)Poll tiers
A poll cycle runs every 15 seconds. On each cycle, every coin due for a check is pulled from DexScreener, in batches of 30 addresses per request.
What puts a coin in each tier
| Tier | Checked every | Condition |
|---|---|---|
| Hot | ~15 seconds (every cycle) | Called, or its market cap set a new all-time high, within the last 14 days |
| Cold | 600 seconds (10 minutes) | Everything else |
Limit
A coin stops being polled entirely after 5000 consecutive checks find no trading pair.
A multiplier is never announced twice
Each coin keeps a list of thresholds already announced. On every poll, the highest threshold the coin’s live multiple has crossed that is not already on that list is the one that gets announced.
When a jump crosses more than one threshold between two polls, every threshold at or below the highest crossed value is marked announced in that same pass, and only the highest is posted. A coin that jumps from below 2x straight to 12x posts a single 10x alert; 2x, 3x, 4x, and 5x are marked done without ever being posted.
The market cap used for this comparison is always derived from the first call’s reference (mcap0 × price ÷ price0), never re-sourced from a live market-cap figure directly. A change in which service reports the market cap cannot manufacture a crossing that did not happen.
Where alerts post
A milestone alert posts once into every chat the coin has been called in — not only the chat where the multiplier was crossed.
In a chat with no achievements forum topic, the alert replies to that chat’s own first call message, inside the same forum topic the call was made in, if any.
In a chat that has an achievements topic configured, through the group’s X automations topic routing, the alert is posted as a new message into that topic instead of replying to the call.
A posted milestone alert
| Input | Output |
|---|---|
| Text | 🏆 <a href="tg://user?id=777">@chris</a> called <b>$PEPE</b> at <b>$420M</b> — it just hit <b>2x</b> and is sitting at <b>$1.05B</b> |
| Below it | <code>0x6982508145454Ce325dDbE47a25d4ec3d2311933</code> |
@chris links to the caller’s Telegram profile. An anonymous-admin caller is shown bold instead of linked.
The alert reuses the same button rows as the original call and carries its own freshly generated graphic (chapter 3.5).