Quick Scan vs Full Scan: Why Scores Can Differ

You may notice that the same token can show different scores depending on where you check it. That is not a bug. It is a deliberate product design choice.

BarryGuard has two analysis surfaces with different goals: Quick Scan for triage, and Full Scan for decisions.

What a Quick Scan optimizes for

Quick Scan is designed to be fast and cost-efficient so you can use it on lists and in lightweight contexts. It focuses on the signals that matter most for early triage: “is this likely dangerous right now?”

What a Full Scan optimizes for

Full Scan is built for a decision. It provides the complete breakdown and aims for maximum context and completeness on a single token page.

If you are about to buy, sell, or share a recommendation, use the full page in the Token Checker.

Why the score can differ

Different surfaces can use different amounts of context, and that can change the result. In practice, three things can shift the score:

• Scope — a quick triage surface uses a smaller set of signals than a full decision surface.
• Freshness — a quick scan may prefer speed over deeper refresh cycles, while a full check will spend more time to deliver a complete view.
• Interpretation — a quick scan should never pretend to be a full audit. It is a warning system, not a verdict.

How to use both correctly

• Use Quick Scan to triage lists and prioritize your attention.
• Use Full Scan before you make a decision or share a token with others.
• If the two disagree, treat it as a signal to open the full page and read the breakdown.