Chapter 8
The Calls tracker
Memescope tells you what passed. Calls tells you what happened next. Every verified Strong Buy is logged once, automatically, and then tracked for as long as it lives — so the scanner is graded on its record, not its promises.
8.1What a call is
A call is a timestamped record that the scanner rated a token STRONG BUY with a passing security verdict, together with the market cap it was at that moment. Nothing about it is a recommendation and nothing about it is a position: it is the scanner putting its own answer on the record so it can be checked later.
Calls are private and per-account. The board is shared; your ledger is not. Two people watching the same Strong Buy each get their own call record, and the win rate on your screen is computed only from your own calls.
8.2How a call is created
On every scan, each signal is tested against four conditions:
- Tier is strong-buy — score 70 or above.
- Security verdict is a full pass, not warn and not pending. See Chapter 6.
- The token is not on your retired list (see 9.5).
- You do not already have a call for it.
All four true, and a call is created. If you already have one, no second call is ever made for the same token — if that existing call was dormant, the new signal wakes it and stamps it re-signalled instead.
The entry snapshot
At creation, and only at creation, the conditions at entry are frozen onto the record. Later refreshes never write them back, because every one of these values moves within minutes and a record that drifts cannot be used to grade anything:
| score | Vol/MC | liquidity | market cap |
| pair age | trending | bundler % | dev hold % |
| insider volume % | sniper hold % | bot flow % | holder count |
| smart-money count | top 10 % |
This snapshot is what makes the rule-by-rule backtest in Chapter 10 honest. It is the only way to ask “would filtering on this condition have helped?” without asking it of data that has since changed.
8.3The three buckets
The Calls board is three columns, and unlike Memescope's lanes they describe where a call is now, not how good it looked at entry. The dividing line is the current multiple against the entry market cap.
| Column | Current multiple | Means |
|---|---|---|
| Good Calls | above 1.6x | Trading meaningfully above where it was called. |
| Watch | 1.0x – 1.6x | Above entry, but not by much. The undecided middle. |
| Bad Calls | below 1.0x | Under the market cap it was called at. |
Each header carries the column's count and, when any of its calls ever reached 2x, a n paid ≥2x note. That note is the important one: a call sitting in Bad Calls having already run to 4x and come back is a completely different outcome from one that never moved, and the column alone cannot tell them apart.
Order inside a column
- Calls made in the last 10 minutes first — they carry a NEW badge and are the ones still actionable.
- Then by best post-call high, highest first.
- Then most recently called.
8.4Anatomy of a call card
Call card · Good Calls bucket
- 1
- Header. Name, $SYMBOL, chain pill, and the score the token had when it was called — not its score now. Then any status badges: NEW called within 10 minutes · dormant parked well below entry · re-signalled the scanner tiered it Strong Buy again · no live pair nothing answered on several consecutive refreshes.
On the right, the current multiple against entry, coloured by column. When a call has lost its pair this reads last seen instead of now. - 2
- Entry · Now · ATH after call. The three market caps that matter. The third is the highest the token reached after the call, as both a multiple and a dollar figure, and turns green once it clears 2x.
- 3
- Held-run bar. How much of the post-call gain is still standing. A call that ran to 2.31x and now sits at 2.14x has held 87% of its run. The bar is drawn only once there was a real run — an empty bar on a call that never moved would read as a loss it did not take.
- 4
- Peak notes. Appear only when a reading is being held back — a large jump waiting for a second confirming check, or a peak held pending verification and excluded from the win rate. Both are explained in Chapter 9.
- 5
- Timestamps. When the call was made, and when its market cap was last refreshed. A dormant call shows ·30m beside Now — it is deliberately on the slow sweep.
- 6
- Actions. Chart, Copy CA, and — on a paid plan — a dismiss control that removes the call and retires the token so a later scan will not log it again.
A round-tripped call also carries a yellow strip: Round-tripped — hit 4.10x ATH after call. It means the call paid and then gave it back. The win rate still counts it as a win, because the move it predicted did happen; what you did with it is a separate question.
8.5The win rail
Down the left of the board is a rail of win cards: every call whose post-call high reached 2x or better, sorted highest first. Calls at 10x or more get a heavier treatment. Toggle the rail with the Wins button on the toolbar; the choice is saved to your account.
Win card · the rail down the left of the Calls board
Each card shows the multiple, the symbol, the entry-to-ATH move, and where it is now — the “now” line turns green when the call is still holding above 1.6x. Click a card for the full detail panel, which adds:
- Run still held — the same figure as the bar on the card, as a percentage.
- Tags for the chain, the score at entry, and any of Round-tripped, Dormant, No live pair.
- When it was called, when it was re-signalled, when the market cap was last checked.
- The full contract address, a chart link, and Copy CA.
8.6The stats strip
| Stat | What it counts |
|---|---|
| Calls | How many calls match your current filters. A +n retired note appears when calls have been evicted past the retention cap — they are gone from the board but still counted below (see 9.4). |
| Win rate ≥2.0x | Share of calls whose post-call high reached 2x, with the raw fraction beside it. 50%+ green, 25–49% yellow, under 25% red. |
| Avg ATH | Mean post-call high across every call in view, as a multiple of entry. |
| Best | The single highest post-call multiple, and its symbol. |
8.7Filters, search and export
Chain and search
The chain segment narrows to one chain; the search box matches name, symbol or address. Both are view filters over your own ledger.
The filter menu
Three groups, and the grouping is the point.
| Group | Filter | Keeps |
|---|---|---|
| Timing | Fresh under 2h | Calls made in the last two hours — the window where the entry is still actionable. |
| Entry rules | Trending at entry | Calls whose token was in the trending feed at the moment of the call. |
| Entry rules | Pair over 24h | Calls whose pair was already a day old at entry. |
| Entry rules | Bundles 15% or less | Calls with low bundled-wallet ownership at entry. |
| Outcome | Running | Calls currently at or above their entry market cap. |
| Outcome | Dormant | Calls parked well below their entry. |
Calls that predate the entry snapshot cannot prove they pass an entry rule, so they are excluded from those filters rather than assumed to pass. Running and Dormant are mutually exclusive; selecting one clears the other.
Refresh and export
- Refresh MCs Pro / Edge — re-prices exactly the calls currently shown by your filters and search, outside the normal sweep.
- CSV / JSON Edge — exports the ledger. The JSON form also carries the grading constants and the retired totals, so an external analysis grades calls the same way the app does.
AlgoLens user manualChapter 8 · The Calls tracker