Quick Scans Now Use Verified-Source Lookups for Fairer EVM Scores
By BarryGuard Team · May 18, 2026 · 4 min read
BarryGuard's quick scans on Ethereum, BSC, and Base check token contracts for code verification and contract structure in seconds. The faster the scan, the more important it is to be fair to legitimate new projects. Until now, if the primary block explorer hadn't yet indexed a contract's source code, our quick scan would fall back to conservative scoring — treating missing data as a risk signal.
Today, that changes. Quick scans now consult a public verified-source archive when the primary explorer doesn't yet have verification. For newly deployed but legitimate tokens, that means an honest, evidence-based score instead of a default penalty for missing data.
What We Changed
BarryGuard's quick scan mode on Ethereum, BSC, and Base now runs two verification lookups in sequence. First, it checks the primary block explorer (Etherscan V2 for Ethereum and Base, BSCScan for BSC) for source code and verification status. If the explorer has not yet indexed the contract, the quick scan moves to a second source: Sourcify, a public, decentralized repository of verified contract sources.
If Sourcify has the source on file, our quick scan can now read the contract internals — mint functions, transfer restrictions, ownership controls — without waiting for the explorer's indexing to catch up. If neither the explorer nor Sourcify has the source, scoring remains honest: the token gets a cautious score that reflects the data gap (ADR-018: missing evidence is a confidence signal, not a risk direction).
Why This Matters for Traders
A token deployed an hour ago is not automatically suspicious. It just hasn't had time to be indexed. The old behavior was conservative and honest — “we don't know enough, so we're cautious” — but it lumped together honest fresh launches and tokens deployed with genuinely hidden capabilities. With the additional verification source, an honest launch can now demonstrate transparency right away, even during the indexing window.
Meanwhile, a contract that nobody verified anywhere still gets the cautious score. If the code is opaque to Sourcify and the explorer, it's opaque to us too. That design is by intention, and it's what protects you.
What Stays the Same
Quick scans remain quick. The Sourcify check adds no provider credits, runs as a single lightweight HTTP call with a 3-second timeout, and only kicks in when the primary source misses. Tokens that aren't verified anywhere keep the cautious “limited data coverage” treatment — that score reflects genuine opacity, and it's what keeps you safe from truly hidden contracts.
The underlying scoring weights and thresholds are unchanged. We're not boosting scores or creating special paths for early projects — we're replacing a data gap with real data, and letting honest contracts show it.
What You'll See in Practice
Newly launched tokens with serious teams behind them — projects that verify their source code within minutes of deployment — will increasingly receive an accurate, evidence-based score instead of a default “we couldn't tell” floor. You see the contract features, mint restrictions, and ownership controls the moment we do, not hours later when the explorer catches up.
Older or anonymous deployments with no verification anywhere keep the cautious treatment. In our experience, that's where the real risks hide.
This update is available now on quick scans across Ethereum, BSC, and Base. Use it to check new tokens as soon as they deploy — you'll get a real answer instead of a placeholder.