Skip to main content
Menu
Update

Tighter Scoring for Established DeFi Tokens and Sharper Risk Detection

By BarryGuard Team · May 25, 2026 · 4 min read

Two related problems have been nagging at BarryGuard’s scoring quality for months. Established DeFi tokens with years of proven history were losing points on checks that were never designed to catch them. And on the other end of the spectrum, certain confirmed scam profiles on Solana were slipping through with scores that did not reflect how dangerous they actually were. This update addresses both.

There is also a smaller but genuinely annoying fix: token detail pages were triggering repeated automatic re-checks in the same browser session, causing unnecessary loading states. That loop is now gone.

Established DeFi tokens now score more accurately

Tokens like LINK, AAVE, BUSD, CAKE, and AERO have been around long enough, and traded at enough scale, that certain on-chain features they carry are protocol design choices — not warning signs. A DeFi protocol token with a non-renounced contract and an active governance setup looks different from an anonymous new token with the same features. BarryGuard was not always drawing that distinction cleanly.

The fix: when a token has a substantial holder base, meaningful market depth, verifiable on-chain age, and passes verification, certain checks that were producing unnecessary penalties now apply a floor. Liquidity lock status, silent-burn flags, and mintable ownership checks all behave more sensibly for tokens that meet a strict establishment threshold.

The threshold is not lenient. Tokens that are young, unverified, thinly traded, or lack a credible holder base get no benefit from this change. The floor only lifts for tokens where the evidence genuinely supports a different interpretation.

A similar refinement applies specifically to regulated stablecoins — tokens in the BUSD and USDC family. Their compliance design means they must have mintable supply and active admin controls. Before this update, those features could still pull their score down even on tokens with full issuer verification and confirmed listings. That inconsistency is corrected.

Confirmed Solana scam profiles now hit harder score caps

Certain Solana token profiles leave very little room for doubt: concentrated authority addresses, no real liquidity, coordinated control over supply. Tokens matching those profiles — the kind of structure seen in cases like HAWK and the Gen Z Quant launch — can sometimes end up with scores that look moderate because positive signals elsewhere average out the obvious red flags.

Two new hard caps address this. When a Solana token shows a tightly concentrated authority cluster and cannot demonstrate any real pool activity, the score is now capped at a danger level regardless of other signals. When an established-profile token simultaneously carries active risk indicators that make no sense for a genuinely established token — such as an unexplained active mint authority or a scam-linked deployer history — a second cap prevents the established profile from masking that risk.

Both caps are triggered only by confirmed positive evidence. Missing data or unresolvable providers do not trigger them. This is the same conservative standard BarryGuard applies across all scoring changes.

Token pages no longer refresh endlessly

When a token detail page detected that its cached data was older than a certain threshold, it would request a background re-check. That is expected behavior. What was not expected: in some sessions the re-check would complete, but the page would immediately queue another one, causing a loop of visible loading states with no practical benefit.

The fix is a session-level lock. Once a background re-check has been requested for a given token in your current session, no additional automatic re-checks are triggered for that token until you start a new session or manually request a fresh scan. The data is still refreshed — it just stops asking repeatedly.

What does not change

The fundamental approach is unchanged. BarryGuard does not maintain allowlists. No token gets a better score because it is well-known or widely held — it gets a better score because the on-chain evidence genuinely supports it. The new floors only apply within strict, verifiable gates. Everything outside those gates scores exactly as it did before.