Skip to main content
Menu
Update

Fairer EVM Scores for Established Tokens

By BarryGuard Team · April 14, 2026 · 4 min read

When we launched EVM support for Ethereum, BNB Chain, and Base, our scoring engine treated all tokens the same way. That was intentional — we wanted to apply consistent rules before making exceptions.

But consistent rules on inconsistent inputs produce unfair results. Established tokens like native chain wrappers and regulated stablecoins were scoring lower than their actual risk profile warranted, for reasons that had nothing to do with real danger. We fixed that.

What was happening

Three specific problems were dragging scores down unfairly on well-established EVM tokens:

  • Burn addresses counted as concentrated holders: When tokens are burned, they are sent to an address that can never spend them. But BarryGuard was treating burn addresses the same as any other large holder. A token with 30% of its supply burned looked concentrated. It is not — burned tokens are effectively removed from circulation.
  • Regulatory features flagged as risks: Regulated stablecoins have features like pause functions and blacklists. These exist for compliance reasons — they let issuers freeze accounts under legal order. BarryGuard was treating them the same as a random token with a hidden kill switch. They are not the same thing.
  • Bytecode patterns too broad: Our contract analysis used pattern matching to detect dangerous code patterns. Some of those patterns were broad enough to flag standard implementations used by major protocol contracts, even when those contracts have no credible risk.

What changed

Burn addresses excluded from concentration checks

BarryGuard now recognizes the standard burn addresses on EVM chains and removes them from holder concentration calculations. If a large share of a token's supply has been burned, that burned portion no longer counts against the score. The holder concentration check now reflects the live, circulating supply — not including tokens that can never move.

Asset classification for regulated tokens

BarryGuard now identifies two special asset categories on EVM chains:

  • Native wrappers — tokens like WETH and WBNB that represent the native chain currency in ERC-20 form. Their minting mechanics are by design, not a risk.
  • Issuer-managed fungibles — established tokens where an issuer maintains operational control for compliance purposes. Pause and blacklist functions on these tokens are regulatory features, not hidden attack vectors.

For both categories, features that would otherwise lower the score are now evaluated in context. A pause function on a token that has been operating transparently for years under regulatory oversight is scored differently from the same function on a new anonymous token.

More precise bytecode pattern matching

Our bytecode analysis was tightened to reduce false positives on standard protocol implementations. Patterns that match known-safe contract structures no longer trigger the same penalties as patterns that appear exclusively in suspicious code.

What this means for you as a trader

If you trade on Ethereum, BNB Chain, or Base, scores for a narrow set of well-established tokens will look more accurate after this update. Tokens that are widely used, transparently operated, and structurally distinct from new launches are now assessed on their own terms.

This does not affect how BarryGuard treats unknown or new tokens. The classification system only applies to tokens that meet specific on-chain criteria — not a list of names we chose, but verifiable on-chain facts like address constants, age, and contract structure. No token-specific exceptions were added. The rules are the same for every address.

A few things that did not change:

  • New tokens with pause functions or blacklists still get flagged. The classification threshold requires meaningful age and transparent issuer structure.
  • Missing liquidity is still a risk signal. An established token with no active trading pool still scores poorly for market structure.
  • Honeypot detection is unchanged. A confirmed sell block is a Danger finding regardless of token age or category.

Why accuracy over time matters

A risk score is only useful if it reflects the actual risk. If well-understood, widely-held tokens with no credible danger score in the Danger range, traders learn to ignore the score. That is the worst outcome — not a false positive for one token, but lost trust in the signal overall.

Getting established EVM tokens right is part of building a score that traders can rely on for the tokens that actually matter most: the unknown ones, the new ones, the tokens where nobody has done the analysis yet.

These changes are live now across all EVM chains. No action needed on your end. Paste any token address and the updated scoring applies automatically.

Check a token now →