← Back

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 covered market runs through the same pipeline. Streams come in, each condition is scored against that ticker's own baseline, and the stack only counts when the pieces confirm together — on one ticker, at the same time.

trades ─┐ depth ─┤ ┌─ volume expansion ▸ 0-100 OI ─┼─▶ per ticker ──┼─ OI build-up ▸ 0-100 ranks ─┘ ├─ liquidity thinning ▸ 0-100 ├─ aggressive flow ▸ 0-100 └─ attention ▸ 0-100 │ stack confirms (N of 5) │ ▼ ◆ EXECUTION WINDOW OPEN

Why a stack, not a signal

Any single reading fires constantly — volume spikes on news, books thin overnight, flow leans on every sweep. Alone, each one is noise. Flashpoint treats them as one structure: the same conditions, on the same ticker, 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 thin the book is — not a bare "buy" arrow. Flashpoint flags conditions. The decision stays yours.

See it live

The engine runs in the terminal. A typical session:

# watch one market flashpoint watch SOL # scan everything it covers, ranked by stack score flashpoint scan # what fired and why flashpoint why SOL ▸ volume 92 expanding vs baseline ▸ OI 81 building, price flat ▸ depth 74 thinning both sides ▸ flow 88 takers one-sided ▸ attention 79 compressing into SOL ◆ window open — 4 of 5 confirmed

The full live terminal is token-gated: hold the Flashpoint token on Solana and every signal streams to you as it fires. Launch is announced on @useflashpoint.

Ask Flashpoint Look inside