Flashpoint
Watch. Confirm. Execute.
Under the hood it's one pipeline: raw market streams in, five scored conditions, and a window that only opens when the stack agrees.
The trigger stack
Every Solana mover runs through the same pipeline. Live pump.fun and DEX data comes in, each condition is scored against that token's own baseline, and the stack only counts when the pieces confirm together — on one token, at the same time.
Why a stack, not a signal
Any single reading fires constantly — volume spikes on a shill, pools are always thin, buys lean on every green minute. Alone, each one is noise. Flashpoint treats them as one structure: the same conditions, on the same token, inside the same minutes. That coincidence is rare, and it's the part worth alerting on.
From alert to action
When the window opens you get the readings that triggered it — each score, the direction of flow, and how hard the pool is turning — not a bare "buy" arrow, and a link straight to the chart. Flashpoint flags conditions. The decision stays yours.
See it live
The radar runs in the terminal. A window looks like this:
$FLASH is early access: hold it and every window fires to you the instant the stack confirms; without it you're on a 90-second delay. The contract address drops on @useflashpoint.