Pulse

What it is for

Not every winner is a brand-new token. Plenty traded quietly for days before they moved. Launch alerts cannot see those by definition — the token was not new when it started running.

Pulse scans tokens already trading and fires when several momentum signals line up on the same token at the same time.

What it reads

• Volume surge — volume against the token's own recent baseline, not an absolute number
• Buy pressure — the buy-to-sell ratio tilting hard toward buyers
• Holder velocity — wallets arriving faster than price is moving, which is what accumulation looks like before a chart shows it
• Sustainment — confirmation the move has legs rather than one wick
• Convergence — several independent signals on one token simultaneously, the strongest configuration
• Catalyst — whether a real cluster of accounts is forming, or it is a random pump

Its current limits, stated plainly

Base only. The scanner does not run on Robinhood Chain.

The same admission gate applies. A token without a paid profile is skipped, exactly as with Launch. Most of what the scanner sees is dropped there.

It fires rarely. In one measured day: 62 scan cycles, 12 pattern hits, one alert that survived every gate. Whether that is admirable precision or a mis-tuned gate is not something we can claim yet — the sample is far too small.

Its thresholds are unvalidated. They were set from a prior generation of the system and have not been re-measured against current data. Publishing tuned constants as if they were established is exactly the failure this documentation is built to avoid.

Why it is not shipped

Because the honest answer to "how well does it work?" is we do not know yet, and shipping an alert stream we cannot characterise would undo the thing the rest of the product is for.

Every Pulse alert will run the same safety stack as Launch. When it ships, this page will say what it does instead of what it is intended to do.

➡️ See also: Launch alerts · Coverage