Learn how HyperStats public alerts work on Hyperliquid, what gets filtered, where alerts are published, and how to use daily recaps correctly.
How to use HyperStats public alerts, Telegram/X alert channels, and daily recap posts without confusing filtered signal with the raw feed.
HyperStats public alerts are meant to be high-signal, not complete. They filter the raw feed down to larger opens, meaningful exits, liquidations, and recap-worthy market events that are actually useful to read and share.
The right way to use the alerts product is simple: treat the alert as the trigger, then move into the wallet page, Live Activity, or token terminal for the full context.
HyperStats publishes filtered public alerts across the site, Telegram, and X. Those alerts cover meaningful opens, adds, exits, and liquidations instead of every tiny adjustment from the raw event stream.
The product also generates a daily recap that highlights the biggest long, biggest short, best close, worst close, biggest liquidation, top trader, and global market bias for the prior UTC day.
Public alerts apply size floors and additional anti-noise rules so the channel does not fill with low-value events. That means the alerts product is intentionally stricter than Live Activity and far stricter than raw tracked events.
This is why you should not treat the public alert stream as a complete audit log. It is a curated market-intelligence layer designed for speed and readability.
When a public alert matters, the next step is almost always one of three pages: the wallet page for trader history, Live Activity for surrounding flow, or token terminal for current market structure.
The alert itself gives you the trigger. The HyperStats product pages give you the reason the move matters or the evidence that it does not.
No. Public alerts are filtered on purpose. They are a high-signal public layer, not a complete event archive.
The daily recap summarizes the biggest long, biggest short, best close, worst close, biggest liquidation, top trader, and global bias for the previous UTC day.