Chapter 3
The signal card
Every card on the board carries the same nine rows in the same order. This chapter names all of them — what each measures, where the value comes from, and the threshold that decides its colour.
3.1Anatomy of a card
The numbers in the margin key to the list below.
Signal card · full density
- 1
- Header. Token image (or the first two letters of the symbol), name, $SYMBOL, and a chain pill in that chain's colour — then the context pills, then the score.
TRENDING the token is in the ranked volume feed for its chain · CALLED n.nnx you are already tracking it, and the multiple is against the market cap you called it at (hover for that figure) · PINNED you pinned it, so it stays on the board and jumps the verification queue.
On the right, the 0–100 score coloured by lane, the change since the previous scan (▲ 6, ▼ 4, — 0, or nothing at all on a token's first scan), and the lane name beneath. - 2
- Composition bar. What the score is made of — section 3.2.
- 3
- Metrics. Market cap, liquidity, Vol/MC, age — section 3.3.
- 4
- Momentum and buy pressure. Price change over 5m / 1h / 6h / 24h, and the buy-versus-sell split of the last hour — section 3.4.
- 5
- ATH bar. Only on tokens you have called. Current market cap against the post-call high — section 3.6.
- 6
- Risk strip. LP · Authority · Holders · Real — section 3.5.
- 7
- Band hit rate. Only on cards scoring 70+, on a paid plan. How calls in this score band have actually resolved — section 3.6.
- 8
- Actions. Chart and Copy CA always; Bubbles, Explorer, Refresh and Pin appear on hover or keyboard focus, on the row below — section 3.7.
- 9
- Why this score. Expands the full list of matched rules as chips — section 3.7.
The left edge of every card is a 3px stripe in its lane colour, so a card stays identifiable after you have scrolled past the lane header. Hovering a card highlights its border and reveals the second action row.
3.2The score and its composition bar
The score is a single 0–100 figure, and the bar under it is what that figure is made of. The range has a floor and a ceiling: a catastrophic token shows 0 rather than a negative number, so two 0s are not equally bad underneath. What the number measures is Chapter 5.
The four segments
| Segment | Colour | What feeds it |
|---|---|---|
| Market | Blue | Whether the token is tradeable at all — liquidity depth, market cap, pair age. |
| Flow | Green | Volume turnover (Vol/MC), buy-versus-sell pressure, notable wallets. |
| Momentum | Yellow | Price movement across the available time windows. |
| Penalty | Red | Everything working against it: bot flags, holder concentration, contract problems, volume that does not look real. |
Segment widths are proportional, so the bar answers “what is this score made of” at a glance. Two tokens at 74 can read completely differently: one carrying a wide green Flow segment is being bought; one built almost entirely from a blue Market segment is a well-shaped token that nobody is trading yet.
A visible red segment means the risk side of the card netted out against it. When the risk side is a net positive instead — a renounced authority and locked liquidity both count in the token's favour — there is no red band at all and that credit is folded into the rest of the bar.
3.3The four metrics
| Metric | Meaning | How to read it |
|---|---|---|
| MC | Market cap (fully diluted where that is the reliable reading). | Very small is a token with no real float; very large is a move that has already happened. The board is built around the range in between. |
| Liq | Dollars in the pool. Sets how much size the token can absorb and how violent the exit is. | Thin liquidity is the reason a good entry becomes a bad exit. Size the position to the pool, not to the score. |
| Vol/MC | 24h volume divided by market cap. Turnover. The most informative single number on the card. | ≥1.0x green · ≥0.8x yellow · below red |
| Age | Time since the trading pair was created. | Minutes old means most checks have nothing to work with yet; days old only stays interesting while turnover holds up. |
Why Vol/MC carries the most weight. A token at 1.0x turned over its entire market cap in a day: real people are trading it. Below 0.8x the chart is mostly decoration — you can get in, but the bid that gets you out has to show up later, and often does not. The tile is coloured on exactly that reading, and it is the one number on the card worth checking before the score itself.
3.4Momentum and buy pressure
Momentum strip
Four bars — 5m, 1h, 6h, 24h — each showing that window's price change. Heights are scaled against the largest absolute move on that card, so the shape is a within-token comparison, not a cross-token one. Hover any bar for the exact percentage.
- Green — up more than 0.5%
- Red — down more than 0.5%
- Grey — flat, inside ±0.5%
The useful pattern is the staircase: 24h and 6h modest, 1h and 5m green. That is a token waking up. The inverse — a huge 24h bar and a red 5m — is a token you are late to.
Buy pressure
The bar beside it splits the last hour's transactions: green is the buy share, the red ground behind it is sells. The percentage below is the buy share, and its colour switches at ≥55% green, 45–55% yellow, under 45% red. Counts sit either side.
Read the counts as well as the ratio. 6 buys vs 3 sells is 67% and means nothing; 318 buys vs 187 sells is the same ratio and means a crowd.
3.5The risk strip
Four tiles, always in the same order, each an independent verification. These are the checks that decide whether a high score is allowed into Strong Buy at all.
| Tile | The question it asks | The value it prints |
|---|---|---|
| LP | How much of the liquidity pool is locked or burned? | 100% — the share that cannot be pulled. Green when effectively all of it is locked, red when most of it is not. |
| Authority | Can the deployer still mint, freeze, or block your sell? | renounced green · not renounced is a warning · a blacklist or cannot-sell result is red and terminal. |
| Holders | What share do the top ten wallets hold? | top10 38% — the lower the better; the tile turns as concentration climbs. |
| Real | Does the candle history look like human trading or a bot loop? | chart clean · n flags · run check when nobody has looked yet. |
The four tile states
- ● pass — solid green dot, green value, green border.
- ◆ warn — yellow diamond. The check answered and the answer is uncomfortable.
- ■ fail — red square. Treat as terminal.
- ○ unknown — dashed outline, grey value. No answer yet. Nothing has been verified and nothing has been ruled out.
Running the Real check by hand
The Real tile is the one tile you can trigger yourself. When it reads run check it is a button: pressing it pulls the token's candle history and runs the four bot-pattern detectors in Chapter 7. It needs a pool address and a signed-in account. Results:
- chart clean — enough history was available to judge, and nothing bot-shaped was found in it.
- n flags — patterns found. Anything found is charged against the card straight away and can drop it into a lower lane on the spot.
- retry check — a previous check ran but there were not enough candles to judge.
The strongest cards on the board get a chart check automatically each scan, so a high-scoring card usually arrives with this tile already answered.
3.6ATH bar and band hit rate
These two rows appear only under specific conditions, and both connect Memescope to your Calls ledger.
The ATH bar
Shown only on a token you have already called, once it has a recorded post-call high. The fill is the current market cap as a share of that high, and the label spells out the distance: 53% below ATH, or At ATH within 3%.
- Red fill — within 35% of its post-call high. The card is extended.
- Yellow fill — 35–70% below.
- Green fill — more than 70% below its high.
This is a position-context row, not a signal. It answers “where in this call's own range am I looking?” — which is exactly the question a score cannot answer, because the score has no idea you are already in.
Band hit rate
The dashed-rule line under the risk strip, shown on cards scoring 70+ at full density on a paid plan. It reports how calls in this score band have actually resolved:
Band 80–85: 44% hit 2x across 18 calls
- Measured only over mature, server-recorded calls — not open positions, not guesses.
- A band needs at least 8 resolved calls before it reports. Until then the line reads not enough history yet (3/8 calls).
- The percentage is coloured: 50%+ green, 30–49% yellow, under 30% red.
This is the honesty line. It is the board grading itself with its own history, and it is the number to argue with when a score feels more confident than it has earned.
3.7Card actions and “Why this score”
| Action | Does | Requires |
|---|---|---|
| Chart | Opens the token's chart in a new tab. | — |
| Copy CA | Copies the contract address; the button confirms with ✓ Copied. | — |
| Bubbles | Opens the holder bubble map — the fastest visual read on wallet clustering. | hover |
| Explorer | Opens the chain explorer for the address. | hover |
| Refresh | Re-prices this one token and re-asks for its security verdict now, outside the scan cadence. | Pro / Edge |
| Pin | Keeps the token on the board across scans and moves it to the front of the verification queue. | signed in |
Chart and Copy CA are always visible. The other four appear when you hover the card or focus it with the keyboard, so the resting board stays readable.
Pinning, and why it matters
A pin is the strongest instruction you can give the scanner. A pinned token is checked before everything else and stays on the board even when the discovery feeds stop surfacing it. That is how you stop a token you actually care about from sitting on PENDING forever while fresher coins keep taking its place in the queue.
You can hold 20 pins. Pinning a 21st drops the oldest. A pin is an instruction to the scanner rather than a private bookmark, which is why there is a cap on it at all.
Why this score
The expander at the foot of the card lists every check that matched, as a coloured chip carrying the value the scanner actually saw — and, on the card itself, what that check was worth to this token. It is the audit trail behind the number:
The n rules counter beside the actions is the number of chips waiting inside. Chips are green for a passed rule, yellow for a warning, red for a failure, grey for a neutral observation. When a score surprises you, open this first — the answer is always here.
AlgoLens user manualChapter 3 · The signal card