Tiers & Thresholds
A mint becoming “watched” by News Pulse is not the same as it firing an alert.
The two stages
Section titled “The two stages”- Enrollment. As soon as a mint deploys with a twitter URL pointing to a watchlist tweet, the threshold watcher starts polling its market cap every ~15 seconds.
- Fire. When the mint’s MC crosses the $20,000 threshold, an alert is sent to all News Pulse subscribers.
Mints can sit in stage 1 (enrolled, not yet fired) for hours or never reach stage 2 if they don’t hit the threshold.
Why $20k
Section titled “Why $20k”The threshold has moved over time. Current setting:
| Date | Threshold | Reasoning |
|---|---|---|
| Pre-May 11 | $10,000 | Too noisy — most fires were micro-cap noise that never moved |
| May 11–12 | $16,000 | Reduced noise but still too many sub-$30k peaks |
| May 12+ | $20,000 | Current — based on backtest of news-driven launches |
Higher thresholds catch more meaningful momentum but miss earlier entries. Lower thresholds catch earlier but include more noise. $20k is the current sweet spot.
Late-entry filter (trader-side only)
Section titled “Late-entry filter (trader-side only)”Even if a mint crosses $20k and fires an alert, the automated trader bot (an internal Argus component, not user-controllable) will skip the buy if the MC has already moved past $35,000 by the time it processes the fire. This protects against chasing late.
Users still get the alert. The trader skip only affects internal auto-buying.
Multiple fires per mint
Section titled “Multiple fires per mint”The same mint can fire News Pulse multiple times in different sessions (e.g., once on its way up, again after a redeploy by the same creator with a different mint address). Each fire is per (mint, tier), so:
- A mint that hits $20k, dumps to $5k, and pumps back to $20k → fires once, not twice
- A mint that hits $20k, then dumps and the creator deploys a new copycat mint → fires once per new mint