EVM Scoring Now Delivers Complete Data on Every Check

A risk score is only as reliable as the data behind it. If a check runs but some of the signals go missing, you get a number that looks complete but is not. That is exactly the kind of gap we fixed for EVM token analysis on Ethereum, BSC, and Base.

Starting with this update, BarryGuard delivers consistent, complete analysis results for every EVM token check. No more sporadic missing signals, no more scores that drift between checks for no visible reason.

What was happening before

When BarryGuard analyzes an EVM token, it runs several data lookups in parallel — holder data, liquidity figures, contract details, deployer history, and more. Under certain conditions, these parallel lookups could interfere with each other and cause some of them to fail silently.

The result was inconsistent scores. A token you checked twice in a row could come back with a different score the second time, simply because one data signal was missing in the first run. Holder concentration, contract ownership, or liquidity depth might appear as unavailable even when the data was there to be fetched. This is not an acceptable state for a tool that traders rely on before making a decision.

What changed

We fixed the underlying coordination issue that caused data lookups to block each other during parallel analysis. The fix is structural — it does not touch any scoring rules, thresholds, or check weights. The scoring logic itself is unchanged.

What is different now is that all data fetches for a single token check run as they should: independently and in parallel, without any one fetch accidentally blocking another. Every signal that can be fetched gets fetched.

• Holder data: wallet concentration signals now arrive consistently instead of occasionally showing as unavailable.
• Liquidity data: pool depth and liquidity figures are fetched reliably alongside other signals.
• Contract details: ownership status, verified source code, and proxy implementation data load as part of every analysis.
• Deployer history: the creator wallet lookup and its associated risk signals complete correctly on every run.

What this means for you

If you check the same EVM token twice, you should now get the same score both times — assuming nothing about the token has actually changed on-chain. Scores that previously swung between runs were not reflecting different risk levels. They were reflecting data gaps. Those gaps are now closed.

Tokens that previously scored lower than they should because signals went missing will now show their correct score. This applies to both genuine high-risk tokens and established legitimate ones — the fix is neutral by design. It simply ensures the score is based on complete evidence, not partial evidence.

If you have cached results for EVM tokens that predate this update, a fresh check on the check page will run a new analysis with the fixed data pipeline and give you the most accurate current score.

Which chains are affected

The fix applies to all three EVM chains supported by BarryGuard:

• Ethereum
• BNB Smart Chain (BSC)
• Base

Solana scoring is not affected by this change. The Solana analysis pipeline was already running correctly.

How to get the updated score

For any EVM token you have checked before, simply run a fresh analysis. The updated pipeline activates automatically for all new checks. You do not need to change any settings or clear anything manually.

If you want to understand what each score signal means and how BarryGuard weighs different risk factors, the methodology page explains the full scoring approach.

Check a token now →