Signal feed explorer

loading… Operations
runs every heuristic now: 30-90 seconds · any chain DexScreener lists; the chain is detected from the address
enter a token address

recent research

whentokenchainwhoscorewhat that band has done

plansone full plan, three terms; paying again adds days

pay from your walletpick a term, a chain and an asset; then one click in your wallet, or scan the QR

1 · term

2 · chain

3 · pay with

Each payment gets an exact amount (and, on Solana and for ETH, a reference) so the chain itself tells us it was yours, even from an exchange. That is what the order record below is.

my orders

whentermchainamountstatus
Everything New launches Momentum Entries Mine
momentum follows funder launches wallet buys wallet sells caller posts bots agree wallets consolidatingknown cabal wallets buyingNetwork buyingoff-launchpad launchbots leaving lineage catalysts entries undertow · buying undertow · scored wallets undertow · bots out undertow · liq added my exits targets positions closed outcomes newest first · tap for the token

entries: first pullback after a catalyst, buyers holdingthe actionable moment · judged at +6h / +24h from the entry price

whentokencatalystcat pxhighentryretracebuys/h+6h max+6h final+24h max+24h final

catalyst eventsa surviving token traded harder than its own normal, with outside evidence, before the price moves

How a catalyst is decided
  • Trading — two of three, against the token's own hourly baseline: volume at least 3x, buyers at least 2.5x, at least 1.2 buys per sell
  • Outside evidence — a scored wallet, a scored caller or bot consensus in the last hour
  • Not already moved — the price is not up more than 25% in the hour or 40% over its baseline, and liquidity is holding
  • Judged — on its own price log, 6 and 24 hours later
  • This is rule v2, used since 2026-09-10. Rows without a v2 tag used the old rule and are not counted in the tiles above.
whentokencomponentspool agepx vs refliq+6h max+6h final+24h max+24h final
on watch list
walletclassnhitsdeadprecrecordscore× baselead htok/daylastwatch
include bot-like
handlefollowersnhitsdeadprecscore× baselead hlast
funder (lineage key)launchesdeployersscoreddeadhit 3xverdictlast
fresh pool wallet bought dev not sold promo before pool has outcome

tokens

seentokenpool age liq @0px @2hpx last max 24hfinal 24hflags sel/botsx maxfol

the momentum strategyan established token bought harder than its own average, before its price has moved

How a momentum alert is decided

    firingsan established token bought harder than its own average, before the price moved

    whentokenchainage liqvol xbuyersbuys/sells 24h then+6h max+24h final

    reading the record…

    How to read this. Every alert is compared with a matched control -- a different token on the same chain, the same number of hours old, read at the same moment -- so a week when everything went up does not count as a finding. The bracket is a 90% interval: where the true value probably sits, given how few firings there are. And nothing is called proven under 30 scored firings that beat that control twice running, because at smaller numbers luck looks exactly like skill.

    what to act on, what to avoidthe two tables below, drawn

    Each row is a detector scored from its own firing against a matched control, with its 90% interval; colour is what the record says to do with it. The right-hand chart is the one that settles it: a ratio above 1.00 with an absolute below 1× means the detector picked tokens that lost less than their peers — real, and not the same as a trade that made money.

    what each alert has been worthbought at the close of the hour the alert fired, held, against a matched control: a different token on the same chain launched within three days, read at the same age. "sell@3x" takes 3x if it ever traded there, otherwise whatever was left, minus 4% round trip. The 90% interval is the honest part — if it spans 1.00 the sample cannot tell yet.

    alertchainn≥2xdeadmedian finalsell@3xcontrolvs control90% intervalverdict

    data integrityevery number in the log against the rules in Help → Data integrity: bounds on every column, cross-source agreement, derived numbers recomputed from their inputs

    checkrowsstatewhat it meansexamples

    what each exit has been worthsold at the close of the hour the exit fired, judged on what the token did over the next 24 h against ten matched controls at the same age. "vs control" is the geometric mean of the controls ÷ that of the exits (geometric, because one 50x runner in the draw must not decide the verdict): above 1.00 means the token fell further after this exit than a random token of that age, so heeding it beat holding. "≥2x after" is the rule's cost.

    exitchainnmedian 24h aftermean≤0.5x after≥2x aftercontrol mediancontrol geo meanvs control90% intervalverdict

    early entry: every rule tested

    How this works

    what each score band has been worthevery pooled token gets the quick score at its 2h snapshot; each band is bought at that hour and held. The bands are each other's controls. A band below 30 tokens is shown but the score label calls it uncalibrated.

    bandchainn≥2x≥3xdeadmedian finalsell@3x

    chainseach chain is its own forward log with its own base rate; click a row to see its flag table below. "lite" = market, promotion, candles and outcomes only

    outcomes by flag (fresh promoted pools, vs this chain's base rate)

    market regime, hourlyrunner rate = share of 24h outcomes in the trailing day that reached 2x

    hour (UTC)promotedfreshoutcomes 24h≥2x≥3xdeadnative

    detail

    select a signal, wallet, caller, or token